[Xymon] semop failed, Invalid argument - Ubuntu

Thu Sep 17 10:04:58 CEST 2020

Hi

One other thing I’ve noticed, when it happens, xymond_channels have failed. I am running the history channel with debug logging too, this is the log for the same period:

18838 2020-09-17 01:21:44.225110 startpos 5009227, fillpos 5009227, endpos -1
2020-09-17 01:21:44.226297 Will not update /home/xymon/data/hist/qweaurap01.wupdate - color unchanged (green)
18838 2020-09-17 01:21:44.226313 Want msg 9897, startpos 5009227, fillpos 5009227, endpos -1, usedbytes=0, bufleft=3743924
2020-09-17 01:52:31.401094 Peer not up, flushing message queue
26615 2020-09-17 01:52:31.417730 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=8753151
26615 2020-09-17 01:52:31.417795 Got 1201 bytes

In other words, nothing between 01:21:44 and 01:52:31, and I think the xymond_channel processes were not running at this time. Xymonlaunch shows a restart at 01:52.

Thanks

Zak Beck

From: Beck, Zak
Sent: 17 September 2020 08:55
To: xymon at xymon.com
Subject: RE: [Xymon] semop failed, Invalid argument - Ubuntu

Hi

Sorry for resurrecting this but I get this periodically too and it's really annoying 😊

2020-09-17 01:45:23.945832 semop failed, Invalid argument

2020-09-17 01:45:23.945839 Dropping message due to semaphore error

One particular server just started doing this about 10 days having not done it for months.

It's Ubuntu 16.04 LTS, 4.4.0-189-generic, x64. I have other Ubuntu 16.04 servers where it does not happen or at least, has not happened recently.

I turned on debug logging but I'm not too familiar with the server code so it doesn't really say much to me. Here are the additional debug entries:

18723 2020-09-17 01:45:23.945758 Beginning conn_t cleanup

18723 2020-09-17 01:45:23.945762 conn_t cleanup complete

18723 2020-09-17 01:45:23.945783 -> do_message/1 (362 bytes): status+60m awdhrprtldb5.sessions clear Thu Sep 17 01:45:23 MDT 2020

18723 2020-09-17 01:45:23.945790 -> update_statistics

18723 2020-09-17 01:45:23.945793 <- update_statistics

18723 2020-09-17 01:45:23.945797 -> get_hts

18723 2020-09-17 01:45:23.945809 <- get_hts

18723 2020-09-17 01:45:23.945813 ->handle_status

18723 2020-09-17 01:45:23.945818 posting to status channel

18723 2020-09-17 01:45:23.945823 -> posttochannel

2020-09-17 01:45:23.945832 semop failed, Invalid argument

2020-09-17 01:45:23.945839 Dropping message due to semaphore error

18723 2020-09-17 01:45:23.945844 <-handle_status

18723 2020-09-17 01:45:23.945864 <- do_message/1

Xymond eventually falls over and needs restarting.

Can anyone help me with this - I can't be the only one with it!

Zak Beck

-----Original Message-----
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> On Behalf Of John Horne
Sent: 12 November 2019 19:22
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: [External] Re: [Xymon] semop failed, Invalid argument

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

On Tue, 2019-11-12 at 17:03 +0000, Rothlisberger, John R. via Xymon wrote:

>

> Does anyone have any helpful ideas?

>

...

>

> 2019-11-01 11:45:07.083973 semop failed, Invalid argument

> 2019-11-01 11:45:07.083982 Dropping message due to semaphore error

>

Not really I'm afraid.

The actual error is the invalid argument bit. It refers to a call to 'semop'. A

very quick look at the xymond code seems to indicate that it would be the

semaphore id that it is objecting to - basically it doesn't exist or the id is

less than zero.

How that came about though, I have no idea. It may be that the code is being

called when it shouldn't be - perhaps a lack of argument checking. It would

require much further checking of the code to see what is happening. Maybe

running xymond is debug mode will give more information.

John.

--

John Horne | Senior Operations Analyst | Technology and Information Services

University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK

________________________________

[https://urldefense.proofpoint.com/v2/url?u=http-3A__www.plymouth.ac.uk_images_email-5Ffooter.gif&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=hxVvOEJZ-L5r9Nxgc9lsvl-WrhG5oFV5EJjI2aDKSfU&s=H0f2NDb_6_6tTQITYlDrh2iW299AzF2U0DJPMam9Sg8&e= ]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.plymouth.ac.uk_worldclass&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=hxVvOEJZ-L5r9Nxgc9lsvl-WrhG5oFV5EJjI2aDKSfU&s=ZL1Rv3au4aX8m81BMmvBy6qv-QmQxYFe7ltOCoJxMCs&e= <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.plymouth.ac.uk_worldclass&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=hxVvOEJZ-L5r9Nxgc9lsvl-WrhG5oFV5EJjI2aDKSfU&s=ZL1Rv3au4aX8m81BMmvBy6qv-QmQxYFe7ltOCoJxMCs&e=%20> >

This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

_______________________________________________

Xymon mailing list

Xymon at xymon.com<mailto:Xymon at xymon.com>

https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xymon.com_mailman_listinfo_xymon&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=hxVvOEJZ-L5r9Nxgc9lsvl-WrhG5oFV5EJjI2aDKSfU&s=tNoVkWPSzh_BTQpflmBcznFnmy_fkRWU4r7J71Rj0_k&e=

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20200917/e8ca7ab7/attachment.htm>