Kann mir keiner sagen wo ich die values in der DB nachtragen kann?
Beiträge von Yodaxy
-
-
Hallo ich möchte gerne in OMV bei OpenVPN tcp6 auswählen können, da ich nur mit meiner ip6 auf den host zugreifen kann. Manuell habe ich dies natürlich schon umgestellt in /etc/openvpn/server
Ich habe außerdem die Datei in /www/openmediavsult/js/omv/module/admin/service/openvpn/settings.js bearbeitet und kann diese im Interface auswählen.
['udp', 'UDP'],
['tcp', 'TCP'],
['tcp6', 'TCP6'
Dies wird mir im Interface auch angezeigt nur bekomme ich nun die Fehlermeldung brim speichern, was muss ich noch ändern wo stehen diese Werte drin?? Vielen dank!
Code
Alles anzeigenprotocol: Invalid value 'tcp6', allowed values are 'udp,tcp'. Fehler #0: OMV\Json\SchemaValidationException: protocol: Invalid value 'tcp6', allowed values are 'udp,tcp'. in /usr/share/php/openmediavault/json/schema.inc:582 Stack trace: #0 /usr/share/php/openmediavault/json/schema.inc(378): OMV\Json\Schema->checkEnum(Array, Array, 'protocol') #1 /usr/share/php/openmediavault/json/schema.inc(301): OMV\Json\Schema->validateString('tcp6', Array, 'protocol') #2 /usr/share/php/openmediavault/json/schema.inc(631): OMV\Json\Schema->validateType('tcp6', Array, 'protocol') #3 /usr/share/php/openmediavault/json/schema.inc(399): OMV\Json\Schema->checkProperties(Object(stdClass), Array, '') #4 /usr/share/php/openmediavault/json/schema.inc(289): OMV\Json\Schema->validateObject(Object(stdClass), Array, '') #5 /usr/share/php/openmediavault/json/schema.inc(261): OMV\Json\Schema->validateType(Object(stdClass), Array, '') #6 /usr/share/php/openmediavault/rpc/paramsvalidator.inc(59): OMV\Json\Schema->validate(Object(stdClass)) #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(179): OMV\Rpc\ParamsValidator->validate('{"enable":true,...') #8 /usr/share/openmediavault/engined/rpc/openvpn.inc(107): OMV\Rpc\ServiceAbstract->validateMethodParams(Array, 'rpc.openvpn.set...') #9 [internal function]: OMV\Engined\Rpc\OpenVpn->setSettings(Array, Array) #10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #11 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSettings', Array, Array) #12 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('OpenVpn', 'setSettings', Array, Array, 1) #13 {main} [tt]<span id="selection-marker-1" class="redactor-selection-marker woltlab-bbcode-marker"></span>[/tt]
-
Nobody any idea for the spindown issue?
-
Hello i have a problem with fail2ban its not sending a mail. In Notification the mail was sent and it arrives from the System. I also noticed that since I installed the plugin the hdds do not go in spindown anymore. What do I have to put in the ram to restore spindown? Thanks
Edit;
I solved the problem with the Notification of fail2ban but the hdds wont go into spindown if fail2ban is on.
In which folders does fail2ban write files?
I only know these 3 folders and they are in my ram with folder2ram and the hdds do not go into spindown.
var/lib/fail2ban
etc/fail2banvar/log
-
Thank u so much!
-
Hallo ich möchte gerne eine E-Mail Benachrichtigung erhalten und bekomme leider diese Fehlermeldung wenn ich die Daten übernehmen will.
Finde leider nichts dazu und die datei etc/cron.daily/mdadm exestiert auch nicht und wurde auch nicht angelegt?
Vielen dank im vorraus! mfg yoda
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color mdadm 2>&1' with exit code '1': xxxx:
---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 18:08:52.480288 Duration: 7.394 ms Changes:
---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm is in the correct state Started: 18:08:52.488138 Duration: 149.993 ms Changes:
---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 18:08:52.638586 Duration: 100.234 ms Changes: ---------- diff: --- +++ @@ -23,6 +23,3 @@ MAILFROM root
# definitions of existing MD arrays -ARRAY /dev/md/2 metadata=1.2 name=(none):2 UUID=3c192d59:88ad15ec:642c3e7f:a4c4476a -ARRAY /dev/md/1 metadata=1.2 name=(none):1 UUID=2ad85ad0:f43e400a:06632729:0b2d562f -ARRAY /dev/md/0 metadata=1.2 name=(none):0 UUID=5d1a207e:0f22cb33:14b5d441:5de469db
---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 18:08:52.741544 Duration: 47.556 ms Changes: ---------- pid: 13744 retcode: 0 stderr: stdout:
---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 18:08:52.789733 Duration: 14.385 ms Changes: ---------- pid: 13746 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout:Summary fo rxxxxxxx
------------
Succeeded: 4 (changed=3)
Failed: 1
------------
Total states run: 5
Total run time: 319.562 msDie Konfiguration wurde geändert. Sie müssen die Änderungen bestätigen damit sie wirksam werden.
xxxxxx
Allgemeine Einstellungen
SMTP Einstellungen
Die Serveradresse des SMTP Mail Servers, z.B. smtp.meinefirma.com
Der Standardport des SMTP Mail Servers, z.B. 25 oder 587.
Empfänger
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color mdadm 2>&1' with exit code '1': xxxxxxx:
---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 18:08:52.480288 Duration: 7.394 ms Changes:
---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm is in the correct state Started: 18:08:52.488138 Duration: 149.993 ms Changes:
---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 18:08:52.638586 Duration: 100.234 ms Changes: ---------- diff: --- +++ @@ -23,6 +23,3 @@ MAILFROM root
# definitions of existing MD arrays -ARRAY /dev/md/2 metadata=1.2 name=(none):2 UUID=3c192d59:88ad15ec:642c3e7f:a4c4476a -ARRAY /dev/md/1 metadata=1.2 name=(none):1 UUID=2ad85ad0:f43e400a:06632729:0b2d562f -ARRAY /dev/md/0 metadata=1.2 name=(none):0 UUID=5d1a207e:0f22cb33:14b5d441:5de469db
---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 18:08:52.741544 Duration: 47.556 ms Changes: ---------- pid: 13744 retcode: 0 stderr: stdout:
---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 18:08:52.789733 Duration: 14.385 ms Changes: ---------- pid: 13746 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout:Summary for xxxxxx
------------
Succeeded: 4 (changed=3)
Failed: 1
------------
Total states run: 5
Total run time: 319.562 ms