Is it possible that you have another syslog listening on port 514?? (we think that the real error is getting masked by the one we see in the trace.) Check by doing a netstat -an | grep :514

-EAD

On Jul 31, 2006, at 2:21 AM, Juan Pedro Escalona Rueda wrote:

Hello again!

OS: Gentoo 2006.0

Python Version: Python 2.4.2

Here is status of Zenoss:

Daemon: zeoctl program running; pid=10881
Daemon: zopectl program running; pid=10885
Daemon: zenmodeler program running; pid=10895
Daemon: zenperfsnmp program running; pid=10907
Daemon: zenping program running; pid=10920
Daemon: zensyslog (pid 10930) not running
Daemon: zenstatus program running; pid=10947
Daemon: zenactions program running; pid=10964


And here ps aux:

root 10880 0.0 0.5 9212 6944 ? Ss Jul28 0:00 / usr/bin/python2.4 /usr/local/zenoss/lib/python/zdaemon/zdrun.py -S / usr/local/zenoss/lib/py root 10881 0.0 1.0 14884 12060 ? S Jul28 0:54 / usr/bin/python2.4 /usr/local/zenoss/lib/python/ZEO/runzeo.py -C / usr/local/zenoss/etc/zeo.c root 10884 0.0 0.4 7784 5464 ? Ss Jul28 0:00 / usr/bin/python2.4 /usr/local/zenoss/lib/python/zdaemon/zdrun.py -S / usr/local/zenoss/lib/py zenoss 10885 0.2 6.2 111012 72600 ? Sl Jul28 11:06 / usr/bin/python2.4 /usr/local/zenoss/lib/python/Zope2/Startup/run.py -C /usr/local/zenoss/et zenoss 10895 0.7 4.6 66852 53804 ? Sl Jul28 31:43 / usr/local/zenoss/bin/python /usr/local/zenoss/Products/ DataCollector/zenmodeler.py --config zenoss 10907 5.5 2.4 56452 28380 ? Rl Jul28 219:59 / usr/local/zenoss/bin/python /usr/local/zenoss/Products/ZenRRD/ zenperfsnmp.py --configfile / root 10920 0.0 2.0 36460 23736 ? S Jul28 2:04 / usr/local/zenoss/bin/python /usr/local/zenoss/Products/ZenStatus/ zenping.py --configfile /u root 10947 1.1 2.2 38952 26308 ? S Jul28 47:08 / usr/local/zenoss/bin/python /usr/local/zenoss/Products/ZenStatus/ zenstatus.py --configfile zenoss 10964 0.0 1.8 34228 21480 ? S Jul28 0:24 / usr/local/zenoss/bin/python /usr/local/zenoss/Products/ZenEvents/ zenactions.py --configfile

Thanks! Regards!

Erik A. Dahl wrote:
We are totally stumped by this. What platform, python version are you running? Are you sure that zeo is running?

-EAD

On Jul 28, 2006, at 6:54 AM, Juan Pedro Escalona Rueda wrote:

Hello! I have problems with zensyslog. It isn't start... here log error:

-------------------------------------------------------------------- ---------------------------------
/iagrazo log # ../bin/zensyslog run -v 1
INFO:zen.Syslog:starting Thread-1
DEBUG:zen.Events:EventClassInst=Start
DEBUG:zen.Events:Found device=iagrazo.iavantefundacion.com
DEBUG:zen.Events:delete from status where
device='iagrazo.iavantefundacion.com' and component='zensyslog' and
eventKey='' and (eventClass='/App/Stop' or eventClass='/App/Start')
DEBUG:zen.Events:insert into history set
Location='/',prodState='1000',firstTime='1154083466.1',severity='0', component='zensyslog',DeviceGroups='|/',summary='zensyslog
collector
started',dedupid='iagrazo.iavantefundacion.com|zensyslog|/App/ Start||0|zensyslog
collector
started',manager='iagrazo.iavantefundacion.com',DeviceClass='/ Server/Linux',device='iagrazo.iavantefundacion.com',eventClass='/ App/Start',lastTime='1154083466.1',Systems='|/ Linux',message='zensyslog
collector
started',eventKey='',deletedTime=null,evid='0a4979d3342d970afffffff'
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenEvents/zensyslog.py", line 190, in ?
    ZenSyslog().serve()
File "/usr/local/zenoss/Products/ZenEvents/zensyslog.py", line 59, in
__init__
    severity=0, component="zensyslog"))
File "/usr/local/zenoss/Products/ZenEvents/zensyslog.py", line 149, in
sendEvent
    zem._p_jar.close()
File "/usr/local/zenoss/lib/python/Products/ZODBMountPoint/ Mount.py",
line 226, in close
    self._real_close()
File "/usr/local/zenoss/lib/python/ZODB/Connection.py", line 240, in close raise ConnectionStateError("Cannot close a connection joined to " ZODB.POSException.ConnectionStateError: Cannot close a connection joined
to a transaction
Exception in thread Thread-1 (most likely raised during interpreter
shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
File "/usr/local/zenoss/Products/ZenEvents/ SyslogProcessingThread.py",
line 91, in run
exceptions.AttributeError: 'NoneType' object has no attribute 'Empty'
Unhandled exception in thread started by
Error in sys.excepthook:

Original exception was:/
-------------------------------------------------------------------- --------------------------------------------------

There are some connection yet? I think....

Regards!


--
*Juan Pedro Escalona Rueda*
**Becario de Sistemas**
FUNDACIÓN IAVANTE
[EMAIL PROTECTED]
Tel. 958 002 270



Este correo electrónico y, en su caso, cualquier fichero anexo, contiene
información confidencial exclusivamente dirigida a su(s)
destinatario(s). Toda copia o divulgación deberá ser autorizada por IAVANTE.
This e-mail and any attachments are confidential and exclusively
directed to its adressee(s). Any copy or distribution will have to be
authorized by IAVANTE.

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users


--
Juan Pedro Escalona Rueda
Becario de Sistemas
FUNDACIÓN IAVANTE
[EMAIL PROTECTED]
Tel. 958 002 270


Este correo electrónico y, en su caso, cualquier fichero anexo, contiene información confidencial exclusivamente dirigida a su(s) destinatario(s). Toda copia o divulgación deberá ser autorizada por IAVANTE. This e-mail and any attachments are confidential and exclusively directed to its adressee(s). Any copy or distribution will have to be authorized by IAVANTE.

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to