UNIX Socket FAQ

santoshkumar

Member

Registered: 2007-08-21

Posts: 53

minilogd hogs my application ports when restarted syslog service,

minilogd hogs my application ports(2050/2052/2054) when restarted syslog service, causing my application throwing error port already in use (Could not bind to specified port (error 98 Address already in use))

tcp        0      0 127.0.0.1:2050              0.0.0.0:*                   LISTEN      2244/minilogd 
tcp        0      0 127.0.0.1:2052              0.0.0.0:*                   LISTEN      2244/minilogd 
tcp        0      0 127.0.0.1:2054              0.0.0.0:*                   LISTEN      2244/minilogd 

when syslog service is stopped  or start minilogd automatically starts.

Is there way to disable minilogd in system or untie with syslog deamon service

I have to reboot or pkill minilogd in order to relinquish the ports back from minilogd.

Last edited by santoshkumar (2015-01-06 08:07 AM)

RobSeace

Administrator

From: Boston, MA

Registered: 2002-06-12

Posts: 3,839

Website

Re: minilogd hogs my application ports when restarted syslog service,

Odd...  I've never even heard of minilogd before...  But, searching around,  it's apparently something added in later RHEL/CentOS releases of initscripts, which is basically a lightweight replacement for syslogd which is supposed to just hold onto incoming messages in memory until the real syslogd starts up, then hand them over to it and exit...  I have no clue why it would be listening on any TCP ports, though!  Based on code I can find online for it, it sure looks to me like it only opens the standard syslog "/dev/log" Unix domain socket...  And, it's only supposed to be running if the real syslogd is NOT running...  So, I have no idea WTF is going on with your system!