Date: Mon, 7 Oct 2013 10:47:09 +0200 From: Julian Fagir <gnrp@komkon2.de> To: freebsd-questions@freebsd.org Subject: init(8) not executing everything cron, getty on some hosts Message-ID: <20131007104709.2d137cf9@adolfputzen>
next in thread | raw e-mail | index | archive | help
--Sig_/GJSr.eLqMsSCCz9cNhGr/Xc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, I've been experiencing a strange problem with one of my hosts (I think, sin= ce 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 servic= es 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 shoul= d, 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 none unknown 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 =20 My rc.conf(5) (this should not affect starting gettys), the second host does not even have jails: > fsck_y_enable=3D"YES" > dumpdev=3D"AUTO" > ip_kerberos2=3D"XXX" > ip_ldap1=3D"XXX" > hostname=3D"XXX" > ipv4_addrs_bge0=3D"XXX $ip_ldap1 $ip_kerberos2" > defaultrouter=3D"XXX" > ezjail_enable=3D"YES" > jail_flags=3D"-s 3" > nfs_client_enable=3D"YES" > rpcbind_enable=3D"YES" > rpc_statd_enable=3D"YES" > rpc_lockd_enable=3D"YES" > kerberos5_server_enable=3D"YES" > saslauthd_enable=3D"YES" > saslauthd_flags=3D"-a kerberos5" > slapd_enable=3D"YES" > slapd_flags=3D'-c 147 -h "ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap:/= // ldaps:///"' > slapd_sockets=3D"/var/run/openldap/ldapi" > slapd_sockets_mode=3D"666" > nrpe2_enable=3D"YES" > nut_upsmon_enable=3D"YES" > munin_node_enable=3D"YES" > sshd_enable=3D"YES" > ntpd_enable=3D"YES" > ntpd_sync_on_start=3D"YES" > fscd_enable=3D"YES" > bsdstats_enable=3D"YES" =20 Do you have any clues what could have gone wrong? freebsd-update's IDS does not show any wrong checksums. Regards, Julian --Sig_/GJSr.eLqMsSCCz9cNhGr/Xc Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlJSdQ0ACgkQc7h7cu1Hpp5pFQCgtCYgUoj4NYw2hTPw2xL6qa3c nlUAnjOU4lHzntvx2v1OOY8MPdqnD6ZO =xv5a -----END PGP SIGNATURE----- --Sig_/GJSr.eLqMsSCCz9cNhGr/Xc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131007104709.2d137cf9>