CGRU Forum

Really nice feature. Can't wait to use it in production

Should we let it replace the project attribute?

A few spelling mistakes, will submit a pull request later

Until it's fixed and if you don't need to kill the process like does, you might want to look at which doesn't seem to kill it but will restart the task (after it's done).

timurhai wrote: ↑Fri Mar 03, 2017 12:07 pm No. My laptop has HDD.

So perhaps it's when the thread queue gets too long?
Will try to limit afserver IO on my laptop, to see if it will crash sooner.

Just launch 200 renders on the same host with afserver. On ubuntu 16lts it craches in a minute. On ubuntu 14lts i did not wait crash. I launched about 1400 clients on Ubuntu 16.04 and it didn't crash. This was using a self compiled version from latest git on my laptop. Did your test machine have SSD?

seven11 wrote: ↑Thu Mar 02, 2017 9:26 pm Timur,
Aah I see it's a bug on github #308.
https://github.com/CGRU/cgru/issues/308
Scott

Not a bug, a feature request

How do you imitate heavy load? I'm trying my best to get afanasy to crash on a test system, without any luck.

I'm trying to connect hundreds of dummy renders while adding jobs in an endless loop.

Our server just crashed and I got this in 'dmesg':

Awesome!

We're seeing the same thing, but only if the job is submitted with a parser that does not exist on the client running afwatch (in our case a custom parser for fumefx sims through maya). If it has the parser it displays correctly.

It seems it is happening here after a while if I add all workstations to the farm. If I add the workstations to a separate server all is fine with them and no crashes. @lithorus: How many clients are online at your place? @selsner : Clients as in renders or workstations monitoring? Have 21 renders ...