Bug#775578: systemd kills spamassassin on system start

On Thu, 2016-02-11 at 23:41 +0100, Michael Biebl wrote: > Control: tags -1 + moreinfo > > On Sat, 17 Jan 2015 09:08:32 -0800 James Bottomley > wrote: > > Package: systemd > > Version: 215-8 > > Severity: normal > > > > Almost every time the system reboots, spamassassin fails to start. > > The

Processed: fixed 813702 in 217-1

Processing commands for cont...@bugs.debian.org: > fixed 813702 217-1 Bug #813702 [systemd] systemd: Oneshot service doesn't get killed after timeout. Marked as fixed in versions systemd/217-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 813702: http://bugs.de

Bug#775578: systemd kills spamassassin on system start

Control: tags -1 + moreinfo On Sat, 17 Jan 2015 09:08:32 -0800 James Bottomley wrote: > Package: systemd > Version: 215-8 > Severity: normal > > Almost every time the system reboots, spamassassin fails to start. The > systemd logs for this are: > > # systemctl status -l spamassassin.service >

Processed: Re: systemd kills spamassassin on system start

Processing control commands: > tags -1 + moreinfo Bug #775578 [systemd] systemd kills spamassassin on system start Added tag(s) moreinfo. -- 775578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___

Bug#783692: marked as done (systemd: systemctl output is unreadable on light background)

Your message dated Thu, 11 Feb 2016 21:54:23 + with message-id and subject line Bug#783692: fixed in systemd 229-1 has caused the Debian Bug report #783692, regarding systemd: systemctl output is unreadable on light background to be marked as done. This means that you claim that the problem h

Bug#805514: marked as done (gitignore in sources ignores needed file)

Your message dated Thu, 11 Feb 2016 21:54:23 + with message-id and subject line Bug#805514: fixed in systemd 229-1 has caused the Debian Bug report #805514, regarding gitignore in sources ignores needed file to be marked as done. This means that you claim that the problem has been dealt with.

Bug#775651: marked as done (systemd: /run/user/$UID directories are created with type tmpfs_t on SE Linux)

Your message dated Thu, 11 Feb 2016 21:54:23 + with message-id and subject line Bug#775651: fixed in systemd 229-1 has caused the Debian Bug report #775651, regarding systemd: /run/user/$UID directories are created with type tmpfs_t on SE Linux to be marked as done. This means that you claim

Bug#802780: marked as done (systemd: systemctl 227 fails in chroots (instead of ignoring))

Your message dated Thu, 11 Feb 2016 21:54:23 + with message-id and subject line Bug#802780: fixed in systemd 229-1 has caused the Debian Bug report #802780, regarding systemd: systemctl 227 fails in chroots (instead of ignoring) to be marked as done. This means that you claim that the problem

systemd_229-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Feb 2016 21:02:39 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libsystemd0 libs

Bug#813599: marked as done (random-seed: don't ignore errors when failing to create /var/lib/systemd/random-seed)

Your message dated Thu, 11 Feb 2016 22:51:31 +0100 with message-id <56bd0263.7070...@debian.org> and subject line Re: systemd - systemd-random-seed.service fails to start in clean install has caused the Debian Bug report #813599, regarding random-seed: don't ignore errors when failing to create /

Bug#802780: marked as done (systemd: systemctl 227 fails in chroots (instead of ignoring))

Your message dated Thu, 11 Feb 2016 22:42:48 +0100 with message-id <56bd0058.7000...@debian.org> and subject line Re: systemd: systemctl 227 fails in chroots (instead of ignoring) has caused the Debian Bug report #802780, regarding systemd: systemctl 227 fails in chroots (instead of ignoring) to b

Bug#783692: marked as done (systemd: systemctl output is unreadable on light background)

Your message dated Thu, 11 Feb 2016 22:39:56 +0100 with message-id <56bcffac.5000...@debian.org> and subject line Re: systemd: systemctl output is unreadable on light background has caused the Debian Bug report #783692, regarding systemd: systemctl output is unreadable on light background to be mar

Bug#775651: marked as done (systemd: /run/user/$UID directories are created with type tmpfs_t on SE Linux)

Your message dated Thu, 11 Feb 2016 22:41:17 +0100 with message-id <56bcfffd.7020...@debian.org> and subject line Re: Bug#775651: systemd: /run/user/$UID directories are created with type tmpfs_t on SE Linux has caused the Debian Bug report #775651, regarding systemd: /run/user/$UID directories ar

Bug#805514: marked as done (gitignore in sources ignores needed file)

Your message dated Thu, 11 Feb 2016 22:35:49 +0100 with message-id <56bcfeb5.2020...@debian.org> and subject line Re: Bug#805514: gitignore in sources ignores needed file has caused the Debian Bug report #805514, regarding gitignore in sources ignores needed file to be marked as done. This means t

Processing of systemd_229-1_amd64.changes

systemd_229-1_amd64.changes uploaded successfully to localhost along with the files: systemd_229-1.dsc systemd_229.orig.tar.gz systemd_229-1.debian.tar.xz libnss-myhostname_229-1_amd64.deb libnss-mymachines_229-1_amd64.deb libnss-resolve_229-1_amd64.deb libpam-systemd_229-1_amd64.deb

Bug#787473: systemd: Segfault while adding a new job

Maybe i found another hint: $ ps aux | grep defunct draghi5416 0.0 0.3 4224 1968 pts/0S+ 12:08 0:00 grep defunct $ sudo poweroff Failed to start poweroff.target: Connection reset by peer Failed to open initctl FIFO: No such device or address Failed to talk to init daemon. $ sudo p