CGRU Forum

Not much clients.
Not much open sockets.
Should work.
Also you can raise up open descriptors limit in the system - default for most distributives is 1024 - it is not much for servers, set at least 10240.

There in documentation:
http://cgru.info/afanasy/job#block_command
- left column, blue text color

Terminology 'zombie' took from Linux processes. ( Node class can't delete itself, but can consider that it is not needed, it set zombie to true, then container deletes zombie nodes ) Renders and monitors became zombies after some time they have not connected to server. 40 seconds for monitors by def...

Hi.

Sorry, to few info, can't say anything. Try to 'catch' the bug.

Hi. Afanasy serve stores state (current jobs, renders, users) in a local JSON files. Default store folder location on linux is /var/tmp/afanasy. Also it stores some data if deleted jobs in SQL database for statistics. Job id is not unique, new job can take the same id as previously deleted job. ID i...

In web gui you can do some action and look at network log.
You can run afwatch in terminal and look at process output.
This way you can see JSON protocol.

Also you can run 'afcmd h' to see some commands.
( afcmd will send JSON requests too )

Hi.
You can delete host from GUI in admin mode.
Default 'god' password is 'iddqd'.

Hi.
What exact submission type you use? (what item of menu)
2.0.4 version works?

BTW
I am new to forum administration.
Now you can post without approval, can you test it?

Hi.

You can write some command wrapper for it.
Or you can do something in a Python service class.

PS
For now i do not see any general way that will suit all studious for it.
If you find some simple generic way to solve this issue we can talk about to implement it in the project.

Hi.
Can you tell Linux distribution and GCC version too.
I know about that leaks, that shows valgrind, and they does not accumulating, so does not affect anything really.
Valgrind shows the same functions back trace on server crash? ( i see only mem leaks info )