Skip navigation
3807 Views 0 Replies Latest reply: Dec 1, 2010 12:25 PM by jblaine RSS
jblaine Rank: White Belt 11 posts since
Nov 17, 2010
Currently Being Moderated

Dec 1, 2010 12:25 PM

SOLUTION: (bug?) zeoctl no longer stays running, port 8080 unresponsive

Zenoss 3.0.3

 

After rebooting, I could no longer get data from port 8080.  The connection is made, but no data is ever returned.  Solution is below.

 

[root@zenoss log]# uptime

12:10:40 up  1:03,  1 user,  load average: 0.89, 0.47, 0.22

[root@zenoss log]# uname -a

Linux zenoss 2.6.18-194.17.4.el5 #1 SMP Mon Oct 25 15:50:53 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@zenoss log]#

 

 

[root@zenoss log]# su - zenoss -c "/opt/zenoss/bin/zenoss status"

Daemon: zeoctl daemon manager not running

Daemon: zopectl program running; pid=5263

Daemon: zenhub program running; pid=5303

Daemon: zenjobs program running; pid=5334

Daemon: zenping program running; pid=5400

Daemon: zensyslog program running; pid=5437

Daemon: zenstatus program running; pid=5442

Daemon: zenactions program running; pid=5472

Daemon: zentrap program running; pid=5570

Daemon: zenmodeler program running; pid=5575

Daemon: zenperfsnmp program running; pid=5609

Daemon: zencommand program running; pid=5636

Daemon: zenprocess program running; pid=5662

Daemon: zenwin program running; pid=5701

Daemon: zeneventlog program running; pid=5740

Daemon: zenjmx program running; pid=5770

[root@zenoss log]#

zeo.log contains:

 

...

 

2010-12-01T12:06:34 INFO root spawned process pid=5757

------

2010-12-01T12:06:35 INFO ZEO.runzeo (5757) created PID file '/opt/zenoss/var/ZEO.pid'

------

2010-12-01T12:06:35 INFO ZEO.runzeo (5757) opening storage '1' using FileStorage

------

2010-12-01T12:06:35 DEBUG ZODB.BaseStorage create storage /opt/zenoss/var/Data.fs

------

2010-12-01T12:06:35 INFO ZEO.runzeo (5757) removed PID file '/opt/zenoss/var/ZEO.pid'

------

2010-12-01T12:06:35 INFO root sleep 9 to avoid rapid restarts

------

2010-12-01T12:06:35 INFO root pid 5757: exit status 1

------

2010-12-01T12:06:44 INFO root spawned process pid=5772

------

2010-12-01T12:06:44 INFO ZEO.runzeo (5772) created PID file '/opt/zenoss/var/ZEO.pid'

------

2010-12-01T12:06:44 INFO ZEO.runzeo (5772) opening storage '1' using FileStorage

------

2010-12-01T12:06:44 DEBUG ZODB.BaseStorage create storage /opt/zenoss/var/Data.fs

------

2010-12-01T12:06:44 INFO ZEO.runzeo (5772) removed PID file '/opt/zenoss/var/ZEO.pid'

------

2010-12-01T12:06:44 CRITICAL root restarting too frequently; quit

 

Then by googling around, I ended up at http://plone.293351.n2.nabble.com/zeoserver-won-t-start-td3372254.html and noticed the following permissions in $ZENHOME/var
-rw-r--r--  1 root   root   67687692 Nov 28 03:10 Data.fs.old
-rw-r--r--  1 root   root    1121800 Nov 28 04:32 Data.fs.index
-rw-r--r--  1 root   root   52259608 Dec  1 11:01 Data.fs
-rw-r--r--  1 root   root          0 Dec  1 11:05 Data.fs.index.index_tmp
Setting these to owner zenoss and group zenoss, with a restart of /etc/init.d/zenoss, solved the problem.
HOW the data got that way, I will never know.  It was not by my hand, and I am the only one with access to the box.
WHY Zope can't simply log, "Storage XYZ is not writeable.", I cannot understand.

More Like This

  • Retrieving data ...