Your message dated Sat, 29 Nov 2014 23:04:33 +0000 with message-id <e1xur45-0004yp...@franck.debian.org> and subject line Bug#766943: fixed in ifupdown 0.7.50 has caused the Debian Bug report #766943, regarding systemd: server no longer gets networking after switching to systemd to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd Version: 215-5+b1 Severity: important Hi. Tonight I switched my last server still running with sysvinit to systemd, since I've experience no major problems with it on my other systems. That server however, didn't come up anymore (i.e. not even pinging back). I've sent a Ctrl-Alt-Del event via the hosting company's web interface, and it actually came back and I could log in. The logs from syslog didn't show much interesting stuff, only that apache httpd (which runs on that node) couldn't bind to the IPv4 addres. I've rebooted another time then (and several more times since then), but now it's back to no booting (or rather said: no networking - at least the first time where it didn't work, syslog showed, that it actually started up, and also got a clean shutdown). I can't say much about the system or logs right now,... it's a physical machine, IPv4 and v6 addresses, brought up via ifupdown using allow-auto for eth0 in /e/n/interfaces. It uses mdadm with a RAID1. The only other "special" thing that I remember is, that I use rootdelay=10 as a kernel parameter. TBH, I forgot why, but there was something that the disks were detected too lated and the initramfs could never mount the rootfs. But that shoudln't affect systemd, right? I write the bug already now, since it's really complicated to get access to the server by other means,... hetzner (the company) does provide some KVM interface, but that's implemented quite insecurely and it costs when one needs it for a longer time. So it would be great if you could already tell me in advance which logs to look for, and which things to test. Obviously I'll set systemd.log_level=debug at the kernel command line... anything else? Cheers, Chris. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-2 ii libc6 2.19-12 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-57 ii udev 215-5+b1 ii util-linux 2.25.2-2 Versions of packages systemd recommends: ii dbus 1.8.8-2 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: ii systemd-ui 3-2 -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Source: ifupdown Source-Version: 0.7.50 We believe that the bug you reported is fixed in the latest version of ifupdown, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Shadura <andre...@debian.org> (supplier of updated ifupdown package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 29 Nov 2014 14:32:32 +0100 Source: ifupdown Binary: ifupdown Architecture: source i386 Version: 0.7.50 Distribution: unstable Urgency: medium Maintainer: Andrew Shadura <andre...@debian.org> Changed-By: Andrew Shadura <andre...@debian.org> Description: ifupdown - high level tools to configure network interfaces Closes: 709378 741579 766943 Changes: ifupdown (0.7.50) unstable; urgency=medium . [ Andrew Shadura ] * Configure the loopback interface by default only if user hasn't defined their own loopback interface (Closes: #709378). * Update udhcp command-line options (Closes: #741579). * Fix compiler warnings. * Update the documentation regarding "source" keyword. . [ Michael Biebl ] * Call "udev settle" explicitly before configuring any devices (Closes: #766943). Checksums-Sha1: c2dab2db906924cdb4510adb31eb8f0e3deedf42 1539 ifupdown_0.7.50.dsc e5a428e3b245e64bc6781fc842464d86efd82fb3 76740 ifupdown_0.7.50.tar.xz 402188489e66887f37c2c35f2a00f3d03ae0ccbb 67394 ifupdown_0.7.50_i386.deb Checksums-Sha256: 6e10d042bb591f7abf3274c2fd6339e028641c92a384ac88e20bc7ee13bb26b3 1539 ifupdown_0.7.50.dsc cab6b02d1f9e014aab9588e04ed7e254ba2bebee42b6a7854ec231ffc99c833a 76740 ifupdown_0.7.50.tar.xz cfaa8f963b6e810a969a1fea1e55243a716719339a7e145c8b0e7da0b9c5a80e 67394 ifupdown_0.7.50_i386.deb Files: 5cfba399d38683166ce81bfde060ddbf 1539 admin important ifupdown_0.7.50.dsc 0e72b182cc5c8a17fb2636663f13639e 76740 admin important ifupdown_0.7.50.tar.xz 66200dbea2372132e0448df535628c98 67394 admin important ifupdown_0.7.50_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJUek9FAAoJEG6k0jEaLSaN2MIP/1FH9SCAeQVIdGLT2CnAds6z /PiOBeSkI1dR5cYVf3WoTRB+TcOhr9yuuyMLzoxtddKKDpaykTaB4l5mPH/nhDmn 11JgmrEZ0B7UxoCq8tPEs07tkY6GZdtjdZSnlbSnAJRLWtRdqzWp0tbzjym05JE3 LBgqj3icLSPl+lfwZ71XT3VBv3AsuNONo24+TG8WEqYaElt0488xj7sqw7GkcTTF 6szqEow65rhwWhjP2pbMSgFpagI2e6G2Cpv+2BF8iqJCO7icTg5fAwID3RrI0wPV JBOELPTLMSElEO0xSISfwJxOfM8gE3Pqywb0OFLU+Ja8l5annVYJWx7CNQ1EbEUQ 6Fhp22oEeynKLArybeKFc90WtBkfpDtz2McGX/2w9gesoMmvyAz0N+1C/UyjJlKP 2XALeIpKfc30nIAFXZO1jUrj7cahzfjd2E5qtMBUt6pjjEn9q6iHJIllb83SrEvM stAUvpquQI8bLEZvoYXfMrRAckMcl8uXXhHAVZp56oKHUDKphijAVMVKYD5TgUyt +2zH3BAAj9oaMsmYh2JxIDOHtSiGU+5R2fFsVF0Wm1kkRdRtCV5XQFeBKY8xmB0e LYOWOvpPyvKAmulavxRhB4iFQvcOIBv6jqQxa1K0FFcJUxJM3ALHPLLem18F9DZ+ 4bMQlwFXzOOSFkuPPYTk =gA2S -----END PGP SIGNATURE-----
--- End Message ---
