Help! FTP access shuts down Zope (solved) NOT!! [repost]
After starting with 'nohup' we got FTP access to Zope again. But after 1 or 2 FTP logins (with no errors and clean exits) the retrieval of the filelisting fails and everything hangs again. This occurs wheither we start normally or with the 'nohup' prefix. Anny suggestions? TIA, R. zope 2.5.1, linux redhat 7.0, cmf 1.2
-----Oorspronkelijk bericht----- Van: zope-admin@zope.org [mailto:zope-admin@zope.org]Namens Roel Van den Bergh Verzonden: maandag 10 juni 2002 15:09 Aan: Chris McDonough CC: zope@zope.org Onderwerp: RE: [Zope] Help! FTP access shuts down Zope (solved)
Tnx very much, everything seems to be working fine now!
-----Oorspronkelijk bericht----- Van: Chris McDonough [mailto:chrism@zope.com] Verzonden: maandag 10 juni 2002 14:42 Aan: roel@planetinterior.com CC: zope@zope.org Onderwerp: Re: [Zope] Help! FTP access shuts down Zope
Roel,
It seems as if Zope is trying to write to a nonexistent console... although it probably shouldn't. If you are using UNIX, try to start Zope using "nohup".
On Mon, 2002-06-10 at 04:17, Roel Van den Bergh wrote:
*This is what happens when you take a break from work to see your newborn son*
Everytime when we try to access Zope trough FTP at 8021, the whole Zope server locks out and has to be restarted.
This occurred after my colleague downloaded some files directly from the source of zope while zope was still running. He says he only downloaded stuff like stupidFileLogger and index_html.dmtl and main.dtml.
Result: we can no longer FTP into the zope database When restarting zope it also says Hotfix_2002-04-15 is broken
FTP log file :
WINSOCK.DLL: WinSock 2.0 WS_FTP LE 5.08 2000.01.13, Copyright C 1992-2000 Ipswitch, Inc. - - connecting to 194.78.49.253:8021 Connected to 194.78.49.253 port 8021 220 piwebserver.planetinterior.be FTP server (Medusa Async V1.18.60.1 [experimental]) ready. USER TimW 331 Password required. PASS (hidden) 230 Login successful. PWD 451 Server Error: exceptions.IOError, [Errno 32] Broken pipe: file: /home/zope/2-5-0/lib/python/ZLogger/stupidFileLogg 10:10:38 2002 Hostname: piwebserver.planetinterior.be Port: 9800 ------ 2002-06-10T08:10:38 INFO(0) ZServer FTP server started at Mon Jun 10 10:10:38 2002 Hostname: piwebserver.planetinterior.be Port: 8021 ------ 2002-06-10T08:10:38 INFO(0) ZServer PCGI Server started at Mon Jun 10 10:10:38 2002 Unix socket: /home/zope/2-5-0/var/pcgi.soc
_______________________________________________ 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 )
_______________________________________________ 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 )
On Mon, Jun 24, 2002 at 09:48:30AM +0200, Roel Van den Bergh wrote:
After starting with 'nohup' we got FTP access to Zope again. But after 1 or 2 FTP logins (with no errors and clean exits) the retrieval of the filelisting fails and everything hangs again. This occurs wheither we start normally or with the 'nohup' prefix.
If you keep the window where you had run the 'nohup' up, would you see any text being printed to that console? If so, that's an unfortunate intersection between product writers writing software that gives warnings (or worse, still has debugging 'print' statements in it) and a lack of nohup capturing both standard output and standard error. As an example, at least on my 2.5.1 install (Debian packages of Zope and Python, so I'm not sure where the fault lies yet), I get the following on a Zope start: Starting Zope...../usr/lib/zope/lib/python/ts_regex.py:15: DeprecationWarning: the regex module is deprecated; please use the re module import regex, regsub #, Sync /usr/lib/python2.1/regsub.py:15: DeprecationWarning: the regsub module is deprecated; please use re.sub() DeprecationWarning) ... done. Solutions: - Run Zope inside a screen session, and do any command-line restarts or stops from that screen session. 'screen' will fool any application into thinking it still has a terminal attached, even if you disconnect the session from your physical terminal and log out. You can reconnect to the screen session later, too, handy if you're not sure where the messages are coming from. - Change how you run nohup, or force Zope's standard output and standard error descriptors away from the terminal. Something like: # ./start > /dev/null 2>&1 in a Bourne-derived shell should do fine, and should be nohup-compatible. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
Also please note that the "write-to-stdout-when-there-is-no-controlling-terminal" problem is fixed in Zope 2.6, so none of these workarounds should be necessary when running under it. - C ----- Original Message ----- From: "Mike Renfro" <renfro@tntech.edu> To: "Roel Van den Bergh" <roel@planetinterior.com> Cc: "Zope Org" <zope@zope.org> Sent: Monday, June 24, 2002 10:03 AM Subject: Re: [Zope] Help! FTP access shuts down Zope (solved) NOT!! [repost]
On Mon, Jun 24, 2002 at 09:48:30AM +0200, Roel Van den Bergh wrote:
After starting with 'nohup' we got FTP access to Zope again. But after 1 or 2 FTP logins (with no errors and clean exits) the retrieval of the filelisting fails and everything hangs again. This occurs wheither we start normally or with the 'nohup' prefix.
If you keep the window where you had run the 'nohup' up, would you see any text being printed to that console? If so, that's an unfortunate intersection between product writers writing software that gives warnings (or worse, still has debugging 'print' statements in it) and a lack of nohup capturing both standard output and standard error.
As an example, at least on my 2.5.1 install (Debian packages of Zope and Python, so I'm not sure where the fault lies yet), I get the following on a Zope start:
Starting Zope...../usr/lib/zope/lib/python/ts_regex.py:15: DeprecationWarning: the regex module is deprecated; please use the re module import regex, regsub #, Sync /usr/lib/python2.1/regsub.py:15: DeprecationWarning: the regsub module is deprecated; please use re.sub() DeprecationWarning) ... done.
Solutions:
- Run Zope inside a screen session, and do any command-line restarts or stops from that screen session. 'screen' will fool any application into thinking it still has a terminal attached, even if you disconnect the session from your physical terminal and log out. You can reconnect to the screen session later, too, handy if you're not sure where the messages are coming from.
- Change how you run nohup, or force Zope's standard output and standard error descriptors away from the terminal. Something like:
# ./start > /dev/null 2>&1
in a Bourne-derived shell should do fine, and should be nohup-compatible.
-- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
_______________________________________________ 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 )
participants (3)
-
Chris McDonough -
Mike Renfro -
Roel Van den Bergh