Hi All,
I saw a blurb elsewhere about trying to start the server/console via the web and nothing happening. for me, running as the apache user, I get the following:
-- snip, snip --
bash-2.05b$ /usr/local/bin/zmdc.pl start zmwatch.pl
Unable to connect, starting server
Can't open log file: Permission denied at /usr/local/bin/zmdc.pl line 153.
Can't connect: No such file or directory at /usr/local/bin/zmdc.pl line 145.
bash-2.05b$ id
uid=48(apache) gid=48(apache) groups=48(apache)
-- snip, snip --
combing through an strace I ran, I see that one of the complaints it has is trying to open /tmp/zmdc.sock
When I run /etc/init.d/zm start, it reports success, and while this is happening 'ps -ax' shows me that it's trying 'zmpkg.pl start' and 'zmdc.pl start zmc -d', with another zmdc.pl process that is defunct. after a bit, All these processes go away.
from zmpkg.log, I see the following each time I run the init script:
Executing: /usr/local/bin/zmdc.pl check
Removing shared memory
Executing: /usr/local/bin/zmfix
Executing: /usr/local/bin/zmdc.pl status
Can't open log file: Permission denied at /usr/local/bin/zmdc.pl line 153.
Can't connect: No such file or directory at /usr/local/bin/zmdc.pl line 145.
Executing: /usr/local/bin/zmdc.pl start zmc -d 0
Can't open log file: Permission denied at /usr/local/bin/zmdc.pl line 153.
Can't connect: No such file or directory at /usr/local/bin/zmdc.pl line 145.
Executing: /usr/local/bin/zmdc.pl start zmaudit.pl -d 900 -y
Can't open log file: Permission denied at /usr/local/bin/zmdc.pl line 153.
Can't connect: No such file or directory at /usr/local/bin/zmdc.pl line 145.
Executing: /usr/local/bin/zmdc.pl start zmwatch.pl
Can't open log file: Permission denied at /usr/local/bin/zmdc.pl line 153.
Can't connect: No such file or directory at /usr/local/bin/zmdc.pl line 145
Any Thoughts? Thanks for any help!
Cheers,
Erik.
Starting ZM on RH9
-
- Posts: 9
- Joined: Wed Aug 27, 2003 4:24 pm
Re: Starting ZM on RH9
/me shakes his head
You'd think that for all the poking around I did that I'd check to see that the place I specified for the logs was actually writable by the apache user. I had it group-writable, but that didn't suffice. I changed it to /tmp and am done with it.
Onwards and upwards.
You'd think that for all the poking around I did that I'd check to see that the place I specified for the logs was actually writable by the apache user. I had it group-writable, but that didn't suffice. I changed it to /tmp and am done with it.
Onwards and upwards.