(SOLVED) AMD 64 6/13 snapshot failing after approx 4 hours
-
This appears it could be related to: http://redmine.pfsense.org/issues/1425
– The above bug is in reference to BGE drivers and I am using BCE drivers, related?quick question, what is the latest snapshot I can use / when did you swap to FreeBSD 8.1? Running a uname -a on the 5/24 version shows:
FreeBSD host.name.here 8.1-RELEASE-p3 FreeBSD 8.1-RELEASE-p3 #1: Tue May 24...Can anyone provide info on what version I can run (and where to get it)?
Thanks,
-
Bad news… 5/27 snapshot just took a dirt nap... I'll have to go onsite to gain console access and I'll try modifying the kern.ipc.nmbcluster...
Does anyone know where I could get a Feb 24 snapshot?
Any Ideas?
-
Ah the joys of the HP DL series of servers.
First run
netstat -m
You will probably see a line similar to this0/1564137/323086 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
This is most likely the cause of your problems and IIRC has existed on the DL360 G6/7 since day 1
You need it to be all zeros so from a command prompt try
sysctl kern.ipc.nmbclusters=51200
That is twice the default value but you may need to increase it depending on your requirements.
I run my G6 and G7 boxes at 4x default value but I've got full internet BGP routes on them and I've got the 13th May image running solidly since it's release with no issues.NB This setting will not persist through upgrades or reboots.
-
Thanks.. I will check once I'm onsite later today. (luckily, this is in a lab environment and not prod).
If I add this via /boot/loader.conf.local, it should persist a reboot, but not an upgrade, correct?
Looking at the freeBSD tuning guide (http://www.freebsd.org/doc/handbook/configtuning-kernel-limits.html) they recommend a max of 32K
We recommend values between 4096 and 32768 for machines with greater amounts of memory. Under no circumstances should you specify an arbitrarily high value for this parameter as it could lead to a boot time crash.
I'm not worried about memory, so I may set it to 64K (65536) which would consume 128MB of ram. This should not be an issue as this server has 24GB (it's overkill, but it's what we had laying around that I could use in a lab… One of the advantages of working in a large shop ;))
-
lol and here was me thinking my 16Gb was OTT
Yes loader.conf.local will survive a reboot.
The handbook is a little conservative in it's values. Assuming you are running the 64bit build and have the physical memory it's safe to take it up quite a bit higher with the 8.x versions of FreeBSD.
-
I was able to work on this today and have made the following changes:
Upgraded to today's snapshot: (6/14)
ran sysctl kern.ipc.nmbclusters=65536
edited /boot/loader.conf and replaced
kern.ipc.nmbclusters="0"
with
kern.ipc.nmbclusters="65536"I am watching the netstat -m outbut and have seen no denied mbuf allocations (although I did not see any before the change either).
-
I don't want to call it fixed yet… but so far, so good. Will update tomorrow.
Dumb question... is there any reason I couldn't add this to "System: Advanced: System Tunables" as a manual entry if it proves to be stable similar to the following?
And Thank you all for the help!
-
Dumb question… is there any reason I couldn't add this to "System: Advanced: System Tunables" as a manual entry if it proves to be stable similar to the following?
that's only for sysctls, not loader items.
-
I ran kern.ipc.nmbclusters="131072" on an amd64 machine with 4GB RAM with no problem, due to mbuf numbers steadily climbing. When your mbuf number hits the set value of that variable, everything stops.
-
@CMB:
Understood, but if these sysctls commands are executed at startup, wouldn't this effectively have the same impact for this particular entry given that the buffers don't fill up that quickly and can be modified post-boot?
I would like to have it in the config so that If i forget to modify the loader after an upgrade, the setting still gets applied.
-
It used to work several months ago when you added it in there then it stopped for some reason I can't remember, there is a post about it you might be able to find. So now I just stick it in /boot/loader.conf.local and remember to set it after each update.
-
If you put it in /boot/loader.conf.local it should get copied across an update automatically.
Steve
-
If you put it in /boot/loader.conf.local it should get copied across an update automatically.
Steve
I just tested and can confirm. Good info… Thanks!
This should make it into the next guide book. I didn't see any mention of it in the 1.2.3 book. -
I updated the first port with issue details and resolution steps. please feel free to let me know if I have any inaccuracies / bad advice listed.
Thanks again.
