Re: Followup On Perl Dumping Core
On 6/18/2010 2:45 PM, Tim Daneliuk wrote: On 6/18/2010 2:33 PM, Greg Larkin wrote: Tim Daneliuk wrote: On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. Hi Tim, I apologize if you mentioned this before, but are you using Spamassassin with mailscanner? This message describes a problem that sounds very similar to yours, and there's a solution included: http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html Hope that helps, Greg Aha! Der plot thickens. I am indeed running SA. I've just clobbered /root/.spamassassin/* This may well be the issue ... Many thanks. It would seem that this was the problem. Clearing out the old contents of .spamassassin made the perl SEGVs stop... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Followup On Perl Dumping Core
I have rebuilt world to today's 8.1-PRERELEASE sources I have forced a rebuild of every port on the system with: portupgrade -f * I have rebooted. I am still seeing these log messages: (perl5.10.1), uid 0: exited on signal 11 The long running perl processes on this system are associated with MailScanner. MailScanner does periodically restart itself thereby killing these perl processes, but I wouldn't expect this to throw a signal 11... Ideas anyone? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
Hi, On 6/18/10 2:24 PM, Tim Daneliuk wrote: I have rebuilt world to today's 8.1-PRERELEASE sources I have forced a rebuild of every port on the system with: portupgrade -f * I have rebooted. I am still seeing these log messages: (perl5.10.1), uid 0: exited on signal 11 The long running perl processes on this system are associated with MailScanner. MailScanner does periodically restart itself thereby killing these perl processes, but I wouldn't expect this to throw a signal 11... Ideas anyone? Have you recently upgraded perl without running perl-after-upgrade afterwards? Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/2010 1:27 PM, Glen Barber wrote: Hi, On 6/18/10 2:24 PM, Tim Daneliuk wrote: I have rebuilt world to today's 8.1-PRERELEASE sources I have forced a rebuild of every port on the system with: portupgrade -f * I have rebooted. I am still seeing these log messages: (perl5.10.1), uid 0: exited on signal 11 The long running perl processes on this system are associated with MailScanner. MailScanner does periodically restart itself thereby killing these perl processes, but I wouldn't expect this to throw a signal 11... Ideas anyone? Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? Thanks, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/10 2:30 PM, Tim Daneliuk wrote: Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? portupgrade does not do this for you. If you don't remember, I'd suggest running it. Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/2010 1:34 PM, Glen Barber wrote: On 6/18/10 2:30 PM, Tim Daneliuk wrote: Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? portupgrade does not do this for you. If you don't remember, I'd suggest running it. Regards, Well, I just did, and it reports no changes were necessary... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/2010 1:52 PM, Tim Daneliuk wrote: On 6/18/2010 1:34 PM, Glen Barber wrote: On 6/18/10 2:30 PM, Tim Daneliuk wrote: Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? portupgrade does not do this for you. If you don't remember, I'd suggest running it. Regards, Well, I just did, and it reports no changes were necessary... I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwbxFQACgkQ8Mjk52CukIwOFACfWpg3voC/YqPXRWLS6NHyQZxy F0UAn178RJ7+eQvU7kygDSB24fZMsayL =QJmo -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. --- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Daneliuk wrote: On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. Hi Tim, I apologize if you mentioned this before, but are you using Spamassassin with mailscanner? This message describes a problem that sounds very similar to yours, and there's a solution included: http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMG8on0sRouByUApARAmSwAKCnYeOhGo4OOKFGr2irxGAEJadVewCgh4aC 8XQhVF7fINhH5ADDOjNhTCg= =FriQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Followup On Perl Dumping Core
On 6/18/2010 2:33 PM, Greg Larkin wrote: Tim Daneliuk wrote: On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. Hi Tim, I apologize if you mentioned this before, but are you using Spamassassin with mailscanner? This message describes a problem that sounds very similar to yours, and there's a solution included: http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html Hope that helps, Greg Aha! Der plot thickens. I am indeed running SA. I've just clobbered /root/.spamassassin/* This may well be the issue ... Many thanks. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
