Trying to get started with Zope, I've compiled 2.0.0a1 on RedHat 5.2 with Python 1.5.2. No errors during compile, but when I try http://localhost:9673/manage I get (after the username/password challenge) Zope Error Zope has encountered an error while publishing this resource. exceptions.NameError The traceback is: <!-- Traceback (innermost last): File /usr/src/Zope-2.0.0a1-src/lib/python/ZPublisher/Publish.py, line 255, in publish_module File /usr/src/Zope-2.0.0a1-src/lib/python/ZPublisher/Publish.py, line 161, in publish File /usr/src/Zope-2.0.0a1-src/lib/python/ZPublisher/mapply.py, line 145, in mapply (Object: manage) NameError: |en --> This happens whether I run ZopeHTTPD or ZServer, and whether I access localhost or use a browser remotely. Guess I've missed something somewhere. Can anybody give me a hint? Michael Beddow
Michael Beddow wrote:
Trying to get started with Zope, I've compiled 2.0.0a1 on RedHat 5.2 with Python 1.5.2. No errors during compile, but when I try http://localhost:9673/manage I get (after the username/password challenge) <snip> This happens whether I run ZopeHTTPD or ZServer, and whether I access localhost or use a browser remotely.
Guess I've missed something somewhere. Can anybody give me a hint?
Did you override the default username and password ? Michael Bernstein
Michael Bernstein wrote:
Michael Beddow wrote:
Trying to get started with Zope, I've compiled
2.0.0a1 on RedHat
5.2 with Python 1.5.2. No errors during compile, but when I try http://localhost:9673/manage I get (after the username/password challenge) <snip> This happens whether I run ZopeHTTPD or ZServer, and whether I access localhost or use a browser remotely.
Guess I've missed something somewhere. Can anybody give me a hint?
Did you override the default username and password ?
Michael Bernstein
I tried it with the default superuser/123 combination, then with a variety of others via the access file. Same result. I'm authenticated OK, but then I get the error and the backtrace in my original posting. The server logs show it happening, first the 401 authentication challenge then the 500 of the server error. wks01 - - [08/Jun/1999 19:57:41] "GET /manage HTTP/1.1" 401 - wks01 - - [08/Jun/1999 19:57:50] "GET /manage HTTP/1.1" 500 - It's very frustrating reading about the great things Zope can do and not being able to get off the ground with it. I thought about getting a binary of 1.x.x instead, but I prefer to have control of what goes where on my system, so I guess I'll have to give up for now. Michael Beddow
Michael Beddow wrote:
Trying to get started with Zope, I've compiled
2.0.0a1 on RedHat
5.2 with Python 1.5.2. No errors during compile, <snip> I'm authenticated OK, but then I get the error and the backtrace in my original posting. The server logs show it happening, first the 401 authentication challenge then the 500 of the server error.
wks01 - - [08/Jun/1999 19:57:41] "GET /manage HTTP/1.1" 401 - wks01 - - [08/Jun/1999 19:57:50] "GET /manage HTTP/1.1" 500 -
It's very frustrating reading about the great things Zope can do and not being able to get off the ground with it. I thought about getting a binary of 1.x.x instead, but I prefer to have control of what goes where on my system, so I guess I'll have to give up for now.
Don't give up yet. When you compiled, did you use w_pcgi or wo_pcgi ? Here is a link to the instructions that I used: http://www.zope.org/pipermail/zope/1999-May/004670.html Also, did you install the RPMs for Python 1.5.2, or did you compile it yourself? Cheers, Michael Bernstein.
I may just have the answer, after installing Zope 2.0.0a1 on RedHat 5.2, Python 1.5.2 I had to make a slight adjustment to the RewriteRule :- From: RewriteRule ^/Zope/(.*) /usr/local/apache/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l] To: RewriteRule ^/Zope(.*) /usr/local/apache/cgi-bin/Zope.cgi$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l] Notice the lack of '/' on both sides of the rule. This was done because when Zope was looking for certain parts of it's system, it was not finding, update screens, management interfaces etc. This seems to have cured it for the moment and all is now working great 8^). HTH Phil phil@philh.org ----- Original Message ----- From: Michael Bernstein <mbernstein@profitscape.net> To: <beddow01@globalnet.co.uk> Cc: <zope@zope.org> Sent: Wednesday, June 09, 1999 5:41 PM Subject: Re: [Zope] Newbie q: Name.error at startup
Michael Beddow wrote:
Trying to get started with Zope, I've compiled
2.0.0a1 on RedHat
5.2 with Python 1.5.2. No errors during compile, <snip> I'm authenticated OK, but then I get the error and the backtrace in my original posting. The server logs show it happening, first the 401 authentication challenge then the 500 of the server error.
wks01 - - [08/Jun/1999 19:57:41] "GET /manage HTTP/1.1" 401 - wks01 - - [08/Jun/1999 19:57:50] "GET /manage HTTP/1.1" 500 -
It's very frustrating reading about the great things Zope can do and not being able to get off the ground with it. I thought about getting a binary of 1.x.x instead, but I prefer to have control of what goes where on my system, so I guess I'll have to give up for now.
Don't give up yet. When you compiled, did you use w_pcgi or wo_pcgi ?
Here is a link to the instructions that I used: http://www.zope.org/pipermail/zope/1999-May/004670.html
Also, did you install the RPMs for Python 1.5.2, or did you compile it yourself?
Cheers,
Michael Bernstein.
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Michael Bernstein wrote:
Don't give up yet. When you compiled, did you use w_pcgi or wo_pcgi ?
Here is a link to the instructions that I used: http://www.zope.org/pipermail/zope/1999-May/004670.html
Also, did you install the RPMs for Python 1.5.2, or did you compile it yourself?
Thanks for the pointers, Phil and Michael, but I'm still stuck. I installed Python and devel-Python 1.5.2 from rpms and compiled Zope with wo_pcgi In the meantime, I've used Microsoft-type support techniques, i.e. zapped everything and reinstalled/rebuilt everything from scratch. No change. Some more output (sorry folks!) in the hope that something may click with someone [root@smlc02 zope]# python z2.py -d 129.11.193.42 & [1] 2389 [root@smlc02 zope]# zinit: Thu Jun 10 21:30:05 1999: Houston, we have forked zinit: Thu Jun 10 21:30:05 1999: Houston, we have forked zinit: Thu Jun 10 21:30:05 1999: Hi, I just forked off a kid: 2390 log: adding channel <trigger at 83ca680> log: adding channel <zhttp_server at 83efda8> Medusa (V1.6) started at Thu Jun 10 21:30:08 1999 Hostname: smlc02.leeds.ac.uk Port:9673 log: adding channel <FTPServer at 83ea6b0> FTP server started at Thu Jun 10 21:30:08 1999 Authorizer:None Hostname: localhost Port: 9221 A first check of the process table gives: [root@smlc02 zope]# ps auxwww | grep z2 nobody 2390 0.9 8.4 5724 5292 p2 S 21:30 0:02 /usr/bin/python z2.py -d 129.11.193.42 root 2389 0.0 1.7 1640 1108 p2 S 21:30 0:00 python z2.py -d 129.11.193.42 Then I try to access Zope, with the results I described already. Z2.log now shows arts2-pc040.leeds.ac.uk:3512 - - [10/Jun/1999:21:32:01 +0100] "GET /manage HTTP/1.1" 401 1748 arts2-pc040.leeds.ac.uk:3512 - - [10/Jun/1999:21:32:49 +0100] "GET /manage HTTP/1.1" 500 1541 A recheck of the process table now shows: [root@smlc02 zope]# ps auxwww | grep z2 nobody 2390 0.6 8.5 5812 5356 p2 S 21:30 0:02 /usr/bin/python z2.py -d 129.11.193.42 nobody 2393 0.0 8.5 5812 5356 p2 S 21:32 0:00 /usr/bin/python z2.py -d 129.11.193.42 nobody 2394 0.0 8.5 5812 5356 p2 S 21:32 0:00 /usr/bin/python z2.py -d 129.11.193.42 nobody 2395 0.0 8.5 5812 5356 p2 S 21:32 0:00 /usr/bin/python z2.py -d 129.11.193.42 nobody 2396 0.0 8.5 5812 5356 p2 S 21:32 0:00 /usr/bin/python z2.py -d 129.11.193.42 nobody 2397 0.0 8.5 5812 5356 p2 S 21:32 0:00 /usr/bin/python z2.py -d 129.11.193.42 root 2389 0.0 1.7 1640 1108 p2 S 21:30 0:00 python z2.py -d 129.11.193.42 [root@smlc02 zope]# I haven't followed up Phil's suggestion, since I'm not using Apache for the time being. I don't want to interfere with my working Apache configuration till I have more confidence with Zope (if I ever get any confidence, that is ;-) Michael Beddow
participants (3)
-
Michael Beddow -
Michael Bernstein -
Phil Harris