[SOLVED] Leftover scripts in /etc/init.d after OMV 2 to 3 upgrade

    • OMV 3.x
    • Upgrade 2.x -> 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • [SOLVED] Leftover scripts in /etc/init.d after OMV 2 to 3 upgrade

      Upgrading from OMV 2 to 3 brings the underlying Debian 7 to 8 upgrade and the switch from sysvinit to systemd.

      After performing a successful upgrade from OMV 2 to 3 (I just have to fix some glitches, solved by searching on this precious forum), I however noticed that the beep sound on system startup and shutdown were generated twice. I then suspected that there were some duplicated scripts in /etc/init.d and in the new systemd configuration. In fact, I both find:


      Source Code

      1. /lib/systemd/system/openmediavault-beep-down.service
      2. /lib/systemd/system/openmediavault-beep-up.service
      AND

      Source Code

      1. /etc/init.d/openmediavault-beep
      Indeed, in /etc/init.d I find:

      Source Code

      1. /etc/init.d/openmediavault
      2. /etc/init.d/openmediavault-beep
      3. /etc/init.d/openmediavault-configimport
      4. /etc/init.d/openmediavault-engined
      I suspect al those scripts shouldn't be in there any more. Can you confirm? What is the right way to remove them?


      Thanks in advance,


      Mauro
    • mauromol wrote:

      I suspect al those scripts shouldn't be in there any more. Can you confirm? What is the right way to remove them?
      Just a note that Init scripts still work on systemd but OMV 3.x did move to using unit files for its services. Just delete them. We did recommend fresh installs over upgrades from 2.x to 3.x. And not to kick a dead horse since I know you don't want to upgrade to 4.x but you are asking for support on an unsupported version.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Just a note that Init scripts still work on systemd but OMV 3.x did move to using unit files for its services. Just delete them. We did recommend fresh installs over upgrades from 2.x to 3.x. And not to kick a dead horse since I know you don't want to upgrade to 4.x but you are asking for support on an unsupported version.
      Yes, I know, but please note that those orphaned scripts would still be a problem if I upgrade from 3.x to 4.x, unless the 4.x upgrade process is smart enough to remove them ;)

      Thanks for your hint: I know those init scripts still work, in fact I get the "double beep" problem at boot/shutdown. And, exactly for this reason, I didn't know whether the other openmediavault scripts in there could still be required in some way. Now that you confirm that they are not needed any more (because they were all migrated to systemd), I can remove them. Thank you for your help! :thumbup:
    • As I side note: I decided to try the update from 2.x to 3.x even though it was suggested to perform a new installation because I didn't want to reconfigure all from scratch. In particular I was wondering whether OMV is still missing a "save/restore" configuration feature, which is a basic thing IMHO.
      It it's still missing, what is the recommended way to perform a "clean upgrade" by reinstall? Just reconfigure all the system from scratch by hand?
    • mauromol wrote:

      please note that those orphaned scripts would still be a problem if I upgrade from 3.x to 4.x, unless the 4.x upgrade process is smart enough to remove them
      Which is why I mentioned that the OMV 2.x -> 3.x upgrade was not recommended. I haven't seen the init scripts being left behind though. Something must have gone wrong in the upgrade.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • mauromol wrote:

      whether OMV is still missing a "save/restore" configuration feature, which is a basic thing IMHO.
      While it sounds like a basic thing, it is very difficult to implement. With the upcoming features in OMV 5.x, it will be easier to implement but I don't know if it is on the 5.x radar. Probably a 6.x feature.

      mauromol wrote:

      what is the recommended way to perform a "clean upgrade" by reinstall? Just reconfigure all the system from scratch by hand?
      Yes. Personally, I think this is good for people for go through this process so they don't forget how to do the setup. Helpful for disaster recovery.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      While it sounds like a basic thing, it is very difficult to implement. With the upcoming features in OMV 5.x, it will be easier to implement but I don't know if it is on the 5.x radar. Probably a 6.x feature.Yes. Personally,
      Basic feature does not necessarily mean "easy to implement", but it's indeed a basic feature that all network devices (routers, NASes, SANs, etc.) have and has had for years, ranging from home and SOHO products up to professional products. So I still believe it's a major lack in OMV, especially if we consider we're at version 4.x already...


      ryecoaaron wrote:

      Yes. Personally, I think this is good for people for go through this process so they don't forget how to do the setup. Helpful for disaster recovery.
      Well, this is certainly an optimistic point of view! :D
    • Returning back on topic, I disabled and removed all the services and scripts regarding openmediavault in /etc/init.d, but now when I start the system monit alerts that:

      [pre]
      Does not exist Service omv-engined

      Date: Wed, 31 Jul 2019 21:47:18
      Action: restart
      Host: openmediavault.local.lan
      Description: process is not running

      Your faithful employee,
      Monit
      [/pre]

      And then monit restarts this service (I guess by running the omv-engined command directly, since the script in /etc/init.d was removed...):

      [pre]
      Exists Service omv-engined

      Date: Wed, 31 Jul 2019 21:47:51
      Action: alert
      Host: openmediavault.local.lan
      Description: process is running with pid 1440

      Your faithful employee,
      Monit
      [/pre]

      Before removing omv-engined I saw that it was indeed running. So the question now is: is it needed (and hence I should restore it) or it's just some configuration of monit that needs to be changed (to avoid it to restarting omv-engined)?

      P.S.: how the hell can I insert a piece of preformatted text without formatting it as "source code" in this forum? X/

      The post was edited 1 time, last by mauromol: Fix formatting ().

    • mauromol wrote:

      Before removing omv-engined I saw that it was indeed running. So the question now is: is it needed (and hence I should restore it) or it's just some configuration of monit that needs to be changed (to avoid it to restarting omv-engined)?
      The init script is not needed. The openmediavault-engined unit file takes its place. I would make sure that unit file is enabled and try omv-mkconf monit

      mauromol wrote:

      how the hell can I insert a piece of preformatted text without formatting it as "source code" in this forum?
      I use spoilers. Otherwise, you use the inline-code on every line (but that is a pain).

      mauromol wrote:

      Basic feature does not necessarily mean "easy to implement", but it's indeed a basic feature that all network devices (routers, NASes, SANs, etc.) have and has had for years, ranging from home and SOHO products up to professional products. So I still believe it's a major lack in OMV, especially if we consider we're at version 4.x already...
      Actually it was in OMV 0.2. Just didn't work well. How do you restore your Windows config?? I work with many things that don't have a config restore. VMware is a huge one. Plenty of appliances have restores but most OSes don't. FreeNAS does but it is a commercially supported product. OMV is targeted at home users who usually don't have a complicated config and really just need a backup.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      The init script is not needed. The openmediavault-engined unit file takes its place. I would make sure that unit file is enabled and try omv-mkconf monit
      What do you mean exactly by "unit file" and how can I check if it's in place / enabled?


      ryecoaaron wrote:



      Actually it was in OMV 0.2. Just didn't work well. How do you restore your Windows config?? I work with many things that don't have a config restore. VMware is a huge one. Plenty of appliances have restores but most OSes don't. FreeNAS does but it is a commercially supported product. OMV is targeted at home users who usually don't have a complicated config and really just need a backup.
      I personally see OMV more like an appliance rather than an OS. Or, at least, I miss the feature to save settings I can change through the web UI. Saving and restoring the whole OS configuration is obviously a different story, but if we assume the basic OMV configuration can be done entirely through the UI, having the ability to export and restore all the settings the user can change from the UI would be a big plus. Exactly what all the other "embedded" NAS systems do.
      Of course, if I customise the system by changing the underlying Debian configuration, I should then take care or restoring all my customisation if I reinstall the system: I don't expect OMV to make it for me with an export/restore configuration operation.
    • mauromol wrote:

      What do you mean exactly by "unit file" and how can I check if it's in place / enabled?
      Systemd unit file. systemctl is-enabled openmediavault-engined.service

      mauromol wrote:

      I personally see OMV more like an appliance rather than an OS. Or, at least, I miss the feature to save settings I can change through the web UI. Saving and restoring the whole OS configuration is obviously a different story, but if we assume the basic OMV configuration can be done entirely through the UI, having the ability to export and restore all the settings the user can change from the UI would be a big plus. Exactly what all the other "embedded" NAS systems do.
      Of course, if I customise the system by changing the underlying Debian configuration, I should then take care or restoring all my customisation if I reinstall the system: I don't expect OMV to make it for me with an export/restore configuration operation.
      You still make it sound like it should be simple. I still don't know how other NASes do it. What if a drive is missing or has a different UUID or something else hardware related has changed? Maybe they don't have the hierarchy in the database like OMV where if a filesystem is gone, it screws up sharedfolders which would break plugins. Either way, it won't be me creating it and I think it will be a pain in the ass. I would rather just use lvm or btrfs snapshots to revert to a prior state on the OS drive.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Systemd unit file. systemctl is-enabled openmediavault-engined.service
      Thanks, I'll try!


      ryecoaaron wrote:


      You still make it sound like it should be simple. I still don't know how other NASes do it. What if a drive is missing or has a different UUID or something else hardware related has changed? Maybe they don't have the hierarchy in the database like OMV where if a filesystem is gone, it screws up sharedfolders which would break plugins. Either way, it won't be me creating it and I think it will be a pain in the ass. I would rather just use lvm or btrfs snapshots to revert to a prior state on the OS drive.

      I think OMV could just skip those preferences that can't be restored. Which is, I'm pretty sure, what other NASes do... A nice to have feature could be a final report that says which settings could not be restored, but as a first step simply skipping what can't be restored would be enough. I still believe that in a "normal" situation (a system upgrade by reinstall, for instance, or a boot drive failure with no backup at hand) this would help a lot.