On Wed, 11 May 2022 22:59:41 +0200 Thomas Liske
wrote:
> Hi,
>
> you are using some ansible deployment? Could you share your ansible
> role?
>
> This is a long-standing bug and it feels like that affected users are
> using aptitude. I wonder if this is related - could you give it a try
>
Ho great...
Found out that there's the same trouble on some debian9 hosts.
I say some because not all servers did the blockage.
# cat /etc/debian_version
9.13
# dpkg -l | grep needrestart
ii needrestart 2.11-3+deb9u1 all check
which daemons need to be restarted
Poking around I found this, could there be a relationship ?
├─sshd,14441
│ └─sh,14736 -c /usr/bin/python
/root/.ansible/tmp/ansible-tmp-1650945060.61-15873-131215080055549/AnsiballZ_apt.py
&& sleep 0
│ └─python,14737
Tried to install debian11 needrestart-3.5 package, no problem regarding
dependencies, but problem still the same.
├─sshd,13265
│ └─sh,14854 -c /usr/bin/python
/root/.ansible/tmp/ansible-tmp-1650508029.18-25277-93685447926498/AnsiballZ_apt.py
&& sleep 0
│ └─python,14855
Problem still exists in debian 10
After installing needrestart and doing a apt upgrade you get the following :
[...]
Setting up libirs161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up bind9-host (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up dnsutils (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
On Mon, 25 Oct 2021 07:57:22 +0300 Aleksi Suhonen
wrote:
> Package: unbound
> Version: 1.13.1-1
> Severity: normal
Hi,
got the same issue with backport on debian10 1.13.1-1~bpo10+1
We made a fleet of cache servers running Unbound behind a L4 load-balancer.
We got crashes on 3 of the machines
6 matches
Mail list logo
