Bug#754121: aiccu fails to start with systemd

2014-11-14 Thread Jeroen Massar
Severity: important


Lowering severity to important. Causing a package for removal because
somebody decided on a new init system that is not backwards compatible
is not a critical thing.

Also, you can always start AICCU simply by typing 'aiccu start' which is
what the init script does.


I'll install a VM over the weekend and check what the heck is wrong with
this and resolve it properly.


It would be extremely useful if you can actually provide logs and other
details btw.

Greets,
 Jeroen


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754121: aiccu fails to start with systemd

2014-11-14 Thread Pascal Volk
On 11/14/2014 09:44 AM, Jeroen Massar wrote:
 Severity: important
 
 
 Lowering severity to important. Causing a package for removal because
 somebody decided on a new init system that is not backwards compatible
 is not a critical thing.

,--[ https://www.debian.org/Bugs/Developer#severities ]--
| critical
|   makes unrelated software on the system (or the whole system) break …
`--

As mentioned in my message from yesterday, the system is unable to
finish the boot process. The message `A start job is running for LSB: …'
can't be interrupted. While the red asterisks are moving from left to
right and back again, there is only one accepted keyboard shortcut:

Ctrl+Alt+Del

So I'm able to reboot the system. But even in single user / recovery
mode systemd tries to start aiccu.
The only workaround, known to me, is enabling systemd's debug shell. In
the (INSECURE!) debug shell I'm able to find out the PID of the
systemclt job, which tries to start aiccu. Then I'm able to kill that job.

For me, the problem is *critical*, with the symptoms described above.

 Also, you can always start AICCU simply by typing 'aiccu start' which is
 what the init script does.

This is what I've done within the last months, since I've reported the
problem.


 I'll install a VM over the weekend and check what the heck is wrong with
 this and resolve it properly.

Maybe you'll find the patch from the Gentoo project useful.
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/aiccu/files/aiccu-2007.01.15-systemd.patch?view=markup


 It would be extremely useful if you can actually provide logs and other
 details btw.

Sorry, there are not much useful information. After killing the
systemctl job - up to three times - the system boots.

Contents of syslog:
host aiccu[1092]: Successfully retrieved tunnel information for T12345
host aiccu[1138]: AICCU running as PID 1138

In the initial report message I've attached a few relevant lines from
journalctl. This time I'm attaching the last available lines of
systemd's debug shell.


Regards,
Pascal
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown
 | `-742 /bin/systemctl start aiccu
 |-systemd-journald.service
 | `-226 /lib/systemd/systemd-journald
 |-mdmonitor.service
 | `-489 /sbin/mdadm --monitor --scan
 |-systemd-udevd.service
 | `-245 /lib/systemd/systemd-udevd
 `-debug-shell.service
   |-215 /bin/bash
   |-745 systemctl status
   `-746 systemctl status
[**] A start job is running for LSB: Raise network interfaces. (26s / no 
limit)
[* ] A start job is running for LSB: Raise network interfaces. (37s / no 
limit)
* el-presidente
State: starting
 Jobs: 61 queued
   Failed: 0 units
Since: Fri 2014-11-14 20:58:51 CET; 48s ago
   CGroup: /
   |-1 /sbin/init
   `-system.slice
 |-networking.service
 | |-673 /bin/sh -e /etc/init.d/networking start
 | |-680 ifup -a
 | |-741 /bin/sh -c /bin/systemctl start aiccu
 | `-742 /bin/systemctl start aiccu
 |-systemd-journald.service
 | `-226 /lib/systemd/systemd-journald
 |-mdmonitor.service
 | `-489 /sbin/mdadm --monitor --scan
 |-systemd-udevd.service
 | `-245 /lib/systemd/systemd-udevd
 `-debug-shell.service
   |-215 /bin/bash
   |-747 systemctl status
   `-748 pager
[   ***] A start job is running for LSB: Raise network interfaces. (40s / no 
limit)
[**] A start job is running for LSB: Raise network interfaces. (1min / no 
limit)
[  *** ] A start job is running for LSB: Raise network interfaces. (1min 8s / 
no limit)
* el-presidente
State: starting
 Jobs: 61 queued
   Failed: 0 units
Since: Fri 2014-11-14 20:58:51 CET; 1min 18s ago
   CGroup: /
   |-1 /sbin/init
   `-system.slice
 |-networking.service
 | |-673 /bin/sh -e /etc/init.d/networking start
 | |-680 ifup -a
 | |-741 /bin/sh -c /bin/systemctl start aiccu
 | `-742 /bin/systemctl start aiccu
 |-systemd-journald.service
 | `-226 /lib/systemd/systemd-journald
 |-mdmonitor.service
 | `-489 /sbin/mdadm --monitor --scan
 |-systemd-udevd.service
 | `-245 /lib/systemd/systemd-udevd
 `-debug-shell.service
   |-215 /bin/bash
   |-749 systemctl status
   `-750 pager
[   ***] A start job is running for LSB: Raise network interfaces. (1min 18s / 
no limit)
[  *** ] A start job is running for LSB: Raise network interfaces. (1min 18s / 
no limit)


signature.asc
Description: OpenPGP digital signature


Bug#754121: aiccu fails to start with systemd

2014-11-14 Thread Jeroen Massar
On 2014-11-14 22:28, Pascal Volk wrote:
 On 11/14/2014 09:44 AM, Jeroen Massar wrote:
[..]
 As mentioned in my message from yesterday, the system is unable to
 finish the boot process. The message `A start job is running for LSB: …'
 can't be interrupted. 

You are using a 'testing' branch of Debian.

Problems are to be expected. Especially when changing init systems.

You should be filing a critical bug with systemd for breaking your
system in this way.

 The only workaround, known to me, is enabling systemd's debug shell. In
 the (INSECURE!) debug shell I'm able to find out the PID of the
 systemclt job, which tries to start aiccu. Then I'm able to kill that job.

Definitely sounds like a systemd issue.


AICCU does not cause that error, it is systemd causing you all that
grief and no way out to simply solve it.


 Also, you can always start AICCU simply by typing 'aiccu start' which is
 what the init script does.
 
 This is what I've done within the last months, since I've reported the
 problem.

Hence, AICCU works. It is just something messy in systemd that is
causing this.

I'll look into it this weekend, though diving into systemd will be 'fun'.

Greets,
 Jeroen


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754121: aiccu fails to start with systemd

2014-11-13 Thread Pascal Volk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Version: 20070115-15.2
Severity: critical

Dear aiccu package maintainers,

out of curiosity I've enabled aiccu again (`update-rc.d aiccu defaults`).
Since that time systemd can't finish booting! Systemd shows the following
message - forever:

[   *   ] A start job is running for LSB: Raise network interfaces. (Xmin Ys / 
no limit)

Dunno, maybe systemd will also count hours after 60 minutes …

The only way to work around this problem is `systemctl mask aiccu`. But
when aiccu is masked, it can't be started!


Regards,
Pascal
- -- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJUZQSgAAoJEIgLCU7FETn+HgAL/jdvRN/ziqBgzXDgVvX+MpuU
1FmuXckNt4zyYgEujqmoTjnVzRYdS6/jcsOQML01Ei2St/XK1g75e0VD5+4slBXg
CSodnQWlw7lVSwIujBMIwVHOkzqESorM9EZ0/NO+aSLHeJA9CzANx1tq56k4nT8H
TyNnnb6aABxVftcn9RswHQ8XguGosRb/WmNQbKDjcINdsmZFMSU1cAiu28rdEN0y
yDl6dx4UDOGlxM7+rcFkmjH2HQwsSBHYsOUrJzdo8R6I1Xe68JjgrfxA2vnFiB9K
YMwaoxBJwoMGlKFg3mwLqxDC5e6bbrJmD4zCr6WpMg8iMn1xkv0BlbZFnjXN87Qs
8zq2uoYFA2l1y2soajhpx2C95YPDkhl8XKt6K6OBMyAvX6Sgws37wNW6pR+MTVfg
BvXLxsdrw58ZaRRB46U2GnurqKWA7Fh5/PFD4KREidv5eOW0N1TOop66q4Xk0kfg
Ug4+iZGmCaWJ+w3qLOw9whem/AmdZSJUdXaOxFdUlQ==
=y04r
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754121: aiccu fails to start with systemd

2014-07-07 Thread Pascal Volk
Package: aiccu
Version: 20070115-15.1
Severity: normal
Tags: ipv6

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear aiccu package maintainers,

since switching from sysvinit-core to systemd-sysv aiccu is no longer
started on system boot. journalctl shows some entries about aiccu (see
attached file journalctl.log).

When I'm logged in, I'm able to start aiccu with `service aiccu start`.


Regards,
Pascal

- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aiccu depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  iproute1:3.15.0-2
ii  iputils-ping   3:20121221-5+b1
ii  iputils-tracepath  3:20121221-5+b1
ii  libc6  2.19-4
ii  libgnutls262.12.23-16
ii  lsb-base   4.1+Debian13
ii  ucf3.0030

Versions of packages aiccu recommends:
ii  bind9-host  1:9.9.5.dfsg-4
ii  dnsutils1:9.9.5.dfsg-4
ii  openntpd [time-daemon]  20080406p-7

aiccu suggests no packages.

- -- Configuration Files:
/etc/aiccu.conf [Errno 13] Permission denied: u'/etc/aiccu.conf'

- -- debconf information:
  aiccu/notunnels:
* aiccu/brokername: tic://tic.sixxs.net
  aiccu/nobrokers:
  aiccu/badauth:
* aiccu/username: PV-RIPE
* aiccu/tunnelname: T1

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJTut84AAoJEIgLCU7FETn+jy0L+wTqadb0vTyUO8crnynyceDk
w+im0bwS2Tzzzko/xFHPsPgbjxw0TYczJgf6mJwHKiNtV/16a+/b5ncaz+KYi50b
ZuQoquA/MogBPwVAvH9J2Mn8zL8KJGeFfaEim79ToaDfRBjbRvW3PXl7QCFpA8hK
UHmGFlZvi59rfNl07AmAT9lwm5Bd5FGwyvPSurCRhFIcULVHFvCe0KuN9qIW6UAV
iU1Lop+9RDDx1uvcuAQbGScIa9Of+c7CLgWd3HgH511P3L/R/sYfjcPREwJwJGF/
NKc+558bR27Fv5Sgcp6cW79QLOu3YpV31YZebZd2K6MX7sshwtP/4Bu1HVyrY6wU
VUU0J6JzOO5WVlyzu1IMy0Aa5mi37+sPGcl8rLzg4KGNKamkSdURyJShgnhe0sG5
P06dpoSqNe6CPuQtFCBSfXw/vZlzcH38a2Xhrv44jvMDpbCsd1cTHpRV/+5hZiSe
BVYAyfANQEWZ78c9Yn7OwEZku+Cd1G/JEqKIogKkdg==
=4nVQ
-END PGP SIGNATURE-
Jul 07 17:59:02 el-presidente kernel: r8169 :05:00.0 eth0: link up
Jul 07 17:59:02 el-presidente kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
Jul 07 17:59:06 el-presidente kernel: r8169 :06:00.0 eth1: link up
Jul 07 17:59:06 el-presidente kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link 
becomes ready
Jul 07 17:58:53 el-presidente systemd[1]: Walked on cycle path to 
aiccu.service/start
Jul 07 17:58:53 el-presidente systemd[1]: Walked on cycle path to 
aiccu.service/start
Jul 07 17:58:53 el-presidente systemd[1]: Walked on cycle path to 
aiccu.service/start
Jul 07 17:58:53 el-presidente systemd[1]: Breaking ordering cycle by deleting 
job aiccu.service/start
Jul 07 17:58:53 el-presidente systemd[1]: Job aiccu.service/start deleted to 
break ordering cycle starting with basic.target/start