I'm going back to V6!!

1st Official Post
    • Official Post

    This is now going to be a rant, after a failed upgrade which worked on the second attempt, I was getting an nginx.service error on start up, this I thought I fixed here that was Saturday 5/10, omv-backup ran on Sunday 06/10. I have just wrote the backup image to one of backup flash drives.


    The nginx problem has resurfaced, I even uninstalled file browser and rebooted, same problem, and every time the error occurs I get 4 emails, I'm sorry but I don't have a clue where to look.


    V6 was solid, I never shut down my server, it had been running 6+ months (hadn't changed the boot flash drive in a while, which I normally do once a month), but V7 I'm lost as to why there is a problem.

    boot.txt

    Raid is not a backup! Would you go skydiving without a parachute?


    OMV 7x amd64 running on an HP N54L Microserver

    Code
    2024-10-07T16:19:28+0100 wookie nginx[921]: 2024/10/07 16:19:27 [emerg] 921#921: open() "/var/log/nginx/error.log" failed (2: No such file or directory)

    It seems this happens from time to time and with very different rigs.


    After boot, what is the output of:
    ls -al /var/log/nginx

    systemctl status nginx



    You can try to run again:

    omv-salt deploy run nginx


    OR, create the folder and restart nginx:

    mkdir -p /var/log/nginx

    systemctl restart nginx

    • Official Post

    Thanks for the reply,

    ls-al output

    The systemctl will tell you it's running at the time of running the command, that's in one of the emails,

    However another command from the emails suggest you run this,

    This shows that nginx whilst it initially fails, it does eventually start, but that delay prevents the GUI from loading


    When I thought I had fixed it in the here link in #1 file browser and docker started after GUI login


    So question is, why is the nginx.service failing to start during the initial boot process, but does finally start allowing you to login, this delay did not happen on V6

    • Official Post
    Quote from geaves

    So question is, why is the nginx.service failing to start during the initial boot process, but does finally start allowing you to login, this delay did not happen on V6

    This isn't an omv7 issue. It is an issue on your system. For some reason, upgrades have not been going well on your system. I would be curious if folder2ram is causing this because you have a bunch of junk and/or large files it is syncing? Uninstall the flash memory plugin and see if it is slow.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from ryecoaaron

    Uninstall the flash memory plugin and see if it is slow

    OK, that solved the nginx.service problem and it loads as it should with docker loading after a GUI login


    So how does one clear junk and/or large files periodically from folder2ram?


    I take it that being the problem I can reinstall the plugin

    • Official Post
    Quote from geaves

    So how does one clear junk and/or large files periodically from folder2ram?

    They aren't in the plugin. The large files/junk is on your system. The plugin just has to sync it to ram when starting. I would look for large files or lots of small files in the directories sync'd by folder2ram (listed in /etc/folder2ram/folder2ram.conf).

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    OK remove flash memory plugin, reboot nginx.service starts, clear log files and any larger files, reinstall flash memory plugin -> failed to start nginix.service confirmed by the following and yet another 4 emails,

    Returning to v6 is an obvious choice, remove or modify something nginx starts as expected, reinstall or revert the modification nginx fails and you have to watch the paint dry before you can login, is this a problem, yes and no, yes in so much as you now have to wait longer to login, no, well it does finally get there

    • Official Post

    To solve this I suggest using omv-regen to get a clean installation. The only downside is that this will result in a missed opportunity to actually investigate and resolve this issue for other users.

    • Official Post
    Quote from chente

    The only downside is that this will result in a missed opportunity to actually investigate and resolve this issue for other users.

    I concur, a solution/fix would be a better option, but I do have another alternative I'm going to try, thanks to another mod :) we'll see if that works

    • Official Post
    Quote from geaves

    I do have another alternative I'm going to try, thanks to another mod :) we'll see if that works

    What alternative is that?

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    ryecoaaron I found this issue from the original upgrade failure, crashtest had sent me his upgrade procedure which I followed it all appeared to go well, including no grub-pc errors, until the last line;

    E: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/pve-no-subscription/binary-amd64/proxmox-kernel-6.2.16-20-pve_6.2.16-20_amd64.deb Error reading from server. Remote end closed connection [IP: 51.91.38.34 80] this is right after Restarting engine daemon, so there were no kernels /boot

    I then remembered your post here and ran omv-installproxmox 6.8 this appears to have worked, I am yet to reboot

    • Official Post

    Yes, that works!! but still the nginx.service fails to start, this only occurs after a reboot or shutdown then restart


    When you finally get into the GUI both docker and file browser services are loaded, if these are delayed until after the GUI is loaded then there are no nginx.service failed errors on boot


    V5/6 never had this nginx.service issue

    • Official Post
    Quote from geaves

    V5/6 never had this nginx.service issue

    You keep blaming OMV7 but OMV7 isn't the problem. Since uninstalling the flashmemory plugin fixed the nginx start issue previously, that tells me the change to folder2ram is likely causing the problem on your system. This is really hard to "fix" when your system is the only one with the issue though.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    Does the following allow nginx to start on boot?

    sudo mkdir -p /etc/systemd/system/folder2ram_startup.service.d

    echo -e "[Unit]\nBefore=nginx.service\nBefore=php8.2-fpm.service" | sudo tee /etc/systemd/system/folder2ram_startup.service.d/override.conf

    sudo systemctl daemon-reload

    then reboot

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    You must have run it before I added the mkdir line.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    Please post the output. It is just making a directory

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from geaves

    Yes, there's no override.conf file

    The second line after mkdir is creating the file.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login