Re: [pfSense Support] Argg! My PfSense just died!
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
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
RE: [pfSense Support] Argg! My PfSense just died!
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
RE: [pfSense Support] Argg! My PfSense just died!
Did you send in your config.xml? BTW add this to the list of commands to run (at the top). ( ifconfig -a ; echo ) /usr/crash.info; -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 10:24 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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
Re: [pfSense Support] Argg! My PfSense just died!
I have not received anything. On 9/26/05, Fleming, John (ZeroChaos) [EMAIL PROTECTED] wrote: Did you send in your config.xml? BTW add this to the list of commands to run (at the top). ( ifconfig -a ; echo ) /usr/crash.info; -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 10:24 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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
Re: [pfSense Support] Argg! My PfSense just died!
Not yet guys, tryin' to keep up, had a real busy day and night :) I will try to get all this together soon and send it. Just wanted to get you the hardware info while I was in front of it this morning. Todd - Original Message - From: Scott Ullrich [EMAIL PROTECTED] To: support@pfsense.com Sent: Monday, September 26, 2005 11:48 AM Subject: Re: [pfSense Support] Argg! My PfSense just died! I have not received anything. On 9/26/05, Fleming, John (ZeroChaos) [EMAIL PROTECTED] wrote: Did you send in your config.xml? BTW add this to the list of commands to run (at the top). ( ifconfig -a ; echo ) /usr/crash.info; -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 10:24 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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
Re: [pfSense Support] Argg! My PfSense just died!
On 9/25/05, Mojo Jojo [EMAIL PROTECTED] wrote: This just happen again after about two days of uptime. Thing is, it's on totally different hardware. How different? Same CPU? Same NICS? Same power supply? [snip] Makes me think it's not hardware at this point but that's just because I have the same result with two drastically different sets of hardware. Funny that we don't get any other reports of this. Not sure where to go at this point, I may have back off of using PfSense I am sad to say. I just can't seem to make sense of the downtime I am ending up with. Ever heard of CARP? We have that you know. [snip] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Argg! My PfSense just died!
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]
Re: [pfSense Support] Argg! My PfSense just died!
On 9/25/05, Mojo Jojo [EMAIL PROTECTED] wrote: Ever heard of CARP? We have that you know. Yes, it's one of the reasons I chose your product over others.. However, I was going to set it up in case of unplanned failure of hardware or software. In this case, I am basically planning on failure because that's exactly what's happening AND it's consistent. I plan on my machines failing, so I run carp...if I didn't plan on them failing, I wouldn't :) With that said, yes it shouldn't be hanging or locking up on you. But if it does, it's likely to be an OS bug that we can't fix. I don't know what more to tell you - none of my pfSense boxes randomly hang, from time to time I've seen a kernel panic - but even that's cleaned up alot as the FreeBSD betas have stabilized. This is sort of like putting a UPS battery on a server because the power goes out every two or three days. The UPS is a good idea but it's a better idea to fix the real problem. Erm, sometimes you can't fix the power company...actually, I've never been able to fix the power company. --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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]
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]
Re: [pfSense Support] Argg! My PfSense just died!
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. Any other info needed, just let me know and I will be happy to supply it. Thanks, Todd - Original Message - From: Mojo Jojo [EMAIL PROTECTED] To: support@pfsense.com Sent: Tuesday, September 20, 2005 8:33 PM Subject: Re: [pfSense Support] Argg! My PfSense just died! I will be happy to give you all the info I have, just not sure what you need. :) Todd - Original Message - From: Scott Ullrich [EMAIL PROTECTED] To: support@pfsense.com Sent: Tuesday, September 20, 2005 1:24 PM Subject: Re: [pfSense Support] Argg! My PfSense just died! I have no idea without knowing more information. Scott On 9/20/05, Mojo Jojo [EMAIL PROTECTED] wrote: Well, I did read all of the post.. This does hopefully keep the boot issues from occurring again but.. The even bigger question I still have is why did PfSense just stop working in the middle of doing it's business? As mentioned, I made a bunch of config changes and all was fine, PF continued routing and filtering traffic to a from my servers. I made one last change which was simply an allow all in and out of a particular server, once I did this everything worked fine for about two minutes then all traffic stopped passing through Pfs. I could still move around the GUI fine but all other functions of PfS were dead as a doornail. This is scary considering I have no explanation as to why it happen. I have the box with me, fixed the boot issue and I guess I will go put it back in place at the office later and hope it doesn't die again in the middle of the night :) See what I am saying? It's not just the boot issue, it's the issue that caused me to reboot in the first place. Todd - Original Message - From: Scott Ullrich [EMAIL PROTECTED] To: support@pfsense.com Sent: Tuesday, September 20, 2005 9:44 AM Subject: Re: [pfSense Support] Argg! My PfSense just died! Yes, someone didn't read every message when they said they did :P We have no idea of the cause. We're still looking. But this should prevent it from happening again... If not we have a huge kernel / ufs issue on our hands. Scott On 9/20/05, Mojo Jojo [EMAIL PROTECTED] wrote: Nevermind, I just saw this which should keep this from happening again. Thanks! ## Everyone if you can go to a shell (option 8, and issue): chmod a-w /boot/loader.rc chflags schg /boot/loader.rc ## - Original Message - From: Mojo Jojo To: support@pfsense.com Sent: Monday, September 19, 2005 11:37 PM Subject: Re: [pfSense Support] Argg! My PfSense just died! OK, none of that happen to me either. Just trying to dig and see if I can figure out what happen so I can feel good about moving forward with PfSense. It's not too comforting I guess to just fix it and move on, my brain wants to find a reason I guess. Thanks for any help anyone can offer, otherwise I will just have hope it doesn't happen again. Todd - Original Message - From: Bill Marquette To: support@pfsense.com Sent: Monday, September 19, 2005 11:28 PM Subject: Re: [pfSense Support] Argg! My PfSense just died! On 9/19/05, Mojo Jojo [EMAIL PROTECTED] wrote: Any idea why my Pf died in the middle of running? I didn't do an upgrade, it was a system running on a fresh install of 0.84 days before. Also, besided the booting problem, I am wondering why it just stopped working which is what caused me to reboot it in the first place. Thanks for any insight on this.. We've had reports on the IRC channel of this happening after a power hit, or other crash too. --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED
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]
Re: [pfSense Support] Argg! My PfSense just died!
One nic only? How about system logs? Console messages? Scott On 9/21/05, Chris Buechler [EMAIL PROTECTED] wrote: 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]
Re: [pfSense Support] Argg! My PfSense just died!
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]
Re: [pfSense Support] Argg! My PfSense just died!
When it happens again, try: pfctl -f /tmp/rules.debug from a shell. It smells like something bad hardware + software combination wise. Scott On 9/21/05, Mojo Jojo [EMAIL PROTECTED] wrote: I have never ever seen a box just all of the sudden stop working. Now you have :) Maybe I missed the point you were trying to make here. I am sure it stops passing traffic to my DMZ (OPT 2) interface and I am also sure that the GUI and SSH continue to operate. Additionally I am sure that /etc/rc.bootup at the shell does not change anything at all once the machine is in this state and that only a reboot brings it all back. As for console messages, I have not been in front of the machine at the console to see if there were any. This has happened twice so far, the first time after 4 days of uptime and the second after about 4 or 6 hours of uptime (can't remember exactly). Todd - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Argg! My PfSense just died!
Oh yes, GUI still constantly blows up on me. Not sure if this is related to my issues or not. Interestingly, when the GUI blows up the box continues all other functions perfectly and passes traffic as normal. /etc/rc.bootup brings my GUI back up each time. Lastly, just wanted to mention again that I am not here to complain, just to give info to you guys to: A- Help with the development of the product B- Help me personally get a production PfSense system stable enough to rely on C- Possibly help others having the same issues. If my nagging is not welcome, I can certainly tone it down. Todd - Original Message - From: Mojo Jojo [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 11:32 AM Subject: Re: [pfSense Support] Argg! My PfSense just died! See my last message regarding what NICS are plugged in, I didn't explain that quite right earlier :) As for logs, the GUI on shows the last 100 or so log entries (even when I tell it to give me more, I think). With log viewing from the GUI limited I assume I need to look at some logs at the shell prompt. What are the names and locations of the logs that would be useful for me to look at? Thanks! Todd - Original Message - From: Scott Ullrich [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 9:31 AM Subject: Re: [pfSense Support] Argg! My PfSense just died! One nic only? How about system logs? Console messages? Scott On 9/21/05, Chris Buechler [EMAIL PROTECTED] wrote: 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]
Re: [pfSense Support] Argg! My PfSense just died!
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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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]
Re: [pfSense Support] Argg! My PfSense just died!
Nowhere near strapped for memory. If you have extra nic cards, I would change those out for different ones. On 9/21/05, Mojo Jojo [EMAIL PROTECTED] wrote: 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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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
Re: [pfSense Support] Argg! My PfSense just died!
$ netstat -m 294/486/780 mbufs in use (current/cache/total) 263/143/406/4800 mbuf clusters in use (current/cache/total/max) 0/3/1456 sfbufs in use (current/peak/max) 599K/407K/1007K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 7 calls to protocol drain routines $ netstat -in NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll fxp0* 1500 Link#1 00:03:47:70:0d:5a0 00 0 0 dc01500 Link#2 00:12:17:55:3d:dc0 00 0 0 dc01500 fe80:2::212:1 fe80:2::212:17ff:0 - 4 - - dc01500 192.168.1 192.168.1.1 0 - 0 - - dc11500 Link#3 00:12:17:55:00:1c 2469246 0 3370226 0 0 dc11500 fe80:3::212:1 fe80:3::212:17ff:0 - 4 - - dc11500 **REMOVED IP** **REMOVED IP** 283 - 1748 - - dc21500 Link#4 00:12:17:55:00:18 3883347 0 2474537 0 0 dc21500 fe80:4::212:1 fe80:4::212:17ff:0 - 4 - - dc3* 1500 Link#5 00:12:17:55:00:100 00 0 0 pflog 33208 Link#6 0 00 0 0 pfsyn 2020 Link#7 0 00 0 0 lo0 16384 Link#8 0 00 0 0 lo0 16384 ::1/128 ::1 0 - 0 - - lo0 16384 fe80:8::1/64 fe80:8::10 - 0 - - lo0 16384 127 127.0.0.10 - 0 - - bridg 1500 Link#9 ac:de:48:4e:3f:64 6333840 0 5844759 0 0 - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 11:53 AM Subject: RE: [pfSense Support] Argg! My PfSense just died! Might be a long show but also get the output of netstat -m And netstat -in -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 11:47 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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
RE: [pfSense Support] Argg! My PfSense just died!
Is that a quad dc card? Output looks fine. Did you send dmesg output? -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 12:04 PM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! $ netstat -m 294/486/780 mbufs in use (current/cache/total) 263/143/406/4800 mbuf clusters in use (current/cache/total/max) 0/3/1456 sfbufs in use (current/peak/max) 599K/407K/1007K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 7 calls to protocol drain routines $ netstat -in NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll fxp0* 1500 Link#1 00:03:47:70:0d:5a0 00 0 0 dc01500 Link#2 00:12:17:55:3d:dc0 00 0 0 dc01500 fe80:2::212:1 fe80:2::212:17ff:0 - 4 - - dc01500 192.168.1 192.168.1.1 0 - 0 - - dc11500 Link#3 00:12:17:55:00:1c 2469246 0 3370226 0 0 dc11500 fe80:3::212:1 fe80:3::212:17ff:0 - 4 - - dc11500 **REMOVED IP** **REMOVED IP** 283 - 1748 - - dc21500 Link#4 00:12:17:55:00:18 3883347 0 2474537 0 0 dc21500 fe80:4::212:1 fe80:4::212:17ff:0 - 4 - - dc3* 1500 Link#5 00:12:17:55:00:100 00 0 0 pflog 33208 Link#6 0 00 0 0 pfsyn 2020 Link#7 0 00 0 0 lo0 16384 Link#8 0 00 0 0 lo0 16384 ::1/128 ::1 0 - 0 - - lo0 16384 fe80:8::1/64 fe80:8::10 - 0 - - lo0 16384 127 127.0.0.10 - 0 - - bridg 1500 Link#9 ac:de:48:4e:3f:64 6333840 0 5844759 0 0 - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 11:53 AM Subject: RE: [pfSense Support] Argg! My PfSense just died! Might be a long show but also get the output of netstat -m And netstat -in -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 11:47 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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
Re: [pfSense Support] Argg! My PfSense just died!
Is that a quad dc card? No, it's 4 identical Linksys cards. Did you send dmesg output? Sorry, I don't follow.. --Todd - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 12:10 PM Subject: RE: [pfSense Support] Argg! My PfSense just died! Is that a quad dc card? Output looks fine. Did you send dmesg output? -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 12:04 PM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! $ netstat -m 294/486/780 mbufs in use (current/cache/total) 263/143/406/4800 mbuf clusters in use (current/cache/total/max) 0/3/1456 sfbufs in use (current/peak/max) 599K/407K/1007K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 7 calls to protocol drain routines $ netstat -in NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll fxp0* 1500 Link#1 00:03:47:70:0d:5a0 00 0 0 dc01500 Link#2 00:12:17:55:3d:dc0 00 0 0 dc01500 fe80:2::212:1 fe80:2::212:17ff:0 - 4 - - dc01500 192.168.1 192.168.1.1 0 - 0 - - dc11500 Link#3 00:12:17:55:00:1c 2469246 0 3370226 0 0 dc11500 fe80:3::212:1 fe80:3::212:17ff:0 - 4 - - dc11500 **REMOVED IP** **REMOVED IP** 283 - 1748 - - dc21500 Link#4 00:12:17:55:00:18 3883347 0 2474537 0 0 dc21500 fe80:4::212:1 fe80:4::212:17ff:0 - 4 - - dc3* 1500 Link#5 00:12:17:55:00:100 00 0 0 pflog 33208 Link#6 0 00 0 0 pfsyn 2020 Link#7 0 00 0 0 lo0 16384 Link#8 0 00 0 0 lo0 16384 ::1/128 ::1 0 - 0 - - lo0 16384 fe80:8::1/64 fe80:8::10 - 0 - - lo0 16384 127 127.0.0.10 - 0 - - bridg 1500 Link#9 ac:de:48:4e:3f:64 6333840 0 5844759 0 0 - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 11:53 AM Subject: RE: [pfSense Support] Argg! My PfSense just died! Might be a long show but also get the output of netstat -m And netstat -in -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 11:47 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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
Re: [pfSense Support] Argg! My PfSense just died!
On 9/21/05, Mojo Jojo [EMAIL PROTECTED] wrote: Sorry, I don't follow.. cat /var/log/dmesg.boot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Argg! My PfSense just died!
:48:4e:3f:64 ## - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 12:10 PM Subject: RE: [pfSense Support] Argg! My PfSense just died! Is that a quad dc card? Output looks fine. Did you send dmesg output? -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 12:04 PM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! $ netstat -m 294/486/780 mbufs in use (current/cache/total) 263/143/406/4800 mbuf clusters in use (current/cache/total/max) 0/3/1456 sfbufs in use (current/peak/max) 599K/407K/1007K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 7 calls to protocol drain routines $ netstat -in NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll fxp0* 1500 Link#1 00:03:47:70:0d:5a0 00 0 0 dc01500 Link#2 00:12:17:55:3d:dc0 00 0 0 dc01500 fe80:2::212:1 fe80:2::212:17ff:0 - 4 - - dc01500 192.168.1 192.168.1.1 0 - 0 - - dc11500 Link#3 00:12:17:55:00:1c 2469246 0 3370226 0 0 dc11500 fe80:3::212:1 fe80:3::212:17ff:0 - 4 - - dc11500 **REMOVED IP** **REMOVED IP** 283 - 1748 - - dc21500 Link#4 00:12:17:55:00:18 3883347 0 2474537 0 0 dc21500 fe80:4::212:1 fe80:4::212:17ff:0 - 4 - - dc3* 1500 Link#5 00:12:17:55:00:100 00 0 0 pflog 33208 Link#6 0 00 0 0 pfsyn 2020 Link#7 0 00 0 0 lo0 16384 Link#8 0 00 0 0 lo0 16384 ::1/128 ::1 0 - 0 - - lo0 16384 fe80:8::1/64 fe80:8::10 - 0 - - lo0 16384 127 127.0.0.10 - 0 - - bridg 1500 Link#9 ac:de:48:4e:3f:64 6333840 0 5844759 0 0 - Original Message - From: Fleming, John (ZeroChaos) [EMAIL PROTECTED] To: support@pfsense.com Sent: Wednesday, September 21, 2005 11:53 AM Subject: RE: [pfSense Support] Argg! My PfSense just died! Might be a long show but also get the output of netstat -m And netstat -in -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 11:47 AM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! 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 SIZERES STATETIME WCPU COMMAND 6247 _pflogd 1 -580 1536K 1108K bpf 0:05 0.49% pflogd 6586 root1 -8 10 11032K 9848K piperd 0:00 0.20% php 6598 root1 139 10 2196K 1300K RUN 0:00 0.20% top 6597 root1 8 10 1620K 1156K wait 0:00 0.20% sh 264 root1 -580 6060K 3980K bpf 34:50 0.00% tcpdump 3390 root1 -580 5528K 3456K bpf 6:42 0.00% tcpdump 470 root1 760 1332K 768K select 3:17 0.00% syslogd 265 root1 -80 1188K 604K piperd 1:50 0.00% logger 3391 root1 -80 1188K 604K piperd 0:26 0.00% logger 263 _pflogd 1 -580 1536K 1036K bpf 0:08 0.00% pflogd 3388 _pflogd 1 -580 1536K 1056K bpf 0:04 0.00% pflogd 550 root1 80 232K 104K nanslp 0:01 0.00% check_reload_status 539 root1 80 1300K 840K nanslp 0:00 0.00% cron 3620 root1 80 1620K 928K wait 0:00 0.00% sh 6248 root1 -80 1188K 688K piperd 0:00 0.00% logger 121 root1 760 1208K 664K select 0:00 0.00% usbd 5883 root1 760 5580K 2088K select 0:00 0.00% sshd 555 root1 50 1632K 920K ttyin0: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
RE: [pfSense Support] Argg! My PfSense just died!
This doesn't look good. pnpbios: Bad PnP BIOS data checksum This looks bad as well. pci_link3: BIOS IRQ 11 does not match initial IRQ 9 Looks like you've got a dc nic on 9 and 11. Do you have your serial ports disabled in the BIOS? Looks like you also have a dc nic on IRQ 3. I'd bet the problems are all related to this. Maybe try a bios update and what ever that reset option is called under the pci options. It should be around the same place where you enable/disable PNPBIOS. Speaking of you might also try enable/disable PNPBIOS. -Original Message- From: Mojo Jojo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 1:45 PM To: support@pfsense.com Subject: Re: [pfSense Support] Argg! My PfSense just died! OK, I assume you wanted me to send you the output to this. Not sure, here it is anyhow. # $ cat /var/log/dmesg.boot Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-BETA4 #0: Fri Sep 9 03:28:50 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/pfSense.6 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (930.32-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,MMX,FXSR,SSE real memory = 132907008 (126 MB) avail memory = 120291328 (114 MB) pnpbios: Bad PnP BIOS data checksum wlan: mac acl policy registered ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL MUMMY on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 11 on acpi0 pci_link1: ACPI PCI Link LNKB irq 10 on acpi0 pci_link2: ACPI PCI Link LNKC irq 3 on acpi0 pci_link3: ACPI PCI Link LNKD irq 9 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82810E (i810E GMCH) SVGA controller mem 0xf800-0xfbff,0xffa8-0xffaf irq 11 at device 1.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci_link3: BIOS IRQ 11 does not match initial IRQ 9 pci1: ACPI PCI bus on pcib1 fxp0: Intel 82559 Pro/100 Ethernet port 0xdf00-0xdf3f mem 0xff8ef000-0xff8e,0xff70-0xff7f irq 9 at device 1.0 on pci1 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:70:0d:5a dc0: ADMtek AN985 10/100BaseTX port 0xde00-0xdeff mem 0xff8ff000-0xff8ff3ff irq 11 at device 8.0 on pci1 miibus1: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:12:17:55:3d:dc dc1: ADMtek AN985 10/100BaseTX port 0xd000-0xd0ff mem 0xff8ff400-0xff8ff7ff irq 10 at device 9.0 on pci1 miibus2: MII bus on dc1 ukphy1: Generic IEEE 802.3u media interface on miibus2 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: Ethernet address: 00:12:17:55:00:1c dc2: ADMtek AN985 10/100BaseTX port 0xd400-0xd4ff mem 0xff8ff800-0xff8ffbff irq 3 at device 10.0 on pci1 miibus3: MII bus on dc2 ukphy2: Generic IEEE 802.3u media interface on miibus3 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: Ethernet address: 00:12:17:55:00:18 dc3: ADMtek AN985 10/100BaseTX port 0xd800-0xd8ff mem 0xff8ffc00-0xff8f irq 9 at device 11.0 on pci1 miibus4: MII bus on dc3 ukphy3: Generic IEEE 802.3u media interface on miibus4 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc3: Ethernet address: 00:12:17:55:00:10 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH UDMA66 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: Intel 82801AA (ICH) USB controller port 0xef80-0xef9f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801AA (ICH) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: serial bus, SMBus at device 31.3 (no driver attached) speaker0: PC speaker port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: floppy drive controller port 0x3f0-0x3f1,0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc8fff on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem
Re: [pfSense Support] Argg! My PfSense just died!
On Sep 19, 2005, at 8:46 PM, Mojo Jojo wrote: Running on a 900 or so Mhz processor inside of a Dell desktop type PC. boot to your dell utility partition (I hope you didn't zap that when you installed pfSense). then run the system diagnostics. you probably want to turn off interactive tests so it checks out most of your system without bothering you. i'll bet it finds some hardware fault. freebsd works extremely well on most dell hardware as it is quite generic. Vivek Khera, Ph.D. +1-301-869-4449 x806 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Argg! My PfSense just died!
OK, I have read every post within this thread. Thing I don't understand is this.. All the people who had trouble mentioned it happen during an upgrade.. So, question is.. Any idea why my Pf died in the middle of running? I didn't do an upgrade, it was a system running on a fresh install of 0.84 days before. Also, besided the booting problem, I am wondering why it just stopped working which is what caused me to reboot it in the first place. Thanks for any insight on this.. Todd - Original Message - From: Scott Ullrich [EMAIL PROTECTED] To: support@pfsense.com Sent: Monday, September 19, 2005 9:36 PM Subject: Re: [pfSense Support] Argg! My PfSense just died! This thread is played out now. Solutions and everything else is located at: http://www.mail-archive.com/support%40pfsense.com/msg01108.html On 9/19/05, Vivek Khera [EMAIL PROTECTED] wrote: On Sep 19, 2005, at 8:46 PM, Mojo Jojo wrote: Running on a 900 or so Mhz processor inside of a Dell desktop type PC. boot to your dell utility partition (I hope you didn't zap that when you installed pfSense). then run the system diagnostics. you probably want to turn off interactive tests so it checks out most of your system without bothering you. i'll bet it finds some hardware fault. freebsd works extremely well on most dell hardware as it is quite generic. Vivek Khera, Ph.D. +1-301-869-4449 x806 - 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]
Re: [pfSense Support] Argg! My PfSense just died!
On 9/19/05, Mojo Jojo [EMAIL PROTECTED] wrote: Any idea why my Pf died in the middle of running? I didn't do an upgrade, itwas a system running on a fresh install of 0.84 days before.Also, besided the booting problem, I am wondering why it just stopped working which is what caused me to reboot it in the first place.Thanks for any insight on this.. We've had reports on the IRC channel of this happening after a power hit, or other crash too. --Bill
