Package: systemd
Version: 215-17
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
systemd doesn't survive two days on my bare minimal headless NAS
installation. I already purged all unused packages, reinstalled systemd
and reverted all config files to factory default, re
never make it to
the disk. I hope i can provide more with the next crashes.
Tell me if you need any configuration files, I'm happy to provide them.
Am 01.06.2015 um 23:22 schrieb Michael Biebl:
> Am 01.06.2015 um 23:13 schrieb Tino:
>> Package: systemd
>> Version: 215-17
>> S
It took quite a long this time. The system was running over a week. I
got a log of the crash and all other services were running normal
(except for sshd and systemd of course) for another ~30h until i
rebootet it. I looks like sshd crashed first and systemd followed while
adding a restart job. debs
Another crash. This time while doing an apt upgrade. I seems not related
to adding new jobs or the hashmap iteration. I have no idea where this
signal is coming from. There is nothing but the usual watchdog messages
in the log before the SEGV.
Jun 30 12:02:08 Storage-Blue systemd[1]: systemd-journa
t -v
-pf /run/dhclient.eth1.pid -lf /var/lib/dhcp/dhclient.eth1.leases eth1
root 919 0.0 0.2 4356 1484 ?Ss Jun30 0:00 /sbin/rpcbind
-w
statd 928 0.0 0.3 4544 1616 ?Ss Jun30 0:00 /sbin/rpc.statd
root 943 0.0 0.2 2812 1136 ?Ss Jun30 0
Another systemd segfault.
I still didn't find a workaround for this problem and the reboots every
few days is getting quite annoying. :/ At least it looks like i am the
only one with this problem.
Jul 02 06:32:05 Storage-Blue systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destinat
Am 05.07.2015 um 14:32 schrieb Michael Biebl:
> Sorry for the inconvenience.
>
> I think the best course of action would be, if you could install systemd
> v221 from testing, and if the problem is still reproducible there, we
> take this upstream.
>
> Would you be willing to do that?
I upgraded sy
Ths system was running for two weeks now with no issues. I almost
gathered some hope, that it's finally stable now. :( Next crash..
This time sshd crashed in the first place and the stack of the coredump
seems broken. Both very strange, that never happened before.
As usual, all other services remai
right?
I don't know if the problem of these SEGV is still the same with version
221-1. At least the system is somewhat stable if i don't touch anything.
Have a nice weekend
Tino
login as: draghi
draghi@Storage-Blue's password:
Welcome to Storage-Blue!
Last login: Thu Aug 13 13:24:58 20
i have to flip the power switch, because i
can't even login via ssh anymore.
Am 28.01.2016 um 18:26 schrieb Michael Biebl:
> Hi Tino
>
> On Sat, 22 Aug 2015 13:13:20 +0200 Tino wrote:
>> Hi everyone,
>>
>> it has been one month since the last crash. I wanted to check
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
. Maybe there is another person on this world that tries to run debian
on a QNAP TS-419P II, encouters these issues and maybe finds this bugreport.
Merry Christmas :)
Tino
signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers
12 matches
Mail list logo
