Hello jcc, Deleting Data.fs*, restarting zope and running zpasswd.py again solved the problem. I think this is an issue with SuSE 9.0, because this happened in 2 different installations.... Anyway, thanks to all the folks that helped me. Parra
The 'inituser' only works if your ZODB is getting created (the first time you run Zope.) You can simply delete Data.fs* if you want this to happen again.
--jcc
On Friday 14 November 2003 02:46, parra_zope wrote:
Hello jcc,
Deleting Data.fs*, restarting zope and running zpasswd.py again solved the problem. I think this is an issue with SuSE 9.0, because this happened in 2 different installations....
I am unable to sign into my myserver:8080/manage page. I get the loggin window but fail authentication with user and password I have just created via /opt/ zope/utilities/zpasswd.py. I restarted Zope ( with /etc/init.d/zope restart ) of course, after running zpasswd.py. I also tried deleting /opt/zope/var/ Data.fs and trying all over again with zpasswd.py and restart. My new Zope user and password stisll fail loggin. Any suggestions? Please help me.. "access" Hm.. where is the file "access" suposted to be located? Zope seems to put it into whatever directory I am in when I do the zpasswd.py. That can't be right unless I happen to be in the appropriate dir at the time. Whick dir should "access" be located in? Thank you, Roger SuSE 9
Roger Chrisman wrote:
On Friday 14 November 2003 02:46, parra_zope wrote:
Hello jcc,
Deleting Data.fs*, restarting zope and running zpasswd.py again solved the problem. I think this is an issue with SuSE 9.0, because this happened in 2 different installations....
I am unable to sign into my myserver:8080/manage page. I get the loggin window but fail authentication with user and password I have just created via /opt/ zope/utilities/zpasswd.py. I restarted Zope ( with /etc/init.d/zope restart ) of course, after running zpasswd.py. I also tried deleting /opt/zope/var/ Data.fs and trying all over again with zpasswd.py and restart. My new Zope user and password stisll fail loggin. Any suggestions? Please help me..
I do not know how SuSE packages Zope, because (a) I have never used SuSE and (b) I have never used a non-zope.org packaged Zope. Here's how it works: Zope has a SOFTWARE_HOME and an INSTANCE_HOME. Unless you tell it differently, Zope will assume them to be the same. I don't know if SuSE sets up a separate INSTANCE_HOME. SOFTWARE_HOME is by default the directory with zpassword.py and the rest of the Zope software. An INSTANCE_HOME has your var directory and maybe a Products directory (among possible others.) Your SOFTWARE_HOME has a var directory as well, but if there's a separate INSTANCE_HOME, it is not used. 'access' defines an emergency user for an existing ZODB. 'inituser' defines the user that will be created when a new ZODB is made upon first run of Zope. They are made in SOFTWARE_HOME, but must be put in INSTANCE_HOME to work. (If its the same directory as SOFTWARE_HOME, you're set.) A sure way to tell what's happening is to delete your Data.fs, create an 'inituser', start Zope, and check if 'inituser' still exists: it will be consumed if it is used. Otherwise, it's in the wrong place. So: Find your INSTANCE_HOME. The startup script (or a conf file if you're using zctl or 2.7) probably defines this, you can locate it there. Delete the Data.fs in its 'var' directory, move the 'inituser' in, and start Zope. Now things should work. If you're not in an INSTANCE_HOME setup, well, got me. Make sure things are done in the right order and it should work. --jcc -- "My point and period will be throughly wrought, Or well or ill, as this day's battle's fought."
My SuSE 9 seems to have Zope in only one place, here: p3a:/opt/zope # l total 71 drwxr-xr-x 10 zope root 384 2003-11-14 15:52 ./ drwxr-xr-x 3 root root 72 2003-11-14 10:48 ../ drwxr-xr-x 4 root root 576 2003-11-14 10:49 doc/ drwxr-xr-x 2 zope root 80 2003-11-14 10:48 Extensions/ drwxr-xr-x 2 zope root 160 2003-11-14 10:49 import/ -rw------- 1 root root 10 2003-11-14 15:49 inituser drwxr-xr-x 4 zope root 104 2003-11-14 10:49 lib/ drwxr-xr-x 7 zope root 704 2003-11-14 10:49 pcgi/ drwxr-xr-x 3 zope root 688 2003-11-14 14:44 utilities/ drwxr-xr-x 2 zope daemon 216 2003-11-14 15:50 var/ -rw-r--r-- 1 zope root 31553 2003-01-30 06:41 z2.py -rw-r--r-- 1 zope root 23195 2003-09-23 16:26 z2.pyc -rwxr-xr-x 1 zope root 373 2003-09-23 16:30 Zope.cgi* drwxr-xr-x 4 zope root 1008 2003-11-14 10:48 ZServer/ Neither SOFTWARE_HOME nor INSTANCE_HOME are in my bash env. Where can I look to see if I have an INSTANCE_HOME? Is it a variable in a zope config file? Which dir should I copy 'inituser' into? Thanks Roger On Friday 14 November 2003 15:07, J. Cameron Cooper wrote:
Roger Chrisman wrote:
On Friday 14 November 2003 02:46, parra_zope wrote:
Hello jcc,
Deleting Data.fs*, restarting zope and running zpasswd.py again solved the problem. I think this is an issue with SuSE 9.0, because this happened in 2 different installations....
I am unable to sign into my myserver:8080/manage page. I get the loggin window but fail authentication with user and password I have just created via /opt/ zope/utilities/zpasswd.py. I restarted Zope ( with /etc/init.d/zope restart ) of course, after running zpasswd.py. I also tried deleting /opt/zope/var/ Data.fs and trying all over again with zpasswd.py and restart. My new Zope user and password stisll fail loggin. Any suggestions? Please help me..
I do not know how SuSE packages Zope, because (a) I have never used SuSE and (b) I have never used a non-zope.org packaged Zope.
Here's how it works:
Zope has a SOFTWARE_HOME and an INSTANCE_HOME. Unless you tell it differently, Zope will assume them to be the same. I don't know if SuSE sets up a separate INSTANCE_HOME.
SOFTWARE_HOME is by default the directory with zpassword.py and the rest of the Zope software. An INSTANCE_HOME has your var directory and maybe a Products directory (among possible others.) Your SOFTWARE_HOME has a var directory as well, but if there's a separate INSTANCE_HOME, it is not used.
'access' defines an emergency user for an existing ZODB. 'inituser' defines the user that will be created when a new ZODB is made upon first run of Zope. They are made in SOFTWARE_HOME, but must be put in INSTANCE_HOME to work. (If its the same directory as SOFTWARE_HOME, you're set.) A sure way to tell what's happening is to delete your Data.fs, create an 'inituser', start Zope, and check if 'inituser' still exists: it will be consumed if it is used. Otherwise, it's in the wrong place.
So: Find your INSTANCE_HOME. The startup script (or a conf file if you're using zctl or 2.7) probably defines this, you can locate it there. Delete the Data.fs in its 'var' directory, move the 'inituser' in, and start Zope. Now things should work.
If you're not in an INSTANCE_HOME setup, well, got me. Make sure things are done in the right order and it should work.
--jcc
Hi, Doing a clear install of SuSE 9 (I caved, needed a fresh start this morning) I discovered the following: In the SuSE 9 installer > Software Selection > Zope > Description... it says, (1) See /usr/share/doc/packages/zope/README.SuSE for past installation hints. (2) Check http://www.zope.org/Products for available products and save time. In SuSE 9 installer > Software Selection > Zope > Dependencies... it says further that, (3) Zope requires Python 2.1. SuSE automatically includes Python 2.1 when you click "Check Dependencies." Python 2.3 is also available in the SuSE 9 installer but the installer gives a note in the description for Python 2.3 (sic) that recommends Python 2.1 instead if you will use Zope, due to some bugs that cause Zope to crash under Python 2.2 (sic, does NOT mention Python 2.3). This is Zope 2.6.1-132 on the SuSE 9 CDs. So I will use Python 2.1. Clean system install is almost done. I will look at that SuSE Readme and let you all know what I learn. Roger "What a difference a day makes."
Hi, Even after the complete reinstall of my SuSE 9 system I still have the same problem authenticating into http://localhost:8080/manage. I just get the loggin form again and again. I have Apache off so it can't be Apache's fault. I learned so far that in SuSE 9, - '/etc/init.d/zope start' will start Zope. - Initial login user for Zope management is 'superuser' with password '123', but this fails the login at http://localhost:8080/manage. - /usr/share/doc/packages/zope/README.SuSE did not tell me much. I copied it below anyway incase you see something there I didn't. What am I doing wrong? Do I need to set up Zope's env with the various SOFTWARE_HOME="/opt/zope" type env variables? And if so how? Any Zope config files I need to know about? Thanks, Roger :-) stuck on this for 48 hours :-\ *************** /usr/share/doc/packages/zope/README.SuSE ******************* Post installation notes ----------------------- Default system account is: user superuser, password 123. You should change system password by 'zpasswd'. It is wise to set also some domain restriction for this user. After installation, zope is set up to use its own web server. If you want to use Apache with Zope (thru PCGI), set ZOPE_PCGI=yes in /etc/sysconfig/apache (see also variable ZOPE_KEEP_HOMES). More options for Zope can be found in /etc/sysconfig/zope! More options for Zope can be found in /etc/sysconfig/zope or via 'yast2 sysconfig &' in section 'Network/WWW/Zope'. $ZOPE_HOME is /opt/zope/. For German documentation feel free to visit www.dzug.org, website of Deutsche Zope User Group (DZUG). Note: Apache redirection is configured in /etc/httpd/zope.conf. This configuration file is included from /etc/httpd/httpd.conf by Apache web server. Have a lot fun... *****************************************************************************************
I'm not a Suse user so this is just a guess. Go the directory in which Zope resides ( lib, bin, zpasswd.py, and var should be there). Runs ./bin/python zpasswd inituser and fill in the requested dialog. Then restart Zope. That should set a new initial password. On Sat, 15 Nov 2003, Roger Chrisman wrote:
Hi,
Even after the complete reinstall of my SuSE 9 system I still have the same problem authenticating into http://localhost:8080/manage. I just get the loggin form again and again. I have Apache off so it can't be Apache's fault.
I learned so far that in SuSE 9,
- '/etc/init.d/zope start' will start Zope.
- Initial login user for Zope management is 'superuser' with password '123', but this fails the login at http://localhost:8080/manage.
- /usr/share/doc/packages/zope/README.SuSE did not tell me much. I copied it below anyway incase you see something there I didn't.
What am I doing wrong?
Do I need to set up Zope's env with the various SOFTWARE_HOME="/opt/zope" type env variables? And if so how? Any Zope config files I need to know about?
Thanks,
Roger :-) stuck on this for 48 hours :-\
*************** /usr/share/doc/packages/zope/README.SuSE *******************
Post installation notes -----------------------
Default system account is: user superuser, password 123.
You should change system password by 'zpasswd'. It is wise to set also some domain restriction for this user.
After installation, zope is set up to use its own web server. If you want to use Apache with Zope (thru PCGI), set ZOPE_PCGI=yes in /etc/sysconfig/apache (see also variable ZOPE_KEEP_HOMES).
More options for Zope can be found in /etc/sysconfig/zope!
More options for Zope can be found in /etc/sysconfig/zope or via 'yast2 sysconfig &' in section 'Network/WWW/Zope'.
$ZOPE_HOME is /opt/zope/.
For German documentation feel free to visit www.dzug.org, website of Deutsche Zope User Group (DZUG).
Note: Apache redirection is configured in /etc/httpd/zope.conf. This configuration file is included from /etc/httpd/httpd.conf by Apache web server.
Have a lot fun...
*****************************************************************************************
_______________________________________________ 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 )
On Saturday 15 November 2003 21:36, Dennis Allison wrote:
I'm not a Suse user so this is just a guess. Go the directory in which Zope resides ( lib, bin, zpasswd.py, and var should be there). Runs
./bin/python zpasswd inituser
and fill in the requested dialog. Then restart Zope. That should set a new initial password.
Tried that. Still can't login on the localhost:8080/manage page. Yesterday, J. Cameron Cooper posted: A sure way to tell what's happening is to delete your Data.fs, create an 'inituser', start Zope, and check if 'inituser' still exists: it will be consumed if it is used. Otherwise, it's in the wrong place. So: Find your INSTANCE_HOME. The startup script (or a conf file if you're using zctl or 2.7) probably defines this, you can locate it there. Delete the Data.fs in its 'var' directory, move the 'inituser' in, and start Zope. Now things should work. I tried that, too. Didn't work either. inituser was not consumed. Someone, please give me another tip... Roger :-)
Take a look at the permissions of the var directory in which Data.fs resides. Try setting the permissions to 0777 and set the files inside to 0666 -- it's a bad idea to run that way (just like it's a bad idea to run zope as root) but it'll help localize your problem. If, after doing this and restarting Zope you can log it, you then need to think through and reset the permissions for your setup. Also, for the moment you may want to run Zope in debug mode. Out of debug mode some versions of Zope enforce commenting rules, for example. On Sat, 15 Nov 2003, Roger Chrisman wrote:
On Saturday 15 November 2003 21:36, Dennis Allison wrote:
I'm not a Suse user so this is just a guess. �Go the directory in which Zope resides ( lib, bin, zpasswd.py, and var should be there). �Runs
��������./bin/python zpasswd inituser
and fill in the requested dialog. �Then restart Zope. �That should set a new initial password.
Tried that. Still can't login on the localhost:8080/manage page.
Yesterday, J. Cameron Cooper posted:
A sure way to tell what's happening is to delete your Data.fs, create an 'inituser', start Zope, and check if 'inituser' still exists: it will be consumed if it is used. Otherwise, it's in the wrong place.
So: Find your INSTANCE_HOME. The startup script (or a conf file if you're using zctl or 2.7) probably defines this, you can locate it there. Delete the Data.fs in its 'var' directory, move the 'inituser' in, and start Zope. Now things should work.
I tried that, too. Didn't work either. inituser was not consumed.
Someone, please give me another tip...
Roger :-)
_______________________________________________ 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 )
On Saturday 15 November 2003 22:22, Dennis Allison wrote:
Take a look at the permissions of the var directory in which Data.fs resides. Try setting the permissions to 0777 and set the files inside to 0666 -- it's a bad idea to run that way (just like it's a bad idea to run zope as root) but it'll help localize your problem. If, after doing this and restarting Zope you can log it, you then need to think through and reset the permissions for your setup. Also, for the moment you may want to run Zope in debug mode. Out of debug mode some versions of Zope enforce commenting rules, for example.
Dennis, Thanks for this tip. Tried it and still can't login though. Just get another little login window popping up every time I try. Any other tips, anyone? thx, Roger
Thanks for this tip. Tried it and still can't login though. Just get another little login window popping up every time I try.
Well, I guess I'd next try to download a fresh copy of zope (2.6.2b5 is the latest stable with bug fixes). I'd get the binary version and unpack it into a new directory and try to get it to run. It should pretty much run out of the box. When you get that to work you can then work backwards to get it installed as a Suse service.
On Saturday 15 November 2003 22:48, Dennis Allison wrote:
Thanks for this tip. Tried it and still can't login though. Just get another little login window popping up every time I try.
Well, I guess I'd next try to download a fresh copy of zope (2.6.2b5 is the latest stable with bug fixes). I'd get the binary version and unpack it into a new directory and try to get it to run. It should pretty much run out of the box. When you get that to work you can then work backwards to get it installed as a Suse service.
Thanks, trying that now.. .. first attempt failed. Trying again, following installation notes in the Zope Book: http://zope.org/Documentation/Books/ZopeBook/2_6Edition/InstallingZope.stx YES! (0) Remove all my Zope and Python stuff with SuSE 9's Yast device. Then, (1) Create a 'zope' user with # useradd -d /opt/zope (2) Create 'zope's home dir # mkdir /opt/zope # chown zope:users /opt/zope (3) Give user 'zope' a system password with # passwd zope (enter a password you can remember here) (4) Unpack the downloaded binary (downloaded from zope.org) in the /opt/zope dir. Move it there first if that is not where it is. # tar -xvzf Zope-2.6.2-linux2-x86.tgz (5) IMPORTANT! Change ownership of everything (recursively, option -R) in /opt/zope to user 'zope' group 'users' # chown -R zope:users /opt/zope/* (6) Logged out 'root' and back in as 'zope' ...tap tap tap (takes me to user 'zope's home dir -- /opt/zope) (7) Install Zope $ ./install (Yes! it worked this time. Had tried it before chowning all /opt/zope to 'zope:users' and it had failed.) IMPORTANT! Note the username and password shown by the installer. --------------------------------- afterthoughts... ----------------------------------------- Why not chown /opt/zope dir itself to 'zope:users'? $ su [root password] # chown zope:users /opt/zope # exit Please advise me.. Should the group be 'users'? Someone please advise me if it should be something else :--) For this installation of Zope I will use Zserver instead of Apache. Now.. can I sign into the browser based management window? :-/ (http://myserver:8080/manage1) (0) Start Zope (logged in a 'zope') $ /opt/zope/start (cool, it starts!) (1) On my desktop computer (Zope is running on my server computer) login to the Zope's Wed manage interface. Startup Mozilla and go to, http://myserver:8080/manage (or is in manage1? I already forgot but I'm on manage now, no numeral 1 here) Sign in.. Failed! Ouch! Sign in and *cut and paste* the password from my still open server terminal window into the browser authentication window... Yes! Works! I'm IN THE ZOPE ADMIN WEB PAGE! .. it was a dicey password to type in by hand on my goofy DataHand keyboard 8=) Hope this helps someone. Took me THREE DAYS to get to this point! :-| Thanks all who offered tips. I'm sure I will need more.. Roger :-)
Also, In case you see something helpfull in this that I don't, here is SuSE's /etc/sysconfig/zope file ***************************************************************************************** ## Path: Network/WWW/Zope ## Description: Zope configuration ## ServiceRestart: zope # ## Type: yesno ## Default: no # # Run in Zope debug mode. This causes the Zope process not to # detach from the controlling terminal, and is equivalent to # supplying the environment variable setting Z_DEBUG_MODE=1 # ZOPE_DEBUG="no" # ## Type: yesno ## Default: yes # # Sould the Zope FTP port be enabled? # ZOPE_FTP="yes" # ## Type: integer ## Default: 8021 # # The FTP port. The standard port for FTP services is 21. # The default Zope FTP port is 8021. # ZOPE_FTP_PORT="8021" # ## Type: integer ## Default: 8080 # # The Web server (HTTP) port. This defaults to 8080. The # standard port for HTTP services is 80. # ZOPE_HTTP_PORT="8080" # ## Type: ip ## Default: # # The IP address to listen on. If this is an empty string # (e.g. -a ''), then all addresses on the machine are used. The # default is . # ZOPE_IP_ADDRESS="" # ## Type: integer ## Default: 4 # # The number of threads to use, if ZODB3 is used. The default is 4. # ZOPE_THREADS="4" # ## Type: yesno ## Default: yes # # Sould the Zope WebDAV port be enabled? # ZOPE_WEBDAV="yes" # ## Type: integer ## Default: 8088 # # The "WebDAV source" port. The default is disabled. Note that # this feature is a workaround for the lack of "source-link" support # in standard WebDAV clients. # ZOPE_WEBDAV_PORT="8088" # ## Type: yesno ## Default: no # # Sould the Zope monitor port be enabled? # ZOPE_MONITOR="no" # ## Type: integer ## Default: 8089 # # The secure monitor server port. The monitor server # allows interactive Python style access to a running ZServer. To # access the server see medusa/monitor_client.py # The monitor server password is the same as the Zope # emergency user password set in the 'access' # file. The default is to not start up a monitor server. # ZOPE_MONITOR_PORT="8089" # ## Type: string ## Default: # # Enable locale (internationalization) support. The value passed for # this option should be the name of the locale to be used (see your # operating system documentation for locale information specific to # your system). If an empty string is passed for this option (-L ''), # Zope will set the locale to the user's default setting (typically # specified in the $LANG environment variable). If your Python # installation does not support the locale module, the requested # locale is not supported by your system or an empty string was # passed but no default locale can be found, an error will be raised # and Zope will not start. # ZOPE_LANG=""
participants (4)
-
Dennis Allison -
J. Cameron Cooper -
parra_zope -
Roger Chrisman