Re: [pfSense Support] rrdtool core dump
On Oct 30, 2007 5:15 PM, Rainer Duffner [EMAIL PROTECTED] wrote: Wally Mono wrote: Yeah, this could probably be improved. On the other hand, once you've written it to flash or CD, it's not obvious anymore anyway, which version you have in front of you - unless you label the media... The System page tells you which version and the build date. The build date is useful for tracking snapshots. sai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Scott Ullrich wrote: On 10/29/07, Wally Mono [EMAIL PROTECTED] wrote: I realize this is bad form, but how do I actually get someone to respond to an apparent problem? I tried the contact on the web page and was referred here. What other hoops must I jump through to get someone to give me what probably amounts to a very simple answer? All due respect, gratitude and adulation for the software is explicitly implied in this message. How can you expect someone to reply over the weekend immediately? Believe it or not developers do have a life outside of their keyboards. Either way we will look into the problem. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chris, I tried renaming the OPT1 interface (reverting FROM ATT back TO OPT1 made the core dump go away in the first place) to ATT, but it does not appear to be dumping core at this point, only doing the 'exited on signal 11' thing. (Next Morning) I rebooted the router and it resumed dumping core. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
On 10/31/07, Wally Mono [EMAIL PROTECTED] wrote: Chris, I tried renaming the OPT1 interface (reverting FROM ATT back TO OPT1 made the core dump go away in the first place) to ATT, but it does not appear to be dumping core at this point, only doing the 'exited on signal 11' thing. (Next Morning) I rebooted the router and it resumed dumping core. Your RRD databases are corrupted per [EMAIL PROTECTED]From a shell do this: rm -rf /var/db/rrd/* Now click save on the Interfaces - LAN page. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Scott Ullrich wrote: On 10/31/07, Wally Mono [EMAIL PROTECTED] wrote: Chris, I tried renaming the OPT1 interface (reverting FROM ATT back TO OPT1 made the core dump go away in the first place) to ATT, but it does not appear to be dumping core at this point, only doing the 'exited on signal 11' thing. (Next Morning) I rebooted the router and it resumed dumping core. Your RRD databases are corrupted per [EMAIL PROTECTED]From a shell do this: rm -rf /var/db/rrd/* Now click save on the Interfaces - LAN page. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Scott, You are the man. It worked as you expected. Thanks for your help and Chris and everyone else who pitched in on this issue. Sorry for the impatience, as well. You got a quick fix for that? ;) Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Rainer Duffner wrote: Am 30.10.2007 um 00:39 schrieb Wally Mono: Rainer, Thanks so much for your response. To be clear, I am running the live cd version, so there is nothing to re-install. Are you saying just reconfigure from scratch? Would this imply some sort of corruption in the configuration file? Ah. Can't you just try a newer snapshot? (Yours said to be from August) Just to be sure it isn't fixed already. I know that the devs don't like to debug problems with months-old snapshots I just checked - I'm running an August 8th snapshot on a WRAP and I don't have this problem. I'm too lazy to update regularly (I've got to dismantle the WRAP completely and I don't like to do that too often) cheers, Rainer So if I understand you correctly, the pfSense-1.2-RC2-Embedded.img.gz on http://pfsense.untouchable.net/downloads/pfSense-1.2-RC2-Embedded.img.gz on the download site today is not the same as the one I downloaded in August? That seems a little problematic. Perhaps I COULD contribute something to this project in the way of version control advice; put a build # on the release! It could be yy.mm.dd. I'm not sure this is actually how they are released, but I have always been a little annoyed and leery of the fact that the timestamp on the files in the download area always have the current date. If indeed the current RC2 is actually a silently rolling version, some indication needs to be place either on it (my preference) or, at the very least, in a readme file called something like AA_VERSION.txt I will try burning a new copy this weekend. FWIW I have another box running the identical version, but not using OPT1(multiwan) and I do not have this same problem of the rrdtool crashing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] rrdtool core dump
Date: Tue, 30 Oct 2007 06:42:09 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] rrdtool core dump Rainer Duffner wrote: Am 30.10.2007 um 00:39 schrieb Wally Mono: Rainer, Thanks so much for your response. To be clear, I am running the live cd version, so there is nothing to re-install. Are you saying just reconfigure from scratch? Would this imply some sort of corruption in the configuration file? Ah. Can't you just try a newer snapshot? (Yours said to be from August) Just to be sure it isn't fixed already. I know that the devs don't like to debug problems with months-old snapshots I just checked - I'm running an August 8th snapshot on a WRAP and I don't have this problem. I'm too lazy to update regularly (I've got to dismantle the WRAP completely and I don't like to do that too often) cheers, Rainer So if I understand you correctly, the pfSense-1.2-RC2-Embedded.img.gz on http://pfsense.untouchable.net/downloads/pfSense-1.2-RC2-Embedded.img.gz on the download site today is not the same as the one I downloaded in August? That seems a little problematic. Perhaps I COULD contribute something to this project in the way of version control advice; put a build # on the release! It could be yy.mm.dd. I'm not sure this is actually how they are released, but I have always been a little annoyed and leery of the fact that the timestamp on the files in the download area always have the current date. If indeed the current RC2 is actually a silently rolling version, some indication needs to be place either on it (my preference) or, at the very least, in a readme file called something like AA_VERSION.txt I will try burning a new copy this weekend. FWIW I have another box running the identical version, but not using OPT1(multiwan) and I do not have this same problem of the rrdtool crashing. The build server rebuilds the image every 2 hours incorporating CVS changes that are going on. after 1.2 release they are already looking at incorporating a build version into the image nameto be able to discern whether your version is actually out of date. its an issue with the build server that they are treating as a low priority until the next full release. to actually see what changes are currently incorporated, check the CVStrac website at http://cvstrac.pfsense.com/timeline so in essence, build version issue is old news and will be fixed eventually. until then, the image on the snapshots server will always be the latest and greatest even if version name doesnt change. -Sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Windows Live Hotmail and Microsoft Office Outlook – together at last. Get it now. http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033
Re: [pfSense Support] rrdtool core dump
Wally Mono wrote: So if I understand you correctly, the pfSense-1.2-RC2-Embedded.img.gz on http://pfsense.untouchable.net/downloads/pfSense-1.2-RC2-Embedded.img.gz on the download site today is not the same as the one I downloaded in August? No. RC2 is still RC2. Snapshots is what the previous person was referring to, which are not found on the mirrors. There haven't been many, if any rrdtool changes so I doubt if using a snapshot would change anything. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Chris Buechler wrote: Wally Mono wrote: So if I understand you correctly, the pfSense-1.2-RC2-Embedded.img.gz on http://pfsense.untouchable.net/downloads/pfSense-1.2-RC2-Embedded.img.gz on the download site today is not the same as the one I downloaded in August? No. RC2 is still RC2. Snapshots is what the previous person was referring to, which are not found on the mirrors. There haven't been many, if any rrdtool changes so I doubt if using a snapshot would change anything. sorry to reply to myself, I forgot one thing - do you have a reliable way to replicate the core dump? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Wally Mono wrote: Wally Mono wrote: I am continuously getting these: kernel: pid # (rrdtool), uid 0: exited on signal 11 (core dumped) about 1 a minute. Any ideas why? More importantly how do I make it stop? I'm running: 1.2-RC2 built on Fri Aug 17 17:46:06 EDT 2007multi-wan. 1 static, 1 DHCP router provides DHCP 128 meg of ram @ 42% usage I really don't need rrdtool. How do I just disable it for now? Is this a problem? Seems like it would take up space at the least. Any insight would be appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] After researching a little further I find a bug (http://cvstrac.pfsense.com/tktview?tn=898) that might apply; I DID change the name of OPT1 to ATT. I changed it back and while I am still getting kernel: pid # (rrdtool), uid 0: exited on signal 11 there is no longer an accompanying core dump. Does this help? I would sure like to turn off this noise in my logs, as I am sure that it is eating up memory and slowing performance. Adding more memory is not a fix to the underlying problem unless that is what is causing the rrdtool to fail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I realize this is bad form, but how do I actually get someone to respond to an apparent problem? I tried the contact on the web page and was referred here. What other hoops must I jump through to get someone to give me what probably amounts to a very simple answer? All due respect, gratitude and adulation for the software is explicitly implied in this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Wally Mono wrote: I realize this is bad form, but how do I actually get someone to respond to an apparent problem? I tried the contact on the web page and was referred here. What other hoops must I jump through to get someone to give me what probably amounts to a very simple answer? All due respect, gratitude and adulation for the software is explicitly implied in this message. No offense taken. You probably don't want to hear that but: could you backup your config and re-install? cheers, Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
On 10/29/07, Wally Mono [EMAIL PROTECTED] wrote: I realize this is bad form, but how do I actually get someone to respond to an apparent problem? I tried the contact on the web page and was referred here. What other hoops must I jump through to get someone to give me what probably amounts to a very simple answer? All due respect, gratitude and adulation for the software is explicitly implied in this message. How can you expect someone to reply over the weekend immediately? Believe it or not developers do have a life outside of their keyboards. Either way we will look into the problem. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Rainer Duffner wrote: Wally Mono wrote: I realize this is bad form, but how do I actually get someone to respond to an apparent problem? I tried the contact on the web page and was referred here. What other hoops must I jump through to get someone to give me what probably amounts to a very simple answer? All due respect, gratitude and adulation for the software is explicitly implied in this message. No offense taken. You probably don't want to hear that but: could you backup your config and re-install? cheers, Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Rainer, Thanks so much for your response. To be clear, I am running the live cd version, so there is nothing to re-install. Are you saying just reconfigure from scratch? Would this imply some sort of corruption in the configuration file? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Am 30.10.2007 um 00:39 schrieb Wally Mono: Rainer, Thanks so much for your response. To be clear, I am running the live cd version, so there is nothing to re-install. Are you saying just reconfigure from scratch? Would this imply some sort of corruption in the configuration file? Ah. Can't you just try a newer snapshot? (Yours said to be from August) Just to be sure it isn't fixed already. I know that the devs don't like to debug problems with months-old snapshots I just checked - I'm running an August 8th snapshot on a WRAP and I don't have this problem. I'm too lazy to update regularly (I've got to dismantle the WRAP completely and I don't like to do that too often) cheers, Rainer -- Rainer Duffner CISSP, LPI, MCSE [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] rrdtool core dump
Wally Mono wrote: I am continuously getting these: kernel: pid # (rrdtool), uid 0: exited on signal 11 (core dumped) about 1 a minute. Any ideas why? More importantly how do I make it stop? I'm running: 1.2-RC2 built on Fri Aug 17 17:46:06 EDT 2007multi-wan. 1 static, 1 DHCP router provides DHCP 128 meg of ram @ 42% usage I really don't need rrdtool. How do I just disable it for now? Is this a problem? Seems like it would take up space at the least. Any insight would be appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] After researching a little further I find a bug (http://cvstrac.pfsense.com/tktview?tn=898) that might apply; I DID change the name of OPT1 to ATT. I changed it back and while I am still getting kernel: pid # (rrdtool), uid 0: exited on signal 11 there is no longer an accompanying core dump. Does this help? I would sure like to turn off this noise in my logs, as I am sure that it is eating up memory and slowing performance. Adding more memory is not a fix to the underlying problem unless that is what is causing the rrdtool to fail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] rrdtool core dump
I am continuously getting these: kernel: pid # (rrdtool), uid 0: exited on signal 11 (core dumped) about 1 a minute. Any ideas why? More importantly how do I make it stop? I'm running: 1.2-RC2 built on Fri Aug 17 17:46:06 EDT 2007 multi-wan. 1 static, 1 DHCP router provides DHCP 128 meg of ram @ 42% usage I really don't need rrdtool. How do I just disable it for now? Is this a problem? Seems like it would take up space at the least. Any insight would be appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
