After installation zope and zope-config attempt to start zope instance by "/etc/init.d/zope-instance start" start zope. But after 5-10 sec zope hang without attempt to open port, write to log, or other visual effect. Start instance by "/var/lib/zope/zope-instance/bin/runzope" hang with next text to screen: ------ 2004-09-25T14:43:27 INFO(0) ZServer HTTP server started at Sat Sep 25 14:43:27 2004 Hostname: host-1 Port: 8080 ------ 2004-09-25T14:43:27 INFO(0) ZServer FTP server started at Sat Sep 25 14:43:27 2004 Hostname: host-1 Port: 8021 ------ 2004-09-25T14:43:27 INFO(0) Zope Set effective user to "zope-instance" Traceback (most recent call last): File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/run.py", line 50, in ? File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/run.py", line 19, in run File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/__init__.py", line 49, in start_zope File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/__init__.py", line 245, in makeLockFile ImportError: No module named misc.lock_file Reproducible: Always Steps to Reproduce: 1. Install Zope from scratch 2. Configure 3. Attempt to start.
seems to be a umask problem ... is '/usr/lib/zope-2.7.2/' world readable? question to the maintainers: should the permissions on the libs be set eplicitly on install? if so - what if /usr/lib/ is not world readable?
the permissions maybe borked up by the previous installation, they should be 755/644 on everything in /usr/lib/zope-2.7.2
i can not confirm this bug. after tests on two machines, installing zope-2.7.2-r2 from scratch and creating new instance using zope-config works ok. Could You Fyodor provide more information? Maybe some tests with "mv /var/lib/zope /var/lib/zope.old" would help?
It's my fault. /usr/lib/zope-2.7.2 is not world readable. May be this ticket should be renamed to "zope installer do not set correct umask if /usr/lib/zope* directory already exists"? But anyway, sorry for my wrong trobleticket.
