This is what top says, if it's of any help:

##############################################################
$ top
last pid: 6598; load averages: 0.34, 0.29, 0.22 up 0+14:30:39 11:46:07
54 processes:  1 running, 53 sleeping

Mem: 27M Active, 39M Inact, 35M Wired, 4992K Cache, 22M Buf, 9828K Free
Swap: 256M Total, 256M Free


 PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
6247 _pflogd     1 -58    0  1536K  1108K bpf      0:05  0.49% pflogd
6586 root        1  -8   10 11032K  9848K piperd   0:00  0.20% php
6598 root        1 139   10  2196K  1300K RUN      0:00  0.20% top
6597 root        1   8   10  1620K  1156K wait     0:00  0.20% sh
 264 root        1 -58    0  6060K  3980K bpf     34:50  0.00% tcpdump
3390 root        1 -58    0  5528K  3456K bpf      6:42  0.00% tcpdump
 470 root        1  76    0  1332K   768K select   3:17  0.00% syslogd
 265 root        1  -8    0  1188K   604K piperd   1:50  0.00% logger
3391 root        1  -8    0  1188K   604K piperd   0:26  0.00% logger
 263 _pflogd     1 -58    0  1536K  1036K bpf      0:08  0.00% pflogd
3388 _pflogd     1 -58    0  1536K  1056K bpf      0:04  0.00% pflogd
550 root 1 8 0 232K 104K nanslp 0:01 0.00% check_reload_status
 539 root        1   8    0  1300K   840K nanslp   0:00  0.00% cron
3620 root        1   8    0  1620K   928K wait     0:00  0.00% sh
6248 root        1  -8    0  1188K   688K piperd   0:00  0.00% logger
 121 root        1  76    0  1208K   664K select   0:00  0.00% usbd
5883 root        1  76    0  5580K  2088K select   0:00  0.00% sshd
 555 root        1   5    0  1632K   920K ttyin    0:00  0.00% sh
#################################################
----- Original Message ----- From: "Scott Ullrich" <[EMAIL PROTECTED]>
To: <support@pfsense.com>
Sent: Wednesday, September 21, 2005 11:33 AM
Subject: Re: [pfSense Support] Argg! My PfSense just died!


top from a shell will tell you this.

I have never ever seen a box just all of the sudden stop working.  If
a box blows up, it goes big time with kernel panics, etc.  And even
this I have not seen since being on crappy 5.X.   6.X of FreeBSD is
looking mighty fine.

Scott


On 9/21/05, Mojo Jojo <[EMAIL PROTECTED]> wrote:
I meant, nothing plugged into the LAN NIC and nothing plugged into the OPT 2
NIC.

Sorry about that.

I am starting to wonder if this could be a RAM issue, as in, not enough of
it.

Todd


----- Original Message -----
From: "Chris Buechler" <[EMAIL PROTECTED]>
To: <support@pfsense.com>
Sent: Wednesday, September 21, 2005 9:19 AM
Subject: Re: [pfSense Support] Argg! My PfSense just died!


> Mojo Jojo wrote:
>
>>
>> Just some further info..
>>
>> System died last night again after approx 6 hours of uptime.
>>
>> I could still get to the GUI, could still SSH to it but it would pass >> any
>> traffic through to the OPT 2 (DMZ) interface.
>>
>> I attempted to run /etc/rc.bootup at the command line which restarted >> Pf
>> fine. After the restart of Pf (not the whole computer) everything thing
>> was still in the same shape with no traffic passing through to the DMZ.
>>
>> The only thing that corrected this was a reboot which I initiated via >> the
>> Pf GUI.
>>
>> Further info:
>> V. 0.84
>> Running on a PIII 933 with 128mb of ram. I have 4 Linksys NICS >> installed
>> on the PCI bus and one on the motherboard which I had disabled.
>>
>> Onboard NIC (disabled in BIOS)
>> Linksys NIC 1 > LAN
>> Linksys NIC 2 > WAN (static IP on a T1 with ascend T1 router on other
>> end)
>> Linksys NIC 3 > OPT 1 (DMZ where servers are)
>> Linksys NIC 4 > OPT2 (not in use at the moment)
>>
>> The PC is a DELL, Pf is running on a Hard Drive.
>>
>> I installed a fresh copy of 0.84, this is not an upgrade.
>>
>> All Linksys/Network Everywhere NICS are identical model NC100.
>>
>> I have 26 aliases setup, 46 rules on the WAN tab, 14 rules on the DMZ >> tab
>> and none on the LAN or OPT 2.
>>
>> I have nothing plugged into the WAN NIC and nothing plugged into the >> LAN
>> NIC at this time.
>>
>
> umm, above you say it stops passing traffic, here you say you only have
> one NIC plugged in?  It can't pass traffic with only one NIC plugged in.
> system logs after it stops passing traffic if it happens again may prove
> very useful.
> -cmb
>
> ---------------------------------------------------------------------
> 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]



---------------------------------------------------------------------
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]

Reply via email to