Daemon terminates..

Sharad Chandra <[email protected]>
Newsgroups gmane.network.net-snmp.user
Organization Niksun India
Message-ID <[email protected]>
Hi,

I am coding a module which gives information about storage devices.
I made changes in storageStatusTable_data_access.c.
it works fine as i start the storageStatusTable but when it started updating 
the Table after STORAGESTATUSTABLE_CACHE_TIMEOUT seconds it turminates 
without saying any errors. The outputs ...

[root@/home/vcr/fm/snmp/storageStatusTable]# ./storageStatusTable -f -Dstorage
NET-SNMP version 5.2.3 AgentX subagent connected
storageStatusTable:init_storageStatusTable: Registering storageStatusTable as 
a mibs-for-dummies table.
Logical volume 1 does not exist.
storage cache init done
storageStatusTable:storageIndex: new storageIndex 1 for V3VHL32A0
storageStatusTable:storageIndex: new storageIndex 2 for V3VRGPZA0
storageStatusTable:storageIndex: new storageIndex 3 for V3VPA15A0
storageStatusTable:storageIndex: new storageIndex 4 for V3VP66DA0
storageStatusTable:storageIndex: new storageIndex 5 for
Logical volume 1 does not exist.
storage cache init done
[root@/home/vcr/fm/snmp/storageStatusTable]#


while at the snmpwalk side...

[sharad@/usr/home/sharad]$ snmpwalk -v2c -c public app210.in.niksun.com
NIKSUN-HEALTH-TRAPS::storageIndex.1 = INTEGER: 1
NIKSUN-HEALTH-TRAPS::storageIndex.2 = INTEGER: 2
NIKSUN-HEALTH-TRAPS::storageIndex.3 = INTEGER: 3
NIKSUN-HEALTH-TRAPS::storageIndex.4 = INTEGER: 4
NIKSUN-HEALTH-TRAPS::storageIndex.5 = INTEGER: 5
NIKSUN-HEALTH-TRAPS::storageName.1 = STRING: Physical Drive 0:0 Serial No. 
V3VHL32A0
NIKSUN-HEALTH-TRAPS::storageName.2 = STRING: Physical Drive 0:2 Serial No. 
V3VRGPZA0
NIKSUN-HEALTH-TRAPS::storageName.3 = STRING: Physical Drive 0:4 Serial No. 
V3VPA15A0
NIKSUN-HEALTH-TRAPS::storageName.4 = STRING: Physical Drive 0:5 Serial No. 
V3VP66DA0
NIKSUN-HEALTH-TRAPS::storageName.5 = STRING: Logical volume 0 MegaRAID SCSI 
320-1 RAID5 205.10 GB
NIKSUN-HEALTH-TRAPS::storageId.1 = STRING: 0:0
NIKSUN-HEALTH-TRAPS::storageId.2 = STRING: 0:2
NIKSUN-HEALTH-TRAPS::storageId.3 = STRING: 0:4
NIKSUN-HEALTH-TRAPS::storageId.4 = STRING: 0:5
NIKSUN-HEALTH-TRAPS::storageId.5 = STRING: 0
NIKSUN-HEALTH-TRAPS::storageType.1 = INTEGER: raid(2)
NIKSUN-HEALTH-TRAPS::storageType.2 = INTEGER: raid(2)
NIKSUN-HEALTH-TRAPS::storageType.3 = INTEGER: raid(2)
NIKSUN-HEALTH-TRAPS::storageType.4 = INTEGER: raid(2)
NIKSUN-HEALTH-TRAPS::storageType.5 = INTEGER: raid(2)
NIKSUN-HEALTH-TRAPS::storageStatusString.1 = STRING: online
NIKSUN-HEALTH-TRAPS::storageStatusString.2 = STRING: online
NIKSUN-HEALTH-TRAPS::storageStatusString.3 = STRING: online
NIKSUN-HEALTH-TRAPS::storageStatusString.4 = STRING: online
NIKSUN-HEALTH-TRAPS::storageStatusString.5 = STRING: optimal
NIKSUN-HEALTH-TRAPS::storageStatus.1 = INTEGER: ok(3)
NIKSUN-HEALTH-TRAPS::storageStatus.2 = INTEGER: ok(3)
NIKSUN-HEALTH-TRAPS::storageStatus.3 = INTEGER: ok(3)
NIKSUN-HEALTH-TRAPS::storageStatus.4 = INTEGER: ok(3)
NIKSUN-HEALTH-TRAPS::storageStatus.5 = INTEGER: ok(3)
[sharad@/usr/home/sharad]$ snmpwalk -v2c -c public app210.in.niksun.com 
storageStatusTable
Error in packet.
Reason: (genError) A general failure occured
Failed object: NIKSUN-HEALTH-TRAPS::storageStatusTable

NIKSUN-HEALTH-TRAPS::storageStatusTable = No Such Object available on this 
agent at this OID

What could be the reason?

Thanks 
Sharad Chandra

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.