I am sure I am not the only one who has seen the message:
Oversize data/client msg from n.n.n.n truncated (n=787987, limit 786432)
I was wondering if there were any plans to put msgs, and ports in their own channels to avoid that? Some of our log file monitoring is done on the server, additional log file monitoring is done using the old bb-msgs.sh script. Perhaps I could increase the shared memory sizes, but I am not sure with only a 1G of memory available on the server.
David Gore (v965-3670) Enhanced Technology Support (ETS) Network Management Systems (NMS) IMPACT Transport Team Lead - SCSA, SCNA Page: 1-800-PAG-eMCI pin 1406090 Vnet: 965-3676
I always get error messages, when windows clients make config update from server. I always get the following messages on Server:
*application: error - 2007/03/23 09:26:36 - BigBrotherHobbitClient (17) - n/a "The agent bbwinupdate generated this event message : bbwin namespace update is not permitted. Please check the bbwin/vega-bbwin.cfg on your hobbit server."*
I changed the configfiles on server and on client like in the manual in
http://sourceforge.net/forum/forum.php?thread_id=1671582&forum_id=460874
When I check the tmp directory in hobbit client, I can see the update from server, but it looks like the client cannot update the local config file.
What did I do wrong? Or did I forget something in the config?
Here is my client config file. Same one is laying on server, too.
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="xxx.xxx.xxx.xxx" /> <!-- <setting name="bbdisplay" value="yoursecondbbdisplay:port" />--> <!-- BB Pager Part --> <!--<setting name="usepager" value="false" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="pagerlevels" value="red yellow" /> --> <!-- bbwin mode local or central --> <setting name="mode" value="local" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="5m" /> * <load name="bbwinupdate" value="bbwinupdate.dll" />* <load name="cpu" value="cpu.dll" /> <load name="disk" value="disk.dll" /> <!-- <load name="externals" value="externals.dll"/> --> <load name="memory" value="memory.dll" /> <load name="msgs" value="msgs.dll" /> <load name="procs" value="procs.dll" /> <load name="stats" value="stats.dll" /> <load name="svcs" value="svcs.dll" /> <load name="uptime" value="uptime.dll" /> <setting name="loglevel" value="3" /> <setting name="logpath" value="C:\Program Files\BBWin\logs\BBWin.log" /> <!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="false" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="85%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="E" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <!-- <load value="cscript mybbscript.vbs" /> <load value="memory.exe" /> <load value="cscript wlbs.vbs" timer="15m" /> <load value="cluster.exe" timer="90s" /> --> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="78" paniclevel="98" /> <setting name="page" warnlevel="70" paniclevel="90" /> <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs> <setting name="alwaysgreen" value="false" /> <match logfile="System" type="error" delay="1h" alarmcolor="red" /> <match logfile="System" type="warning" alarmcolor="yellow" /> <match logfile="Application" type="error" delay="1h" alarmcolor="red" /> <match logfile="Application" type="warning" alarmcolor="yellow" /> <match logfile="Security" type="fail" /> <!-- Some ignore rules examples --> <ignore logfile="Application" eventid="1030" /> <ignore logfile="System" source="W32Time" /> </msgs> <procs> <!-- some procs rules example <setting name="drwtsn" rule="-1" alarmcolor="red" /> <setting name="pageant.exe" rule="=1" comment="Putty agent deamon" /> --> </procs> <svcs> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- If true, the agent will restart all "automatic services" which would be stopped--> <setting name="autoreset" value="false" /> <setting name="alarmcolor" value="yellow" /> <!-- The line bellow show you svcs rules. If the "Automatic Updates" service is stopped, it will be automatically restarted and a red status will be sent until the service get it's correct status --> <setting name="Automatic Updates" value="started" autoreset="true" alarmcolor="red" /> </svcs> <uptime> <setting name="delay" value="30m" /> </uptime>
- <bbwinupdate> <setting name="filename" value="bbwin/vega-bbwin.cfg" /> </bbwinupdate>* </configuration>
Thank you four your help!
Maik
Hello Maik,
Your configuration is good.
To suppress this warning, you have to delete the bbwin section on the vega-bbwin.cfg stored on the hobbit server. When I created the bbwinupdate agent, I put a small security to prevent people to update the bbwin section. bbwinupdate just helps you to update agents sections from a central point.
Regards,
2007/3/23, Maik Heinelt <maik at vegasystems.com>:
I always get error messages, when windows clients make config update from server. I always get the following messages on Server:
application: error - 2007/03/23 09:26:36 - BigBrotherHobbitClient (17) - n/a "The agent bbwinupdate generated this event message : bbwin namespace update is not permitted. Please check the bbwin/vega-bbwin.cfg on your hobbit server."
I changed the configfiles on server and on client like in the manual in
http://sourceforge.net/forum/forum.php?thread_id=1671582&forum_id=460874
When I check the tmp directory in hobbit client, I can see the update from server, but it looks like the client cannot update the local config file.
What did I do wrong? Or did I forget something in the config?
-- Etienne GRIGNON
Hello Grignon,
I changed the vega-bbwin.cfg configfile. Now it is working well without any error messages! Thanks for your help!
I`m looking for some more manuals about hobbit and bbwin. Are there some detailed pages, where I can get more informations for how to config the bbwin and hobbit system?
For example.. I would like to see the temperature of linux clients and I found the temperature.sh script on deadcat.net.au. But there was no complete manual in it. just some notice inside the script.
Reagards
Etienne Grignon wrote:
Hello Maik,
Your configuration is good.
To suppress this warning, you have to delete the bbwin section on the vega-bbwin.cfg stored on the hobbit server. When I created the bbwinupdate agent, I put a small security to prevent people to update the bbwin section. bbwinupdate just helps you to update agents sections from a central point.
Regards,
2007/3/23, Maik Heinelt <maik at vegasystems.com>:
I always get error messages, when windows clients make config update from server. I always get the following messages on Server:
application: error - 2007/03/23 09:26:36 - BigBrotherHobbitClient (17) - n/a "The agent bbwinupdate generated this event message : bbwin namespace update is not permitted. Please check the bbwin/vega-bbwin.cfg on your hobbit server."
I changed the configfiles on server and on client like in the manual in
http://sourceforge.net/forum/forum.php?thread_id=1671582&forum_id=460874
When I check the tmp directory in hobbit client, I can see the update from server, but it looks like the client cannot update the local config file.
What did I do wrong? Or did I forget something in the config?
On Thu, Mar 22, 2007 at 11:47:42PM +0000, Gore, David W (David) wrote:
I am sure I am not the only one who has seen the message:
Oversize data/client msg from n.n.n.n truncated (n=787987, limit 786432)
I was wondering if there were any plans to put msgs, and ports in their own channels to avoid that? Some of our log file monitoring is done on the server, additional log file monitoring is done using the old bb-msgs.sh script. Perhaps I could increase the shared memory sizes, but I am not sure with only a 1G of memory available on the server.
Putting them in a separate channel would not lower the shared-memory usage. You would still need a segment large enough to handle the biggest set of "ports" data.
But on a 1 GB server, would it be a problem to allocate 1 or 2 MB for such a shared memory area ? 2 MB is only 0.2 % of the total amount of memory ... the only bothersome thing is that some systems have rather low default settings for the max. size of shared memory segments, so it is possible that you would have to tune some kernel parameters.
Regards, Henrik
Just some info: On HP-UX the default value of shmmax is 64M
on my 512 MB HP-UX server I have this
shmmax 71582788
shmmni 400
shmseg 120
----- Original Message ----- From: "Henrik Stoerner" <henrik at hswn.dk> To: <hobbit at hswn.dk> Sent: Friday, March 23, 2007 11:04 AM Subject: Re: [hobbit] Next release suggestion, msgs, ports?
On Thu, Mar 22, 2007 at 11:47:42PM +0000, Gore, David W (David) wrote:
I am sure I am not the only one who has seen the message:
Oversize data/client msg from n.n.n.n truncated (n=787987, limit 786432)
I was wondering if there were any plans to put msgs, and ports in their own channels to avoid that? Some of our log file monitoring is done on the server, additional log file monitoring is done using the old bb-msgs.sh script. Perhaps I could increase the shared memory sizes, but I am not sure with only a 1G of memory available on the server.
Putting them in a separate channel would not lower the shared-memory usage. You would still need a segment large enough to handle the biggest set of "ports" data.
But on a 1 GB server, would it be a problem to allocate 1 or 2 MB for such a shared memory area ? 2 MB is only 0.2 % of the total amount of memory ... the only bothersome thing is that some systems have rather low default settings for the max. size of shared memory segments, so it is possible that you would have to tune some kernel parameters.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (5)
-
david.gore@verizonbusiness.com
-
etienne.grignon@gmail.com
-
henrik@hswn.dk
-
lars.ebeling@leopg9.no-ip.org
-
maik@vegasystems.com