Posts by scottjcpp

    Hey again friends.


    So OMV is Rsyncing drive a to drive b every night.

    Both identical 4TB drives


    The primary drive shows 699 GB used

    The backup drive shows 1.3 TB used


    Any thoughts on how that may have happened? I turned on delete files that don't exist on primary... ran a job... it removed some stuff but did not make them equal.


    Backstory: never NOTICED (emphasis NOTICED) this on the previous iteration of this OMV system. I reinstalled OMV due to some issues discussed and closed in other threads. I do notice the primary drive 'Data1' used to be flagged by linux as sda1 and the backup 'Data2' was sdb1 but now post install Linux calls Data1 sdb1...they are reversed. Most likely unimportant info but thought I'd share.


    Granted I'm a relative newbie and probably making a boo boo but any advice would (as always) be much appreciated.


    Thanks,


    Scott

    Hey gang. Reinstalled OMV today to overcome a laundry list of issues post upgrade on a (previous) system.

    Seems to be humming along nicely but I tried to manually run a local rsync job (two NAS drives... one to the other... just like we've done daily over the past year or so).


    Now I get an error as shown below.

    Of note: the u/i was quite buggy for me when I went back in to look at the rsync settings... the destination selection kept clearing out and the stupid browser was trying to enter 'admin'. I finally clicked the + rather than the \/ to select the destination drive. I finally forced it to accept it (and applied changes).

    But.. still not joy... same error. I'm sure it's a dumb dumb mistake... any help is appreciated.


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export SHELL=/bin/sh; sudo --shell --non-interactive -- /var/lib/openmediavault/cron.d/rsync-d4274a5f-17e9-45cf-b60e-efaa2cb19bb2 2>&1' with exit code '1':

    Error #0:
    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export SHELL=/bin/sh; sudo --shell --non-interactive -- /var/lib/openmediavault/cron.d/rsync-d4274a5f-17e9-45cf-b60e-efaa2cb19bb2 2>&1' with exit code '1': in /usr/share/openmediavault/engined/rpc/rsync.inc:263
    Stack trace:
    #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): Engined\Rpc\Rsync->Engined\Rpc\{closure}('/tmp/bgstatusqR...', '/tmp/bgoutput14...')
    #1 /usr/share/openmediavault/engined/rpc/rsync.inc(267): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
    #2 [internal function]: Engined\Rpc\Rsync->execute(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('execute', Array, Array)
    #5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Rsync', 'execute', Array, Array, 1)
    #6 {main}

    Have an unresolved issue in the forum:

    "Broken connection to shared directories"


    Since we were thus far unable to resolve that issue, out of desperation I'm prepared to reinstall OMV fresh and reconnect to the existing two NAS drives.

    Possible, yes? The system ran fine with the two drives until (well... that's on the other post). Can we connect to those healthy drives with a new install? I assume yes otherwise a situation where a user experiences computer hardware failure would be catastrophic.


    Being a nervous newbie can you point me to something perhaps already written on this subject or give me the big picture steps of what to do and more importantly what NOT to do?


    Many many thanks in advance... wanna git this sucka up and running again :-)


    Scott

    Fingers crossed someone has the key to resolving this issue. Thank you for your time and suggestions to this point.


    Worse case (I'm not there yet) a reinstall I suppose :-(


    I assume it is not a big deal to reintsall OMV and connect to the two existing drives and data again....

    OK omv-update did not seem to change anything.


    The quotaoff -v /srv/* command reported back that five differernt mountpoints or devices were not found or have no quota enabled.


    Still when trying to apply changes, I receive the error. Uggh :-)


    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 quota 2>&1' with exit code '1': Compound: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1 found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 69, column 1

    Hey there thanks. I set it to "none"... it was indeed an invalid entry. Now that I apply changes I get a different error:


    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 quota 2>&1' with exit code '1': Compound: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1 found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 69, column 1

    Error #0:
    OMV\ExecException: 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 quota 2>&1' with exit code '1': Compound: Data failed to compile:
    ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1
    found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 69, column 1 in /usr/share/php/openmediavault/system/process.inc:182

    **Comment: Clicked 'reset' for quota on each volume in the hopes something was off but that didn't help (maybe it's not in reference to a disk quota). They're all 0**


    Stack trace:
    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
    #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatush7...', '/tmp/bgoutputNU...')
    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
    #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
    #12 {main}

    Thanks for that. Your assist is much appreciated. So...


    Reset perms on the shared folders (clearing all acl’s) did not seem to resolve anything.

    Removed shared folders from services then shared folders. 'Shared folders in use' now show a blank slate.


    Applying the changes reports the following error has occured, and of course the shared folder names still advertise on the network (undoubtedly because the changes are unable to be applied). What might you suggest as the next step? As a reminder all this fun started after updates failed to be applied... then I reverted the updates.



    Error #0: OMV\ExecException: 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 monit 2>&1' with exit code '1': Compound: Data failed to compile:


    ---------- Rendering SLS 'base:omv.deploy.monit.default' failed: Jinja error: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'. Traceback (most recent call last):




    File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 498, in render_jinja_tmpl output = template.render(**decoded_context)



    File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs)


    File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True)


    File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb)


    File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb)


    File "<template>", line 37, in top-level template code


    File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 39, in get objs = db.get(id_, identifier)


    File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 85, in get query.execute()


    File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 724, in execute self._response = self._elements_to_object(elements)


    File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 485, in _elements_to_object result.validate()


    File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 235, in validate self.model.validate(self.get_dict())


    File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 200, in validate self.schema.validate(data)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 170, in validate self._validate_type(value, schema, name)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 224, in _validate_type raise last_exception


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 195, in _validate_type self._validate_object(value, schema, name)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 300, in _validate_object self._check_properties(value, schema, name)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 508, in _check_properties self._validate_type(value[propk], propv, path)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 224, in _validate_type raise last_exception


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 204, in _validate_type self._validate_string(value, schema, name)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 279, in _validate_string self._check_enum(value, schema, name)


    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 468, in _check_enum % (valuev, ", ".join(schema['enum'])), openmediavault.json.schema.SchemaValidationException: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'. ; line 37 --- [...] # http://www.debianadmin.com/mon…-servers-using-monit.html # http://www.uibk.ac.at/zid/systeme/linux/monit.html # http://wiki.ubuntuusers.de/Monit # http://viktorpetersson.com/201…-and-postgresql-on-ubuntu {% set email_config = salt['omv_conf.get']('conf.system.notification.email') %} <====================== configure_default_monit: file.managed: - name: "/etc/default/monit" - contents: [...]


    --- in /usr/share/php/openmediavault/system/process.inc:182 Stack trace:


    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuscw...', '/tmp/bgoutputxB...')

    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

    #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)

    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1) #12 {main}

    Hello friends. I'm hoping an Obi-Wan among you can help me out of this hole I've fallen into :-)


    V 5.5.13-1 (Usul)


    Applied all updates and had some failures… reverted changes. All seemed ok but now I see the shared directories (Data1 for example… as well as the others) are no longer accessible.


    Poking around, I went to modify shared folder ACLs and was presented with the following error (and details). I think we’re on to something but sadly I’m not sure where to go from here. Can someone point me off in the right direction to get on the right road again?


    **Update: If I add a NEW shared folder (within Data1) the new folder works with no issue... but the folders/directories that existed before my update woes are inaccessible. What's the best way to fix those links?**


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; setfacl --remove-all -M '/tmp/setfaclYYdfDQ' -- '/srv/dev-disk-by-label-Data1/Data1/' 2>&1' with exit code '1': setfacl: /srv/dev-disk-by-label-Data1/Data1/: No such file or directory


    Error #0: OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; setfacl --remove-all -M '/tmp/setfaclYYdfDQ' -- '/srv/dev-disk-by-label-Data1/Data1/' 2>&1' with exit code '1': setfacl: /srv/dev-disk-by-label-Data1/Data1/: No such file or directory in /usr/share/openmediavault/engined/rpc/sharemgmt.inc:1055 Stack trace: #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): Engined\Rpc\ShareMgmt->Engined\Rpc\{closure}('/tmp/bgstatusuU...', '/tmp/bgoutputV5...') #1 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(1062): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure), NULL, Object(Closure)) #2 [internal function]: Engined\Rpc\ShareMgmt->setFileACL(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setFileACL', Array, Array) #5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('ShareMgmt', 'setFileACL', Array, Array, 1) #6 {main}

    Have two WD 4TB NAS drives
    Have two USB 3.0 powered adapter trays.
    Have Raspberry PI 4 running OMV (5.3.2-1)


    OMV only seeing one of the 4TB NAS drives (sdb) on the USB 3.0 ports.


    Again newbie so my apologies but I see apparently I can NOT use RAID 1 (or any RAID for that matter) with a USB interface. True under all circumstances?
    Is there a workaround for my lovely WD NAS HDD's as storage devices?
    If no, any suggestion on getting an 'almost' RAID 1' setup (maybe with some regular automatic or manual maintenance copying data from hdd1 to hdd2?


    Help me obi wan... you're my only hope :-)


    Scott

    Files

    • IMG_1126.jpg

      (78.4 kB, downloaded 306 times, last: )