Aug 5, 2011 5:39 PM
zenping/zensyslog/zentrap won't start on Ubuntu 10.04
-
Like (1)
Hi, all,
I have just got zenoss core 3 installed. While trying to get it to process syslog, I found out that those 3 daemons were not running:
zenoss$ zenoss status
Daemon: zeoctl program running; pid=30543
Daemon: zopectl program running; pid=30548
Daemon: zenhub program running; pid=25243
Daemon: zenjobs program running; pid=30602
Daemon: zenping not running
Daemon: zensyslog not running
Daemon: zenstatus program running; pid=30688
Daemon: zenactions program running; pid=30719
Daemon: zentrap not running
Daemon: zenmodeler program running; pid=30806
Daemon: zenperfsnmp program running; pid=30840
Daemon: zencommand program running; pid=30866
Daemon: zenprocess program running; pid=30892
Daemon: zenwin program running; pid=30931
Daemon: zeneventlog program running; pid=30970
Also, the 3 log files (zenping.log, zensyslog.log and zentrap.log) are all zero in size, which doesn't give me much to troubleshoot.
I have searched in the forum for the problem. I believe I have fixed the "sudoer" configuration.
When I manually start or restart zenoss, it shows that those 3 are being restarted, but then they won't run.
All help are much appreciated!
--
Wei
If something is alreay using the syslog port ( 514 ) maybe zensyslog would not start, try stopping the syslogd on the box if its running.
Same for zentrap, maybe you already have some sort of trap listener running? Try doing a netstat and look for port 162, something like netstat -a|grep 162, look for LISTEN
Zenping, I cant thing of anything for this one,even if something else was pinging, it should still start. I would work on the other two first and see if you can get them running.
I've successfully run Zenoss on 10.04, so your issue is not an incompatibility with the OS, it has to be something else.
Manuel
Thanks for the reply.
I have checked for anything on port 514 or 162, both UDP and TCP. There are nothing on those ports:
# lsof -iudp:514
# lsof -iudp:162
# lsof -itcp:162
# lsof -itcp:514
As expected, "netstat -an | grep 514" returns nothing either.
well the only standard response is, turn up the logging level for the daemons and start them and if your lucky you will see something that makes sense.
In the config file for the daemon:
logseverity 10
then try to start the daemon and look in the log file.
The "logseverity" value was 20, I am not sure setting to 10 turns it up or down.
But either way, nothing shows up on the "zensyslog start" command line, or in the "log/zensyslog.log" file.
try 10
Make sure the zenoss user is in the proper group with permissions on $ZENHOME/bin/zensocket. I've had the same problem in the past and this was the fix.
Regards,
John
/usr/local/zenoss/bin$ ls -l zensocket
-rwsr-xr-x 1 zenoss zenoss 18466 2011-07-07 12:39 zensocket
I think that should be good for the zenoss user, which is what's running all the Zenoss daemons.
@mwcotton: Yes, I tried both 10 and 20. The result does not change either way.
it needs to be owned by root
That does not change the result:
zenoss@lab252:~/zenossinst$ zenoss start
Daemon: zeoctl .
daemon process started, pid=29644
Daemon: zopectl .
daemon process started, pid=29649
Daemon: zenhub starting...
Daemon: zenjobs starting...
Daemon: zenping starting...
Daemon: zensyslog starting...
Daemon: zenstatus starting...
Daemon: zenactions starting...
Daemon: zentrap starting...
Daemon: zenmodeler starting...
Daemon: zenperfsnmp starting...
Daemon: zencommand starting...
Daemon: zenprocess starting...
Daemon: zenwin starting...
Daemon: zeneventlog starting...
zenoss@lab252:~/zenossinst$ zenoss status
Daemon: zeoctl program running; pid=29644
Daemon: zopectl program running; pid=29649
Daemon: zenhub program running; pid=29685
Daemon: zenjobs program running; pid=29713
Daemon: zenping not running
Daemon: zensyslog not running
Daemon: zenstatus program running; pid=29790
Daemon: zenactions program running; pid=29816
Daemon: zentrap not running
Daemon: zenmodeler program running; pid=29908
Daemon: zenperfsnmp program running; pid=29941
Daemon: zencommand program running; pid=29977
Daemon: zenprocess program running; pid=30003
Daemon: zenwin program running; pid=30042
Daemon: zeneventlog program running; pid=30081
zenoss@lab252:~/zenossinst$ ls -l /usr/local/zenoss/bin/zensocket
-rwxr-xr-x 1 root zenoss 18466 2011-07-07 12:39 /usr/local/zenoss/bin/zensocket
zensocket needs the following very specific permissions. It needs to be owner by the root user and the zenoss group. It also needs to be setuid. You can set this up using the following commands.
cd /usr/local/zenoss/bin
chown root:zenoss zensocket
chmod 4750 zensocket
The permissions on the file should like like this..
-rwsr-x--- 1 root zenoss 22443 Aug 17 22:19 zensocket
Thanks, Chet!
You are right. That was the reason that those three commands refused to start.
The Zenoss install script created the "zensock" with "zenoss.zenoss" ownership. I did a "chown root zensock" after receiving the tip from mwcotton. That command actually took the "s" bit out of zensock's permission list. I noticed that after re-installing zenoss.
Now those 3 are running OK with "zenoss start", I've got a different problem: zopectl no longer starts -- after I re-installed everything.
But that should be another topic. Thanks to everyone for helping.
----
[edit] -- The "zopectl" issue was my fault -- I had forgotten that I setup Apache2 to function as an HTTPS front end to Zenoss. All processes are up and running now.
Hi Chet, just want to say thank you for your solution. I've been battling with the same issue for the whole day until I found this post.
Ngoc
hi Chet,
Thank you for your solution.
Sambhav
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||