search for: unconn

Attempting to lookup why rsyslogd is listening on the high port UDP/51427. Have not succeeded in what this port is used for and what directive controls what interface it binds to. [root at bedrock ~]# netstat --listen --inet --program --numeric | grep syslog udp??0??0 0.0.0.0:51427??0.0.0.0:*???66655/rsyslogd? -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383

Hi all, I have a problem with ntpd daemon in my CentOS7 vm. When I try to list peers, command fails: [root at c7tst ntpstats]# ntpq ntpq> pe ntpq: read: Connection refused ntpq> My actual ntp.conf: # For more information about this file, see the man pages # ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5). driftfile /var/lib/ntp/drift # Permit time

...nctional. On 14 July 2016 at 05:10, Petr Man <petr at madnetwork.org> wrote: > Good morning, > > Here is the log, I don't see anything unusual. I took the same tinc binary > and tried on two other machines and it works fine - binds to 655/UDP > without issues: > udp UNCONN 0 0 *:655 > *:* users:(("tincd",18872,7)) > tcp LISTEN 0 3 *:655 > *:* users:(("tincd",18872,6)) > > > Petr > > On Thu, Jul 14, 2016 at 12:18 AM, Rob Townley <rob.townley at gmail...

...he client side of the UDP session. You can verify this by running tcpdump to capture traffic when a syslog message is passed. I can report that I also see this netstat (and similar with ss) state for systems with rsyslog set up to send to a remote log server, where ss reports that the process has UNCONN state on high UDP ports. I suspect it's part of the UDP handshake that rsyslog uses for sending syslogs, but I'm not familiar enough with how it works to say definitively. Since it's UDP, it's a sessionless protocol, so it's not strictly LISTENing, but with ss you can see it...

Hi guys, I have now done the obvious - swapped out the kernel. Upgrading to 4.5.7 fixed the problem! udp UNCONN 0 1408 *:655 *:* users:(("tincd",pid=3242,fd=7)) tcp LISTEN 0 3 *:655 *:* users:(("tincd",pid=3242,fd=6)) Thank you very much for your time. Petr On Fri, Jul 15, 2016 at 7:22 AM, Petr Man <pe...

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

All, Running dovecot 2.3.10 on a CentOS 7.x and logging via syslog seems to stop when i restart rsyslog process. Reload doesnt get it working again only a dovecot restart. Tested this with dovecot 2.2.36 and this did not exhibit the same behaviour. systemctl restart dovecot rsyslog ----- this gets a working state systemctl restart rsyslog ------------- this restarts syslog other processes

Good morning, Here is the log, I don't see anything unusual. I took the same tinc binary and tried on two other machines and it works fine - binds to 655/UDP without issues: udp UNCONN 0 0 *:655 *:* users:(("tincd",18872,7)) tcp LISTEN 0 3 *:655 *:* users:(("tincd",18872,6)) Petr On Thu, Jul 14, 2016 at 12:18 AM, Rob Townley <rob.townley at gmail....

...t 05:10, Petr Man <petr at madnetwork.org> wrote: > >> Good morning, >> >> Here is the log, I don't see anything unusual. I took the same tinc >> binary and tried on two other machines and it works fine - binds to 655/UDP >> without issues: >> udp UNCONN 0 0 *:655 >> *:* users:(("tincd",18872,7)) >> tcp LISTEN 0 3 *:655 >> *:* users:(("tincd",18872,6)) >> >> >> Petr >> >> On Thu, Jul 14, 2016 at 12:18 AM, Rob...