Strange errormessages while packing the Database
Hello all While packing my database some strange errormessages appeared in my error_log: <error_log> 2002-06-21T08:02:28 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 211.110.7.215:39202 at 0x1abfc784 channel#: 4741 requests:> (socket.error:(32, 'Broken pipe') [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/asynchat.py|handle_read|82] [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/http_server.py|recv|420] [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/asyncore.py|recv|357]) </error-log> Could somebody tell me, if this is serious and what this means? The Data.fs was about 1.3 GBytes(!) big and is now 512MByte. We had a disc space problem, and the server was not able to do the nightly packings (cronjob) for several days (couldn't write Data.fs.old). This is the reason why Data.fs was so big. After packing the Database I restarted the server and found the following error messages. <error_log> 2002-06-21T08:10:46 ERROR(200) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Aiieee! 1069 exited with error code: 256 ------ 2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Houston, we have forked ------ 2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Hi, I just forked off a kid: 1492 ------ 2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Houston, we have forked- </error_log> This seems to be a programmers joke, but I am a little bit scarred now, so I take it serious. But is this really serious? The server seems to be ok now. I don't see any "misbehaviour" and no data seems to be missing. But we have appr. 15.000 documents in the database, so it's difficult to be sure. Thanks in advance for any help Sven Rudolph -- Sven Rudolph, Programmierer GermanMedicalServices.de GmbH Unter den Eichen 5, 65195 Wiesbaden Tel.: 06 11 / 97 46 25 2
On Friday 21 Jun 2002 10:59 am, Sven Rudolph wrote:
Hello all
While packing my database some strange errormessages appeared in my error_log: <error_log>
2002-06-21T08:02:28 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 211.110.7.215:39202 at 0x1abfc784 channel#: 4741 requests:> (socket.error:(32, 'Broken pipe') [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/asynchat.py|h andle_read|82] [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/http_server.p y|recv|420] [/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/asyncore.py|r ecv|357])
</error-log>
That looks like a client disconnecting at a point where ZServer is not expecting it. not a problem.
Could somebody tell me, if this is serious and what this means? The Data.fs was about 1.3 GBytes(!) big and is now 512MByte. We had a disc space problem, and the server was not able to do the nightly packings (cronjob) for several days (couldn't write Data.fs.old). This is the reason why Data.fs was so big.
Is 512Mb about the size you expected it to pack to?
After packing the Database I restarted the server and found the following error messages.
<error_log>
2002-06-21T08:10:46 ERROR(200) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Aiieee! 1069 exited with error code: 256 ------
This is the Zope server process stopping with exit code 1
2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Houston, we have forked ------ 2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Hi, I just forked off a kid: 1492 ------ 2002-06-21T08:10:46 INFO(0) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Houston, we have forked-
....and the Zope supervisor process automatically restarting another Zope server process. Is 08:10:46 the time you requested a restart?
The server seems to be ok now. I don't see any "misbehaviour" and no data seems to be missing. But we have appr. 15.000 documents in the database, so it's difficult to be sure.
check the undo log. Its probably ok if your most recent transactions are present
Hello Toby, thank you very much for your quick answer. [snip]
[/export/home/www/medizin/zopeweb/zope-2.5.1b1/ZServer/medusa/asyncore.py|r ecv|357])
</error-log>
That looks like a client disconnecting at a point where ZServer is not expecting it. not a problem.
That means it's harmless. Thats good news :-)
Is 512Mb about the size you expected it to pack to?
Yes, that is what I expected.
2002-06-21T08:10:46 ERROR(200) zdaemon zdaemon: Fri Jun 21 10:10:46 2002: Aiieee! 1069 exited with error code: 256 ------
This is the Zope server process stopping with exit code 1
Harmless too. More good news.
....and the Zope supervisor process automatically restarting another Zope server process.
Even more good news.
Is 08:10:46 the time you requested a restart?
Yes.
check the undo log. Its probably ok if your most recent transactions are present
All my recent transaction are present, so finally it seems that there is nothing to worry about :-) Thank you again Sven -- Sven Rudolph, Programmierer GermanMedicalServices.de GmbH Unter den Eichen 5, 65195 Wiesbaden Tel.: 06 11 / 97 46 25 2
participants (2)
-
Sven Rudolph -
Toby Dickenson