[Opa] after a long day of hacking...
cedric.soulas at mlstate.com
Tue Nov 8 05:24:15 EST 2011
On Nov 8, 2011, at 8:19 AM, Alok Menghrajani wrote:
> Do you know if / why nohup would hard close a terminal after a few hours?
I can't imagine nohup is responsible of closing the terminal.
By hard close I meant for eg. :
- shutting down ou rebooting the computer, without properly closing (with ctrl-D or exit) the terminal that initiate the ssh connection
- force quitting the terminal with the "exit cross" icon of the window
> The fact that I had "Internal error: what's this absolute URI doing here?"
> seems to indicate that it was not an issue with nohup. I haven't seen the
> service crash since then, so I can't debug / validate anything more than
> what I already shared with you :(
Your error was
> 04/11/11 06:36:49.07 [error]: File "stdlib/core/web/server/server.opa",
> line 237, characters 16-77, (237:16-237:77 | 9469-9530)
> @fail: Internal error: what's this absolute URI doing here?
> 04/11/11 07:03:20.57 [warn]: SIGHUP received, exitin
According to the date, the SIGHUP was received 33min after the Opa error.
I agree the date are close, but I don't think it's related. This kind of failure should only kill the client thread, not the server.
> Opa mailing list
> Opa at lists.owasp.org
More information about the Opa