I am getting an error after logging into the Zenoss webpage. The error states File "/opt/zenoss/lib/python/zenoss/protocols/services/___init__.py" line 126 in _executeRequest raise ServiceResponseError|response reason, response.status, request, response, content) Service RespnseError: Service Unavailable. This occured after a crash of the system. I am kind of new to this and would like some guidance.
It sort of sounds like one of your daemons isn't running or is frozen (preventing a new instance from starting), you may have a stale pid file sitting somewhere that is causing the issue. Become the zenoss user and do "zenoss status". You'll see the running status of each daemon as well as a pid for each.
Daemon: zeoctl program running; pid=1013
Daemon: zopectl program running; pid=1023
Daemon: zenhub program running; pid=1069
Daemon: zenjobs program running; pid=1103
Daemon: zenping program running; pid=1180
Daemon: zensyslog program running; pid=1239
Daemon: zenstatus program running; pid=1245
Daemon: zenactions program running; pid=1305
Daemon: zentrap program running; pid=1377
Daemon: zenperfsnmp program running; pid=1382
Daemon: zencommand program running; pid=1417
Daemon: zenprocess program running; pid=1447
Daemon: zenwin program running; pid=1491
Daemon: zenwinsrvsnmp program running; pid=1527
Daemon: zeneventlog program running; pid=1584
Daemon: zenperfwmi program running; pid=1632
Daemon: zensla program running; pid=1665
Daemon: zenticket program running; pid=1678
After that do "zenoss stop" and check the status again to make sure they all show as stopped.
Now check to make sure that you can't find any processes that are shown as stopped but are actually still running...
zenoss@lab01:~$ ps aux | grep zeoctl
zenoss 1011 0.0 0.3 62848 9448 ? Ssl Jul10 0:05 /usr/local/zenoss/python/bin/.python.bin /usr/local/zenoss/zenoss/lib/python/zdaemon/zdrun.py -S /usr/local/zenoss/zenoss/lib/python/ZEO/zeoctl.xml -C /usr/local/zenoss/zenoss/etc/zeo.conf /usr/local/zenoss/zenoss/bin/runzeo
zenoss 3035 0.0 0.0 7628 936 pts/0 S+ 11:30 0:00 grep zeoctl
If you find one kill it by pid, for instance to kill the example process above:
kill -9 1011
Repeat for each daemon that you find still running.
Once you have confirmed that no daemons are running and they all show as stopped under status, check in /opt/zenoss/var for stale .pid files. If you find any pid files in that location (for example: zenperfsnmp-localhost.pid or ZEO.pid) remove them.
After you have confirmed all of the above start Zenoss again. Let me know if this resolves the issue or not.
It looks like all of the services are stopping with the zenoss stop command. I did not see any *.pid files once the services were supposedly shutdown. From what I can see, it appears to be something with Zope services. Is there any further information I can provide.
I added several text files to show what I am getting with shutting down and restarting the services. I also included the text from the error details on the webpage. All of the services show as starting. Not sure if there is a dependant service which is not starting.
Based on that dump you're running Enterprise 4. Enterprise 4 is so different from Core 3 that I don't have any practical experience to help you based on. Had they done their usual release cycle and released Core 4 before Enterprise 4 we wouldn't have this type of community support issue. I would advise that you open a ticket with Enterprise support for your issue as it's going to be effectively impossible for anyone in the community to understand the new architechture well enough to assist you until Core 4 is released and we gain some experience with it.