aheimsbakk/container-munin

Update Munin

kroese opened this issue · 9 comments

kroese commented

The container has a pretty old version of Munin, can it be updated to the last release?

aheimsbakk commented

Hi, thank you for the interest in this container. I'm currently using the Munin version packaged with the OS, and not looked into installing it from source. Munin version will follow what Alpine provides. At the moment I've not the time to look into installing Munin from source, but would welcome pull request in that direction :)

kroese commented

Then maybe update the version of Alpine to something more recent?

aheimsbakk commented

I've just updated to the latest version of alpine, 3.16. I don't think that affected the version of Munin though...

kroese commented

According to https://pkgs.alpinelinux.org/packages?name=munin&branch=v3.16 version 3.16 should contain Munin 2.0.67 while the current container has version 2.0.54

aheimsbakk commented

Try to update your container, and you should get the container based on Alpine 3.16.

kroese commented

After updating the container to the latest version, I cannot even acces the Munin page anymore (error 502).

Logs:

Must specify a writable directory with -j! (Permission denied)

Process Backgrounded

2022/08/11-23:15:44 Munin::Node::Server (type Net::Server::Fork) starting! pid(235)

Resolved [*]:4949 to [::]:4949, IPv6

Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6

Binding to TCP port 4949 on host :: with IPv6

Setting gid to "0 0"

Can't open /var/log/munin/munin-update.log (Permission denied) at /usr/share/perl5/vendor_perl/Log/Log4perl/Appender/File.pm line 151.

spawn-fcgi: child spawned successfully: PID: 265

spawn-fcgi: child spawned successfully: PID: 346

2022/08/11 23:15:50 [error] 362#362: *1 connect() to unix:/var/run/munin/fastcgi-html.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.111, server: , request: "GET /munin/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/munin/fastcgi-html.sock:", host: "10.0.0.191:3355"

I updated the container many times before without issues, so it looks something changed.

aheimsbakk commented

I would like to help you start the container. It started as it should in my Kubernetes. How do you invoke the container, the command, Kubernetes or compose definition? I need more information if I'm able to help debug your issue.

kroese commented

I am using Docker and manage the container with Portainer. I just updated the container (without making any changes) and now I run into these errors.

kroese commented

I think this must be some kind of permission issue, according to the errors in the log that say that /var/log/munin is not writeable.

So I looked at the permissions for the mounted directories, and saw that they had really weird owner/groups: “_apt” and “systemd-journal” as owners and "systemd-networking" as group? Maybe because the ID of munin:munin does not exist on the host machine?

So as a test I changed the owner/group to root:root for all of the munin files, but it made no change, still getting the same error. And now they are still owned by root:root, so the "chown" command in your bash script does not seem to reset them?

I saw that you changed the syntax of the chown command from "munin.munin" to "munin:munin" in the recent commit, so maybe it is related to this issue?

I really have no clue why /var/log/munin has the wrong permissions, do you have any clues?