Mailwarning "Does not exist collectd"

nachtmensch · 15. Dezember 2016

Hi!
I just updated my omv via webgui.
(First omv-extras; Second different debian updates)
Then I restarted my system and it took minutes to boot up.

When I had access to the webui again, i saw that ups-service is not working. I stopped the service and restarted the system.
Again it took minutes to come up...
Stuck at ...syncronise systemtime...

Since the update I keep getting two emails:
1. [OMV.local.lan] monit alert -- Does not exist collectd
2. [OMV.local.lan] monit alert -- Execution failed collectd

Help, please!

P.S.: I would like to say, I don't play around with my system! I just set it up last week and since then i can not remember I changed any of my settings...
The only thing I do regulary is updating the system via webui.

votdev · 16. Dezember 2016

what is displayed in 'System Logs | Logs | UPS' ?

nachtmensch · 16. Dezember 2016

UPS-Log:

Zitat

Dec 15 18:29:40 OMV upsmon[1434]: Signal 15: exiting

Dec 15 18:29:40 OMV upsd[1416]: User monmaster@127.0.0.1 logged out from UPS [myusv]
Dec 15 18:29:40 OMV upsmon[1423]: upsmon parent: read
Dec 15 18:29:40 OMV upsd[1416]: mainloop: Interrupted system call
Dec 15 18:29:40 OMV upsd[1416]: Signal 15: exiting
Dec 15 19:44:37 OMV upsd[2387]: fopen /var/run/nut/upsd.pid: No such file or directory
Dec 15 19:44:37 OMV upsd[2387]: listening on 127.0.0.1 port 3493
Dec 15 19:44:37 OMV upsd[2387]: Connected to UPS [myusv]: usbhid-ups-myusv
Dec 15 19:44:37 OMV upsd[2387]: listening on 127.0.0.1 port 3493
Dec 15 19:44:37 OMV upsd[2387]: Connected to UPS [myusv]: usbhid-ups-myusv
Dec 15 19:44:37 OMV upsd[2406]: Startup successful
Dec 15 19:44:37 OMV upsmon[2431]: fopen /var/run/nut/upsmon.pid: No such file or directory
Dec 15 19:44:37 OMV upsmon[2431]: UPS: myusv@localhost (master) (power value 1)
Dec 15 19:44:37 OMV upsmon[2431]: Using power down flag file /etc/killpower
Dec 15 19:44:37 OMV upsmon[2438]: Startup successful
Dec 15 19:44:37 OMV upsmon[2442]: Init SSL without certificate database
Dec 15 19:44:37 OMV upsd[2406]: User monmaster@127.0.0.1 logged into UPS [myusv]
Dec 15 19:50:40 OMV upsmon[2442]: Signal 15: exiting
Dec 15 19:50:40 OMV upsd[2406]: User monmaster@127.0.0.1 logged out from UPS [myusv]
Dec 15 19:50:41 OMV upsd[2406]: mainloop: Interrupted system call
Dec 15 19:50:41 OMV upsd[2406]: Signal 15: exiting
Dec 15 21:49:14 OMV upsd[8768]: fopen /var/run/nut/upsd.pid: No such file or directory
Dec 15 21:49:14 OMV upsd[8768]: listening on 127.0.0.1 port 3493
Dec 15 21:49:14 OMV upsd[8768]: listening on 127.0.0.1 port 3493
Dec 15 21:49:14 OMV upsd[8768]: Connected to UPS [myusv]: usbhid-ups-myusv
Dec 15 21:49:14 OMV upsd[8768]: Connected to UPS [myusv]: usbhid-ups-myusv
Dec 15 21:49:14 OMV upsd[8769]: Startup successful
Dec 15 21:49:14 OMV upsmon[8787]: fopen /var/run/nut/upsmon.pid: No such file or directory
Dec 15 21:49:14 OMV upsmon[8787]: UPS: myusv@localhost (master) (power value 1)
Dec 15 21:49:14 OMV upsmon[8787]: Using power down flag file /etc/killpower
Dec 15 21:49:14 OMV upsmon[8788]: Startup successful
Dec 15 21:49:14 OMV upsmon[8789]: Init SSL without certificate database
Dec 15 21:49:14 OMV upsd[8769]: User monmaster@127.0.0.1 logged into UPS [myusv]
Dec 15 21:49:14 OMV upsd[8769]: User monmaster@127.0.0.1 logged out from UPS [myusv]
Dec 15 21:49:14 OMV upsmon[8789]: Signal 15: exiting
Dec 15 21:49:14 OMV upsmon[8804]: fopen /var/run/nut/upsmon.pid: No such file or directory
Dec 15 21:49:14 OMV upsmon[8804]: UPS: myusv@localhost (master) (power value 1)
Dec 15 21:49:14 OMV upsmon[8804]: Using power down flag file /etc/killpower
Dec 15 21:49:14 OMV upsmon[8805]: Startup successful
Dec 15 21:49:14 OMV upsmon[8806]: Init SSL without certificate database
Dec 15 21:49:14 OMV upsd[8769]: User monmaster@127.0.0.1 logged into UPS [myusv]
Dec 15 22:11:06 OMV upsmon[8806]: Signal 15: exiting
Dec 15 22:11:06 OMV upsd[8769]: User monmaster@127.0.0.1 logged out from UPS [myusv]
Dec 15 22:11:06 OMV upsd[8769]: mainloop: Interrupted system call
Dec 15 22:11:06 OMV upsd[8769]: Signal 15: exiting

Alles anzeigen

Something I found in the Boot-Log:

Zitat

2016-12-15T20:34:08+0100 OMV systemd-udevd[736]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 3, starting at character 1 ('K')

2016-12-15T20:34:08+0100 OMV systemd-udevd[736]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 4, starting at character 1 ('a')
2016-12-15T20:34:08+0100 OMV systemd-udevd[736]: invalid key/value pair in file /etc/udev/rules.d/99-openmediavault-nut-serialups.rules on line 5, starting at character 1 ('v')
2016-12-15T20:34:08+0100 OMV systemd[1]: Started udev Kernel Device Manager.
2016-12-15T20:34:08+0100 OMV systemd-udevd[771]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32.
2016-12-15T20:34:08+0100 OMV kbd[713]: setterm: $TERM is not defined.
2016-12-15T20:34:08+0100 OMV systemd[1]: Starting LSB: Set preliminary keymap...
2016-12-15T20:34:08+0100 OMV systemd[1]: Starting udev Write the /dev/root link rules...
2016-12-15T20:34:08+0100 OMV systemd[1]: Starting LSB: MD array assembly...
2016-12-15T20:34:08+0100 OMV systemd[1]: Starting LSB: Tune IDE hard disks...
2016-12-15T20:34:08+0100 OMV systemd[1]: Started LSB: Prepare console.
2016-12-15T20:34:08+0100 OMV systemd[1]: Starting LSB: Set console font and keymap...
2016-12-15T20:34:08+0100 OMV openmediavault-write_dev_root_link_rules[784]: /lib/udev/openmediavault-write_dev_root_link_rules: 34: .: Can't open /lib/udev/rule_generator.functions
2016-12-15T20:34:08+0100 OMV systemd[1]: openmediavault-udev-write-dev-rule-link-rules.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2016-12-15T20:34:08+0100 OMV systemd[1]: Failed to start udev Write the /dev/root link rules.
2016-12-15T20:34:08+0100 OMV systemd[1]: openmediavault-udev-write-dev-rule-link-rules.service: Unit entered failed state.
2016-12-15T20:34:08+0100 OMV systemd[1]: openmediavault-udev-write-dev-rule-link-rules.service: Failed with result 'exit-code'.

Alles anzeigen

Service seems to be running, but in the service list (diagnostics|services|overview) there is a red dot at UPS.

nachtmensch · 16. Dezember 2016

... From here the Systemstart hang up (5 Minutes)...

Zitat

2016-12-15T20:34:10+0100 OMV systemd[1]: Started Network Time Synchronization.

2016-12-15T20:34:10+0100 OMV ifup[1994]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0
2016-12-15T20:34:10+0100 OMV systemd[1]: Reached target System Time Synchronized.
2016-12-15T20:34:13+0100 OMV kernel: tg3 0000:03:00.0 eth0: Link is up at 1000 Mbps, full duplex
2016-12-15T20:34:13+0100 OMV kernel: tg3 0000:03:00.0 eth0: Flow control is on for TX and on for RX
2016-12-15T20:34:13+0100 OMV dhclient[1992]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2016-12-15T20:34:13+0100 OMV sh[1975]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2016-12-15T20:34:13+0100 OMV sh[1975]: DHCPACK from 192.168.0.1
2016-12-15T20:34:13+0100 OMV dhclient[1992]: DHCPACK from 192.168.0.1
2016-12-15T20:39:10+0100 OMV systemd[1]: networking.service: Start operation timed out. Terminating.
2016-12-15T20:39:10+0100 OMV systemd[1]: Failed to start Raise network interfaces.
2016-12-15T20:39:10+0100 OMV systemd[1]: networking.service: Unit entered failed state.
2016-12-15T20:39:10+0100 OMV systemd[1]: networking.service: Failed with result 'timeout'.
2016-12-15T20:39:10+0100 OMV systemd[1]: Reached target Network.
2016-12-15T20:39:10+0100 OMV systemd[1]: Reached target Network is Online.

Alles anzeigen

... later ...

Zitat

2016-12-15T20:39:41+0100 OMV monit[2316]: 'OMV' Monit 5.20.0 started

2016-12-15T20:39:42+0100 OMV monit[2316]: 'collectd' process is not running
...
2016-12-15T20:39:42+0100 OMV monit[2316]: 'collectd' trying to restart
2016-12-15T20:39:42+0100 OMV monit[2316]: 'collectd' start: '/bin/systemctl start collectd'
...
2016-12-15T20:40:12+0100 OMV monit[2316]: 'collectd' failed to start (exit status 0) -- no output
...
2016-12-15T20:40:42+0100 OMV monit[2316]: 'collectd' process is not running
2016-12-15T20:40:42+0100 OMV monit[2316]: 'collectd' trying to restart
2016-12-15T20:40:42+0100 OMV monit[2316]: 'collectd' start: '/bin/systemctl start collectd'
2016-12-15T20:41:13+0100 OMV monit[2316]: 'collectd' failed to start (exit status 0) -- no output
2016-12-15T20:41:43+0100 OMV monit[2316]: 'collectd' process is not running
2016-12-15T20:41:43+0100 OMV monit[2316]: 'collectd' trying to restart
2016-12-15T20:41:43+0100 OMV monit[2316]: 'collectd' start: '/bin/systemctl start collectd'
2016-12-15T20:42:13+0100 OMV monit[2316]: 'collectd' failed to start (exit status 0) -- no output
2016-12-15T20:42:43+0100 OMV monit[2316]: 'collectd' process is not running
2016-12-15T20:42:43+0100 OMV monit[2316]: 'collectd' trying to restart
2016-12-15T20:42:43+0100 OMV monit[2316]: 'collectd' start: '/bin/systemctl start collectd'

Alles anzeigen

2016-12-15T20:43:14+0100 OMV monit[2316]: 'collectd' failed to start (exit status 0) -- no output... this repeats until now...

nachtmensch · 16. Dezember 2016

And when I try to fix the IP-Adress of my Server i get this error:

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start networking 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.

Details:

Fehler #0:exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start networking 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code.See "systemctl status networking.service" and "journalctl -xe" for details.' in /usr/share/php/openmediavault/system/process.inc:175Stack trace:#0 /usr/share/php/openmediavault/system/systemctl.inc(83): OMV\System\Process->execute(Array, 1)#1 /usr/share/php/openmediavault/system/systemctl.inc(140): OMV\System\SystemCtl->exec('start', NULL, false)#2 /usr/share/openmediavault/engined/module/networking.inc(44): OMV\System\SystemCtl->start()#3 /usr/share/openmediavault/engined/rpc/config.inc(189): OMVModuleNetworking->startService()#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(150): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus6e...', '/tmp/bgoutputqh...')#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))#9 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#12 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)#13 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)#14 {main}

Alles anzeigen

but with /etc/network/interfaces the IP is now static!

Is it possible that my System SSD is about to die??? I don't understand what's going on!

At least the system boots up now in less then 1 Minute again.

votdev · 16. Dezember 2016

Hmmm, i also do not have an idea at the moment. The origin problem seem not the only problem on your system, so i think it is not only a UPS service issue. I had to digg into the problem.

votdev · 16. Dezember 2016

Can you please post the output of /etc/udev/rules.d/99-openmediavault-nut-serialups.rules and /etc/network/interfaces.
Please also post a screenshot of your UPS config or the text you've entered in the driver config field.

nachtmensch · 16. Dezember 2016

Actually I think the UPS service is running fine. I see all UPS-Informations like always...

I keep getting those collectd failures every minute:

Zitat

Dec 16 11:53:05 OMV rrdcached[2279]: flushing old values

Dec 16 11:53:05 OMV rrdcached[2279]: rotating journals
Dec 16 11:53:05 OMV rrdcached[2279]: started new journal /var/lib/rrdcached/journal/rrd.journal.1481885585.130228
Dec 16 11:53:07 OMV monit[2410]: 'collectd' process is not running
Dec 16 11:53:07 OMV monit[2410]: 'collectd' trying to restart
Dec 16 11:53:07 OMV monit[2410]: 'collectd' start: '/bin/systemctl start collectd'
Dec 16 11:53:38 OMV monit[2410]: 'collectd' failed to start (exit status 0) -- no output
Dec 16 11:54:08 OMV monit[2410]: 'collectd' process is not running
Dec 16 11:54:08 OMV monit[2410]: 'collectd' trying to restart
Dec 16 11:54:08 OMV monit[2410]: 'collectd' start: '/bin/systemctl start collectd'
Dec 16 11:54:38 OMV monit[2410]: 'collectd' failed to start (exit status 0) -- no output
Dec 16 11:55:08 OMV monit[2410]: 'collectd' process is not running
Dec 16 11:55:08 OMV monit[2410]: 'collectd' trying to restart
Dec 16 11:55:08 OMV monit[2410]: 'collectd' start: '/bin/systemctl start collectd'
Dec 16 11:55:39 OMV monit[2410]: 'collectd' failed to start (exit status 0) -- no output
Dec 16 11:56:09 OMV monit[2410]: 'collectd' process is not running
Dec 16 11:56:09 OMV monit[2410]: 'collectd' trying to restart
Dec 16 11:56:09 OMV monit[2410]: 'collectd' start: '/bin/systemctl start collectd'

Alles anzeigen

nachtmensch · 16. Dezember 2016

/etc/udev/rules.d/99-openmediavault-nut-serialups.rules

Zitat

# This configuration file is auto-generated.

# WARNING: Do not edit this file, your changes will be lost.
KERNEL=="driver = usbhid-ups
auto
vendorid = 051d", GROUP="nut"

/etc/network/interfaces

Zitat

# The loopback network interface

auto lo
iface lo inet loopback

# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
dns-search local.lan
pre-down ethtool -s $IFACE wol g
iface eth0 inet6 manual
pre-down ip -6 addr flush dev $IFACE

Alles anzeigen

After I rebooted omv i did a: omv-mkconf interfaces

votdev · 16. Dezember 2016

What is the output of

Bash

systemctl status collectd

nachtmensch · 16. Dezember 2016

Zitat

● collectd.service - Statistics collection and monitoring daemon

Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
Active: active (running) since Fr 2016-12-16 10:53:05 CET; 1h 55min ago
Docs: man:collectd(1)
man:collectd.conf(5)
https://collectd.org
Process: 2324 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Main PID: 2342 (collectd)
CGroup: /system.slice/collectd.service
└─2342 /usr/sbin/collectd

Dez 16 10:53:05 OMV collectd[2342]: plugin_load: plugin "load" successfully loaded.
Dez 16 10:53:05 OMV collectd[2342]: plugin_load: plugin "memory" successfully loaded.
Dez 16 10:53:05 OMV collectd[2342]: plugin_load: plugin "nut" successfully loaded.
Dez 16 10:53:05 OMV collectd[2342]: Systemd detected, trying to signal readyness.
Dez 16 10:53:05 OMV collectd[2342]: Initialization complete, entering read-loop.
Dez 16 10:53:05 OMV systemd[1]: Started Statistics collection and monitoring daemon.
Dez 16 10:53:05 OMV collectd[2342]: nut plugin: nut_read_one: upscli_connect (localhost, 3493) failed: Connection failure: Can
Dez 16 10:53:05 OMV collectd[2342]: read-function of plugin `nut' failed. Will suspend it for 20.000 seconds.
Dez 16 10:53:25 OMV collectd[2342]: Init SSL without certificate database
Dez 16 10:53:25 OMV collectd[2342]: nut plugin: Connection to (localhost, 3493) established.

Alles anzeigen

votdev · 16. Dezember 2016

First identified problem is fixed: https://github.com/openmediava…eb27dd2e2a15de222fa02b020

nachtmensch · 16. Dezember 2016

Thank you, did the change.

Rebooted OMV with this error:

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; monit summary 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused

Details:

Fehler #0:exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; monit summary 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused' in /usr/share/php/openmediavault/system/process.inc:175Stack trace:#0 /usr/share/php/openmediavault/system/monit.inc(142): OMV\System\Process->execute(Array)#1 /usr/share/php/openmediavault/system/monit.inc(161): OMV\System\Monit->status()#2 /usr/share/openmediavault/engined/module/nut.inc(105): OMV\System\Monit->isRunning()#3 /usr/share/openmediavault/engined/rpc/services.inc(56): OMVModuleNetworkUPSTools->getStatus()#4 [internal function]: OMVRpcServiceServices->getStatus(Array, Array)#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#6 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('getStatus', Array, Array)#7 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('Services', 'getStatus', Array, Array, 1)#8 {main}

Alles anzeigen

votdev · 16. Dezember 2016

It may take some time to analyse the problem.

votdev · 16. Dezember 2016

OK, applied my USV via USB to a virtual machine. Sadly i did not get any problems, so it must be something special in your setup. I saw that we should have more or less the same USV (same vendor id).

What is the output of

Bash

upsc myusv

nachtmensch · 16. Dezember 2016

Well, I'm not in a hurry. Services I need are running "stable", it's just not nice to know that a reboot takes several minutes (when not receiving an IP-Adress) and it keeps sending me E-Mails.

Thanks for your time!

Do you recomment I reinstall the system?
I just don't see what I did wrong... There wasn't a itch of a problem before I hit that update button twice yesterday evening.
Maybe "Scheiße am Finger", remember remember: don't hit that button from the bathtub

nachtmensch · 16. Dezember 2016

Looks pretty good to me!

Zitat

Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: not set
battery.mfr.date: 2011/10/24
battery.runtime: 1545
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 13.7
battery.voltage.nominal: 12.0
device.mfr: APC
device.model: Back-UPS ES 700G
device.serial: 5B1143T09919
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.vendorid: 051d
driver.version: 2.7.2
driver.version.data: APC HID 0.95
driver.version.internal: 0.38
input.sensitivity: medium
input.transfer.high: 266
input.transfer.low: 180
input.transfer.reason: input voltage out of range
input.voltage: 236.0
input.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 871.O2 .I
ups.firmware.aux: O2
ups.load: 18
ups.mfr: APC
ups.mfr.date: 2011/10/24
ups.model: Back-UPS ES 700G
ups.productid: 0002
ups.serial: 5B1143T09919
ups.status: OL
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Alles anzeigen

I don't understand why i still get:
Dec 16 21:38:34 OMV monit[2219]: 'collectd' failed to start (exit status 0) -- no output

votdev · 18. Dezember 2016

You do a lot of modifications in SNMP via extra options: defaultMonitors and linkUpDownNotifications are unknown. The origin OMV scripts do not set these parameters.

I do not know why, but some udev related files (which are shipped with Jessie) are missing in your installation causing OMV udev rules to fail.

Finally the problem seems to be the missing network. Various processes, e.g. Tftp, do not work.
Currently I do not have any idea why the network is not coming up. The related information is not included in the boot log. Maybe it is a driver problem introduced by the backport kernel or the virtual box plugin has corrupted the network stack. I do not know it.

nachtmensch · 18. Dezember 2016

Thank you very much! Don't bother yourself with it any longer please.
With "you did a lot of modification in SNMP" you mean my OMV-System. I don't know why i should change anything there... It's not even activated within the webui

It is the first problem i ever had with OMV. Also the first time I'm using Virtual Box with it. In more then two years using OMV 2 without VB there was never a problem "like" this.

Am I using backport kernel?! Never set that option on purpose. Or does it activate automaticly when installing omv-extras?

The thing about the network intressted me as well, so I checked status of OMV in my ARP-Table. My pfSense seems to "lose" contact to OMV some times...
- It is missing and suddenly coming back in the ARP-Table
I didn't See that happening with my Fhem-VM which is running on OMV actually.

Very strange all of this!

- I will set up OMV again with a fix IP for OMV and try it again

Thanx!!!

ryecoaaron · 18. Dezember 2016

Zitat von nachtmensch

Or does it activate automaticly when installing omv-extras?

No. You can install it manually with omv-extras but it does not automatically install it. Virtualbox shouldn't be causing this problem either.

Jetzt mitmachen!