Zope 2.7.2 still doesn't run as a service in w2k
I tried all what's currently available except to dig into Zope's win32 services machinery: I did install it manually after removing the extra underscore in "INSTANCE__HOME". I added a PYTHONPATH system variable for both the path of the alternate Python installation and the Zope software; and also I changed the PYTHONW variable within zopeservices.py to the executable of this other Python installation (which I need due to I have installed there win32all), but the service refuses to start. The event log just tells : Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. If I run it manually everything is fine. Has anyone else had this same problem? Guess I ran out of stamina at this very moment ;) Ausum
Ausum Studio wrote:
I tried all what's currently available except to dig into Zope's win32 services machinery:
...see the discussion currently underway on zope-dev, the mighty Mark Hammond is weighing in and looks set to help out :-)
If I run it manually everything is fine. Has anyone else had this same problem? Guess I ran out of stamina at this very moment ;)
You could always look at using one of the third party programs that lets you run non-service things as services. I did this a while back with a number of things, but can't remember what the program was I used, it is out there though! cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Ausum Studio wrote:
If I run it manually everything is fine. Has anyone else had this same problem? Guess I ran out of stamina at this very moment ;)
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service. regards, Senra
Ausum Studio wrote:
If I run it manually everything is fine. Has anyone else had this same problem? Guess I ran out of stamina at this very moment ;)
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service.
I haven't tried 2.7.2 yet but I know I had some problems like this earlier when "upgrading". Is that what you did --"upgrade" attempting to use the same instance as you were already running? If I recall the location of the run time is recorded in the instance configuration file -- if it changes the instance fails to start(assuming the runtime files are not in the same spot) producing a problem with the same symptoms as you are seeing. Have you looked at the config file for the instance(s) to see if they are correct?
[Rodrigo Dias Arruda Senra]
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service.
It's unclear what it is, exactly, you mean by "same problem". It's true that Zope can't possibly work as a service in 2.7.2 as shipped, but almost everyone who tried the instructions here was able to repair that easily: http://zope.org/Collectors/Zope/1438
On Thu, 12 Aug 2004 14:01:39 -0400 Tim Peters <tim.peters@gmail.com> wrote:
[Rodrigo Dias Arruda Senra]
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service.
It's unclear what it is, exactly, you mean by "same problem".
Promise to be more specific next time. =) I never meant to sound as a show-stopper for 2.7.2, but now that I read my post again I see it might have sounded that way.
It's true that Zope can't possibly work as a service in 2.7.2 as shipped, but almost everyone who tried the instructions here was able to repair that easily:
Including me! Thank you kindly.
I 'll try to make peace with zope.collector <wink>. tchau, Senra
I did try the Collectors way and, as I wrote, I get this at the event log, after any attempt to start the service: """ Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. """ ..where the number of seconds vary. Part of the problem is the error message itself. It just doesn't help. Ausum ----- Original Message ----- From: "Tim Peters" <tim.peters@gmail.com> To: "Rodrigo Dias Arruda Senra" <rodsenra@gpr.com.br> Cc: <zope@zope.org> Sent: Thursday, August 12, 2004 7:01 PM Subject: Re: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
[Rodrigo Dias Arruda Senra]
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service.
It's unclear what it is, exactly, you mean by "same problem". It's true that Zope can't possibly work as a service in 2.7.2 as shipped, but almost everyone who tried the instructions here was able to repair that easily:
http://zope.org/Collectors/Zope/1438 _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
I must add, I'm trying to use another Python installation( g:\Python23 ), not Zope's default one. BTW, also tried uninstalling Python 2.3.4 and reinstalling Python 2.3.3. No changes whatsoever. Ausum ----- Original Message ----- From: "Ausum Studio" <ausum_studio@hotmail.com> To: <zope@zope.org> Sent: Thursday, August 12, 2004 11:23 PM Subject: Re: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
I did try the Collectors way and, as I wrote, I get this at the event log, after any attempt to start the service:
""" Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. """ ..where the number of seconds vary. Part of the problem is the error message itself. It just doesn't help.
Ausum
----- Original Message ----- From: "Tim Peters" <tim.peters@gmail.com> To: "Rodrigo Dias Arruda Senra" <rodsenra@gpr.com.br> Cc: <zope@zope.org> Sent: Thursday, August 12, 2004 7:01 PM Subject: Re: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
[Rodrigo Dias Arruda Senra]
I had the same problem. It was definetely introduced in 2.7.2, because 2.7.1 works fine as a service.
It's unclear what it is, exactly, you mean by "same problem". It's true that Zope can't possibly work as a service in 2.7.2 as shipped, but almost everyone who tried the instructions here was able to repair that easily:
http://zope.org/Collectors/Zope/1438 _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
I ran the service in debug mode and apparently the problem was in the path. I had already updated it according to http://www.zopelabs.com/cookbook/1091948185 , but I had used long names with spaces in between: "G:\Archivos de programa\Zope27\lib\python" Changed to 8.3 format and that made it.("G:\ARCHIV~1\Zope27\lib\python") Ausum ----- Original Message ----- From: "Ausum Studio" <ausum_studio@hotmail.com> To: <zope@zope.org> Sent: Thursday, August 12, 2004 11:23 PM Subject: Re: [Zope] Zope 2.7.2 still doesn't run as a service in w2k
I did try the Collectors way and, as I wrote, I get this at the event log, after any attempt to start the service:
""" Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. """ ..where the number of seconds vary. Part of the problem is the error message itself. It just doesn't help.
[Ausum Studio]
I ran the service in debug mode and apparently the problem was in the path. I had already updated it according to http://www.zopelabs.com/cookbook/1091948185 , but I had used long names with spaces in between: "G:\Archivos de programa\Zope27\lib\python"
Changed to 8.3 format and that made it.("G:\ARCHIV~1\Zope27\lib\python")
I don't know all the details, but that makes sense.so far as I do. Some basic Win32 API calls have no idea what to do with a space-infected pathname (which is one reason you can still use 8.3 alias names on the newer Windows filesystems, none of which have an *obvious* need for them).
On Thu, 12 Aug 2004 23:23:20 +0100 "Ausum Studio" <ausum_studio@hotmail.com> wrote:
I did try the Collectors way and, as I wrote, I get this at the event log, after any attempt to start the service:
The Collector http://zope.org/Collectors/Zope/1438 worked for me!
""" Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. """ ..where the number of seconds vary. Part of the problem is the error message itself. It just doesn't help.
I noticed you're using G:\, is this a network-mapped file system ? Once I had a problem trying to start a service (not Zope) from a samba-served-FS. If this is the case, I'd suggest you try re-installing the Zope service from a non-mapped local partition. regards, Senra
[Ausum Studio]
I did try the Collectors way and, as I wrote, I get this at the event log, after any attempt to start the service:
That's why I said the method worked for "almost everyone" instead of "everyone".
""" Zope_307702503 (Zope instance at G:\Zope-Instance): process died unexpectedly. Will attempt restart after 160 seconds. """ ...where the number of seconds vary. Part of the problem is the error message itself. It just doesn't help.
It doesn't help me either. I'd start it from the command line instead, in case the Windows services framework itself is throwing away a useful error message or traceback. I'd also look in Zope's logs for clues. Since it *does* work for "almost everyone", you have to start from the assumption that there's something different about your setup. For example, someone else asked whether you upgraded from a previous version of Zope, but are still trying to use an instance home created by a previous version. You have to answer questions like that.
participants (5)
-
Ausum Studio -
Brian Sullivan -
Chris Withers -
Rodrigo Dias Arruda Senra -
Tim Peters