New answers tagged

0

Well, looks like changing the rewrite for phantomJS to this: rewrite ^/snapshot(.*)$ /$1 break; did the trick.


0

@blueben is right. A specific and common example of what can happen when a reverse proxy is not used is that a backend database can run out database connection handles where there's no proxy and there's a traffic spike. This is due to the connections being slow to release as @blueben described. A first instinct to seeing database handles running out might ...


1

As a general rule it is always a good idea to run workers and that kind of thing under a separate user which is specifically only given the permissions it requires in order to run. Running things as root is usually easier as you rarely have to worry about permissions issues, but it is always less secure as anything that can successfully exploit your ...


0

@naill Donegan mentions this in comment above, but it is important enough to warrant an answer. Nginx stops the slow loris attack that gunicorn doesn't handle.


0

I solved this error by adding user munin to group nobody (the same as apache's group) and setting the munin directory writable by the group nobody: chmod -R g+w /usr/local/apache/htdocs/munin Error stopped. Graphs started appearing again.


0

You should create the uauvuro0s8b9v4 user prior to restore the database or the pg_restore will raise such errors (as this user's owns a lot of relations, in your case). In psql try: CREATE USER uauvuro0s8b9v4 WITH PASSWORD '12334444';


1

Solution is to keep the session detached and run commands via tmux send-keys -t <session-name> "Command ENTER"


0

I'm also wondering what is the best approach to tackle a task that takes a long time to compute? Asynchronously? This is what worker queues are for. You should consider separating the submission of the files from processing. Let the user submit the files, save them off, add a message to a worker queue to process them, indeed asynchronously. The user gets ...


0

I see no-one has answered, so I typed your question into Google and found this page. Have you tried increasing all applicable timeouts as it suggests? That seems like the first thing to do.



Top 50 recent answers are included