Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - server_busy: (4 Items)
   
server_busy  

I'm getting "server_busy" entries in the log file.  Upon looking at the source of qnet, may I suggest that more 
information be added to the qnet_error call in the function kif_server/nbound_connect_fail().  Information like the rpid
 and such, anything that would help figure out what is the source of that error.

Thanks.

Re: server_busy  
Have to admit...  Being asked to be MORE verbose with QNET logging is not something that we normally see :).

    We'll see if we can add something more.  I've filed a PR (56677) to track the request.
Re: server_busy  
> Have to admit...  Being asked to be MORE verbose with QNET logging is not 

I'll take that as a compliment, LOL!

> something that we normally see :).
> 
>     We'll see if we can add something more.  I've filed a PR (56677) to track 
> the request.

Any tip on what this log entry actually mean?


RE: server_busy  

> Any tip on what this log entry actually mean?

A packet arrived which was not expected, given
the state of the qnet kif data structures.  Since
this rxd packet was "connect fail" message, this is
an error report about a previous error.  You can 
have many levels of this sort of thing (perhaps 
too many?)

Messages like these are often more useful in
context, when you are trying to diagnose a 
problem - they can give you a clue about what
might be happening.

Are you experiencing any other problems with
qnet?  Timeouts?  Reply-blocked clients?

Really, to properly diagnose a system, you need
complete qnet error logs for both nodes involved,
hopefully with their system times reasonably
synchronized, and a description of what event 
occurred, and when.

If qnet is polluting your sloginfo, there is an
option to turn off slogging.  You can still dump
it's internal event ringbuffer, which reminds me,
I should really increase it's size sometime - I
think it's a whole 8K right now  :-)

--
aboyd