System hangs at Boot when Postfix is enabled (same with pyload plugin)

    • OMV 1.0
    • Resolved

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

    • System hangs at Boot when Postfix is enabled (same with pyload plugin)

      Hi,

      i am currently building my new NAS system but today after enabling the e-mail notifications my system hangs at "Starting Mail-Tranfer Agent postfix" at boot. The system is completely dead no blinking cursor just nothing. I can only do a reset and boot into recovery and disable postfix via "update-rc.d postfix disable".

      I tried to enable it again after "dpkg-reconfigure" and choosing "No configuration" via "update-rc.d postfix enable". Before rebooting i tested the initscript with "sudo /etc/init.d/postfix start" and it worked flawlessly. But at the next boot the same thing happened again and i had to revert everything via recovery mode.

      After that i just let the notifications disabled and tried to install the pyload plugin via omv-extras. After activating the pyload service the same thing happend at the next boot. This time the system hangs at "Starting Service pyload". So i disabled pyload and the system booted without a problem.

      Specs:
      Clean install of Debian 7.6, then install of omv via packages.
      My rootfs is on software-raid 1.
      Using backports kernel 3.14
      CPU: Atom C2550
      Network: eth0 1G (was bonded, but i disabled it after the boot problems)

      As the system is brand new i could do a complete reinstall but i fear to run into the same problems again.
    • How did you install (and which version of OpenMediaVault did you Install)? On what type of OS Drive have you OpenMediaVault installed?

      A reinstallation is not a bad idea in this scenario.

      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.
    • I installed Debian 7.6 via netinst .iso and in the setup process i created my raid1 for "/" and "/home". At first boot i enabled the backports repo and installed 3.14 Kernel. After the first reboot i configured the kralizec repo and installed openmediavault-keyring and openmediavault. I guess postfix came as dependency. I dont remember the exact version of the omv package i guess something like .14 or .10, i did the system install last thursday (4.9).

      Edit: Sorry missed the os drive type: 2x 750GB WD-Black 2,5" HDD in RAID1 via mdadm

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

    • der_Typ wrote:

      I guess postfix came as dependency.


      All manual installation tutorials state to install postfix with the keyring package and OpenMediaVault on a second step. So redo it this way please ;)

      I.e. see here (though for sardaukar): Install OMV on Debian Squeeze via apt

      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.
    • Oh, guess i was too tired that day to read the instructions properly. ;)

      I will try this right now and report back. Thanks for your help!

      Edit:
      I removed everything related to openmediavault with:
      apt-get purge openmediavault
      apt-get autoremove --purge
      Then I installed postfix:
      apt-get install postfix
      Then I enabled postfix and did a reboot to test if it was working correctly -> it did
      Then I reinstalled openmediavault:
      apt-get install openmediavault
      omv-initsystem
      Despite the purge nearly the whole config was present.So i reenabled the e-mail notification and rebootet -> system hangs again at boot
      I will try a full reinstall tomorrow but i suspect some incompatibilities with some service monitors or something else omv uses, because without omv and its dependencies postfix works fine.


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

    • Sorry for double posting, but i want to bump this thread as i just did a complete reinstall of debian + omv.

      I did install everything as stated in the instructions, but after configuring e-mail notifications the same system freeze happend again after rebooting the brand new system.
      I also tried to install debian + omv in a virtual machine for testing. Inside the vm everything worked fine, no hangs no freeze.

      I have absolutely no idea why this system hangs at boot when omv+postfix is enabled. Postfix alone is working fine so i suspect something else which causes the freeze.
    • What about the syslog? Is there any helpful information?
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ok i got it to work now. I reinstalled again with following differences:
      1. Installing with root user (before i selected that i dont want to be able to login as root and instead get a user with sudo).
      2. I installed omv before anything else (so no backports repo or kernel).
      3. I installed using the remotestorage option in my IPMI interface (basically iso over lan)
      I will now try to install the backports kernel and report back asap.
    • It probably has more to do with the OS being on raid 1 than the backports kernel being an issue. In my opinion, it is as waste of drives to put the os on raid 1. You can clone or rsync the OS drive because the OS drive doesn't change that often.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • I installed on Raid1 because i plan to do some virtualization and the vms should run on the system drive so the data drives can sleep and save power. For reliability and (read) performance i choose to install a raid. I didnt suspect such issues because of a raid as system drive mainly because ive seen much more complex systems running on software-raid without issues.
      But some weird software constellation in this particular setup seems to break at least the backports kernel.

      Another thing to add is that maybe its not postfix which causes the problems but the program which is started after postfix (guess its monit, at least its the next thing to print something during boot) because even when the system boots up normaly I see a little pause between postfix and monit. Are there any tools to debug the boot process to determine which service is actually failing ?

      I took a look at my syslog and found many messages like these (every minute):

      Source Code

      1. Sep 10 01:10:37 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      2. Sep 10 01:10:37 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-used.rrd, [1410304237:1553584128.000000], 1) failed with status -1.
      3. Sep 10 01:10:37 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      4. Sep 10 01:10:47 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-free.rrd, [1410304247:91871973376.000000], 1) failed with status -1.
      5. Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      6. Sep 10 01:10:47 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-reserved.rrd, [1410304247:4999819264.000000], 1) failed with status -1.
      7. Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      8. Sep 10 01:10:47 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-used.rrd, [1410304247:1553592320.000000], 1) failed with status -1.
      9. Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      10. Sep 10 01:10:57 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-free.rrd, [1410304257:91871965184.000000], 1) failed with status -1.
      11. Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      12. Sep 10 01:10:57 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-reserved.rrd, [1410304257:4999819264.000000], 1) failed with status -1.
      13. Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      14. Sep 10 01:10:57 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-used.rrd, [1410304257:1553600512.000000], 1) failed with status -1.
      15. Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      16. Sep 10 01:11:07 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-free.rrd, [1410304267:91871956992.000000], 1) failed with status -1.
      17. Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      18. Sep 10 01:11:07 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-reserved.rrd, [1410304267:4999819264.000000], 1) failed with status -1.
      19. Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      20. Sep 10 01:11:07 sirius collectd[2467]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-used.rrd, [1410304267:1553608704.000000], 1) failed with status -1.
      21. Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
      Display All

      I havent looked into it as I plan to sleep now ;)
    • Another Update from my side:

      Today i tried different Kernels to see if all versions above 3.2 are affected. I tested several precompiled Kernels and the 3.12 backports Kernel.
      The results:As stated above i dont actually need a never Kernel than 3.2 because so far everything (hardware sided) works despite my brand new Intel Avoton based system. Something either in the configuration of the backports kernel or simply the kernel itself seems to break something crucial in my system.
      I also tried to disable concurrent boot but it did not help. Maybe i will try and build a kernel myself with the config of backports 3.14 but for now i will stick to 3.2.
    • Try this:

      demo.omv-extras.org/kernel/

      der_Typ wrote:

      Maybe i will try and build a kernel myself with the config of backports 3.14


      Nah. You should reuse the config from your 3.2 kernel, not the 3.14 backports kernel. ;)

      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:

      Try this:

      demo.omv-extras.org/kernel/


      Thank you very much! Looking at the timestamp i guess you have just built it (or at least uploaded it ;)), anyway thanks for the great support in this thread.

      The kernel is working for me, i haven't had time to test it in depth but my system is booting and everything seems to start fine. Tomorrow (or precisely today) I will continue to configure the system with this kernel.

      During installation the following messages appeared (nothing to worry about i guess):

      Source Code

      1. Hmm. There is a symbolic link /lib/modules/3.16.1-unofficial-omv-stable/build
      2. However, I can not read it: No such file or directory
      3. Therefore, I am deleting /lib/modules/3.16.1-unofficial-omv-stable/build
      4. Hmm. The package shipped with a symbolic link /lib/modules/3.16.1-unofficial-omv-stable/source
      5. However, I can not read the target: No such file or directory
      6. Therefore, I am deleting /lib/modules/3.16.1-unofficial-omv-stable/source

    • Just uploaded, but compiled about 18 dayss ago.
      It's also the RC version of the 3.16 kernel, not the final. (not sure if there is a final yet.)

      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.