Hi Preeti, Thanks for trying it with OpenHPI-3.1. PLease let's know results. We have not seen this problem earlier. If it is found in 3.1, then we will need to raise a bug.
Mohan On Thu, 2012-08-09 at 12:48 -0400, Preeti Sharma wrote: > Hi Anton, > I am using OA_SOAP Plugin. I will try OpenHPI 3.1 and will let you know. > > > I am pasting below threads information: > > Loaded symbols for /lib64/libresolv.so.2 > > warning: no loadable sections found in added symbol-file system-supplied DSO > at 0x2aaaaaac7000 > 0x00002aaaac238c0b in accept () from /lib64/libpthread.so.0 > (gdb) set print thread-events on > (gdb) info threads > 13 Thread 0x40a00940 (LWP 25542) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 12 Thread 0x41401940 (LWP 25543) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 11 Thread 0x41e02940 (LWP 25544) 0x00002aaaac235f59 in > pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 > 10 Thread 0x42803940 (LWP 25547) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 9 Thread 0x43204940 (LWP 25548) 0x00002aaaac971221 in nanosleep () > from /lib64/libc.so.6 > 8 Thread 0x45007940 (LWP 25653) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 7 Thread 0x45a08940 (LWP 25654) 0x00002aaaac971221 in nanosleep () > from /lib64/libc.so.6 > 6 Thread 0x43c05940 (LWP 25771) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 5 Thread 0x44606940 (LWP 25773) 0x00002aaaac235f59 in > pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 > 4 Thread 0x46409940 (LWP 25777) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > 3 Thread 0x46e0a940 (LWP 25778) 0x00002aaaac235f59 in > pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 > 2 Thread 0x4780b940 (LWP 26344) 0x00002aaaac238594 in __lll_lock_wait () > from /lib64/libpthread.so.0 > * 1 Thread 0x2aaaace3a360 (LWP 25525) 0x00002aaaac238c0b in accept () > from /lib64/libpthread.so.0 > (gdb) thread 25525 > Thread ID 25525 not known. > (gdb) thread 25542 > Thread ID 25542 not known. > (gdb) thread 25543 > Thread ID 25543 not known. > (gdb) thread 25778 > Thread ID 25778 not known. > (gdb) c > Continuing. > > Program received signal SIGINT, Interrupt. > 0x00002aaaac238c0b in accept () from /lib64/libpthread.so.0 > (gdb) bt > #0 0x00002aaaac238c0b in accept () from /lib64/libpthread.so.0 > #1 0x00002aaaab6b9666 in sstrmsock::Accept (this=0x6adb80) at > strmsock.cpp:381 > #2 0x0000000000407ceb in main (argc=3, argv=0x7fffffffe978) > at openhpid.cpp:320 > (gdb) c > Continuing. > > Regards, > Preeti. > > -----Original Message----- > From: Anton Pak [mailto:[email protected]] > Sent: Thursday, August 09, 2012 11:32 AM > To: [email protected]; Preeti Sharma > Cc: Jay Katti > Subject: Re: [Openhpi-devel] saHpiDiscover gets stuck in OpenHPI Daemon is > running for long > > Hello Preeti, > > Could you show what other threads in openhpid are doing? > What is the plug-in? > Could you reproduce with 3.1 or trunk? > > Anton Pak > > On Thu, 09 Aug 2012 18:45:23 +0400, Preeti Sharma <[email protected]> > wrote: > > > Hi, > > When Daemon is stuck, I attached to the Daemon using gdb traces are here: > > > > Program received signal SIGINT, Interrupt. > > 0x00002aaaac238c0b in accept () from /lib64/libpthread.so.0 > > (gdb) bt > > #0 0x00002aaaac238c0b in accept () from /lib64/libpthread.so.0 > > #1 0x00002aaaab6b9666 in sstrmsock::Accept (this=0x6adb80) at > > strmsock.cpp:381 > > #2 0x0000000000407ceb in main (argc=3, argv=0x7fffffffe978) > > at openhpid.cpp:320 > > > > > > Client gdb trace when Daemon is stuck: > > [root@rm1sgi2 preeti]# gdb --args hpievents -t BLOCK > > GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-37.el5_7.1) > > Copyright (C) 2009 Free Software Foundation, Inc. > > License GPLv3+: GNU GPL version 3 or later > > <http://gnu.org/licenses/gpl.html> > > This is free software: you are free to change and redistribute it. > > There is NO WARRANTY, to the extent permitted by law. Type "show > > copying" > > and "show warranty" for details. > > This GDB was configured as "x86_64-redhat-linux-gnu". > > For bug reporting instructions, please see: > > <http://www.gnu.org/software/gdb/bugs/>... > > Reading symbols from /home/rm/preeti/hpievents...done. > > (gdb) r > > Starting program: /home/rm/preeti/hpievents -t BLOCK > > warning: no loadable sections found in added symbol-file system-supplied > > DSO at 0x2aaaaaac7000 > > [Thread debugging using libthread_db enabled] > > /home/rm/preeti/hpievents (rev 7189) - This program came with OpenHPI > > 2.15.1 > > SAF HPI Version B.03.02 > > > > ************** timeout:[-1] -1**************** > > oh_client_conf.c:504:load_client_config: Done processing conf file. > > Number of parse errors:0 > > oh_client_session.cpp:105:oh_create_connx: Client instance created > > safhpi.c:54:saHpiSessionOpen: saHpiSessionOpen DomainId [0] > > safhpi.c:77:saHpiSessionOpen: Created session 3 for domain 0 > > > > > > Program received signal SIGINT, Interrupt. > > 0x00002aaaabb9a9b0 in __read_nocancel () from /lib64/libpthread.so.0 > > (gdb) bt > > #0 0x00002aaaabb9a9b0 in __read_nocancel () from /lib64/libpthread.so.0 > > #1 0x00002aaaac332aae in strmsock::ReadMsg (this=0x6064e0, > > data=0x7ffffffee070 "\003") at strmsock.cpp:158 > > #2 0x00002aaaaacce460 in saHpiDiscover (SessionId=1) at > > oh_client.cpp:369 > > #3 0x0000000000401004 in main (argc=3, argv=0x7fffffffe998) at > > hpievents.c:133 > > (gdb) > > > > If I restart the Daemon problem goes off. What is happening here any > > idea? > > > > Regards, > > Preeti > > From: Preeti Sharma > > Sent: Wednesday, August 08, 2012 5:28 PM > > To: '[email protected]' > > Cc: Jay Katti > > Subject: [Openhpi-devel] saHpiDiscover gets stuck in OpenHPI Daemon is > > running for long > > > > Hi, > > I am facing the issue with OpenHPI Daemon. I have a client application > > which discovers (via a call to saHpiDiscover) for resources on regular > > basis though call to saHpiDiscover gets stuck if OpenHPI Daemon has been > > running for 4-5 days or more. If I restart the Daemon, stuck application > > starts working fine. I am using release openhpi-2.15.1. > > > > Regards, > > Preeti > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Openhpi-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openhpi-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
