I find this messages kind of weird. Are you saying your servers only run long
periods of uptime with pf and *not* with ipf? I run a server and almost never
put it down. IPF performs very well, including a lot of natting for my home
network.
Correct. IPF is unstable with our SMP (most of the
For me, 5 days up time after switching from IPF to PF. Before the switch a
couple of hours of uptime was the maximum. Seems like the crashes are caused
by ipfilter.
Still same for me :) Uptime almost 20 days now after switching to PF.
___
freebsd-st
Yes, there is absolutely no difference. Disabled HTT in the BIOS and in
FreeBSD, the box still crashes.
Matt again :)
So far a 13 day up time after switching from IPF to PF. If thats not the
problem, I hope I find it soon considering this is a production server ...
but it seems to be more st
What are the chances of a base 5.4-RELEASE system with PF and securelevel
2 and updated packages being cracked and rooted? Is this something that
occurs every day? Or is it difficult?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.o
Could you not use pfsync to mitigate the problem (at least
partially)? As for your original question, I think its less
work to change your hardware to something you know works than
changing operating systems. Why not use single CPU machines
for this?
My boss refuses :-(
_
After changing to PF I did not notice single crash for month (production
servers with, sometimes, heavy load).
I would try FreeBSD with PF anyway. Works perfectly.
You say it didn't crash for a month, but then you say to try FreeBSD with
PF because it works perfectly. To me, a month of uptime
Hi all,
Removing IPF for 5.4-STABLE seems to have made the boxes stable. I
switched all the firewalls to PF and they haven't crashed since, its been
about 3 days now... (before they were crashing every 12 hours).
Here are my worries:
1) If I were to put this machine into production, it cou
On Wed, 29 Jun 2005, Kris Kennaway wrote:
On Tue, Jun 28, 2005 at 11:26:06AM -0400, Matt Juszczak wrote:
OK, when it crashes next and is sat at the "db>" prompt, type "tr" and
press enter to get a trace. Copy this down (or have a serial console to
capture the out
If you experience panics on FreeBSD then you need to follow the advice
in the developers' handbook chapter on kernel debugging and obtain the
necessary information so that a developer can begin to investigate
this problem.
I've tried :-( It locks up before it can do a dump.
_
Yes, SMP is enabled, as is implied by the kernel config tag.
(Very busy compilation, web and database server)
Are you using PF?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
Some people suggested so - pf is supposed to be faster then IPFILTER.
However if you are experiencing machine freezing like I did on 5.4-STABLE
I'm not sure this will help - if nothing else helps try 6.0-CURRENT. I've
also noticed that it is running much faster with all debuging enabled then
reg
Hi,
I have something like 20 boxes (Dell Power Edge 370, Fujitsu-Siemens PRIMERGY
200 and couple of dual AMD64 Fujitsu-Siemens) servers running 5.4-STABLE. So
far, only machine that I have experienced freezing and was unable to get
droped into KDB or to get any sort of vmcore was Dell Power E
Only way to find out is to try. You could build and install the non-SMP
kernel and reboot when you can, or let it boot the new kernel next time
the system(s) crash.
A lot of the issues seem to be SMP-related. I really loaded up a GENERIC
5.4 kernel and wasn't able to get it to panic. What do you
Matt,
Sadly the FreeBSD guys will need more info before a fix is possible. I would
suggest you revert back to FreeBSD 5.3, if you can. Even if you get a patch
you'd want to do a whole lot of regression testing before putting it in
production as it might break something else.
Gary,
Do you kn
Please try out this patch to aid the above problem with hang instead of
dump:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/trap.c.diff?r1=1.275&r2=1.276
This box is now crashing once every 12 hours. I can't apply this patch
:-(. Does anyone have any suggestions on how I can work a
Please try out this patch to aid the above problem with hang instead of
dump:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/trap.c.diff?r1=1.275&r2=1.276
This patch wouldn't go through
I tried patching against:
__FBSDID("$FreeBSD: src/sys/i386/i386/trap.c,v 1.267.2.3 2005/05/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
heavily loaded database servers. none
of them ever crash.
Matt Juszczak wrote:
Other people I've seen complain seem to be running SMP Not sure
if that has anything to do with it but its the only similiarity I can
pull out from any responses I've gotten.
I have 5 modest
Vivek Khera wrote:
On Jun 28, 2005, at 5:20 AM, Alex Povolotsky wrote:
Can anyone enlighten me, if recent crashes are on STABLE only or
5.4-RELEASE is affected as well?
I have three boxes running 5.4-RELEASE. one is a mediumly-loaded web
server, and two are very heavily loaded database
fsck -y# or fsck and read every question, if you're paranoid
mount -f /# remounts root read/write
mount /var
savecore /var/crash
exit
Gary
Gary:
After it crashes, it locks up and hangs, no keyboard response, etc.
When I reboot, I go into single user mode and do:
fsck -p
moun
Gavin Atkinson wrote:
On Tue, 2005-06-28 at 10:49 -0400, Matt Juszczak wrote:
Gleb Smirnoff wrote:
On Mon, Jun 27, 2005 at 01:01:09AM -0400, Matt Juszczak wrote:
M> About three weeks ago, I upgraded my 5.3-RELEASE boxes to 5.4-RELEASE.
M> I also turned on procmail globally
Gleb Smirnoff wrote:
On Mon, Jun 27, 2005 at 01:01:09AM -0400, Matt Juszczak wrote:
M> About three weeks ago, I upgraded my 5.3-RELEASE boxes to 5.4-RELEASE.
M> I also turned on procmail globally on our mail server. Here is our
M> current FreeBSD server setup:
M>
M> URANUS
Can you please build kernel with debugging and obtain a crashdump?
High activity on the box today caused us to be able to crash it again
within 9 hours. I configured all steps per the developers handbook, but
when I went to do savecore, it said "no dumps".
It appears the machine is complet
now I am stuck. I have two -STABLE machines which continue to cause
kernel traps. Tomorrow, I am going to compile a debugging kernel on
orion and try to let it crash again to see what kind of errors it
reports, but I was wondering if anyone else is experiencing these problems.
Thanks in
24 matches
Mail list logo
