[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [hobbit] Hobbitd settings in hobbitserver.cfg

I've had much experience in dealing with this issue, as I have some client messages that are simply huge and required me having MAXMSG_STATUS=2048 and higher.

The problem you are experiencing is running out of shared memory. Here are the settings I have on my hobbit server that has 3.5GB of RAM:

]$ grep kernel.sh /etc/sysctl.conf
kernel.shmmni = 4096
kernel.shmmax = 3758096384

3758096384 is 3.5 * 1024 * 1024 * 1024

Once you edit those values and reboot (or sometimes sysctl -p will do it as root), then Hobbit can use more shared memory.

-Charles


The fix is to edit your /etc/sysctl.conf and define the kernel.shmmax to a value equal to your full system ram.


Michael Dunne wrote: 
Greetings,

 Earlier today we added a system to our main hobbit server. Upon adding the
system we received a hobbitd msg of:

Oversize status msg fro xxx. xxxxx:ports truncated (n=294359, limit=262144)

When I looked in the hobbitserver.cfg file to increase the maxmsg_status
setting I did not see a listing  for maxmsg_status. Thinking that I was
being smart, I added a ling to hobbitserver.cfg for maxmsg_client. The line
added was as followed:

MAXMSG_STATUS="768"

I restarted hobbit after adding the line and saw the following message in
the hobbitlaunch.log:

2006-09-25 11:48:12 Loading hostnames
2006-09-25 11:48:12 Loading saved state
2006-09-25 11:48:12 Setting up network listener on 0.0.0.0:1984
2006-09-25 11:48:12 Setting up signal handlers
2006-09-25 11:48:12 Setting up hobbitd channels
2006-09-25 11:48:12 Could not get shm of size 786432: Cannot allocate memory
2006-09-25 11:48:12 Cannot setup client channel
2006-09-25 11:48:12 Task hobbitd terminated, status 1


I removed the line and restarted hobbit, but hobbitd kept failing. I tried
rebooting the system, but hobbitd was still failing.

Ultimately I stopped hobbit, deleted the hobbitd.pid file and restarted
hobbit. All has been well since, excepting the original oversized status
messages.

My question is, what did I do wrong? Where exactly should I add the
maxmsg_status line (or the maxmsg_client, maxmsg_data, maxmsg_stachg for
that matter)? 

I am running 4.2.0.

Thanks in advance for any assistance.

Mike

Michael Dunne
Network Support Specialist
AccuWeather, Inc. 

~HISTORY, n. An account mostly false, of events mostly unimportant, which
are brought about by rulers mostly knaves, and soldiers mostly fools.

(Ambrose Bierce, "The Devil's Dictionary")~



To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk