Re: [pfSense] pfsens 2.1-beta1 Higly unstable
yep, i created a bug which ha been immediately closed : Issue #2937 has been updated by Jim P. • Status changed from New to Rejected Not enough information here for a legitimate bug report. Please discuss it on the forum first and if an actual bug is discovered, then it can be addressed. I'll be happy to give any further information but i've to know which one … i'll stick to J. Alet solution and wait in the dark until the problem turns solved. Le 5 avr. 2013 à 14:21, Chris Buechler c...@pfsense.org a écrit : On Fri, Apr 5, 2013 at 7:19 AM, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote: kernel panic. hard reboot needed.( You submit a crash report? ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Christophe Ségui Responsable informatique Institut de Mathématiques de Toulouse Université de Toulouse - CNRS 118 Route de Narbonne 31062 Toulouse Cedex 09 Tel : (+33) 5 61 55 63 78 christophe.se...@math.univ-toulouse.fr http://www.math.univ-toulouse.fr smime.p7s Description: S/MIME cryptographic signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
On 4/8/2013 11:04 AM, Christophe Ségui wrote: yep, i created a bug which ha been immediately closed : Issue #2937 has been updated by Jim P. • Status changed from New to Rejected Not enough information here for a legitimate bug report. Please discuss it on the forum first and if an actual bug is discovered, then it can be addressed. I'll be happy to give any further information but i've to know which one … i'll stick to J. Alet solution and wait in the dark until the problem turns solved. That's not what he meant by a crash report. he meant, in the GUI, after you experience a crash, it will offer to submit the crash report to our servers automatically. We need the full crash dump (panic message, backtrace, logs, etc) in order to have any idea what happened. Without the crash report, we can't determine what happened. You said No crash log in the ticket, that crash log is the information we need to diagnose the problem, that's what he was asking for, not a bug report. Jim ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
Le 8 avr. 2013 à 17:16, Jim Pingle li...@pingle.org a écrit : On 4/8/2013 11:04 AM, Christophe Ségui wrote: yep, i created a bug which ha been immediately closed : Issue #2937 has been updated by Jim P. • Status changed from New to Rejected Not enough information here for a legitimate bug report. Please discuss it on the forum first and if an actual bug is discovered, then it can be addressed. I'll be happy to give any further information but i've to know which one … i'll stick to J. Alet solution and wait in the dark until the problem turns solved. That's not what he meant by a crash report. he meant, in the GUI, after you experience a crash, it will offer to submit the crash report to our servers automatically. We need the full crash dump (panic message, backtrace, logs, etc) in order to have any idea what happened. Without the crash report, we can't determine what happened. You said No crash log in the ticket, that crash log is the information we need to diagnose the problem, that's what he was asking for, not a bug report. ok, thanks for the explanation and sorry for my misunderstanding. Jim ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Christophe Ségui Responsable informatique Institut de Mathématiques de Toulouse Université de Toulouse - CNRS 118 Route de Narbonne 31062 Toulouse Cedex 09 Tel : (+33) 5 61 55 63 78 christophe.se...@math.univ-toulouse.fr http://www.math.univ-toulouse.fr smime.p7s Description: S/MIME cryptographic signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
Hi, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote:I'tried pfsense 2.1-BE5A1 as router/firewall (ospf is used for wan) and /22 network as internal network. With PF activated, the node crash after 2 hours up … since pf is deactivated, node stays up (routing functionnalities are OK). Does someone experienced the same issue ?Here we are using 2.1BETA1 for a long time in production. What we've learnt is that from one day to the other, fixes are incorporated, but sometimes fixes break something else, so while we used to upgrade everyday to benefit from the latest fixes, we now stay with a version which mostly works for us : 2.1-BETA1 (amd64) built on Thu Feb 28 04:29:38 EST 2013 Since we're running a two nodes cluster, testing a new release is easy but takes time : upgrade the slave, shutdown the master, see if all works as expected. If not, restore the full backup, else upgrade the master as well. But this can be very very time consuming especially due to pfSense's full backup (when upgrading from the GUI) which saves, slowly, almost everything including Squid's cache content. We're still stuck with some minor problems but this version doesn't crash at least... We've got planned downtime tomorrow, and planned to try an upgrade, but reading your message I think we'll wait a bit more :-) So my advice to you would be to try daily upgrades until you'll find one that works, and stay with it until a BETA2 or an RC is published. bye -- Jerome Alet___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
Le 5 avr. 2013 à 12:02, Chris Buechler c...@pfsense.org a écrit : On Fri, Apr 5, 2013 at 4:59 AM, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote: Hi, I'tried pfsense 2.1-BE5A1 as router/firewall (ospf is used for wan) and /22 network as internal network. With PF activated, the node crash after 2 hours up … since pf is deactivated, node stays up (routing functionnalities are OK). Does someone experienced the same issue ? There are thousands of people running it in production with no issue, not a general problem. Define crash, does it actually kernel panic and reboot? Or just stop accepting new connections? The latter, you're likely running out of states. kernel panic. hard reboot needed.( ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Christophe Ségui Responsable informatique Institut de Mathématiques de Toulouse Université de Toulouse - CNRS 118 Route de Narbonne 31062 Toulouse Cedex 09 Tel : (+33) 5 61 55 63 78 christophe.se...@math.univ-toulouse.fr http://www.math.univ-toulouse.fr smime.p7s Description: S/MIME cryptographic signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
On Fri, Apr 5, 2013 at 7:19 AM, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote: kernel panic. hard reboot needed.( You submit a crash report? ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] pfsens 2.1-beta1 Higly unstable
Hi, Yes, sounds like a good way to test new relaese in production. Unfortunately, we use a single node here :/ thanks anyway Christophe Le 5 avr. 2013 à 12:12, jerome alet jerome.a...@univ-nc.nc a écrit : Hi, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote: I'tried pfsense 2.1-BE5A1 as router/firewall (ospf is used for wan) and /22 network as internal network. With PF activated, the node crash after 2 hours up … since pf is deactivated, node stays up (routing functionnalities are OK). Does someone experienced the same issue ? Here we are using 2.1BETA1 for a long time in production. What we've learnt is that from one day to the other, fixes are incorporated, but sometimes fixes break something else, so while we used to upgrade everyday to benefit from the latest fixes, we now stay with a version which mostly works for us : 2.1-BETA1 (amd64) built on Thu Feb 28 04:29:38 EST 2013 Since we're running a two nodes cluster, testing a new release is easy but takes time : upgrade the slave, shutdown the master, see if all works as expected. If not, restore the full backup, else upgrade the master as well. But this can be very very time consuming especially due to pfSense's full backup (when upgrading from the GUI) which saves, slowly, almost everything including Squid's cache content. We're still stuck with some minor problems but this version doesn't crash at least... We've got planned downtime tomorrow, and planned to try an upgrade, but reading your message I think we'll wait a bit more :-) So my advice to you would be to try daily upgrades until you'll find one that works, and stay with it until a BETA2 or an RC is published. bye -- Jerome Alet ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Christophe Ségui Responsable informatique Institut de Mathématiques de Toulouse Université de Toulouse - CNRS 118 Route de Narbonne 31062 Toulouse Cedex 09 Tel : (+33) 5 61 55 63 78 christophe.se...@math.univ-toulouse.fr http://www.math.univ-toulouse.fr smime.p7s Description: S/MIME cryptographic signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
