Kernel errors after upgrade from 8.1 to 8.2

Lowell Gilbert freebsd-questions-local at be-well.ilk.org
Mon May 9 16:27:34 UTC 2011


Robert Fitzpatrick <robert at webtent.org> writes:

> After following the handbook Chapter 24 to upgrade from 8.1 to 8.2, I
> am getting kernel errors for various postfix commands...
>
> May  9 08:54:13 mx3 kernel: pid 57056 (trivial-rewrite), uid 125:
> exited on signal 11
> May  9 08:56:46 mx3 kernel: pid 57086 (smtpd), uid 125: exited on signal 11
>
> I have searched the maillog and can't find any errors between restart
> and such entries as...
>
> May  9 08:54:13 mx3 postfix/master[19357]: warning: process
> /usr/local/libexec/postfix/trivial-rewrite pid 57056 killed by signal
> 11
> May  9 08:56:46 mx3 postfix/master[19357]: warning: process
> /usr/local/libexec/postfix/smtpd pid 57086 killed by signal 11
>
> I updated the ports after the reboot and did a 'portupgrade -af' after
> the kernel update, restart, etc. I had no issues performing the
> upgrade according to the handbook and the System State Comparison
> seems OK...
>
> mx3# cat outfile.ids | awk '{ print $1 }' | more
> Looking
> Fetching
> Fetching
> Inspecting
> /boot/kernel/linker.hints
> /etc/crontab
> /etc/group
> /etc/hosts
> /etc/mail/aliases
> /etc/mail/mailer.conf
> /etc/manpath.config
> /etc/master.passwd
> /etc/motd
> /etc/passwd
> /etc/pwd.db
> /etc/spwd.db
> /etc/ssh/sshd_config
> /usr/lib32
>
> I also tried 'make deinstall' for postfix and re-installed. And the
> system reports 8.2-RELEASE. All the mail for a test domain seem to be
> flowing without issue, but these kernel messages and warnings tell me
> something is wrong. Can someone suggest what to do next in finding a
> solution? Or is it best to post this to the postfix list?

Make sure to check your memory; it's probably not the culprit here, but
it's an easy thing to check and very hard to catch any other way.

When you say you re-installed postfix, did you do it from a package?
The same package as the first time?  If so, that doesn't test much of
anything.  Try rebuilding from a port, on the same machine...


More information about the freebsd-questions mailing list