Jamie: I was able to reproduce the issue again. I'm thinking the problem
might be related to Ansible, but not 100% sure.
The output of ps auxww|grep ufw is:
root 247851 0.0 0.0 2608 604 pts/1S+ 10:53 0:00 /bin/sh -c
ufw enable ufw allow 22 ufw allow 80 ufw allow 443
root
Jamie: after installing some other things on the server, the problem no
longer exists, so I can't answer the question, unfortunately, nor can I
reproduce this issue. I would say that other ufw commands were not
running because UFW was called via Ansible, but it is not impossible.
Terminating the
Public bug reported:
When installing a new cloudserver (on Amazon EC2, if it makes a
difference), UFW completely hangs on any command, for example ufw
status. Interrupting it with Ctrl+C yields this backtrace:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 130, in
lock =
3 matches
Mail list logo