It looks like it is a memory issue. Zenoss starts now, but during the initial startup it's falling over in places, but still managing to start...
Code: r...@web3 [/usr/src]# service zenoss start Zenoss not initialized. Performing first-boot initialization... Fresh install pre steps Stopping snmpd: [ OK ] Starting snmpd: [ OK ] Shutting down MySQL. SUCCESS! Starting MySQL. SUCCESS! Starting Zope Object Database . daemon process started, pid=28391 Loading initial Zenoss objects into the Zeo database (this can take a few minutes) zport portal object exits; exiting. Stopping Zope Object Database . daemon process stopped Zenoss initialization complete. Daemon: zeoctl . daemon process started, pid=28495 Daemon: zopectl . daemon process started, pid=28499 Daemon: zenhub starting... Daemon: zenjobs starting... Daemon: zenping starting... Daemon: zensyslog starting... Daemon: zenstatus starting... Daemon: zenactions starting... Daemon: zentrap /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable starting... Daemon: zenmodeler /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable starting... Daemon: zenperfsnmp /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable starting... sh: fork: Resource temporarily unavailable Daemon: zencommand /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable /opt/zenoss/bin/zenfunctions: line 35: [: too many arguments /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable Daemon: zenprocess /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable Daemon: zenwin /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable Daemon: zeneventlog /opt/zenoss/bin/zenfunctions: fork: Resource temporarily unavailable Fresh install post step I can still connect to the Web UI no problem, but in certain places certain things don't work, such as the Daemons tab. It throws the message I posted in my 2nd post. However I have noticed memory usage is now nearly maxed out. Perhaps this is the cause after all. cPanel reckons 75% is currently in use. Those daemons that are throwing that resource error probably cannot start due to memory shortage. I know my host is due to upgrade our servers to 1.5GB RAM next week, so I'll wait till then before I start doing any further tests. Thanks for your help. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36364#36364 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
