Displaying 4 results from an estimated 4 matches for "66655".
Did you mean:
6655
2018 Sep 06
6
rsyslog listening on high port
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
OpenGroupware Developer <http://www.opengroupware.us/>
2018 Sep 07
1
rsyslog listening on high port
...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?
> You might want to try running:
> lsof -i -P | grep LISTEN | grep :51427
> to determine what process is actually listening to that port.
That is what is strange; lsof does *not* see the port as listening,
but it is visible if I search by inode [and it is clearly rsyslogd -
but...
2018 Sep 06
0
rsyslog listening on high port
...gd 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,
You might want to try running:
lsof -i -P | grep LISTEN | grep :51427
to determine what process is actually listening to that port.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever
just stops by to say &...
2018 Sep 07
0
rsyslog listening on high port
...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?
The 51427 is the ephemeral port on the 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 lo...