Beiträge von der_Typ

Hi,

while setting up Transmission (via omv-extras) I came across this, and as i dont know where to put it, I made this Thread.

In Transmssion it is possible to enter the desired download-folder (or share) but naturally the permissions must be set correctly (as stated inside the Plugin). I wanted to do this via OMV-Webgui but the gui only shows a few users and even fewer groups that are present on the system (I guess only users/groups created with the gui). I tried to import the group I needed because I thought the Import funtion is intended for importing system groups into OMV, but it just showed a error message that the group id was already in use (which is, of course, correct). So far I havent discovered any other method to get system groups into the gui. The rights-management in the gui is pretty nice so i would like to use it exclusively and prefer not to fiddle with both system-permissions(chown...) and omv-permissions(i guess some acl thing).

The Feature i would like to request is a third import/create option for users and groups that lets you choose a system user or group (etc/passwd,/etc/group) to import in the OMV-Gui.

I had the same errors on my system. I have two different Raids (Raid1 for system, Raid5 for data).
If the devices on the raid 5 (2 LVM Volumes) were unmounted (but formatted) the errors would come every minute, after mounting the drives the errors did go away.

So if you have unmounted drives or volumes try to mount them.

No problem, pm me when you got it ready.

Final has been released 6 days ago (3.16.2; https://www.kernel.org/), so if you got time to build it i would be happy to test it

Zitat von davidh2k

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):

Hmm. There is a symbolic link /lib/modules/3.16.1-unofficial-omv-stable/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/3.16.1-unofficial-omv-stable/build


 Hmm. The package shipped with a symbolic link /lib/modules/3.16.1-unofficial-omv-stable/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/3.16.1-unofficial-omv-stable/source

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:

• 3.12 backports kernel does not work
• 3.16 Kernel works (http://linux.exton.net/content…%80%99s-stable-kernel-316) but i cant install the headers because they depend on libc > 2.14
• 3.14 backports kernel does not work

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.

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):

Sep 10 01:10:37 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:37 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:47 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:10:57 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
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.
Sep 10 01:11:07 sirius collectd[2467]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.

I havent looked into it as I plan to sleep now

I have now installed the backports kernel via omv-extras plugin and the issue reappeared, so it has to do with the kernel.
For now i removed the backports kernel and i will use the standard kernel because i haven't had any issues with it and the main reason for backport was to get the newest version nothing else.

You can actually setup sudo in debian if you choose expert install. Expert mode is also required to setup software-raid for the root filesystem.

Ok i got it to work now. I reinstalled again with following differences:

• 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).
• I installed omv before anything else (so no backports repo or kernel).
• 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.

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.

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.

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

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.