Accepted new SMUX inet socket connection on fd=14

[kramJ]

/var/tmp/snmpdv3.log is continually being written to as follows:

04/22/05 07:56:18 AM - Accepted new SMUX inet socket connection on fd=14 from 127.0.0.1 port 49468.
04/22/05 07:56:19 AM - EOF recieved on SMUX TCP fd 14 .
04/22/05 07:56:19 AM - Closing SMUX connection, fd=14.
04/22/05 07:56:19 AM - Address 127.0.0.1 port 49468.
04/22/05 07:56:24 AM - Accepted new SMUX inet socket connection on fd=14 from 127.0.0.1 port 49469.
04/22/05 07:56:24 AM - EOF recieved on SMUX TCP fd 14 .
04/22/05 07:56:24 AM - Closing SMUX connection, fd=14.
04/22/05 07:56:24 AM - Address 127.0.0.1 port 49469.
04/22/05 07:56:29 AM - Accepted new SMUX inet socket connection on fd=14 from 127.0.0.1 port 49470.
04/22/05 07:56:29 AM - EOF recieved on SMUX TCP fd 14 .
04/22/05 07:56:29 AM - Closing SMUX connection, fd=14.
04/22/05 07:56:29 AM - Address 127.0.0.1 port 49470.
04/22/05 07:56:34 AM - Accepted new SMUX inet socket connection on fd=14 from 127.0.0.1 port 49471.
04/22/05 07:56:34 AM - EOF recieved on SMUX TCP fd 14 .
04/22/05 07:56:34 AM - Closing SMUX connection, fd=14.
04/22/05 07:56:34 AM - Address 127.0.0.1 port 49471.

It's filling up the file system. Anyone know what it is? Thanks.

 

[p5wizard]

If you do not use SNMP, you can stop the snmp daemons

stopsrc -s snmpd
stopsrc -s snmpmibd

then cleanup the SNMP log file(s) from /var/tmp

> /var/tmp/snmpdv3.log
> /var/tmp/snmpmibd.log

But this is a symptomatic approach. Doesn't take away the source of the continuously entering connections...

See if they reappear when restarting the deamons:

startsrc -s snmpd
startsrc -s snmpmibd

The address 127.0.0.1 tells me the source is on the same server. Perhaps you need to reboot?