Hi,
I've been experiencing a strange problem with one of my hosts (I think, since
upgrading to 9.1-RELEASE). The host does not start several services after
booting, especially no getty(8)s and no cron(8). When starting these services
manually, it does so without flaw (you can login via ssh).
I thought about that maybe being a hardware failure, as this host also
refuses to boot 9.2-RELEASE because of something timer-specific.
Now, upgrading two other hosts to 9.2-RELEASE, one of them with the same
hardware, they suddenly show the same behaviour: No getty(8)s are started
(though by hand, it works), no cron (by hand, again, it works), and on one
host no kdc (again, by hand you can start it).
On the other hand, another host upgraded to 9.2-RELEASE behaves as it should,
starting all services.
On the console, there are no errors, there is just no further message after
the last service (ntpd or sshd) is started.
I don't think it's a hardware issue, as one of the three machines runs on
different hardware than the other two (which are identical).
Everything is as standard as possible.
My ttys(5) is the standard one (comments and serial line left out):
console noneunknown off secure
ttyv0 /usr/libexec/getty Pc xterm on secure
ttyv1 /usr/libexec/getty Pc xterm on secure
ttyv2 /usr/libexec/getty Pc xterm on secure
ttyv3 /usr/libexec/getty Pc xterm on secure
ttyv4 /usr/libexec/getty Pc xterm on secure
ttyv5 /usr/libexec/getty Pc xterm on secure
ttyv6 /usr/libexec/getty Pc xterm on secure
ttyv7 /usr/libexec/getty Pc xterm on secure
ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure
My rc.conf(5) (this should not affect starting gettys), the second host does
not even have jails:
fsck_y_enable=YES
dumpdev=AUTO
ip_kerberos2=XXX
ip_ldap1=XXX
hostname=XXX
ipv4_addrs_bge0=XXX $ip_ldap1 $ip_kerberos2
defaultrouter=XXX
ezjail_enable=YES
jail_flags=-s 3
nfs_client_enable=YES
rpcbind_enable=YES
rpc_statd_enable=YES
rpc_lockd_enable=YES
kerberos5_server_enable=YES
saslauthd_enable=YES
saslauthd_flags=-a kerberos5
slapd_enable=YES
slapd_flags='-c 147 -h ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap:///
ldaps:///'
slapd_sockets=/var/run/openldap/ldapi
slapd_sockets_mode=666
nrpe2_enable=YES
nut_upsmon_enable=YES
munin_node_enable=YES
sshd_enable=YES
ntpd_enable=YES
ntpd_sync_on_start=YES
fscd_enable=YES
bsdstats_enable=YES
Do you have any clues what could have gone wrong? freebsd-update's IDS does
not show any wrong checksums.
Regards, Julian
signature.asc
Description: PGP signature
