Errors when Upgrading from OMV 3.0.99 to OMV 4

  • After going back and forth for a while on whether I should take the OMV 4 upgrade, I decided to finally do it. For the most part, it seems that everything went fine, and all of my plugins appear to be working even after the upgrade. I noticed this a the end of my output though, and it's making me nervous. I am not sure what to do about it. Any advice would be much appreciated. (Going to tag @ryecoaaron and @votdev on this.)


  • try apt-get -f install

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • try apt-get -f install

    I am getting the same thing unfortunately, but I have a little more detailed output this time.


  • I also keep getting these e-mails every half-hour @ryecoaaron.


    Code
    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20131226/pam.so' - /usr/lib/php5/20131226/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0
    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20131226/pam.so' - /usr/lib/php5/20131226/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0
    PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20131226/pam.so' - /usr/lib/php5/20131226/pam.so: cannot open shared object file: No such file or directory in Unknown on line 0
  • Looks like php didn't upgrade. What is the output of: dpkg -l | grep -E "php|openm"


    Did you reboot by any chance?

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Looks like php didn't upgrade. What is the output of: dpkg -l | grep -E "php|openm"


    Did you reboot by any chance?


    Here it is! It might be worth noting that after this happened the first time around, I restored a CloneZilla image that I took before the upgrade, tried the upgrade again, and it happened again.


    And I did try rebooting. After doing so, I am now greeted with this error message when I log in.


    The property 'nullpasswords' does not exist in the model 'conf.service.smb'.


  • Yet another update to the WebUI problem. After clearing my web browser's cache, it's even more screwed up now. All that's displaying is the OMV logo.


    Here's what I'm seeing in my web browser.


  • After clearing my web browser's cache, it's even more screwed up now. All that's displaying is the OMV logo.

    That is because your previous post shows that the openmediavault package is at iU (not fully installed). Try apt-get -f install. I have had no problem with upgrades from 3.x to 4.x but I haven't tried lately. Seems like you have something installed that still wants php5.

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • That is because your previous post shows that the openmediavault package is at iU (not fully installed). Try apt-get -f install. I have had no problem with upgrades from 3.x to 4.x but I haven't tried lately. Seems like you have something installed that still wants php5.

    I tried apt-get -f install but unfortunately it still did not resolve the problem. Concerning something still wanting php5, could that be the fault of the openmediavault-nginx plugin? I use it for my NextCloud installation.

  • could that be the fault of the openmediavault-nginx plugin?

    It should get upgraded to the OMV 4.x version that uses php7 although in your output, the omv-extras plugins are still at 3.x version (probably because they depend on OMV 4.x which hasn't finished installing yet).

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • What about collectd? Is that failing because of OMV or is OMV failing because of it?

    Hard to say. Better question for Volker.

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hard to say. Better question for Volker.

    Alright. I've already tagged him here so I'll just wait it out. Yesterday was the last free time that I'll have in a while and I need my OMV server to work perfectly, so I restored my OMV 3 CloneZilla image for now. When I play with the upgrade again, I will be doing so in a VM of the CloneZilla image. Hopefully I will be able to sort out issues in the VM before doing the upgrade to my actual OMV server.

  • I think the problem is that collected was not configured correctly because of a malformed config file:


    Quote

    Process: 12632 ExecStartPre=/usr/sbin/collectd -t

    But i don't have any idea why this happens. I migrated many test systems from 3.x to 4.x without such issues.

  • I think the problem is that collected was not configured correctly because of a malformed config file:


    But i don't have any idea why this happens. I migrated many test systems from 3.x to 4.x without such issues.

    Well that sucks. Is there anything I can do to fix the possibly-malformed config file before trying to take the upgrade again? I restored a CloneZilla image I had of OMV 3 as a way to undo the damage that the upgrade caused.

  • @votdev I finally had time to the OMV upgrade again after running this, and it still did not work. Any other suggestions?


    Here are some of the errors that I've seen when I try to run apt upgrade. I am not sure if any of them will be helpful. Because I do not want to screw up my live OMV server, I'm playing around with the upgrade in a VM clone before I try to do it for real.



    Edited once, last by David B: Added error screenshots. ().

Participate now!

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