3 ms·
Nicely done, but getting stuck at Waiting for GPU server slot, there are None jobs ahead of yours... with a progress bar not longer even crawling. F
by huhtenberg 7y ago
Nicely done, but getting stuck at
Waiting for GPU server slot, there are None
jobs ahead of yours...
with a progress bar not longer even crawling.
From the console:
websocket open app.js:189:14
Got text message: progress: GPU render server received target image... app.js:203:12
Got text message: your ticket is xxx app.js:203:12
Got text message: progress: Waiting for GPU server slot, there is one job ahead of yours... 4 app.js:203:12
Got text message: progress: Waiting for GPU server slot, there are None jobs ahead of yours... 61 app.js:203:12
onclose
- bemmu 7y agoThanks, took me a while to find the issue. I had a feature where if the same client (by IP address) starts another job, their previous jobs are deleted. But after I added secure websockets support by proxying through nginx, all IP addresses from the server's point of view became "127.0.0.1" and every job would just be deleted when a new one came in, because they all had the same IP.
- uranium 7y agoI keep getting countdowns from 8 or 15 to 1 [or partway there], and then "onclose", with the UI saying "Lost connection to server, please try again in a bit". For variety now and then I get a 502 somewhere in websocket setup. When it is counting down, it takes 100+% CPU. The sample render looks really cool, though. Nice project; thanks for sharing it.
- huhtenberg 7y agoCheers, thanks a bunch.