I thought the 15-20 delay was after starting the subagent, not the 
snmpd...

About starting the subagent manually, I meant:
> /usr/sbin/hpiSubagent | tee subagent.log (to capture the output)

Saludos,

        --Renier

"McCrory, Hugh" <[EMAIL PROTECTED]> wrote on 05/02/2007 10:23:46 AM:

> 
> When we start the openhpi-subagent in a separate window the output is 
...
> 
> [EMAIL PROTECTED] init.d]# /etc/init.d/snmpd start
> 
> 
> <----------------------------  15-20 mins between these two 
> messages. 
> 
> Starting snmpd: [  OK  ]
> 
> [EMAIL PROTECTED] init.d]# ./openhpi-subagent start
> 
> Starting up HPI SNMP sub-agent daemon:
> 
> 
> BTW.   This subject in this email thread is a mis-nomer, in that 
> this is NOT an Installation issue, rather it is a openhpi-subagent 
> start-up issue.
> 
> Thanks,
> Hugh
> 
> 
> 
> -----Original Message-----
> From: Renier Morales [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 01, 2007 7:08 PM
> To: McCrory, Hugh
> Cc: [email protected]
> Subject: RE: FW: [Openhpi-devel] Installation Issue
> 
> 
> 
> The 15 minute delay may just be the subagent initializing depending 
> on the system/hardware that HPI needs to communicate with. I'm 
> verifying this directly with the developer. 
> 
> The more pressing problem here is that the subagent is shutting 
> down. Could you start the subagent manually in a separate window and
> grab the output from there? 
> 
> Saludos,
> 
>        --Renier 
> 
> "McCrory, Hugh" <[EMAIL PROTECTED]> wrote on 05/01/2007 12:18:06 PM:
> 
> > Renier, 
> > The output of the ps command just shows the openhpi process  and not
> > the openhpi-subagent process
> > [EMAIL PROTECTED] init.d]# ps -e | grep -i hpi
> >  6665 pts/3    00:01:36 openhpid
> > 
> > Is there an example configuration for openhpi-subagent that should 
> > go into the snmpd.conf file ?
> > I'm guessing here, but it appears from the log below that the 
> > subAgent attempts to generates a trap but may not be configured 
> > correctly in the snmpd.conf file. 
> > 
> > 
> > Thanks,
> > Hugh
> > 
> > 
> > -----Original Message-----
> > From: Renier Morales [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 30, 2007 5:59 PM
> > To: McCrory, Hugh
> > Cc: [email protected]
> > Subject: Re: FW: [Openhpi-devel] Installation Issue
> > 
> > 
> > 
> > When it "stops", what does the following command say? 
> > 
> > ps -e | grep -i hpi 
> > 
> > Saludos,
> > 
> >        --Renier
> > 
> > 
> > "McCrory, Hugh" <[EMAIL PROTECTED]> wrote on 04/27/2007 05:39:01 
PM:
> > 
> > > Renier, 
> > >     I've had a look at the /var/log/messages file and see the 
> > > following output ( during this 15 mins period ). 
> > > It appears to be accessing HPI api OK  but the subAgent appears to 
> > > stop    ..... see the end of this log file ( in bold ) 
> > > This is when the [O.K] messages is dsiplayed) 
> > > 
> > > Thanks, 
> > > Hugh 
> > > 
> > > Apr 26 22:10:36 arcturus hpiSubagent[9492]: Starting $Id: 
> > > hpiSubagent.c 5417 2005-11-14 16:18:37Z ddearauj $
> > > Apr 26 22:10:36 arcturus hpiSubagent: Starting $Id: hpiSubagent.c 
> > > 5417 2005-11-14 16:18:37Z ddearauj $
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:36 arcturus openhpid: DEBUG: (ipmi.cpp, 2265, 
> > > ipmidirect discover_resources)
> > > Apr 26 22:10:36 arcturus hpiSubagent: Hpi Version 131329 
Implemented.
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent: saHpiSessionOpen 
> > > returns with SessionId 23
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent: 
> > > subcsribe_all_sessions() SUCCEEDED!!!!!!!
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:36 arcturus hpiSubagent: saHpiDiscover Success!
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiAdministration, called
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_scalar_saHpiDiscover, called
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent: 
> init_saHpiDomainInfoTable
> > > Apr 26 22:10:36 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: 
> > > initialize_table_saHpiDomainInfoActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiDomainAlarmTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: 
> > > initialize_table_saHpiDomainAlarmActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiDomainReferenceTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiDomainReferenceTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiDomainReferenceActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiResourceTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiResourceTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: 
> > > initialize_table_saHpiResourceActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > init_saHpiRdrTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: 
> initialize_table_saHpiRdrTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiRdrActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: init_saHpiCtrlDigitalTable, 
called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiCtrlDigitalTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiCtrlDigitalActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiCtrlDiscreteTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent:
> > > Apr 26 22:10:37 arcturus hpiSubagent: 
> > > initialize_table_saHpiCtrlDiscreteActiveEntries, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > init_saHpiCtrlAnalogTable, called
> > > Apr 26 22:10:37 arcturus hpiSubagent: hpiSubagent: 
> > > initialize_table_saHpiCtrlAnalogTable, called 
> > > .... 
> > > .... 
> > > and so on .... 
> > > ... 
> > > .... 
> > > Apr 26 22:24:22 arcturus hpiSubagent: SAHPI_ET_SENSOR: rv [0]
> > > Apr 26 22:24:22 arcturus hpiSubagent:         Sensor Type: 
> [ENTITY_PRESENCE]
> > > Apr 26 22:24:22 arcturus hpiSubagent:
> > > Apr 26 22:24:22 arcturus hpiSubagent:         Entry ID [12064]
> > > Apr 26 22:24:22 arcturus hpiSubagent:         EventType [2]
> > > Apr 26 22:24:22 arcturus hpiSubagent:         rv [0]
> > > Apr 26 22:24:22 arcturus hpiSubagent: SAHPI_ET_SENSOR: rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Sensor Type: [MEMORY]
> > > Apr 26 22:24:23 arcturus hpiSubagent:
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Entry ID [12084]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         EventType [2]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent: SAHPI_ET_SENSOR: rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Sensor Type: [MEMORY]
> > > Apr 26 22:24:23 arcturus hpiSubagent:
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Entry ID [12104]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         EventType [7]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent: SAHPI_ET_OEM: rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent:
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Entry ID [-2]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         EventType [2]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent: SAHPI_ET_SENSOR: rv [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Sensor Type: 
> > > [SYSTEM_ACPI_POWER_STATE]
> > > Apr 26 22:24:23 arcturus hpiSubagent:
> > > Apr 26 22:24:23 arcturus hpiSubagent: populate_saHpiEventLog
> > > Apr 26 22:24:23 arcturus hpiSubagent: 
> > ***************************************
> > > Apr 26 22:24:23 arcturus hpiSubagent: 
> > ***************************************
> > > Apr 26 22:24:23 arcturus hpiSubagent:  EVENT LOG TABLES
> > > Apr 26 22:24:23 arcturus hpiSubagent: event_log_clear: done
> > > Apr 26 22:24:23 arcturus hpiSubagent:         Entry ID [0]
> > > Apr 26 22:24:23 arcturus hpiSubagent:         EventType [0]
> > > Apr 26 22:24:24 arcturus hpiSubagent:         rv [-1011]
> > > Apr 26 22:24:24 arcturus hpiSubagent: Released the lock, 0x9401018 -
> > > lockcount 0
> > > Apr 26 22:24:24 arcturus hpiSubagent: hpiSubagent: init_alarm: Exit
> > > Apr 26 22:24:24 arcturus hpiSubagent: hpiSubagent: do_alarm: Entry
> > > Apr 26 22:24:24 arcturus hpiSubagent: hpiSubagent: 
> > > event_log_info_update called
> > > Apr 26 22:24:24 arcturus hpiSubagent: hpiSubagent: 
> > > SA_ERR_HPI_CAPABILITY: event_log_info_update Failed: rv = -1020
> > > Apr 26 22:24:24 arcturus last message repeated 3 times
> > > Apr 26 22:24:24 arcturus hpiSubagent: hpiSubagent: do_alarm: Exit
> > > Apr 26 22:24:24 arcturus openhpi-subagent: hpiSubagent startup 
succeeded
> > > Apr 26 22:25:37 arcturus openhpid: DEBUG: (ipmi.cpp, 2265, 
> > > ipmidirect discover_resources) 
> > > 
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From: McCrory, Hugh 
> > > Sent: Friday, April 27, 2007 5:16 PM
> > > To: '[email protected]'; Prakash, Amit
> > > Subject: RE: [Openhpi-devel] Installation Issue
> > 
> > > Renier, 
> > >      I'm working with Prakash, let me take a step back and clarify 
> > > what he is asking.
> > > Basically we are havng difficulty configuring the openhpi-subAgent 
> > > in the snmpd.conf file. 
> > > 
> > > We have not found documentation that clearly describes the 
> > > configuration options that should be configured in the snmpd.conf 
file.
> > > The OpenHPI-subAgent does start up  and displays the  message "
> > > Starting up HPI SNMP sub-agent daemon:"   but then during the 
> next15-20mins 
> > > there are alot of hpiSubAgent messages written to the 
> > > /var/log/messages files  and then the subAgent appears to stop ( 
> > > after approx the 15-20mins) . 
> > > 
> > > We are speculalting that this happening because we do not the have 
> > > the openHPI-SubAgent configured correctly in the snmpd.conf file. 
> > > 
> > > What he is seeing is when we start the openhpi-subagent is ...
> > > [EMAIL PROTECTED] init.d]# ./openhpi-subagent start 
> > > Starting up HPI SNMP sub-agent daemon:: 
> > > 
> > > 
> > > <----------------------------  15-20 mins between these two 
> > > messages. 
> > > 
> > > [  OK  ] 
> > > 
> > > 
> > > 
> > > Thanks, 
> > > Hugh 
> > > 
> > > 
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to