Cannot Apply Changes

    • OMV 1.0
    • Resolved
    • Cannot Apply Changes

      Hey, guys! I'm having an issue with applying changes. It seemed to start after I installed the Clonezilla boot kernel and made a backup. This is the error I'm receiving.

      Source Code

      1. Failed
      2. to execute command 'export LANG=C; update-rc.d 'postfix' disable
      3. 2>&1': update-rc.d: using dependency based boot sequencing
      4. insserv: warning: current start runlevel(s) (empty) of script `postfix'
      5. overrides LSB defaults (2 3 4 5).
      6. insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
      7. `postfix' overrides LSB defaults (0 1 6).
      8. insserv: warning: current start runlevel(s) (empty) of script `postfix'
      9. overrides LSB defaults (2 3 4 5).
      10. insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
      11. `postfix' overrides LSB defaults (0 1 6).
      12. insserv: warning: script 'fstrim.sh' missing LSB tags and overrides
      13. insserv: There is a loop between service watchdog and fstrim.sh if
      14. stopped
      15. insserv: loop involving service fstrim.sh at depth 2
      16. insserv: loop involving service watchdog at depth 1
      17. insserv: Stopping fstrim.sh depends on watchdog and therefore on system
      18. facility `$all' which can not be true!
      19. insserv: exiting now without changing boot order!
      20. update-rc.d: error: insserv rejected the script header
      Display All


      Also, I'm getting an error that says it cannot connect to 127.0.0.1:8083 when I login via webGUI. Any and all help would be greatly appreciated!
    • The latter error means your virtualbox module isn't loaded.

      The script "fstrim.sh" which you may have installed manually is creating a loop. Fix that and you'll be able to apply again.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • davidh2k wrote:

      The latter error means your virtualbox module isn't loaded.

      The script "fstrim.sh" which you may have installed manually is creating a loop. Fix that and you'll be able to apply again.

      Greetings
      David


      David, thank you for responding. I apologize for asking questions which may seem like common sense! When you say "fix that" are you talking about deleting the file altogether? I put this script in as preventative maintenance to keep my SSD boot drive healthy. Obviously, I'm going to have to take another path if it's causing problems at a basic level. Does OMV automatically run TRIM or is this something I need to SSH into and manually run every so often?

      I believe the VirtualBox error is in regards to the backports kernel. I'll take a closer look at that.

      Thanks so much!
    • David, it said there was problem with the header. Maybe you should take a look at the script.

      Touché....

      On the virtualbox plugin there is a button to update the modules. Click on that button and let the modules upgrade. Then uninstall and reinstall the virtualbox plugin from the plugin section and all should be good. The shared folder you used for the virtual machines will not be deleted by this and be sure to use same shared folder when you re-enable the plugin.

      On postfix:
      update-rc.d -f postfix remove
      update-rc.d postfix defaults

      The post was edited 2 times, last by tekkb ().

    • Post both your script and the watchdog script here.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Thanks for joining, Tekkb, In regards to postfix:

      Source Code

      1. root@NAS:/# update-rc.d -f postfix remove
      2. update-rc.d: using dependency based boot sequencing
      3. insserv: warning: script 'fstrim.sh' missing LSB tags and overrides
      4. insserv: There is a loop between service watchdog and fstrim.sh if stopped
      5. insserv: loop involving service fstrim.sh at depth 2
      6. insserv: loop involving service watchdog at depth 1
      7. insserv: Stopping fstrim.sh depends on watchdog and therefore on system faci
      8. `$all' which can not be true!
      9. root@NAS:/# update-rc.d postfix defaults
      10. update-rc.d: using dependency based boot sequencing
      11. insserv: warning: script 'fstrim.sh' missing LSB tags and overrides
      12. insserv: There is a loop between service watchdog and fstrim.sh if stopped
      13. insserv: loop involving service fstrim.sh at depth 2
      14. insserv: loop involving service watchdog at depth 1
      15. insserv: Stopping fstrim.sh depends on watchdog and therefore on system faci
      16. `$all' which can not be true!
      17. insserv: exiting now without changing boot order!
      18. update-rc.d: error: insserv rejected the script header
      Display All

      This was the error received after I removed the script from rc.local.

      This is now removed, but I did have this in rc.local

      Source Code

      1. ##Run “fstrim” at boot
      2. LOG=/var/log/trim.log
      3. fstrim -v / >>$LOG
      4. echo “Time: $(date)” >>$LOG


      As for the script itself made executable by chmod:

      Shell-Script

      1. #!/bin/sh
      2. #
      3. #
      4. #
      5. #Run “fstrim” command
      6. LOG=/var/log/trim.log
      7. fstrim -v / >>$LOG
      8. echo “Time: $(date)” >>$LOG
      9. exit 0

      It is located in a scripts folder, but there is a copy of it in init.d, and there is a symbolic link of it to /etc/cron.hourly/fstrim

      The post was edited 1 time, last by johndoe86x ().

    • johndoe86x wrote:

      It is located in a scripts folder, but there is a copy of it in init.d, and there is a symbolic link of it to /etc/cron.hourly/fstrim


      Then you should not have to have it in the init folder ;) Just let the cron run the one in the scripts folder.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • This line is very important as it tells the system which Shell to use in executing the script:

      #!/bin/sh

      A lot of times the sh will be symbolic link to bash (Bourne Again Shell). Each Shell's commands and syntax can vary.

      #!/bin/bash

      There are several Shells in Debian that can be used to execute commands.

      wiki.debian.org/Shell
      Images
      • dash.jpg

        53.02 kB, 341×462, viewed 334 times

      The post was edited 1 time, last by tekkb ().

    • Ok, so I went back and deleted the file from rc.local. I had no idea that would create such a fuss. I wiped all the symlinks, changed the rc.local file back to default, and then I rebooted the NAS before I ran the postfix commands inserted by tekkb. Everything seems to be back to normal. I have not uninstalled/reinstalled VirtualBox as the error message is gone after I fixed it for the backports kernel. I guess the million dollar question is .. would it be safe for me to run the script with a symlink from the scripts folder to cron.hourly? I'm just trying to keep the SSD optimized, as I've heard that Debian and OMV is very write heavy. Thank you so much for your help, guys! I'm just starting to learn some of the tricks and syntax Debian from SteamOS, OMV, and Linux Mint. You guys have been immensely helpful; which is one of the reasons that I much prefer OMV over FreeNAS. Thank you so much!
    • tekkb wrote:

      OK, your good script (make it executable) in you script folder, which must be on the system drive as data drives are mounted noexec.
      Symlink in the bin location you want to use to your script.
      In rc.local have a path line to the symlink to execute once at boot.
      Four hourly use cron job.


      Thanks, Tekkb! I had to step away from the Internet for a few days while I visited my in-laws for Christmas! I will definitely symlink according to your instructions. I'm confident I can figure it out from here, and I will mark as resolved accordingly as I don't trust my VPN and SSH from this spotty connection. Thanks, everyone, for their help!