What do you recommend checking first? NIC's? They are 3com and where recommended on the list.
Don't have a huge budget… but I need to get this going J I'll try out anything.
-Tim
From: Scott Ullrich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2006 11:14 AM
To: [email protected]
Subject: Re: [pfSense Support] States Locking Up
This is sounding more and more like hardware issues.
On 6/29/06, Tim Dickson < [EMAIL PROTECTED] > wrote:
Ok… back at it again. This time it locked up at 420 states. I went through and analysed and cleaned up a few machines (found an instance of alexa)… but still the machine with the most states only had 15.
I've attached an image of the RRD graphs showing the packet flow I was describing.
Any ideas are more than welcome… I'll try them all! J
-Tim
-----Original Message-----
From: Holger Bauer [mailto:[EMAIL PROTECTED]]Sent: Wednesday, June 28, 2006 4:32 PM
To: [email protected]
Subject: RE: [pfSense Support] States Locking Up
You should look for the IP with the most state entries in the state table.
-----Original Message-----
From: Tim Dickson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2006 1:14 AM
Subject: RE: [pfSense Support] States Locking Up
what exactly am I looking for?
there are several states in there. I'm I looking for closed:closed or what? Thanks for the help!
-Tim
On Thu, 2006-06-29 at 11:11 +1200, Craig FALCONER wrote:
Okay then - look at the states table when its not working, and see what the source/destination IP is. Go to that machine and unplug it from your network.
Almost guarantee they have p2p software, or spyware, or whatever buzzword it is now.
-----Original Message-----
From: Tim Dickson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 29 June 2006 11:05 a.m.
Subject: RE: [pfSense Support] States Locking Up
It's not start up spikes (those I know about)
when these spikes occur 3 out of every 4 packets I send out drop until I reset my states.
If I leave it alone eventually it will usually clear up, but it could take several minutes to an hour.
-Tim
On Thu, 2006-06-29 at 10:49 +1200, Craig FALCONER wrote:
SNMP causes those spikes afaik. Disable it if you don't need it?
-----Original Message-----
From: Tim Dickson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 29 June 2006 10:28 a.m.
Subject: RE: [pfSense Support] States Locking Up
OK, so it's been a day with my state table at 20,000. RAM is at 20% and CPU time averages around 8%
It is still locking up, but browsing around I have come across something that may help. On the RRD Graphs I had noticed before it seemed traffic peaked when the lock ups occured... but not always. I then w ent to the Graph "packets" and EVERY time the states lock the packets jump up to 2.0k up and 4.0k down. Once I reset the states the packets will go back to a normal state.
So far today (looking at the RRD graph for today) I can see 15 spikes for the last 24 hours. The Greatest time between was 4 hours from 00:00 to 04:30. Hope this helps! I'm thinking of redoing the co nfig from scratch, but I have a lot of virtual IP and 1:1 mappings that I will loose. If I backup, I'm afraid that whatever is causing this will return. Give me your thoughts on this. Thanks!
-Tim
On Wed, 2006-06-28 at 01:18 +0200, Holger Bauer wrote:
Normal should be fine. See what the changed state limit does first.
Holger
> -----Original Message-----
> From: Tim Dickson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 28, 2006 12:55 AM
> To: [email protected]
> Subject: RE: [pfSense Support] States Locking Up
>
>
> OK, I've changed my states to 20k
> What "Mode" should I be using? We are connected via a full T1
> right now I have it set up for normal.
> Thanks!
> -Tim
>
> -----Original Message-----
> From: Holger Bauer [mailto:[EMAIL PROTECTED] ]
> Sent: Tuesday, June 27, 2006 3:09 PM
> To: [email protected]
> Subject: RE: [pfSense Support] States Locking Up
>
>
> As you're not hitting the maximum limit this should not be
> the issue but as you have lots of RAM you can boost this
> value up just to see if it makes any difference.
>
> Holger
>
> > -----Original Message-----
> > From: Tim Dickson [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 27, 2006 5:07 PM
> > To: [email protected]
> > Subject: RE: [pfSense Support] States Locking Up
> >
> >
> > Should I set me state limit to 1000 or something? seems
> > silly, but I'm willing to try anthing to get this to work.
> > -tim
> >
> > -----Original Message-----
> > From: Holger Bauer [mailto:[EMAIL PROTECTED] ]
> > Sent: Monday, June 26, 2006 2:58 PM
> > To: [email protected]
> > Subject: RE: [pfSense Support] States Locking Up
> >
> >
> > What is your state limit at system>advanced and how many
> > states do you hit when the problem occurs?
> >
> > Holger
> > -----Original Message-----
> > From: Tim Dickson [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, June 26, 2006 7:39 PM
> > To: [email protected]
> > Subject: [pfSense Support] States Locking Up
> >
> >
> > I submitted to this list last week and am hoping I can hit
> > some fresh brain cells this week :)
> > I am having an issue with states locking up. This happens
> > every half an hour or so (it's completely random... can go
> > hours or minutes). When it happens if I reset states it
> > clears up and all is well. Also while it happens if I ping
> > google it will drop roughly 3 of every 4 packets sent.
> > Most current connections will remain (like a dowload) but
> > occasionally it will drop also.
> > I'm running beta1RC1a on an AMD 2200 athlon XP with 2gig RAM
> > and 30gb harddrive. I'm running in dual WAN with interface
> > names WAN, LAN and GWAN, GLAN (xl driver)
> > I have advanced outbound NAT enabled and I have Source subnet
> > of LAN to WAN and source subnet GLAN to WAN. I then have
> > rules for lan net to go out the WAN gateway and glan subnet
> > out GWAN gateway.
> >
> >
> > Am I doing something wrong here? basically I ALWAYS want LAN
> > to go out WAN and GLAN to go out GWAN
> > IP's are both Static for the WAN interfaces. Let me know if
> > any more info is needed!
> > -Tim
> >
> > ____________
> > Virus checked by G DATA AntiVirusKit
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ____________
> Virus checked by G DATA AntiVirusKit
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
____________
Virus checked by G DATA AntiVirusKit
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
____________
Virus checked by G DATA AntiVirusKit
I would grab the ultimate boot cd from the internet and start running all of the memory and cpu related tests. Then run anything else that may be applicable.
On 6/29/06,
Tim Dickson <[EMAIL PROTECTED]> wrote:
- Re: [pfSense Support] States Locking Up Scott Ullrich
- RE: [pfSense Support] States Locking Up Tim Dickson
- Re: [pfSense Support] States Locking Up Scott Ullrich
- RE: [pfSense Support] States Locking Up Tim Dickson
