Re: Starting and stopping RAID doesn't work from Cron

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



How are you mounting the filesystem? (I don't remember details from
the prior discussion)  Directly with /dev/mdXXX or are you using some
other link?  If you are using some other link then udev needs time to
get the original mdXXX creation event and then create other links
pointing to mdXXX.

And as someone else said, I would put it all in a single script and
call that single script and add dates and echo's of various sorts and
send both stderr and stdout to a log file.  I usually just appended to
the log file and then once in a while clear the file manually, but you
can also just overwrite.



On Tue, Jun 23, 2020 at 5:05 AM Patrick O'Callaghan
<pocallaghan@xxxxxxxxx> wrote:
>
> On Mon, 2020-06-22 at 18:35 +0200, Roberto Ragusa wrote:
> > On 2020-06-21 18:54, Patrick O'Callaghan wrote:
> > > 0 3 * * * root /usr/local/bin/dock up && /usr/bin/borgmatic ; /usr/local/bin/dock down
> >
> > I would suggest to avoid multiple commands on a cron entry,
> > better to have a simple /usr/local/bin/do_backup with the three commands inside.
> >
> > There you can log with "date" commands the execution the starting of each of the part
> >
> > and probably discover that the up part is working fine
> >
> > (md127: active with 2 out of 2 mirrors)
> >
> > then the backup script is failing (or not starting) and the down part is having problems,
>
> I'll consider that, but the script itself is already logging its
> actions.
>
> > apparently shutting down disks while md is still active.
> > Cron jobs have often problems with missing env variables (e.g. simplified PATH)
> > ,
> > those can also be fixed if you go the do_backup approach.
>
> The script is called with a full path, so I don't think that's it, but
> I guess I'll try it anyway.
>
> Thanks for the feedback.
>
> poc
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux