Continuing Woe with Win98 (but Zope V1.10.3 works!)
A while back I reported a problem with Zope under Win98. The symptoms are that everything looks OK in the MS-DOS command window but that when you try and browse to http://localhost:8080 then nothing happens. A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail. As Zope did _once_ work on this particular PC I went back to Zope 2.1.6 as I had a hunch that this was version I had originally tried (the problems on started when I upgraded to a later version). However, no luck. Then, just for the hell of it, I installed Zope 1.10.3. IT WORKS (over port 9673)! Zope V1 isn't alot of use to me, but I thought I'd report my findings in case it causes any flashes of deduction amongst Windows gurus out there which might lead to a resolution of the problem. For the record, the M$ Personal Web Server (or whatever it's called), works just fine - browsing to http://localhost does what you'd expect. Cheers. Paul -- The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK E-mail: paul.browning@bristol.ac.uk URL: http://www.bris.ac.uk/
----- Original Message ----- From: "Paul Browning" <paul.browning@bristol.ac.uk>
A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail.
Sounds very wierd & painful. I was one of the people who probably suggested editing 'hosts', since it did work for me a couple of times. But you say 'LMHOSTS'... There are two similarly named files in my Win98se system: C:\Windows\LMHOSTS.SAM C:\windows\hosts [no suffix at all] This second file is the one I suggest you try. I know little about Win32 TCP/IP beahvior, so perhaps this is just supersition. good luck - Jason ___________________________________________________________ Jason CUNLIFFE = NOMADICS['Interactive Art and Technology']
The LMHosts file is generally used to do ip to LanManager name addressing. It can be used as the seed file for WINDS addressing (which is another way of saying the same as the line above 8^) ). Paul, when you're in Cardiff next, bring the errant machine you. You never know, another set of eyes might see something obvious. Phil ----- Original Message ----- From: "Jason Cunliffe" <jasonic@nomadicsltd.com> To: "Paul Browning" <paul.browning@bristol.ac.uk>; <zope@zope.org> Sent: Tuesday, April 17, 2001 11:28 PM Subject: Re: [Zope] Continuing Woe with Win98 (but Zope V1.10.3 works!)
----- Original Message ----- From: "Paul Browning" <paul.browning@bristol.ac.uk>
A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail.
Sounds very wierd & painful.
I was one of the people who probably suggested editing 'hosts', since it did work for me a couple of times. But you say 'LMHOSTS'...
There are two similarly named files in my Win98se system:
C:\Windows\LMHOSTS.SAM
C:\windows\hosts [no suffix at all]
This second file is the one I suggest you try. I know little about Win32 TCP/IP beahvior, so perhaps this is just supersition.
good luck - Jason ___________________________________________________________ Jason CUNLIFFE = NOMADICS['Interactive Art and Technology']
_______________________________________________ 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 )
oops I meant WINS addressing ----- Original Message ----- From: "Phil Harris" <phil.harris@zope.co.uk> To: "Jason Cunliffe" <jasonic@nomadicsltd.com>; "Paul Browning" <paul.browning@bristol.ac.uk>; <zope@zope.org> Sent: Tuesday, April 17, 2001 11:32 PM Subject: Re: [Zope] Continuing Woe with Win98 (but Zope V1.10.3 works!)
The LMHosts file is generally used to do ip to LanManager name addressing.
It can be used as the seed file for WINDS addressing (which is another way of saying the same as the line above 8^) ).
Paul, when you're in Cardiff next, bring the errant machine you. You never know, another set of eyes might see something obvious.
Phil ----- Original Message ----- From: "Jason Cunliffe" <jasonic@nomadicsltd.com> To: "Paul Browning" <paul.browning@bristol.ac.uk>; <zope@zope.org> Sent: Tuesday, April 17, 2001 11:28 PM Subject: Re: [Zope] Continuing Woe with Win98 (but Zope V1.10.3 works!)
----- Original Message ----- From: "Paul Browning" <paul.browning@bristol.ac.uk>
A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail.
Sounds very wierd & painful.
I was one of the people who probably suggested editing 'hosts', since it did work for me a couple of times. But you say 'LMHOSTS'...
There are two similarly named files in my Win98se system:
C:\Windows\LMHOSTS.SAM
C:\windows\hosts [no suffix at all]
This second file is the one I suggest you try. I know little about Win32 TCP/IP beahvior, so perhaps this is just supersition.
good luck - Jason ___________________________________________________________ Jason CUNLIFFE = NOMADICS['Interactive Art and Technology']
_______________________________________________ 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 )
The correct host file is called "hosts", not "lmhosts". However, since the Personal Web Server answers to localhost, it's probably not an issue. You can verify this by trying to ping localhost and see if you get a response. A suggestion - get Zope to start up on some other port, say 9080, and see if you can talk to it there (just in case something mysterious is stepping on port 8080). I have run PWS and Zope on the same machine in the past, although I have also had do strange things that led me to unistall it. Another thing to try is to get an ftp client and see if it can talk to Zope on port 8021. When you run Zope, you said that "everything looks normal" in the DOS session. Does that mean that Zope announces which ports it is using and what its host name is? If not, Zope isn't loading correctly. It should look something like this (line breaks in the email client will probably garbage up this printout): ---------------------------------------------------------------------------- ------------ 2001-04-18T15:16:26 INFO(0) ZServer HTTP server started at Wed Apr 18 11:16:26 2001 Hostname: LS1191926A.mitretek.org Port: 8080 ------ 2001-04-18T15:16:26 INFO(0) ZServer FTP server started at Wed Apr 18 11:16:26 2001 Hostname: LS1191926A Port: 8021 ------ 2001-04-18T15:16:26 ERROR(200) ZServer Cannot write PID file. ------ 2001-04-18T15:16:26 INFO(0) ZServer PCGI Server started at Wed Apr 18 11:16:26 2001 Inet socket port: 8090 ---------------------------------------------------------------------------- ----------- Cheers, Tom P Paul Browning wrote -
A while back I reported a problem with Zope under Win98. The symptoms are that everything looks OK in the MS-DOS command window but that when you try and browse to http://localhost:8080 then nothing happens.
A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail.
...
Then, just for the hell of it, I installed Zope 1.10.3. IT WORKS (over port 9673)!
This actually begs a question, since something else was running on 8080 shouldn't Zope have complained that the port was in use? ----- Original Message ----- From: "Thomas B. Passin" <tpassin@mitretek.org> To: <zope@zope.org> Sent: Wednesday, April 18, 2001 4:19 PM Subject: Re: [Zope] Continuing Woe with Win98 (but Zope V1.10.3 works!)
The correct host file is called "hosts", not "lmhosts". However, since the Personal Web Server answers to localhost, it's probably not an issue. You can verify this by trying to ping localhost and see if you get a response.
A suggestion - get Zope to start up on some other port, say 9080, and see if you can talk to it there (just in case something mysterious is stepping on port 8080). I have run PWS and Zope on the same machine in the past, although I have also had do strange things that led me to unistall it.
Another thing to try is to get an ftp client and see if it can talk to Zope on port 8021.
When you run Zope, you said that "everything looks normal" in the DOS session. Does that mean that Zope announces which ports it is using and what its host name is? If not, Zope isn't loading correctly. It should look something like this (line breaks in the email client will probably garbage up this printout):
-------------------------------------------------------------------------- -- ------------ 2001-04-18T15:16:26 INFO(0) ZServer HTTP server started at Wed Apr 18 11:16:26 2001 Hostname: LS1191926A.mitretek.org Port: 8080 ------ 2001-04-18T15:16:26 INFO(0) ZServer FTP server started at Wed Apr 18 11:16:26 2001 Hostname: LS1191926A Port: 8021 ------ 2001-04-18T15:16:26 ERROR(200) ZServer Cannot write PID file. ------ 2001-04-18T15:16:26 INFO(0) ZServer PCGI Server started at Wed Apr 18 11:16:26 2001 Inet socket port: 8090
-------------------------------------------------------------------------- -- ----------- Cheers,
Tom P
Paul Browning wrote -
A while back I reported a problem with Zope under Win98. The symptoms are that everything looks OK in the MS-DOS command window but that when you try and browse to http://localhost:8080 then nothing happens.
A number of people made useful suggestions including making sure the was an entry in the Windoze LMHOSTS file but to no avail.
...
Then, just for the hell of it, I installed Zope 1.10.3. IT WORKS (over port 9673)!
_______________________________________________ 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 18 April 2001 16:27 +0100 Phil Harris <phil.harris@zope.co.uk> wrote:
This actually begs a question,
since something else was running on 8080 shouldn't Zope have complained that the port was in use?
Tom may not have seen my earlier message - it turned out I had a proxy server also running on port 8080. But Phil's comment stands - at least on Win98. Having started up Zope under Linux and caused a clash of ports I _know_ that it complains in that environment. Paul -- The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK E-mail: paul.browning@bristol.ac.uk URL: http://www.bris.ac.uk/
Can you file a collector issue about this? ----- Original Message ----- From: "Paul Browning" <paul.browning@bristol.ac.uk> To: "zope" <zope@zope.org> Cc: "Phil Harris" <phil.harris@zope.co.uk>; "Thomas B. Passin" <tpassin@mitretek.org> Sent: Wednesday, April 18, 2001 12:15 PM Subject: Re: [Zope] Continuing Woe with Win98 (but Zope V1.10.3 works!)
--On 18 April 2001 16:27 +0100 Phil Harris <phil.harris@zope.co.uk> wrote:
This actually begs a question,
since something else was running on 8080 shouldn't Zope have complained that the port was in use?
Tom may not have seen my earlier message - it turned out I had a proxy server also running on port 8080.
But Phil's comment stands - at least on Win98. Having started up Zope under Linux and caused a clash of ports I _know_ that it complains in that environment.
Paul
-- The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK E-mail: paul.browning@bristol.ac.uk URL: http://www.bris.ac.uk/
_______________________________________________ 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 (5)
-
Chris McDonough -
Jason Cunliffe -
Paul Browning -
Phil Harris -
Thomas B. Passin