Hi,
In oh_ssl.c line 506, select() system call is used with last parameter
as NULL when timeout value is zero. In Linux man page it is clearly
stated that "If timeout is NULL (no timeout), select() can block
indefinitely." and hence the thread was blocking and openhpid went in
hung state. I guess Openhpi was tested in HP UX (where select() allows
NULL as timeout value).
Thus, I filled the timeval structure with 0 values and passed the
address of this variable to select() as below
tv.tv_sec = 0;
tv.tv_usec = 0;
err = select(fd + 1, &readfds, &writefds, NULL,
&tv);
Now, when I am running hpitree utility it exits without showing all the
fields. It shows only a few fields. Can someone suggest what would be
the most appropriate way to call select() in the context.
Regards
Mukul
-----Original Message-----
From: Bishop, Michael (ISB Linux/Telco) [mailto:[email protected]]
Sent: Thursday, May 13, 2010 8:57 PM
To: AGRAWAL MUKUL-a24103
Cc: [email protected]
Subject: RE: [Openhpi-devel] openhpid hangs with ilo2 plugin
Mukul -
Thanks for tracing this issue to its root cause. When you find out the
root cause, please submit a ticket.
Regards,
Michael Bishop
Enterprise Servers and Storage (ISB Linux/Telco) Hewlett-Packard Company
3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42 Fort Collins, CO
80528-9599
Phone: 970-898-4393
E-Mail: [email protected]
> -----Original Message-----
> From: AGRAWAL MUKUL-a24103 [mailto:[email protected]]
> Sent: Thursday, May 13, 2010 6:20 AM
> To: Bishop, Michael (ISB Linux/Telco)
> Cc: [email protected]
> Subject: RE: [Openhpi-devel] openhpid hangs with ilo2 plugin
>
>
> Hi,
>
> I am able to reproduce the issue with the top-of-trunk OpenHPI ( taken
> from
> http://openhpi.svn.sourceforge.net/viewvc/openhpi/openhpi/trunk/).
>
> I am not sure where this issue belong. It can be OpenHPI
> infrastructure,
> iLO2 plugin or hpitree utility itself (which I used to simulate). As
> mentioned earlier I found that, in one particular instance a thread is
> calling oh_get_handler (which locks the handler->lock mutex) but is
> not calling oh_release_handler (which unlocks this mutex). I am
> investigating futher to find the exact place where it is originated.
>
> Regards
> Mukul
> -----Original Message-----
> From: Bishop, Michael (ISB Linux/Telco) [mailto:[email protected]]
> Sent: Wednesday, May 12, 2010 9:11 PM
> To: AGRAWAL MUKUL-a24103
> Cc: [email protected]
> Subject: RE: [Openhpi-devel] openhpid hangs with ilo2 plugin
>
> Mukal -
>
> Please check out the OpenHPI top-of-trunk - and see if the problem is
> reproducible there. If you are able to reproduce the issue - please
> submit a ticket for this issue against the OpenHPI project at:
> https://sourceforge.net/tracker/?group_id=71730
>
> Also, from your analysis - are you indicating this to be an OpenHPI
> infrastructure issue - or rather an issue with the iLO2 plugin itself?
>
> Thanks.
>
> --michael
>
> Regards,
> Michael Bishop
> Enterprise Servers and Storage (ISB Linux/Telco) Hewlett-Packard
> Company
> 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42 Fort Collins, CO
> 80528-9599
> Phone: 970-898-4393
> E-Mail: [email protected]
>
>
>
>
> > -----Original Message-----
> > From: AGRAWAL MUKUL-a24103 [mailto:[email protected]]
> > Sent: Wednesday, May 12, 2010 4:43 AM
> > To: Anton Pak; [email protected]
> > Subject: Re: [Openhpi-devel] openhpid hangs with ilo2 plugin
> >
> >
> >
> > Hi,
> >
> > I am seeing this issue in openhpi-2.14.1.
> >
> > Mukul
> >
> > -----Original Message-----
> > From: Anton Pak [mailto:[email protected]]
> > Sent: Wednesday, May 12, 2010 4:09 PM
> > To: [email protected]
> > Cc: AGRAWAL MUKUL-a24103
> > Subject: Re: [Openhpi-devel] openhpid hangs with ilo2 plugin
> >
> > Mukul,
> >
> > Are you able to reproduce the issue with top of trunk
> OpenHPI version?
> >
> > Anton Pak
> >
> > On Wed, 12 May 2010 14:29:26 +0400, AGRAWAL MUKUL-a24103
> > <[email protected]> wrote:
> >
> > > Hi,
> > > I am using OpenHPI with ilo2 plugin. When I use hpitree
> > multiple times
> >
> > > openhpid hangs. On investigation I found that somehow the
> mutex is
> > > getting locked for a handler and never getting unlocked.
> > > Specifically,
> > > In oh_get_handler ()
> > > g_static_rec_mutex_lock(&handler->lock);
> > > gets called. Thus, a thread calling oh_get_handler()
> should ideally
> > > call
> > > oh_release_handler() which unlocks this mutex. However, on
> > running the
> >
> > > hpitree multiple times I found that there is an instance when
> > > oh_release_handle is not at all called. Thus, multiple
> > threads wait on
> >
> > > this mutex and openhpid hangs.
> > > Is anyone aware of the problem? If you have any more
> details please
> > > let me know.
> > > Regards
> > > Mukul
> >
> >
> > --------------------------------------------------------------
> > ----------------
> >
> > _______________________________________________
> > Openhpi-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
> >
>
------------------------------------------------------------------------------
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
