Posts by gderf

What does the Plex application log say?

Quote from monsen

yeah that is what my research pointed to. I think this was not the case before the OMV upgrade. I will try to pinpoint the container that causes it.

Let us know what the culprit is. I am seeing a 90 second hang during shutdown since upgrading to OMV 8.

OMV 8 systemd-shutdown[1]: Waiting for process: 10046 (s6-svscan), 9988 (s6-svscan), 9965 (s6-svscan), 11948 (python3), 882573 (Plex Media Serv), 10031 (s6-svscan), 881402 (s6-svscan), 9984 (s6-svscan), 957120 (s6-svscan), 881448 (s6-supervise), 10737 (s6-supervise)

Quote from ryecoaaron

This seems like something that should be fixed in the image using s6. AI seems to want to attach scripts to systemd units a lot as a fix.

I noticed that.

It was Fix 3. here:

https://chatgpt.com/share/693d8a0d-5914-800b-a711-3852f3355923

When I monitor the shutdown process in the SOL console it will hang at the the following statement for a considerable amount of time before continuing normally.

OMV 8 systemd-shutdown[1]: Waiting for process: 10046 (s6-svscan), 9988 (s6-svscan), 9965 (s6-svscan), 11948 (python3), 882573 (Plex Media Serv), 10031 (s6-svscan), 881402 (s6-svscan), 9984 (s6-svscan), 957120 (s6-svscan), 881448 (s6-supervise), 10737 (s6-supervise)

I let ChatGPT examine the above Code and it offered suggestions some of which I tried. Eventually I got it solved but the fix introduced a new problem. None of my running dockers would automatically restart when booting the machine. I could manually start each one though, but this is not acceptable. None of what ChatGPT suggested to fix the failure to start the dockers worked so I backed out of the fix that solved the hanging shutdown.

Is anyone else seeing a long pause on shutdown?

Thanks.

Quote from ryecoaaron

All I can think is the shutdown was being forced and not syncing. Until you run the commands to fix, nothing will the dpkg problem. The latest plugin should fix the shutdown issue.

I installed the latest, so we'll see.

I am seeing this just about every time I am installing an updated plugin.

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade 2>&1' with exit code '100': E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Quote from drichard58

I will try and change it, but it is set to the same IP address as my laptop - 127.0.0.53

That will only work if you have a working resolver on the machine. Just change it to a public resolver such as 1.1.1.1

Quote from Soma

Did you upgraded from v7?

I'm holding on to do it once I return home next week.

Yes, I upgraded from 7 to 8.

OK, I installed it and just accepted the defaults.

And it didn't even break Postfix. How refreshing!

I haven't installed the plugin yet so I was unaware that there any defaults.

Thanks for the tip.

It could be a simple as plugging the card in and seeing if it is recognized. But before check the Debian 12 hardware compatibility list to see what NICs are supported before making a purchase.

Is all your other in the path gear capable of at least 2GB speed? If not there is no point to upgrading the NIC or the internet connection.

Curious as to what directories users are handling with the openmediavault-writecache 8.0.1 plugin?

I am also seeing similar messages in the journal for folder2ram_temporary, hddtemp, and edac services.

I think they are harmless though.

I decided to try upgrading 7 -> 8 today using a cloned copy of my current OMV 7 SSD system disk.

Although I have not yet to begin looking around OMV 8 much yet, at least all my dockers are running well.

The only thing I had to do was to solve the 502 gateway not found error on the GUI login screen. Running the fix7to8upgrade script solved that one for me.

I really like the new login screen artwork. That's me! (inside joke some of you might get)

Thanks to the devs for all the hard work on this.

You need to find a guide that specifically tells you how to setup a container to use the network of another container. There are many available. Start looking.

I can't say for sure but it would seem to me that if a container can't join the specified network of another container then the current system local network would be used and that would route out via your WAN IP.

Are you referring to any specific guides to do what you are trying to accomplish, there are plenty of examples out there. ChatGPT is pretty good about things like this.

I think that you should not have port statements in containers that use another container's network. They should be defined in the container whose network you want to bind to.

Quote from catwilllmew

Upgrade on my current machine without losing my current configuration. There's no way I can remember every package I've installed and every dotfile I've edited on this machine. If i had to start from scratch I'm not even sure I would stick with OMV.

If that is your goal then your only path is to upgrade 5->6->7. As stated already, this will be very difficult, and likely not to succede. But you have nothing to lose by trying if and only if you try this on a copy of your existing installation.