Hello Cristian Ionescu-Idbohrn,
following is what I get from a buster amd64 qemu VM,
with explicitly downgraded systemd packages to 239-13:
It has quite a similarity to upstream bug [1].
And upstream received a fix for that just a few days ago,
and is therefore not yet contained in an upstream rel
Hello Cristian Ionescu-Idbohrn,
Am 18.12.2018 um 09:35 schrieb Cristian Ionescu-Idbohrn:
> On Mon, 17 Dec 2018, Bernhard Übelacker wrote:
>>
>> Hello Cristian Ionescu-Idbohrn,
>> following is what I get from a buster amd64 qemu VM,
>> with explicitly downgraded systemd packages to 239-13:
>>
>> It
On Tue, 18 Dec 2018, Michael Biebl wrote:
>
> first, thanks a lot Bernhard for providing a properly annotated
> backtrace! It does indeed look very similar to the one in [1]
Agreed.
> Am 18.12.18 um 18:45 schrieb Bernhard Übelacker:
> > Am 18.12.2018 um 09:35 schrieb Cristian Ionescu-Idbohrn:
>
On Mon, 17 Dec 2018, Bernhard Übelacker wrote:
>
> Hello Cristian Ionescu-Idbohrn,
> following is what I get from a buster amd64 qemu VM,
> with explicitly downgraded systemd packages to 239-13:
>
> It has quite a similarity to upstream bug [1].
> And upstream received a fix for that just a few d
On Mon, 17 Dec 2018, Michael Biebl wrote:
>
> What's the output of
> coredumpctl list
# coredumpctl list
No coredumps found.
> ls -la /var/lib/systemd/coredump/
# ls -l /var/lib/systemd/coredump/
-rw-r- 1 root root 873282 Dec 16 17:16
core.systemd.0.829d81de299543c1a445874d1dd7660d.2097.15
Am 17.12.18 um 14:51 schrieb Cristian Ionescu-Idbohrn:
> On Mon, 17 Dec 2018, Michael Biebl wrote:
>>
>> Do you by chance still have a core file of the crash?
>
> If there were one, where would I find it?
>
> Are there instructions somewhere? I do see both
> /usr/lib/sysctl.d/50-coredump.conf a
On Mon, 17 Dec 2018, Michael Biebl wrote:
>
> Do you by chance still have a core file of the crash?
If there were one, where would I find it?
Are there instructions somewhere? I do see both
/usr/lib/sysctl.d/50-coredump.conf and:
# cat /proc/sys/kernel/core_pattern
|/lib/systemd/systemd-cored
Am 17.12.18 um 13:13 schrieb Cristian Ionescu-Idbohrn:
> On Mon, 17 Dec 2018, Michael Biebl wrote:
>>
>> Control: severity -1 important
>> Control: tags -1 moreinfo
>>
>> Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:
>>
>>> | systemd[1]: Caught , dumped core as pid 2097.
>>
>> Please try t
On Mon, 17 Dec 2018, Michael Biebl wrote:
>
> Control: severity -1 important
> Control: tags -1 moreinfo
>
> Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:
>
> > | systemd[1]: Caught , dumped core as pid 2097.
>
> Please try to get a backtrace following
> https://wiki.debian.org/HowToGe
Control: severity -1 important
Control: tags -1 moreinfo
Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:
> | systemd[1]: Caught , dumped core as pid 2097.
Please try to get a backtrace following
https://wiki.debian.org/HowToGetABacktrace
Thanks,
Michael
--
Why is it that all of the inst
Package: systemd
Version: 239-13
Severity: critical
Justification: breaks the whole system
While trying to upgrade postfix* packages I ended up in this mess :(
Every attempt (I know off) to get out of it failed :(
I also lost the ability to ssh login.
,
| systemd[1]: Caught , dumped core as
11 matches
Mail list logo