Hello! After working on my website for a few hours, I sometimes start getting IOErrors from Zope in stupid_log_write. See the full message here: http://zope.levinux.org/ioerror.html This only happens when editing the site. Upon encountering this error once, all subsequent attempts at modifying the site (or even restarting Zope from the control panel) fail with the same error. Simply viewing the site, however, will continue working. This problem is does not crop up constantly, but it is not rare either. I work full-time on the website, and this IOError happens a few times a week. It seems to be happening more recently. (Maybe I should pack my database?) I would like to know why this happens and whether or not I can do something about it. The site is meant to be dynamic user-editable. I can manually restart the Zope server, but my users cannot. So this could easily turn into a big headache if the problem persists. Thank you very much in advance. Cheers, Jérôme Loisel -- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/
What platform is your Zope running on?
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jérôme Loisel Sent: Monday, April 30, 2001 11:52 To: zope@zope.org Subject: [Zope] Zope IOError messages
Hello!
After working on my website for a few hours, I sometimes start getting IOErrors from Zope in stupid_log_write. See the full message here:
http://zope.levinux.org/ioerror.html
This only happens when editing the site. Upon encountering this error once, all subsequent attempts at modifying the site (or even restarting Zope from the control panel) fail with the same error. Simply viewing the site, however, will continue working.
This problem is does not crop up constantly, but it is not rare either. I work full-time on the website, and this IOError happens a few times a week. It seems to be happening more recently. (Maybe I should pack my database?)
I would like to know why this happens and whether or not I can do something about it. The site is meant to be dynamic user-editable. I can manually restart the Zope server, but my users cannot. So this could easily turn into a big headache if the problem persists.
Thank you very much in advance. Cheers,
Jérôme Loisel
Hi Loren, hi all. Loren Stafford -- Lundi 30 Avril 2001 15:30:
What platform is your Zope running on?
I am running Zope 2.3.2 (binary release) on a Mandrake 7.2 system. Thinking about it, I realized that this specific error seemed to happen in relation to me trying to create PythonScript objects which contained bugs. I tried a few things and have come up with a test case. Trying to edit a PythonScript object to the following code will trigger the error. <testcase> print "Allo!" if foo: return printed </testcase> As you can see, the script is buggy. Still, this should not render Zope un-editable. I am not sure that this covers the full extent of the problem, but it could.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jérôme Loisel Sent: Monday, April 30, 2001 11:52 To: zope@zope.org Subject: [Zope] Zope IOError messages
Hello!
After working on my website for a few hours, I sometimes start getting IOErrors from Zope in stupid_log_write. See the full message here:
http://zope.levinux.org/ioerror.html
This only happens when editing the site. Upon encountering this error once, all subsequent attempts at modifying the site (or even restarting Zope from the control panel) fail with the same error. Simply viewing the site, however, will continue working.
This problem is does not crop up constantly, but it is not rare either. I work full-time on the website, and this IOError happens a few times a week. It seems to be happening more recently. (Maybe I should pack my database?)
I would like to know why this happens and whether or not I can do something about it. The site is meant to be dynamic user-editable. I can manually restart the Zope server, but my users cannot. So this could easily turn into a big headache if the problem persists.
Thank you very much in advance. Cheers,
Jérôme Loisel
-- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/
Jerome, Are you seeing "script returned printed without using printed variable" messages inside your log file (STUPID_LOG_FILE?) What messages are you seeing in the logfile? It seems that the problem is related to opening and closing the logfile, which may be symptomatic of an out-of-disk-space issue. - C ----- Original Message ----- From: "Jérôme Loisel" <jerome@levinux.org> To: "Loren Stafford" <lstafford@morphics.com> Cc: <zope@zope.org> Sent: Monday, April 30, 2001 3:45 PM Subject: Re: [Zope] Zope IOError messages (FOUND TEST CASE) Hi Loren, hi all. Loren Stafford -- Lundi 30 Avril 2001 15:30:
What platform is your Zope running on?
I am running Zope 2.3.2 (binary release) on a Mandrake 7.2 system. Thinking about it, I realized that this specific error seemed to happen in relation to me trying to create PythonScript objects which contained bugs. I tried a few things and have come up with a test case. Trying to edit a PythonScript object to the following code will trigger the error. <testcase> print "Allo!" if foo: return printed </testcase> As you can see, the script is buggy. Still, this should not render Zope un-editable. I am not sure that this covers the full extent of the problem, but it could.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jérôme Loisel Sent: Monday, April 30, 2001 11:52 To: zope@zope.org Subject: [Zope] Zope IOError messages
Hello!
After working on my website for a few hours, I sometimes start getting IOErrors from Zope in stupid_log_write. See the full message here:
http://zope.levinux.org/ioerror.html
This only happens when editing the site. Upon encountering this error once, all subsequent attempts at modifying the site (or even restarting Zope from the control panel) fail with the same error. Simply viewing the site, however, will continue working.
This problem is does not crop up constantly, but it is not rare either. I work full-time on the website, and this IOError happens a few times a week. It seems to be happening more recently. (Maybe I should pack my database?)
I would like to know why this happens and whether or not I can do something about it. The site is meant to be dynamic user-editable. I can manually restart the Zope server, but my users cannot. So this could easily turn into a big headache if the problem persists.
Thank you very much in advance. Cheers,
Jérôme Loisel
-- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/ _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Chris McDonough -- Lundi 30 Avril 2001 22:11:
Jerome,
Are you seeing "script returned printed without using printed variable" messages inside your log file (STUPID_LOG_FILE?) What messages are you seeing in the logfile?
I have never really had to muck around STUPID_LOG_FILE, so I am ignorant with regards to it. Care to educate me? The only file which seems to fit the bill in var/ is log.txt, and that is empty. I quickly looked at stupidFileLogger.py and noticed that if STUPID_LOG_FILE is not set, logging is done to stderr. AFAICS, STUPID_LOG_FILE is not set on my system, and the "start" script does not initiate it. If you can tell me how to properly set STUPID_LOG_FILE, I can do more testing and tell you about it.
It seems that the problem is related to opening and closing the logfile, which may be symptomatic of an out-of-disk-space issue.
I am pretty sure that free space is not the issue. The server for this installation has 3 gigs left on the partition which contains Zope... A permission problem, maybe? Why would it only crop up then? Thanks in advance, Jérôme Loisel
- C
----- Original Message ----- From: "Jérôme Loisel" <jerome@levinux.org> To: "Loren Stafford" <lstafford@morphics.com> Cc: <zope@zope.org> Sent: Monday, April 30, 2001 3:45 PM Subject: Re: [Zope] Zope IOError messages (FOUND TEST CASE)
Hi Loren, hi all.
Loren Stafford -- Lundi 30 Avril 2001 15:30:
What platform is your Zope running on?
I am running Zope 2.3.2 (binary release) on a Mandrake 7.2 system.
Thinking about it, I realized that this specific error seemed to happen in relation to me trying to create PythonScript objects which contained bugs. I tried a few things and have come up with a test case.
Trying to edit a PythonScript object to the following code will trigger the error.
<testcase> print "Allo!"
if foo:
return printed </testcase>
As you can see, the script is buggy. Still, this should not render Zope un-editable. I am not sure that this covers the full extent of the problem, but it could.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jérôme Loisel Sent: Monday, April 30, 2001 11:52 To: zope@zope.org Subject: [Zope] Zope IOError messages
Hello!
After working on my website for a few hours, I sometimes start getting IOErrors from Zope in stupid_log_write. See the full message here:
http://zope.levinux.org/ioerror.html
This only happens when editing the site. Upon encountering this error once, all subsequent attempts at modifying the site (or even restarting Zope from the control panel) fail with the same error. Simply viewing the site, however, will continue working.
This problem is does not crop up constantly, but it is not rare either.
I
work full-time on the website, and this IOError happens a few times a week. It seems to be happening more recently. (Maybe I should pack my database?)
I would like to know why this happens and whether or not I can do something about it. The site is meant to be dynamic user-editable. I can manually restart the Zope server, but my users cannot. So this could easily turn into a big headache if the problem persists.
Thank you very much in advance. Cheers,
Jérôme Loisel
-- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/
On Tue, 1 May 2001 11:22:20 -0400 Jérôme Loisel <jerome@levinux.org> wrote:
I have never really had to muck around STUPID_LOG_FILE, so I am ignorant with regards to it. Care to educate me? The only file which seems to fit the bill in var/ is log.txt, and that is empty.
Setting the env var STUPID_LOG_FILE tells Zope where to log event messages.
I quickly looked at stupidFileLogger.py and noticed that if STUPID_LOG_FILE is not set, logging is done to stderr. AFAICS, STUPID_LOG_FILE is not set on my system, and the "start" script does not initiate it.
OK.
If you can tell me how to properly set STUPID_LOG_FILE, I can do more testing and tell you about it.
On UNIX (in the "start" shell script): export STUPID_LOG_FILE='var/debug.log' If you're on Windows, it's probably something like: set STUPID_LOG_FILE=c:\path\to\var\debug.log It may be that the very act of doing this causes your errors to go away. Perhaps stderr was disappearing somehow.
Hello Chris, Chris McDonough -- Lundi 30 Avril 2001 22:11:
Jerome,
Are you seeing "script returned printed without using printed variable" messages inside your log file (STUPID_LOG_FILE?) What messages are you seeing in the logfile?
It seems that the problem is related to opening and closing the logfile, which may be symptomatic of an out-of-disk-space issue.
I have set STUPID_LOG_FILE and my problems have gone away. I have thought about what you told me and now think I understand what the problem was. The server's boot process automatically starts Zope. I do not believe that problems cropped up when this was how Zope was started. I believe that my problems happen when I manually restart Zope. I occasionnally do this when I install new products or experience major problems. To manually restart Zope, I do the following: I open a shell, su, run the stop script, run the start script, check that everything works and exit my shell. You supposed that maybe stderr disappears somehow, causing my IOErrors... Would closing my shell not make stderr disappear? If so, maybe this should be considered a bug in the default setup of the start script? The start script should start a fully functional Zope, even if the shell il later closed. In my opinion, at least. :-) In any case, I very much thank you for your help. My problem seems resolved now. Cheers, Jérôme Loisel -- Jérôme Loisel, étudiant et webmestre Lévinux: GNU/Linux pour la communauté http://www.levinux.org/
On Tue, May 01, 2001 at 02:32:13PM -0400, J?r?me Loisel wrote:
To manually restart Zope, I do the following: I open a shell, su, run the stop script, run the start script, check that everything works and exit my shell. You supposed that maybe stderr disappears somehow, causing my IOErrors... Would closing my shell not make stderr disappear?
Whenever I've manually restarted Zope from a remote session, I've often gotten IOErrors -- you've pretty well nailed the reason it happens. My workarounds: (1) Restart Zope from inside a 'screen' session, then detach screen. Zope always believes it has an open valid stderr, even if I'm not actively watching it. (2) Find whatever product or code is mindlessly spitting debugs out to stderr (usually via Python print statements), and edit them out. I've seen this with WorldPilot, ZopeGUD components, etc. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
participants (4)
-
Chris McDonough -
Jérôme Loisel -
Loren Stafford -
Mike Renfro