Systemd-tty-ask-password-agent : a debian issue or related to a container

LXD
1

Hello,

I have a little ubuntu server for my personnal usage where I am using several ubuntu containers for 1 year or more.
I need to create a debian/jessie container for a project.

So I run : lxc launch images:debian/jessie jeedom2
I updated packages and rebooted.

Now I try to install others packages but installation is stucked :
'root 5406 0.0 0.8 70228 32708 ? S+ 20:28 0:09 _ apt-get -y install locate tar telnet wget logrotate fail2ban dos2unix ntpdate htop iotop vim iftop s
root 6092 0.0 0.1 19604 4064 pts/0 Ss+ 20:28 0:00 _ /usr/bin/dpkg --status-fd 19 --configure libpopt0:amd64 libgpm2:amd64 libmagic1:amd64 libsqlite3
root 6439 0.0 0.0 4336 1532 pts/0 S+ 20:29 0:00 _ /bin/sh /var/lib/dpkg/info/fail2ban.postinst configure
root 6473 0.0 0.0 4336 1584 pts/0 S+ 20:29 0:00 _ /bin/sh /usr/sbin/invoke-rc.d fail2ban start
root 6503 0.0 0.0 24172 2708 pts/0 S+ 20:29 0:00 _ systemctl start fail2ban.service
root 6504 0.0 0.0 13176 1620 pts/0 S+ 20:29 0:00 _ /bin/systemd-tty-ask-password-agent --watch ’
Same for rsync package.
I have not found on the web or debian forums a solution.

I just wonder if it could be related to the fact it is a container and there is something more to configure.
TIA

JPM

My ubuntu server :
'lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial

lxd --version
2.0.10’

The container :
‘lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.8 (jessie)
Release: 8.8
Codename: jessie’

2

Looks like fail2ban is rather unhappy somehow.

Take a look at “journalctl -n 300”, it may contain the reason why it’s failing to start.

3

Thanks to reply.
I have forgotten to say that once I read somewhere that one run a few commands after creation of a debian container but I do not remember where and I do not know at all if it could be related with my issue. That is why I posted here.

I run dpkg --configure -a
Setting up fail2ban (0.8.13-1) …

and form journalctl :

Jul 14 09:36:01 jeedom2 systemd[1]: Looping too fast. Throttling execution a little.
Jul 14 09:36:03 jeedom2 systemd[1]: Looping too fast. Throttling execution a little.
Jul 14 09:36:04 jeedom2 systemd[1]: Reloading.
Jul 14 09:36:04 jeedom2 systemd[1]: Failed to parse /proc/swaps:2
Jul 14 09:36:04 jeedom2 systemd[1]: Reloading.
Jul 14 09:36:04 jeedom2 systemd[1]: Failed to parse /proc/swaps:2
Jul 14 09:36:05 jeedom2 systemd[1]: Looping too fast. Throttling execution a little.
Jul 14 09:36:06 jeedom2 systemd[1]: Looping too fast. Throttling execution a little.
```
I have ~37 per second of "Looping too fast..." 

I am investigating...
(however, do not spend time as it seems a debian issue)