Scheduled job does not start automatically
-
- OMV 4.x
- Nefertiti
-
-
Sorry to insist any one got a solution?
-
Sorry to insist any one got a solution?
I have 4 scheduled jobs all set as root and that run fine as I receive email notifications, when are they set to run and what command option.
-
Well so it is not that I am going to put every 23 hours 59 minutes instead of daily.
Where should I input my email address?
I found it but
I input my google address but google block OMV saying it is not secure -
I input my google address but google block OMV saying it is not secure
You have to set up notifications for the email to work.
-
You have to set up notifications for the email to work.
I did but this is not the issue I believe, google knows I am sending an email but it is blocking it saying it is not secure I also tried with Hotmail but get nothing with test email
-
I did but this is not the issue I believe, google knows I am sending an email but it is blocking it saying it is not secure
With gmail there is a setting you have to change or allow to get gmail to work, that is how I first it up, now I use my ISP's allocated email to send it to gmail using their smtp servers.
-
Thank you took me a while how to find the setting in google but now I got swamped with two errors messages from cron
1 pihole not found I thought I removed it so
How can I remove it properly ?2 Status failed Service mountpoint_srv_dev-dis-by-label-Seagate
I am sure I am not using this disk so how to remove this mount point also? -
1 pihole not found I thought I removed it so
How can I remove it properly ?How was it installed, the last time I used Pi-Hole on OMV was in Docker, it's now on a Pi running independently
2 Status failed Service mountpoint_srv_dev-dis-by-label-Seagate
I am sure I am not using this disk so how to remove this mount point also?You'll need to edit /etc/openmediavault/config.xml and search for mnt this will locate <fstab> and <mntent> and remove the mount point from there.
-
You'll need to edit /etc/openmediavault/config.xml
Hi @Nefertiti: Please make a backup copy of that file, before doing any manual changes.
You'll need to edit /etc/openmediavault/config.xml
Hi @geaves. Is it necessary to run a script command after changing config.xml?
-
Is it necessary to run a script command after changing config.xml?
Possibly, I remember doing this myself once due to an error of my own making, but if memory serves me correctly I just rebooted, but in this case this would change an entry in the fstab, would it be necessary to run omv-mkconf fstab after editing the xml. But good call on the backup before making changes, forgot that
-
How was it installed, the last time I used Pi-Hole on OMV was in Docker, it's now on a Pi running independently
Installed it inside OMV according @'raulfg3 [HOWTO] Install Pi-Hole' since docker never worked for me and on PI it after a while It become unstableYou'll need to edit /etc/openmediavault/config.xml and search for mnt this will locate <fstab> and <mntent> and remove the mount point from there.
I think I did that yesterday, now is not in XML but instead what is in the code below and I can see it in the file system as missing
Not sure it is related I am unable to create a share folder on a new SSD mounted and formatted ext4
Code
Alles anzeigenError #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; systemctl restart 'sharedfolders-AppData.mount' 2>&1' with exit code '1': Job for sharedfolders-AppData.mount failed. See "systemctl status sharedfolders-AppData.mount" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:182 Stack trace: #0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1) #1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false) #2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart() #3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService() #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array) #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusfJ...', '/tmp/bgoutput21...') #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array) #10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array) #11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array) #13 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1) #14 {main}
Coderockpro64 systemd[1]: dev-disk-by\x2dlabel-Segate.device: Job dev-disk-by\x2dlabel-Segate.device/start timed out. Oct 30 00:07:27 rockpro64 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-Segate.device. Oct 30 00:07:27 rockpro64 systemd[1]: Dependency failed for /srv/dev-disk-by-label-Segate. Oct 30 00:07:27 rockpro64 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount/start failed with result 'dependency'. Oct 30 00:07:27 rockpro64 systemd[1]: dev-disk-by\x2dlabel-Segate.device: Job dev-disk-by\x2dlabel-Segate.device/start failed with result 'timeout'
-
There is a time out message related to a Seagate drive. Is the drive carefully connected (data & power supply)? Check connection.
-
There is a time out message related to a Seagate drive. Is the drive carefully connected (data & power supply)? Check connection.
Trust me this drive is not available anymore it has been reformatted and rename it.
-----------------------
Anyway I fixed it by editing the XML
still two Issues
Pi-hole not completely deleted.
and unable to create new or additional shared folder even on drives with shared folders already there I might create a new thread for visibility -
still two Issues
Pi-hole not completely deleted.How did you remove pihole? It should be removed using pihole uninstall I think.
https://docs.pi-hole.net/core/pihole-command/ -
How did you remove pihole? It should be removed using pihole uninstall I think.https://docs.pi-hole.net/core/pihole-command/
Exactly what I did but If you google thsi issue I am not the only one I may reinstall it and try the removal again butI know it will F#$$%^ my dns
-
How was it installed, the last time I used Pi-Hole on OMV was in Docker, it's now on a Pi running independently
You'll need to edit /etc/openmediavault/config.xml and search for mnt this will locate <fstab> and <mntent> and remove the mount point from there.
To get back to this. I removed the mnt point in config.xml, so this fine I cannot see it in disk or file system but in the log I am getting tons of warning about the missing drive
So how Can I stop this?Code
Alles anzeigensoftware="rsyslogd" swVersion="8.24.0" x-pid="1226" x-info="http://www.rsyslog.com"] rsyslogd was HUPed Nov 2 00:06:14 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:06:14 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:06:44 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:06:44 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:07:14 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:07:14 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:07:37 rockpro64 systemd[1]: dev-disk-by\x2dlabel-Segate.device: Job dev-disk-by\x2dlabel-Segate.device/start timed out. Nov 2 00:07:37 rockpro64 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-Segate.device. Nov 2 00:07:37 rockpro64 systemd[1]: Dependency failed for /srv/dev-disk-by-label-Segate. Nov 2 00:07:37 rockpro64 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount/start failed with result 'dependency'. Nov 2 00:07:37 rockpro64 systemd[1]: dev-disk-by\x2dlabel-Segate.device: Job dev-disk-by\x2dlabel-Segate.device/start failed with result 'timeout'. Nov 2 00:07:45 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:07:45 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:08:15 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:08:15 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:08:45 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:08:45 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:09:01 rockpro64 CRON[8008]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Nov 2 00:09:01 rockpro64 systemd[1]: Starting Clean php session files... Nov 2 00:09:02 rockpro64 systemd[1]: Started Clean php session files. Nov 2 00:09:16 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:09:16 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:09:44 rockpro64 cron-apt: CRON-APT RUN [/etc/cron-apt/config]: Sat Nov 2 00:06:08 PDT 2019 Nov 2 00:09:44 rockpro64 cron-apt: CRON-APT SLEEP: 186, Sat Nov 2 00:09:14 PDT 2019 Nov 2 00:09:44 rockpro64 cron-apt: CRON-APT ACTION: 0-update Nov 2 00:09:44 rockpro64 cron-apt: CRON-APT LINE: /usr/bin/apt-get -o Acquire::http::Dl-Limit=25 update -o quiet=2 Nov 2 00:09:44 rockpro64 postfix/postsuper[9523]: fatal: scan_dir_push: open directory hold: No such file or directory Nov 2 00:09:45 rockpro64 anacron[7026]: Job `cron.daily' terminated (exit status: 1) (mailing output) Nov 2 00:09:45 rockpro64 anacron[7026]: Normal exit (1 job run) Nov 2 00:09:45 rockpro64 systemd[1]: anacron.timer: Adding 1min 5.683993s random time. Nov 2 00:09:46 rockpro64 monit[1540]: Device /srv/dev-disk-by-label-Segate not found in /etc/mtab Nov 2 00:09:46 rockpro64 monit[1540]: 'mountpoint_srv_dev-disk-by-label-Segate' status failed (1) -- mountpoint: /srv/dev-disk-by-label-Segate: No such file or directory Nov 2 00:10:01 rockpro64 CRON[9582]: (root) CMD (
-
The output from the above is similar to your post 12 but this makes no sense;
Device /srv/dev-disk-by-label-Segate not found in /etc/mtabmtab?
srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount/start failed with result 'dependency'.
Timed out waiting for device dev-disk-by\x2dlabel-Segate.device.The above the same, makes no sense, it would suggest when this drive was in use it was being referenced by something and that reference be it a share or software has not been removed correctly before the drive was removed.
-
The output from the above is similar to your post 12 but this makes no sense;
Device /srv/dev-disk-by-label-Segate not found in /etc/mtabmtab?
srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dSegate.mount/start failed with result 'dependency'.
Timed out waiting for device dev-disk-by\x2dlabel-Segate.device.The above the same, makes no sense, it would suggest when this drive was in use it was being referenced by something and that reference be it a share or software has not been removed correctly before the drive was removed.
Do not worry I fixed it after reading a post from @ryecoaaron in cli I typed
omv-mkconf fstab
omv-mkconf systemd
-
@cabrio_leo that's the option when you change the mount in config.xml, omv-mkconf fstab you were right, I couldn't remember.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!