As the original Report when rsyslog is lanched with -n, everything is running
just fine....
What's the difference for threads ?

Alain




ecze wrote
> Well not sure that the queue is involved...
> 
> After some seconds ( less than 2 minutes ) 
> netstat -naptu | sed -e 's/127.0.0.1/localhost/g' -e
> 's/\([0-9]*\.[0-9]*\.[0-9]*\.[0-9]*\)/adrshided/g' | grep rsyslog
> 
> tcp        0      0 localhost:41864             localhost:5432             
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 localhost:41871             localhost:5432             
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 adrshided:601          adrshided:46689        
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 localhost:41865             localhost:5432             
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 localhost:41867             localhost:5432             
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 adrshided:601          adrshided:46687        
> ESTABLISHED 28736/rsyslogd
> tcp        0      0 adrshided:601          adrshided:46688        
> ESTABLISHED 28736/rsyslogd
> udp        0      0 :::514                      :::*                          
>          
> 28736/rsyslogd
> 
> 2014-02-04T08:18:32.703380+01:00 serverx rsyslogd-pstats: imuxsock:
> submitted=0 ratelimit.discarded=0 ratelimit.numratelimiters=0
> 2014-02-04T08:18:32.703437+01:00 serverx rsyslogd-pstats: action 1:
> processed=28 failed=0
> 2014-02-04T08:18:32.703443+01:00 serverx rsyslogd-pstats: action 2:
> processed=3817 failed=0
> 2014-02-04T08:18:32.703447+01:00 serverx rsyslogd-pstats: action 3:
> processed=5 failed=0
> 2014-02-04T08:18:32.703472+01:00 serverx rsyslogd-pstats: action 4:
> processed=0 failed=0
> 2014-02-04T08:18:32.703477+01:00 serverx rsyslogd-pstats: action 5:
> processed=1 failed=0
> 2014-02-04T08:18:32.703484+01:00 serverx rsyslogd-pstats: action 6:
> processed=26 failed=0
> 2014-02-04T08:18:32.703487+01:00 serverx rsyslogd-pstats: action 7:
> processed=1 failed=0
> 2014-02-04T08:18:32.703490+01:00 serverx rsyslogd-pstats: action 8:
> processed=0 failed=0
> 2014-02-04T08:18:32.703494+01:00 serverx rsyslogd-pstats: action 9:
> processed=0 failed=0
> 2014-02-04T08:18:32.703497+01:00 serverx rsyslogd-pstats: action 10:
> processed=0 failed=0
> 2014-02-04T08:18:32.703500+01:00 serverx rsyslogd-pstats: action 11:
> processed=0 failed=0
> 2014-02-04T08:18:32.703503+01:00 serverx rsyslogd-pstats: action 12:
> processed=0 failed=0
> 2014-02-04T08:18:32.703505+01:00 serverx rsyslogd-pstats: action 13:
> processed=0 failed=0
> 2014-02-04T08:18:32.703508+01:00 serverx rsyslogd-pstats: imudp(*:514):
> submitted=26
> 2014-02-04T08:18:32.703511+01:00 serverx rsyslogd-pstats: imudp(*:514):
> submitted=0
> 2014-02-04T08:18:32.703513+01:00 serverx rsyslogd-pstats: imtcp(601):
> submitted=3823
> 2014-02-04T08:18:32.703519+01:00 serverx rsyslogd-pstats: action 2
> queue[DA]: size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0
> maxqsize=0
> 2014-02-04T08:18:32.703523+01:00 serverx rsyslogd-pstats: action 2 queue:
> size=0 enqueued=3817 full=0 discarded.full=0 discarded.nf=0 maxqsize=43
> 2014-02-04T08:18:32.703536+01:00 serverx rsyslogd-pstats: action 3
> queue[DA]: size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0
> maxqsize=0
> 2014-02-04T08:18:32.703540+01:00 serverx rsyslogd-pstats: action 3 queue:
> size=0 enqueued=5 full=0 discarded.full=0 discarded.nf=0 maxqsize=1
> 2014-02-04T08:18:32.703556+01:00 serverx rsyslogd-pstats: action 4
> queue[DA]: size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0
> maxqsize=0
> 2014-02-04T08:18:32.703560+01:00 serverx rsyslogd-pstats: action 4 queue:
> size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0 maxqsize=0
> 2014-02-04T08:18:32.703565+01:00 serverx rsyslogd-pstats: action 5
> queue[DA]: size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0
> maxqsize=0
> 2014-02-04T08:18:32.703592+01:00 serverx rsyslogd-pstats: action 5 queue:
> size=0 enqueued=1 full=0 discarded.full=0 discarded.nf=0 maxqsize=1
> 2014-02-04T08:18:32.703597+01:00 serverx rsyslogd-pstats: action 6
> queue[DA]: size=0 enqueued=0 full=0 discarded.full=0 discarded.nf=0
> maxqsize=0
> 2014-02-04T08:18:32.703601+01:00 serverx rsyslogd-pstats: action 6 queue:
> size=0 enqueued=26 full=0 discarded.full=0 discarded.nf=0 maxqsize=2
> 2014-02-04T08:18:32.703605+01:00 serverx rsyslogd-pstats: main Q: size=21
> enqueued=3905 full=0 discarded.full=0 discarded.nf=0 maxqsize=31
> 2014-02-04T08:19:32.763753+01:00 serverx rsyslogd-pstats: imuxsock:
> submitted=0 ratelimit.discarded=0 ratelimit.numratelimiters=0
> 
> no imtcp ipv4/ipv6 601
> no imudp ipv4 514
> 
> Idea ?





--
View this message in context: 
http://rsyslog-users.1305293.n2.nabble.com/Big-issues-with-Rsyslog-listening-on-port-514-with-IMRELP-tp7579826p7584196.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to