search

ddominet / UDMPRO-samba

UDM-PRO drive bay as a network drive
28 stars 8 forks source link

unable to get systemd connection to add healthchecks #1

Open n3roGit opened 3 years ago

n3roGit commented 3 years ago

When I try to run the script I get the following error message.

./samba.sh Error: cannot remove container 952f317acd5e32d299ede95810857556e31ee6e3d91010988e5d1432fdf61411 as it is running - running or paused containers cannot be removed: container state improper ERRO[0000] unable to get systemd connection to add healthchecks: dial unix /run/systemd/private: connect: no such file or directory ERRO[0000] unable to get systemd connection to start healthchecks: dial unix /run/systemd/private: connect: no such file or directory b461bf63588634d492129efd484cb027432c6cc52a41db230158d70c9eea8adc

Also, I can't access the share unfortunately. I can see the ports externally via nmap. I also get a login prompt in some cases. However, without success.

thealpa commented 3 years ago

What's the output of podman ps -a?

You could remove the container with podman rm and then rerun the script to create a new one.

n3roGit commented 3 years ago

Still the same:

image

ddominet commented 2 years ago

Sorry, for the delay. It is important to first kill and than rm container. Last time I checked it worked after reboots, but required said maintenance after updates. I can't test it currently, because I don't possess UDM PRO anymore. One more thing, It can't work with honeypot, because UDM reserves all ports.

LexxM3 commented 2 years ago

There is an obscure bug in the script: 'podman ps -all' is not valid, it needs to be either 'podman ps -a' or 'podman ps --all'. As is (-all), the behaviour is random and unpredictable, sometimes podman ps returns correct results and sometimes the filter fails (which is arguably also a bug in podman 1.6.1 in that it should have returned a parameter invalid error instead of behaving randomly; that caused me to spend a good hour on this typo issue; but this UniFi version of podman is so old that no one is ever likely to care, so let's fix the script instead). This is probably a (root?) cause of this specific issue, but ...

After this is fixed, I am having another trouble and will document it in a new issue momentarily.