Bug 158897 - 'master' agentx socket does not close after master agent closes
'master' agentx socket does not close after master agent closes
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: net-snmp (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-26 13:11 EDT by W Raul S
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 5.2.1.2-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-23 09:39:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description W Raul S 2005-05-26 13:11:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
After the nstAgentModuleObject sub-agentX disconnects from succesful GETs and SETs, the /var/agentx/master socket does not close after the master agent shuts down. The agents are shutdown using Ctrl-C. The non-closing socket indicates an agentx connection error in the master agent. After the master agent is started and shutdown, the socket closes correctly. 

The nstAgentModuleObject can be found here:
http://www.net-snmp.org/tutorial/tutorial-5/toolkit/index.html

The master agent produces no error output on connections or shutdown.

Version-Release number of selected component (if applicable):
net-snmp-5.2.1-12

How reproducible:
Always

Steps to Reproduce:
1. Start /usr/sbin/snmpd -f -Lo
2. Start example-demon 
3. ls /var/agentx
4. Ctl-C example-demon
5. Ctl-C snmpd
6. ls /var/agentx 

Actual Results:  ~ ls /var/agentx
master

Expected Results:  ~ ls /var/agentx

(No socket should exist)

Additional info:
Comment 1 Radek Vokal 2005-08-23 09:39:49 EDT
Fixed in rawhide vesrion of net-snmp

Note You need to log in before you can comment on or make changes to this bug.