Good idea to look through uwsgi.log.
The problem was harakiri on a process after 60 seconds. There was an entry
in the log along the lines of HARAKIRI ON WORKER 4 (pid: 2557, try: 1).
To fix, I increased harakiri to 120 in /etc/uwsgi/web2py.xml.
That created a new problem which showed up in
On Tuesday, March 24, 2015 at 8:07:45 PM UTC, Niphlod wrote:
seems the right job for the scheduler :-P
Yeah, maybe you're right.
Basically my program generates a large image for a user which takes about 1
min. I want to show please wait on the web-page while it's generating,
then show
On Tuesday, March 24, 2015 at 9:34:41 PM UTC+1, Toby wrote:
On Tuesday, March 24, 2015 at 8:07:45 PM UTC, Niphlod wrote:
seems the right job for the scheduler :-P
Yeah, maybe you're right.
Basically my program generates a large image for a user which takes about
1 min. I want to
seems the right job for the scheduler :-P
On Tuesday, March 24, 2015 at 6:10:15 PM UTC+1, Toby wrote:
Good idea to look through uwsgi.log.
The problem was harakiri on a process after 60 seconds. There was an entry
in the log along the lines of HARAKIRI ON WORKER 4 (pid: 2557, try: 1).
To
what are you using between nginx and web2py? uwsgi?
if that's the case check the uwsgi logs for clues
mic
2015-03-19 19:12 GMT+01:00 Dave S snidely@gmail.com:
On Thursday, March 19, 2015 at 5:17:21 AM UTC-7, Toby wrote:
Hi,
I'm having issues using subprocess.call from within a module
On Thursday, March 19, 2015 at 5:17:21 AM UTC-7, Toby wrote:
Hi,
I'm having issues using subprocess.call from within a module file in
web2py.
[...]
The funny thing is that if I use an imagemagick command that's faster to
run (e.g. a lower resolution image) then it works fine.
6 matches
Mail list logo
