Xymon Mailing List Archive search

Oversize data/client msg

10 messages in this thread

list Joshua Krause · Mon, 7 Jan 2008 10:15:55 -0500 ·
I am receiving this msg from one of my solaris boxes and made some changes
still getting the message.

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos

 
Here is what my hobbitserver.cfg has in it:

 
MAXMSG_STATUS="768432"

MAXMSG_DATA="524288"

MAXMSG_CLIENT="768432"

 
I have restarted the hobbit process but I am still receiving these messages.

 
Thanks,

 
Josh
list Iain M Conochie · Mon, 07 Jan 2008 15:18:46 +0000 ·
quoted from Joshua Krause
On Mon, 2008-01-07 at 10:15 -0500, Joshua Krause wrote:
I am receiving this msg from one of my solaris boxes and made some
changes still getting the message.

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)
You need to increase the size of your MAXMSG_DATA parameter.

Cheers

Iain
quoted from Joshua Krause
First line: gsonc-spg-omea-1|sunos|sunos

 
Here is what my hobbitserver.cfg has in it:

 
MAXMSG_STATUS="768432"

MAXMSG_DATA="524288"

MAXMSG_CLIENT="768432"

 
I have restarted the hobbit process but I am still receiving these
messages.

 
Thanks,

 
Josh

list Gary Baluha · Mon, 7 Jan 2008 10:29:00 -0500 ·
Here's your problem:
Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)
MAXMSG_DATA="524288"

n=581293 > MAXMSG_DATA=524288

MAXMSG_STATUS is for the "status"-type alerts (green/yellow/red/etc, but no
trendable data), and MAXMSG_DATA is for the "data"-type alerts.

I have MAXMSG_CLIENT=655360 and this seems to work well for me.  I would try
setting all three to this value, unless you have specifically seen that you
require 768432.  In that case, try setting all three to that value.
However, you don't need to set them all the same; it just makes things a
little more consistent if you do.
quoted from Iain M Conochie

 I am receiving this msg from one of my solaris boxes and made some changes
still getting the message.


Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos


Here is what my hobbitserver.cfg has in it:


MAXMSG_STATUS="768432"

MAXMSG_DATA="524288"

MAXMSG_CLIENT="768432"


I have restarted the hobbit process but I am still receiving these
messages.


Thanks,


Josh
list Joshua Krause · Mon, 7 Jan 2008 10:31:24 -0500 ·
In the server man pages it said that the MSGMAX_DATA defaulted to 256kb so I
raised it to 512kb.  So your saying that I need to raise it to 768kb?  The
only reason I say this is because in the error message it says:

Latest errormessages:
Oversize data/client msg from 172.31.128.50 truncated (n=579186, limit
524288)
First line: gsonc-spg-omea-1|sunos|sunos

Which says the limit is "524588" and if the MSGMAX_DATA is set to 256 by
default then I would think that this value is dealing with the MSGMAX_CLIENT
which is defaulted to 512 and I raised it to 768.
quoted from Iain M Conochie

-----Original Message-----
From: Iain M Conochie [mailto:user-c784e16a5170@xymon.invalid] Sent: Monday, January 07, 2008 10:19 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Oversize data/client msg


On Mon, 2008-01-07 at 10:15 -0500, Joshua Krause wrote:
I am receiving this msg from one of my solaris boxes and made some
changes still getting the message.

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)
You need to increase the size of your MAXMSG_DATA parameter.

Cheers

Iain
First line: gsonc-spg-omea-1|sunos|sunos

 
Here is what my hobbitserver.cfg has in it:

 
MAXMSG_STATUS="768432"

MAXMSG_DATA="524288"

MAXMSG_CLIENT="768432"

 
I have restarted the hobbit process but I am still receiving these
messages.

 
Thanks,

 
Josh

list Joshua Krause · Mon, 7 Jan 2008 10:35:52 -0500 ·
I have made the change on the server and set them all to 768432 and bouced
the hobbit server process and still hadn't seen a change.  So I am
restarting the hobbit process on the client server also.

 
MAXMSG_STATUS="768432"

MAXMSG_DATA="768432"

MAXMSG_CLIENT="768432"

 
Thanks,

 
Josh
quoted from Gary Baluha

 
From: Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid] 
Sent: Monday, January 07, 2008 10:29 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Oversize data/client msg

 
Here's your problem:

Oversize data/client msg from 172.31.128.50 <http://172.31.128.50/>;
quoted from Gary Baluha
truncated (n=581293, limit 524288)
MAXMSG_DATA="524288"

n=581293 > MAXMSG_DATA=524288

MAXMSG_STATUS is for the "status"-type alerts (green/yellow/red/etc, but no
trendable data), and MAXMSG_DATA is for the "data"-type alerts. 

I have MAXMSG_CLIENT=655360 and this seems to work well for me.  I would try
setting all three to this value, unless you have specifically seen that you
require 768432.  In that case, try setting all three to that value.
However, you don't need to set them all the same; it just makes things a
little more consistent if you do. 

I am receiving this msg from one of my solaris boxes and made some changes
still getting the message.

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=581293, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos

 
Here is what my hobbitserver.cfg has in it:

 
MAXMSG_STATUS="768432"

MAXMSG_DATA="524288"

MAXMSG_CLIENT="768432"

 
I have restarted the hobbit process but I am still receiving these messages.

 
Thanks,

 
Josh
list Gary Baluha · Mon, 7 Jan 2008 10:55:48 -0500 ·
quoted from Joshua Krause
On Jan 7, 2008 10:31 AM, Joshua Krause <user-41d3365fe380@xymon.invalid> wrote:
In the server man pages it said that the MSGMAX_DATA defaulted to 256kb so
I
raised it to 512kb.  So your saying that I need to raise it to 768kb?  The
only reason I say this is because in the error message it says:
I mentioned to raise it to 768kb only because the other MAX* variables were
set to that.  In reality, you only need to raise it to whatever the largest
"data/client msg" size is.  In this case, that would be 579186.
quoted from Joshua Krause

Latest errormessages:
Oversize data/client msg from 172.31.128.50 truncated (n=579186, limit
524288)
First line: gsonc-spg-omea-1|sunos|sunos

Which says the limit is "524588" and if the MSGMAX_DATA is set to 256 by
default then I would think that this value is dealing with the
MSGMAX_CLIENT
which is defaulted to 512 and I raised it to 768.

MSGMAX_CLIENT is larger than _DATA because the former generally contains
more data. Other than that, there is no need for the three MAX* settings to
have any specific relationship between each other's values.
list Joshua Krause · Mon, 7 Jan 2008 11:04:01 -0500 ·
I understand what you are saying but after making the change in the
hobbitserver.cfg file I am still getting this message on hobbit:

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=579454, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos
quoted from Gary Baluha

 
Thanks,

Josh

 
From: Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid] 
Sent: Monday, January 07, 2008 10:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Oversize data/client msg

 
On Jan 7, 2008 10:31 AM, Joshua Krause <user-41d3365fe380@xymon.invalid> wrote:

In the server man pages it said that the MSGMAX_DATA defaulted to 256kb so I
raised it to 512kb.  So your saying that I need to raise it to 768kb?  The

only reason I say this is because in the error message it says: 


I mentioned to raise it to 768kb only because the other MAX* variables were
set to that.  In reality, you only need to raise it to whatever the largest
"data/client msg" size is.  In this case, that would be 579186. 
 

Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=579186, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos

Which says the limit is "524588" and if the MSGMAX_DATA is set to 256 by 
default then I would think that this value is dealing with the MSGMAX_CLIENT
which is defaulted to 512 and I raised it to 768.


MSGMAX_CLIENT is larger than _DATA because the former generally contains
more data. Other than that, there is no need for the three MAX* settings to
have any specific relationship between each other's values.
list Charles Jones · Mon, 07 Jan 2008 09:09:00 -0700 ·
Hobbit rehashes most config files automatically, with the exception of hobbitserver.cfg When you change hobbitserver.cfg, you must restart Hobbit for it to take effect.
quoted from Joshua Krause

Joshua Krause wrote:
I understand what you are saying but after making the change in the hobbitserver.cfg file I am still getting this message on hobbit:

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=579454, limit 524288)

First line: gsonc-spg-omea-1|sunos|sunos

 
Thanks,

Josh

 
*From:* Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid]
*Sent:* Monday, January 07, 2008 10:56 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] Oversize data/client msg

 
On Jan 7, 2008 10:31 AM, Joshua Krause <user-41d3365fe380@xymon.invalid <mailto:user-41d3365fe380@xymon.invalid>> wrote:

    In the server man pages it said that the MSGMAX_DATA defaulted to
    256kb so I
    raised it to 512kb.  So your saying that I need to raise it to
    768kb?  The

    only reason I say this is because in the error message it says:


I mentioned to raise it to 768kb only because the other MAX* variables were set to that.  In reality, you only need to raise it to whatever the largest "data/client msg" size is.  In this case, that would be 579186.
 
    Latest errormessages:

    Oversize data/client msg from 172.31.128.50 <http://172.31.128.50>;
    truncated (n=579186, limit
    524288)

    First line: gsonc-spg-omea-1|sunos|sunos

    Which says the limit is "524588" and if the MSGMAX_DATA is set to
    256 by
    default then I would think that this value is dealing with the
    MSGMAX_CLIENT
    which is defaulted to 512 and I raised it to 768.


MSGMAX_CLIENT is larger than _DATA because the former generally contains more data. Other than that, there is no need for the three MAX* settings to have any specific relationship between each other's values.

 
list Chris Ss-is Morris · Mon, 7 Jan 2008 16:15:40 -0000 ·
You need to stop the hobbit server, use the ipcs -m command to check the
shared memory has been released and then restart the hobbit server and the
problem should be resolved.

Regards,
Chris
quoted from Joshua Krause
-----Original Message-----
From:	Joshua Krause [SMTP:user-41d3365fe380@xymon.invalid]
Sent:	Monday, January 07, 2008 4:04 PM
To:	user-ae9b8668bcde@xymon.invalid
Subject:	RE: [hobbit] Oversize data/client msg

I understand what you are saying but after making the change in the
hobbitserver.cfg file I am still getting this message on hobbit:

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=579454, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos

 
Thanks,

Josh

 
From: Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid] Sent: Monday, January 07, 2008 10:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Oversize data/client msg

 
On Jan 7, 2008 10:31 AM, Joshua Krause < user-41d3365fe380@xymon.invalid
<mailto:user-41d3365fe380@xymon.invalid>> wrote:

	In the server man pages it said that the MSGMAX_DATA defaulted to
256kb so I
	raised it to 512kb.  So your saying that I need to raise it to
768kb?  The

	only reason I say this is because in the error message it says: 

I mentioned to raise it to 768kb only because the other MAX* variables
were set to that.  In reality, you only need to raise it to whatever the
largest "data/client msg" size is.  In this case, that would be 579186.  
	Latest errormessages:

	Oversize data/client msg from 172.31.128.50 <http://172.31.128.50>;
truncated (n=579186, limit
	524288)

	First line: gsonc-spg-omea-1|sunos|sunos

	Which says the limit is "524588" and if the MSGMAX_DATA is set to
256 by 	default then I would think that this value is dealing with the
MSGMAX_CLIENT
	which is defaulted to 512 and I raised it to 768.


MSGMAX_CLIENT is larger than _DATA because the former generally contains
more data. Other than that, there is no need for the three MAX* settings
to have any specific relationship between each other's values. 
 
**********************************************************************

This e-mail including any attachments is provided for general information purposes only and does not constitute advice except to the addressee if expressly stated in this email. For the avoidance of doubt the contents of this email and any attachments are subject to contract and are not intended to and will not constitute a legally binding contract or any part of a legally binding contract. 
The information contained in this email and any attachments is confidential.  It is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution or copying of the message or associated attachments is strictly prohibited.

If you have received this e-mail in error, please notify user-36fa688b57c1@xymon.invalid and permanently delete the email and any attachments immediately from your system.  You should not retain, copy or use this email or any attachment for any purpose, nor disclose all or any part of the contents to any other person.  Thank you for your co-operation. 
Neither RWE Systems UK Ltd nor any of the other companies in the RWE Group from whom this e-mail originates accept any responsibility for losses or damage as a result of any viruses and it is your responsibility to check attachments (if any) for viruses. 
RWE Systems UK Ltd Registered office: Mistral, Westlea Campus, Chelmsford Road, Swindon, Wiltshire, SN5 7EZ. Registered in England and Wales: company number 6052966.

*******************************************
list Joshua Krause · Mon, 7 Jan 2008 17:20:43 -0500 ·
Thanks I waited until the shared memory was released and then restarted and
I am good to go now.  Appreciate all the help.

Thanks,
Josh
quoted from Chris Ss-is Morris

-----Original Message-----
From: Morris, Chris (SS-IS) [mailto:user-d235f3ed1ca2@xymon.invalid] Sent: Monday, January 07, 2008 11:16 AM
To: 'user-ae9b8668bcde@xymon.invalid'
Subject: RE: [hobbit] Oversize data/client msg

You need to stop the hobbit server, use the ipcs -m command to check the
shared memory has been released and then restart the hobbit server and the
problem should be resolved.

Regards,
Chris
-----Original Message-----
From:	Joshua Krause [SMTP:user-41d3365fe380@xymon.invalid]
Sent:	Monday, January 07, 2008 4:04 PM
To:	user-ae9b8668bcde@xymon.invalid
Subject:	RE: [hobbit] Oversize data/client msg

I understand what you are saying but after making the change in the
hobbitserver.cfg file I am still getting this message on hobbit:

 
Latest errormessages:

Oversize data/client msg from 172.31.128.50 truncated (n=579454, limit
524288)

First line: gsonc-spg-omea-1|sunos|sunos

 
Thanks,

Josh

 
From: Gary Baluha [mailto:user-ae3e15c22de1@xymon.invalid] Sent: Monday, January 07, 2008 10:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Oversize data/client msg

 
On Jan 7, 2008 10:31 AM, Joshua Krause < user-41d3365fe380@xymon.invalid
<mailto:user-41d3365fe380@xymon.invalid>> wrote:

	In the server man pages it said that the MSGMAX_DATA defaulted to
256kb so I
	raised it to 512kb.  So your saying that I need to raise it to
768kb?  The

	only reason I say this is because in the error message it says: 

I mentioned to raise it to 768kb only because the other MAX* variables
were set to that.  In reality, you only need to raise it to whatever the
largest "data/client msg" size is.  In this case, that would be 579186.  
	Latest errormessages:

	Oversize data/client msg from 172.31.128.50 <http://172.31.128.50>;
truncated (n=579186, limit
	524288)

	First line: gsonc-spg-omea-1|sunos|sunos

	Which says the limit is "524588" and if the MSGMAX_DATA is set to
256 by 	default then I would think that this value is dealing with the
MSGMAX_CLIENT
	which is defaulted to 512 and I raised it to 768.


MSGMAX_CLIENT is larger than _DATA because the former generally contains
more data. Other than that, there is no need for the three MAX* settings
to have any specific relationship between each other's values. 
 
**********************************************************************
This e-mail including any attachments is provided for general information
purposes only and does not constitute advice except to the addressee if
expressly stated in this email. For the avoidance of doubt the contents of
this email and any attachments are subject to contract and are not intended
to and will not constitute a legally binding contract or any part of a
legally binding contract. 
The information contained in this email and any attachments is confidential.
It is intended only for the use of the intended recipient at the email
address to which it has been addressed. If the reader of this message is not
an intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution or
copying of the message or associated attachments is strictly prohibited.

If you have received this e-mail in error, please notify
user-36fa688b57c1@xymon.invalid and permanently delete the email and any
attachments immediately from your system.  You should not retain, copy or
use this email or any attachment for any purpose, nor disclose all or any
part of the contents to any other person.  Thank you for your co-operation. 
Neither RWE Systems UK Ltd nor any of the other companies in the RWE Group
from whom this e-mail originates accept any responsibility for losses or
damage as a result of any viruses and it is your responsibility to check
attachments (if any) for viruses. 

RWE Systems UK Ltd Registered office: Mistral, Westlea Campus, Chelmsford
Road, Swindon, Wiltshire, SN5 7EZ. Registered in England and Wales: company
number 6052966.

*******************************************