Just to be clear, if the boxes goes down again run those commands again without rebooting the box.
-----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 10:35 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! Please gather that John requested and send to the list. Thanks. On 9/26/05, Mojo Jojo <[EMAIL PROTECTED]> wrote: > OK, here is what I have hardware wise: > > CPU: AMD Duron 950 Mhz > RAM: 256 MB not sure of the brand > Hard Drive: Maxtor 5T02oH2 20GB > Motherboard: Soyo with a Via Chipset > WAN NIC: Onboard Realtek (I think it's a RealTek) on a Soyo > LAN NIC: Linksys LNE100TX unused interface > Opt 1 (DMZ) NIC: FA310TX Rev2 this is where my servers are > Opt 2 NIC: FA 311 Rev C-1 > > Hope some of this helps.. > > --Todd > > > ----- Original Message ----- > From: "Mojo Jojo" <[EMAIL PROTECTED]> > To: <support@pfsense.com> > Sent: Monday, September 26, 2005 6:14 AM > Subject: Re: [pfSense Support] Argg! My PfSense just died! > > > > > > OK fellas, once again you are all very helpful.. Sorry for my rant > > earlier, I just got the wrong idea I guess... > > > > I will take all the questions and suggestions as well as any more you can > > provide today and take care of all of them later today. > > > > Just send me any questions you have about my install and I will dig, dig, > > dig and get you all I can. I would love to fix this.. > > > > Some quick info: > > > > WAN = T1 Router (Ascend) static IP > > LAN = Nothing hooked up here > > OPT 1 (DMZ) = Server network with approx 8-10 servers (web, mail, Asterisk > > etc.) BRIDGED TO WAN > > OPT 2 = Unused at the moment > > > > Hardware brands and specifics I am not sure of at the moment, I will have > > to dig a little more. Off the top of my head it looks something like this: > > > > AMD 2200+ CPU (Could be way off here, I have to check > > 512 Mb RAM (Corsair I think) > > Motherboard (via chipset, I think) > > WAN NIC (Onboard Yuck, I know) > > 3 other cards consist of 2 Netgear and 1 Linksys but I don't remember > > which are assigned to which at the moment. > > > > I will get more specifics later. > > > > The big thing to remember here is this.. When this happens, the GUI still > > works, I just can't get to any of the servers behind PfSense.. Restarting > > PfSense with /etc/rc.bootup doesn't fix anything, only a full reboot. > > > > What logs should I look at for a clue? > > > > I wonder if I should stick a PC on the LAN interface just to see if I can > > get to it when this happens again. Maybe it's just the bridging from mt > > WAN to OPT 1 that takes a dump? > > > > > > > > ----- Original Message ----- > > From: "Fleming, John (ZeroChaos)" <[EMAIL PROTECTED]> > > To: <support@pfsense.com> > > Sent: Monday, September 26, 2005 12:55 AM > > Subject: RE: [pfSense Support] Argg! My PfSense just died! > > > > > > I'd like to see dmesg output from the new box as well. What kind of nics > > do you have in this box? It really sounds like we need someway to gather > > as much information as possible during the next outage without rebooting > > the box. Off the top of my head some of the things I would like to know > > are.. > > Send the output of these commands. If you can just paste them into the > > console. Each command should append to the log file. > > ( dmesg ; echo ) >> /usr/crash.info > > ( netstat -in ; echo ) >> /usr/crash.info > > ( netstat -m ; echo ) >> /usr/crash.info > > ( top ; echo ) >> /usr/crash.info > > ( ps -ax ; echo ) >> /usr/crash.info > > ( find / -name "*.core" -print ; echo ) >> /usr/crash.info > > ( df -h ; echo ) >> /usr/crash.info > > ( ls -l /var/crash/* ; echo ) >> /usr/crash.info > > > > I'm also thinking something like this should be in a diag menu and the > > ssh/serial console. That way we could grab some kind of snap shot of > > hosed systems before it gets rebooted. > > > > > > > > > > -----Original Message----- > > From: Chris Buechler [mailto:[EMAIL PROTECTED] > > Sent: Sunday, September 25, 2005 10:50 PM > > To: support@pfsense.com > > Subject: Re: [pfSense Support] Argg! My PfSense just died! > > > > sending your entire config.xml to the list or Scott directly if you need > > > > to keep it private would likely help very much. > > > > > > Scott Ullrich wrote: > > > >>On 9/25/05, Mojo Jojo <[EMAIL PROTECTED]> wrote: > >>[snip] > >> > >> > >>>I have no motive here other than to use the product and possibly help > > where > >>>I can. It almost seems like you feel I am bashing PfSense or > > something, not > >>>really sure. Seems like a strange answer though if this is not your > >>>thought.. > >>> > >>> > >> > >>I do not feel you are bashing pfSense. It's funny because this is > >>going to be difficult to track down without nobody else having the > >>same issue. > >> > >>[snip] > >> > >>Are you running dhcp on the wan? What else can you tell us about the > >>install because I didn't see too much of this type of information when > >>I went back through my archives. > >> > >>Scott > >> > >>--------------------------------------------------------------------- > >>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] > > > > > --------------------------------------------------------------------- > 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]
