RE: [Zope] 2.01 will not run on NT4
Hi Jim - I got it working now. I didn't have it running as a service, but from a shortcut on the desktop that pointed to the real start.bat. Thinking it was a typical shortcut generated command prompt window I was closing it after seeing it produce it's startup messages. This was apparently closing Zope... I've never seen a window need to stay open like this before so just followed my nose. Something should be added to the install notes about this. Is there a place I could suggest this? Thanks to everyone for helping out. Michael Simcich AccessTools -----Original Message----- From: Jim Sanford [mailto:jsanford@atinucleus.com] Sent: Thursday, September 30, 1999 10:55 AM To: Michael Simcich Subject: Re: [Zope] 2.01 will not run on NT4 Don't know if localhost works elsewhere, never tried it. We set this machine up strictly to be an SSL front end to Zope. The data we have to access for our project is in Visual FoxPro tables so we had to use a windows machine for the ODBC connectivity with ZODBCA. I rarely access zope on the machine from the machine. It is sitting in our server room upstairs across the parking lot with a 100mbit connection to the database server and the router attached to our T1. When in the office I access it across the network and at home (where I do most of my programming) I access it via a dialup directly to the router. We do not run Zope 2 as an NT service. We had problems (the exact nature of which I don't currently remember) running it as an NT service so we just run it as a regular program that sits down on the task bar. That is all this machine does - runs IIS 4.0 with SSL solely accessing Zope via zope.pcgi. The default.htm for IIS takes you right to the top index_html for Zope which immediately makes you log in. If you fail login you are redirected to our public website which is on another machine (which is contolled by the marketing department) Zope is installed in a directory under Program Files (not under Inetpub). The zope.pcgi file is installed in the IIS wwwroot\scripts directory. __________________________________________________________________ Jim Sanford ^ Database Engineer ^ ^ ^ Accelerated Technology, Inc. ^ ^ 720 Oak Circle Drive East ^ ^ ^ Mobile, AL 36609 ^ ^ ^ Voice: 334-661-5770 fax: 334-661-5788 ^ ^ E-Mail: jsanford@atinucleus.com Web: http://www.atinucleus.com Source Code, No Royalties, Any CPU...It just make sense ! __________________________________________________________________ -----Original Message----- From: Michael Simcich <msimcich@accesstools.com> To: 'Jim Sanford' <jsanford@atinucleus.com> Date: Thursday, September 30, 1999 12:34 PM Subject: RE: [Zope] 2.01 will not run on NT4 Wow, this is really starting to spook me, I didn't think getting Zope to run was going to be such a big deal. Is the rest of the program this busted/cantankerous? I tried your suggestion but it came back with the same response - basically nothing is there. When you said that on your NT box localhost didn't work either do you mean that localhost doesn't work at all or only as a means to access Zope? On my rig localhost works fine, but adding the 8080: thing seems to mean nothing to it. Thanks Michael Simcich AccessTools -----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jim Sanford Sent: Thursday, September 30, 1999 9:34 AM To: Michael Simcich; zope@zope.org; Martijn Pieters Subject: Re: [Zope] 2.01 will not run on NT4 try http://123.456.789.123:8080/manage instead (where 123.456.789.123 is replace with the nT machine's ip address). My NT box doesn't seem to recognize localhost and this works for me. That would probably change if I created a hosts file in the system32 dir but since the other works I have never gotten around to it. Jim Sanford -----Original Message----- From: Martijn Pieters <mj@antraciet.nl> To: Michael Simcich <msimcich@accesstools.com>; zope@zope.org <zope@zope.org> Date: Thursday, September 30, 1999 10:32 AM Subject: Re: [Zope] 2.01 will not run on NT4 At 16:15 30/09/99 , Michael Simcich wrote:
Hi all -
Followed the install info for the lastest Zope release on NT. I ran start.bat. However browsing to http://localhost:8080/manage gets me a "page not found" message.
Here is what start.bat got me:
>>>>>>>>> C:\ZopeSite>"C:\ZopeSite\bin\python.exe" "C:\ZopeSite\z2.py" -D
1999-09-30T14:12:37 PROBLEM(100) ZServer Computing default hostname ------ 1999-09-30T14:12:37 INFO(0) ZServer Medusa (V1.10) started at Thu Sep 30 07:12:37 1999 Hostname: c147070-a.pinol1.sfba.home.com Port:8080
------ 1999-09-30T14:12:37 INFO(0) ZServer FTP server started at Thu Sep 30 07:12:37 1999 Authorizer:None Hostname: gemini Port: 8021 ------ 1999-09-30T14:12:37 INFO(0) ZServer Monitor Server (V1.5) started on port 8099
>>>>>>>>>
The installed faq has the following:
>>>>>>> 1. After installing Zope, I go to the URL in my web browser but I get a "404 Not Found" or "Server Error" message
This message is coming from your web server, not Zope. It usually means that your web server is misconfigured. Ensure that the PCGI info file generated by the installation procedure exists in a cgi-enabled directory, and that your web server has any required aliases or configuration options set to enable it to find this file and run it as a cgi program.
Look in the error log for your web server for details of the error.
>>>>>>>
This is related to running Zope behind a seperate Web server, like IIS.
This would seem to contradict this from the install.txt:
>>>>>>> 5. Select Destination Directory where you want the software installed. This should *NOT* be a directory that is published by any existing web server software. >>>>>>>
A seperate webserver connects to Zope via a small CGI script, so Zope itself doesn't need to be, and shouldn't be, in a published directory. However, a default install of Zope doesn't install itself to run behind a server, but to run behind ZServer. The output from start.bat indicates it is running fine. It seems you don't have any default content in your object database. Just add /manage to the URL, like so: http://localhost:8080/manage And you can start adding objects. The fact that no default content is provided is however a bug. If you want to have default content, see if the file Data.fs.in exists in the var subdir, and copy that to Data.fs (which is the objetc database file). -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------ _______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope (Related lists - please, no cross posts or HTML encoding! To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) _______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope (Related lists - please, no cross posts or HTML encoding! To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Michael Simcich wrote:
Thinking it was a typical shortcut generated command prompt window I was closing it after seeing it produce it's startup messages. This was apparently closing Zope... I've never seen a window need to stay open like this before so just followed my nose.
It's that way because start.bat starts Zope in debugging mode. Remove the line or the part where it mentions -D and then it will close itself and zope will stay up.
Something should be added to the install notes about this. Is there a place I could suggest this?
not sure about this. -- ~mindlace
At 17:07 1-10-99 , Ethan Fremen wrote:
Michael Simcich wrote:
Thinking it was a typical shortcut generated command prompt window I was closing it after seeing it produce it's startup messages. This was apparently closing Zope... I've never seen a window need to stay open like this before so just followed my nose.
It's that way because start.bat starts Zope in debugging mode. Remove the line or the part where it mentions -D and then it will close itself and zope will stay up.
Erm, no. It won't. It works that way on UNIX, but not on Win32, because that Win32 just doesn't support that. The -D switch stands for Debug, and has more effects than just not disconnecting from the terminal on UNIX. Not running in a window can only be achieved when running Zope as a service, and therefore only on NT. This mode was especially set up to overcome the above problem. Note that when running as a service, there seem to be some problems with ODBC connections. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | T: +31 35 7502100 F: +31 35 7502111 | mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ---------------------------------------------
"Note that when running as a service, there seem to be some problems with ODBC connections." I'm just about to try those out - does the problem just not work at all or is it something that I as a neophyte don't have to worry about? Michael Simcich AccessTools -----Original Message----- From: Martijn Pieters [mailto:mj@antraciet.nl] Sent: Saturday, October 02, 1999 1:07 PM To: Ethan Fremen; Michael Simcich Cc: 'Jim Sanford'; Zope@Zope.Org (E-mail) Subject: Re: [Zope] 2.01 will not run on NT4 At 17:07 1-10-99 , Ethan Fremen wrote:
Michael Simcich wrote:
Thinking it was a typical shortcut generated command prompt window I was closing it after seeing it produce it's startup messages. This was apparently closing Zope... I've never seen a window need to stay open like this before so just followed my nose.
It's that way because start.bat starts Zope in debugging mode. Remove the line or the part where it mentions -D and then it will close itself and zope will stay up.
Erm, no. It won't. It works that way on UNIX, but not on Win32, because that Win32 just doesn't support that. The -D switch stands for Debug, and has more effects than just not disconnecting from the terminal on UNIX. Not running in a window can only be achieved when running Zope as a service, and therefore only on NT. This mode was especially set up to overcome the above problem. Note that when running as a service, there seem to be some problems with ODBC connections. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | T: +31 35 7502100 F: +31 35 7502111 | mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ---------------------------------------------
At 23:08 2-10-99 , Michael Simcich wrote:
"Note that when running as a service, there seem to be some problems with ODBC connections." I'm just about to try those out - does the problem just not work at all or is it something that I as a neophyte don't have to worry about?
I don't know any details about this, I just know that two people have recently reported problems accessing any ODBC sources when running Zope as a service. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | T: +31 35 7502100 F: +31 35 7502111 | mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ---------------------------------------------
Martijn Pieters wrote:
It's that way because start.bat starts Zope in debugging mode. Remove the line or the part where it mentions -D and then it will close itself and zope will stay up.
Erm, no. It won't. It works that way on UNIX, but not on Win32,
erp, sorry. just used to the unix way of doing things... -- ~mindlace
participants (3)
-
Ethan Fremen -
Martijn Pieters -
Michael Simcich