On Thu, 24 Apr 2008 21:48:30 +0200 (CEST) scorpion7@iqonline.net wrote:
location, etc.) it appears that some services still aren't starting:
$$> nav start Starting: cricket iptrace logengine mactrace maintengine networkDiscovery pping smsd thresholdMon Failed: alertengine eventengine getDeviceData servicemon
I've already done some research and had to hand-tool some .py files as there were errors for "import sre as re" and python stated that it was deprecated, ie: it should be "import re" (sre is now re)
That old skeleton... I've just committed a changeset to my local repository to fix those imports for good.
I'm not seeing any log data (even with debug=6 in nav.conf) for the failed services. Does anyone have information that may lead to this being more successful?
The debug setting in nav.conf only applies to the Java subsystems (as I think the comment in nav.conf says). This applies to eventengine and getDeviceData. If these two fail on startup, they might not get the chance to log normally to (eventEngine|getDeviceData).log, but their stderr output will be placed in log/eventEngine/eventEngine-stderr.log and log/getDeviceData/getDeviceData-stderr.log. Those files should tell you why they won't start.
The alertEngine loglevel setting is in etc/alertengine.cfg. It has two log files, alertengine.log and alertengine.err. The latter logs whatever Perl exceptions and errors that occur during alertEngine's runtime.
servicemon (and pping) are sort of notorious for having startup problems. We don't know exactly what's going on with them yet, but usually it helps to just keep "nav start"-ing them a couple of times, until they stick ;-)
BTW - we utilize Apache 2.x with AD authentication for internal resources. I've seen some errors with python and the web pages as well - is there an expectation that it would be Apache 1.x instead?
No, we absolutely recommend Apache 2.x. I think you'll only get an _old_ mod_python to work with 1.x.
Thanks!
You're welcome!