Date: Wed, 29 Apr 2009 12:03:11 +0800 From: Antonio A Hilario <avahilario@gmail.com> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: Syslog doesn't start at boot Message-ID: <49F7D17F.20604@gmail.com> In-Reply-To: <200904291157.07441.doconnor@gsoft.com.au> References: <200904291157.07441.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Connor wrote: > Hi, > I have an odd problem with my 3 week old -current install - syslogd > isn't started. Or rather, it is started before lo0 is up and it fails to > start, eg.. > > Apr 29 11:13:05 inchoate kernel: /dev/ad0s3a: FILE SYSTEM CLEAN; SKIPPING CHECKS > Apr 29 11:13:05 inchoate kernel: /dev/ad0s3a: clean, 381721 free (3297 frags, 47303 blocks, 0.7% fragmentation) > Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoatevar: FILE SYSTEM CLEAN; SKIPPING CHECKS > Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoatevar: clean, 417071 free (4815 frags, 51532 blocks, 1.0% fragmentation) > Apr 29 11:13:05 inchoate kernel: /dev/ufs/inchoateusr: DEFER FOR BACKGROUND CHECKING > Apr 29 11:13:05 inchoate kernel: Apr 29 20:42:48 syslogd: bind: Can't assign requested address > Apr 29 11:13:05 inchoate kernel: Apr 29 20:42:48 syslogd: bind: Can't assign requested address > Apr 29 11:13:05 inchoate kernel: syslogd: > Apr 29 11:13:05 inchoate kernel: child pid 285 exited with return code 1 > Apr 29 11:13:05 inchoate kernel: > Apr 29 11:13:05 inchoate kernel: /etc/rc: WARNING: failed to start syslogd > Apr 29 11:13:05 inchoate kernel: Additional ABI support: > Apr 29 11:13:05 inchoate kernel: linux > Apr 29 11:13:05 inchoate kernel: . > Apr 29 11:13:05 inchoate kernel: Starting wpa_supplicant. > Apr 29 11:13:05 inchoate kernel: Starting Network: lo0 bfe0. > Apr 29 11:13:05 inchoate kernel: add net ::ffff:0.0.0.0: gateway ::1 > > I put '/etc/rc.d/syslogd restart' in rc.local but that's only a work around. > > I ran mergemaster -s and it did find a few changes (worringly) but the > rc.d ones were just removing 'noprofile' from the keyword line which I don't > think would affect things. > > Noticed that your network interface is being brought up * after * the sysklogd startup script runs. I'd try to maybe move the 'syslog_enable="YES"' directive in /etc/rc.conf to some point after the ifconfig_*=* lines.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49F7D17F.20604>