BOARDBUSY messages in logs 🔗 link

I am still seeing BOARDBUSY messages in my logs like the following:
larrd-status.log:
2005-03-04 11:36:11 Tried to down BOARDBUSY: Invalid argument
 
I've narrowed it down to the following code in hobbitd_channel.c, but I
don't know how to fix it.
My log files don't seem to be getting updated properly and I'm wondering if
this has anything to do with it.  I'm on Fedora.
 
 
                        /*
                         * Let master know we got it by downing BOARDBUSY.
                         * This should not block, since BOARDBUSY is upped
                         * by the master just before he ups GOCLIENT.
                         */
                        do {
                                s.sem_num = BOARDBUSY; s.sem_op  = -1;
s.sem_flg = IPC_NOWAIT;
                                n = semop(channel->semid, &s, 1);
                        } while ((n == -1) && (errno == EINTR));
                        if (n == -1) {
                                errprintf("Tried to down BOARDBUSY: %s\n",
strerror(errno));
                        }

Can anyone provide any assistance?
 
Thanks

David Stuffle

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.

On Fri, Mar 04, 2005 at 12:00:22PM -0500, Stuffle, David wrote:

This one is harmless, and happens when Hobbit shuts down. The master
daemon (hobbitd) sends a shutdown-message to all of the
hobbitd_channel worker modules, then marks the shared memory segments
used for communication with the modules for deletion. Depending on how
fast the workers respond, they may try to access the shared memory
segment when it has been deleted, and you'll get this message.

Which log files, specifically ? The only files that Hobbit normally
updates while running are the historical logs in the data/hist/ and
data/histlogs/ directories - and they only get updated when there are
status changes.


Regards,
Henrik

I see, thanks.  My main goal is trying to get the mail acks to work.  That's
why I was digging through the log files.

Anyway, my mail acks are only sometimes working.  I haven't been able to
find a pattern to it yet so I will need to investigate more.  I do know
though that adding MESSAGE=something to the subject line when replying to an
email alert doesn't work.  Should that work, or am I misunderstanding
something?  I get this in the acklog (all one line):

 1109963670  126510  30  126510  np_filename_not_used  zenmaster.memory  red
~~~~~~~~~~~~~~\nAcked by: "Stuffle, David"  user-4d88f4a4f51e@xymon.invalid

Several times that I acked, I get nothing at all in the acklog.
Thanks,
David

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: Friday, March 04, 2005 12:13 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BOARDBUSY messages in logs


On Fri, Mar 04, 2005 at 12:00:22PM -0500, Stuffle, David wrote:

This one is harmless, and happens when Hobbit shuts down. The master daemon
(hobbitd) sends a shutdown-message to all of the hobbitd_channel worker
modules, then marks the shared memory segments used for communication with
the modules for deletion. Depending on how fast the workers respond, they
may try to access the shared memory segment when it has been deleted, and
you'll get this message.

Which log files, specifically ? The only files that Hobbit normally updates
while running are the historical logs in the data/hist/ and data/histlogs/
directories - and they only get updated when there are status changes.


Regards,
Henrik


This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.

On Fri, Mar 04, 2005 at 02:36:53PM -0500, Stuffle, David wrote:

If you are using the hobbit-mailack tool, then keep the subject line
as-is; at most, add a DELAY=N for the number of minutes the
acknowledgement is for.

You can add a message that will be saved with the acknowledgment: the
first non-blank line of the acknowledgment e-mail is saved with the
ack in Hobbit. Does BB's mailack script support a MESSAGE=... in the
subject ? Then perhaps I should teach Hobbit to handle that as well.


Regards,
Henrik

On Fri, Mar 04, 2005 at 11:13:39PM, Henrik Stoerner wrote:

delay 100 msg This is a test mesg

So anything after the word 'msg' considered as message in BB's mailack

-- 

Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"It is not the strongest of the species that survives, not the most intelligent, but
 the one most responsive to change."    - Charles Darwin