On 6/15/07, Maciej Wisniowski < maciej.wisniowski@coig.katowice.pl> wrote:

> Greetings
> thank you for your help.
> first i want to ask if i should reply to you like what i am doing now,
> or send the message to zope@zope.org <mailto: zope@zope.org>? I am new
> to mailing lists and don't know the rules.
You should always stay on the list. It is common to just use 'Reply all'
option when replying.

> In my zope/log folder there is no event.log file, just a simple line
> readme.txt file.
> running the zopectl fg displayed the following:
>
> /** OUTPUT **/
> /tmp/zope/bin/runzope -X debug-mode=on
> 2007-06-15 09:33:41 INFO ZServer HTTP server started at Fri Jun 15
> 09:33:41 2007
>         Hostname: 0.0.0.0 <http://0.0.0.0>
>         Port: 8080
> 2007-06-15 09:33:51 INFO Zope Ready to handle requests
> Traceback (most recent call last):
>   File "/opt/Zope-2.10/lib/python/Zope2/Startup/run.py", line 56, in ?
>     run()
>   File "/opt/Zope- 2.10/lib/python/Zope2/Startup/run.py", line 21, in run
>     starter.prepare()
>   File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line
> 111, in prepare
>     self.setupFinalLogging ()
>   File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line
> 372, in setupFinalLogging
>     self.setupConfiguredLoggers()
>   File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line
> 254, in setupConfiguredLoggers
>     self.cfg.eventlog()
>   File
> "/opt/Zope-2.10/lib/python/ZConfig/components/logger/factory.py", line
> 32, in __call__
>     self.instance = self.create()
>   File
> "/opt/Zope-2.10/lib/python/ZConfig/components/logger/logger.py", line
> 42, in create
>     handler = handler_factory()
>   File
> "/opt/Zope- 2.10/lib/python/ZConfig/components/logger/factory.py", line
> 32, in __call__
>     self.instance = self.create()
>   File
> "/opt/Zope-2.10/lib/python/ZConfig/components/logger/handlers.py",
> line 69, in create
>     logger = self.create_loghandler()
>   File
> "/opt/Zope-2.10/lib/python/ZConfig/components/logger/handlers.py",
> line 87, in create_loghandler
>     handler = loghandler.FileHandler(path)
>   File "/opt/Zope-
> 2.10/lib/python/ZConfig/components/logger/loghandler.py", line 34, in
> __init__
>     StreamHandler.__init__(self, open(filename, mode))
> IOError: [Errno 13] Permission denied: '/tmp/zope/log/event.log'
> /** END **/
So seems  that you have incorrect permissions
set for /tmp/zope/log/event.log and
you need to change them or start zope as different user.
BTW you've chosen strange place (/tmp) to install your zope ;)

what is strange is that event.log does not actually exist in the log folder,
I deleted the /tmp/zope folder and deleted the opt/Zope-2.10  , and installed zope again and created a new instance in /opt/zope.
I am still working in root, and the problem still exist. running ./zopectl fg couldn't continue :

/** OUTPUT **/
[root@localhost bin]# ./zopectl fg
/opt/zope/bin/runzope -X debug-mode=on
2007-06-15 11:39:34 INFO ZServer HTTP server started at Fri Jun 15 11:39:34 2007
        Hostname: 0.0.0.0
        Port: 8080
2007-06-15 11:39:34 CRITICAL Zope A user was not specified to setuid to; fix this to start as root (change the effective-user directive in zope.conf)
Traceback (most recent call last):
  File "/opt/Zope-2.10/lib/python/Zope2/Startup/run.py", line 56, in ?
    run()
  File "/opt/Zope-2.10/lib/python/Zope2/Startup/run.py", line 21, in run
    starter.prepare()
  File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line 98, in prepare
    self.dropPrivileges()
  File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line 234, in dropPrivileges
    return dropPrivileges(self.cfg)
  File "/opt/Zope-2.10/lib/python/Zope2/Startup/__init__.py", line 403, in dropPrivileges
    raise ZConfig.ConfigurationError(msg)
ZConfig.ConfigurationError: A user was not specified to setuid to; fix this to start as root (change the effective-user directive in zope.conf)
/** END **/

When everything was ok in the past I was able to run zope through ./zopectl start (as a root)
but now the stop command displays that  the daemon manager is not open.


--
Maciej Wisniowski