[MonetDB-users] Server socket stays 'open' after crash
Instead of using monetdbd I am using a very simple while [ 1 ]; do monetdb; sleep 2; done command to restart the database after an assertion failed or segmentation fault. For some reason even after a crash MonetDB complains at the start of the application that the port is already in use. Would could -unix wise- be the reason for this, that even after a crash and the program has been terminated resources are still claimed for the terminated program? Stefan
On 11-06-2012 18:56:15 +0200, Stefan de Konink wrote:
Instead of using monetdbd I am using a very simple while [ 1 ]; do monetdb; sleep 2; done command to restart the database after an assertion failed or segmentation fault.
For some reason even after a crash MonetDB complains at the start of the application that the port is already in use. Would could -unix wise- be the reason for this, that even after a crash and the program has been terminated resources are still claimed for the terminated program?
What address it complains about being in use? You might have a stale socket file somewhere, although iirc mserver5 cleans that up itself on the next start. Fabian
On 11-06-12 19:15, Fabian Groffen wrote:
What address it complains about being in use? You might have a stale socket file somewhere, although iirc mserver5 cleans that up itself on the next start.
I run the server at 127.0.0.1:60005, after trying to do a restart, even manually, it complains about being in use. I initially thought it was because of remainig connections to the database(?) Stefan
On 11-06-2012 19:22:05 +0200, Stefan de Konink wrote:
On 11-06-12 19:15, Fabian Groffen wrote:
What address it complains about being in use? You might have a stale socket file somewhere, although iirc mserver5 cleans that up itself on the next start.
I run the server at 127.0.0.1:60005, after trying to do a restart, even manually, it complains about being in use. I initially thought it was because of remainig connections to the database(?)
netstat/lsof might give you clues Fabian
participants (2)
-
Fabian Groffen -
Stefan de Konink