rasserver produces too many log files sometimes

[Dimitar Misev]

In certain cases it seems that rasdaman produces an insane amount of log files. So many that

rm -f *
-bash: /usr/bin/rm: Argument list too long

I think rasservers die before they properly start, and rasmgr keeps forking new ones for way too long.

We need to figure out how to reproduce this first, and probably rasmgr should be fixed, so that it detects such an issue a bit earlier than ~400,000 restarts later. To reproduce we could try inserting a deliberate segfault somewhere early in the initialization of rasserver.

[Dimitar Misev]

To fix this I modified start_rasdaman.sh to try a simple select query after starting rasservers; if it fails to execute it means that no rasserver has probably started (a select version() query should always execute fine otherwise). In this case it shuts down rasmgr and hence prevents it going into the above loop of constantly restarting the rasservers.

Patch is on the way.