When I check the zensyslog.log file, it looks like no messages are ever
received. I've verified that zensyslog is running, and listening on port 514,
and that messages are being sent on port 514, but they never show up in the
above log, nor in origsyslog.log. Am I missing some configuration somewhere?
I've looked at the admin document and at jcurry's Event Management doc, but
haven't gotten any farther.
Here's my zensyslog.conf:
Code:
#PARAMETER VALUE
logorig 1
logseverity 10
Here I can see that zensyslog is running and listening on the right port:
Code:
[r...@zenoss log]# lsof | grep syslog
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
.python.b 20883 zenoss 17u IPv4 112392 UDP
*:syslog
[r...@zenoss log]# ps -ef | grep 20883
zenoss 20883 1 0 08:27 ? 00:00:00
/usr/local/zenoss/python/bin/.python.bin
/usr/local/zenoss/zenoss/Products/ZenEvents/zensyslog.py --configfile
/usr/local/zenoss/zenoss/etc/zensyslog.conf --cycle --daemon
--useFileDescriptor=10
But when I open tcpdump and observe messages coming in, the corresponding
messages don't show up in zensyslog.log or origsyslog.log. Nothing ever shows
up in those logs.
>From two separate windows:
Code:
[r...@zenoss ~]# tcpdump port 514
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
08:36:03.945467 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 128
08:36:04.002857 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 128
08:36:04.002903 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 128
08:36:04.002936 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 137
08:36:04.002969 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 127
08:36:04.003000 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 128
08:36:04.003032 IP mul-gpsvr01-br.nagra.32824 > zenoss.nagra.syslog: SYSLOG
user.notice, length: 128
2009-09-10 08:27:31 INFO zen.ZenSyslog: Using udp file descriptor
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: run
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Connecting to localhost:8789
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Logging in as admin
2009-09-10 08:27:31 INFO zen.ZenSyslog: Connected to ZenHub
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: setting up services EventService
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: chaining getInitialServices with d2
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: callback after getting service
EventService
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Queueing event {'severity': 0,
'component': 'zensyslog', 'agent': 'zensyslog', 'summary': 'started',
'manager': 'localhost', 'device': 'localhost', 'eventClass': '/App/Start'}
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Calling connected.
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Queueing event {'severity': 0,
'component': 'zensyslog', 'agent': 'zensyslog', 'summary': 'zensyslog started',
'manager': 'localhost', 'device': 'localhost', 'eventClass': '/App/Start'}
2009-09-10 08:27:31 INFO zen.ZenSyslog: started
2009-09-10 08:27:31 INFO zen.ZenSyslog: fetching default RRDCreateCommand
2009-09-10 08:27:31 INFO zen.ZenSyslog: getting threshold classes
2009-09-10 08:27:31 DEBUG zen.ZenSyslog: Loading classes
['Products.ZenModel.MinMaxThreshold']
2009-09-10 08:27:32 INFO zen.ZenSyslog: getting collector thresholds
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zeneventlog
cycle time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle
time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zenperfsnmp
cycle time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zenping cycle
time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zenprocess cycle
time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.thresholds: Updating threshold ('zenwin cycle
time', ('localhost', ''))
2009-09-10 08:27:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:27:32 INFO zen.ZenSyslog: Fetching the default syslog priority ...
2009-09-10 08:27:32 INFO zen.ZenSyslog: Default min syslog priority is 6
2009-09-10 08:27:32 INFO zen.ZenSyslog: Configuration finished
2009-09-10 08:28:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:29:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:30:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:31:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:32:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:33:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:34:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:35:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
2009-09-10 08:36:32 DEBUG zen.ZenSyslog: Queueing event {'manager':
'localhost', 'timeout': 180, 'device': 'localhost', 'eventClass': '/Heartbeat',
'component': 'zensyslog', 'agent': 'zensyslog'}
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=39149#39149
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
