-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HotSync: cron sync and avoid execution on slave host #6328
Comments
federicoballarini
added
bug
A defect of the software
forge
The package belongs to NethForge
labels
Nov 9, 2020
I'm going to add sync cron file, to avoid differences (in previous package some cron were deleted) and to sync also custom crons inserted in cron.daily, cron.weekly, cron.hourly, cron.monthly. Cron.d files are regenerated with nethserver-actions so is not necessary to sync them. |
federicoballarini
changed the title
Cron hourly error on hotsync slave machine
Hotsync: cron sync and avoid execution on slave host
Nov 16, 2020
federicoballarini
changed the title
Hotsync: cron sync and avoid execution on slave host
HotSync: cron sync and avoid execution on slave host
Nov 16, 2020
federicoballarini
added a commit
to NethServer/nethserver-hotsync
that referenced
this issue
Nov 16, 2020
federicoballarini
added
the
testing
Packages are available from testing repositories
label
Nov 16, 2020
Test case: OK
|
federicoballarini
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Nov 16, 2020
federicoballarini
added a commit
to NethServer/nethserver-hotsync
that referenced
this issue
Nov 26, 2020
- HotSync: cron sync and avoid execution on slave host - Bug NethServer/dev#6328 - HotSync: permissions are not fixed after master sync - Bug NethServer/dev#6335
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
run-parts /etc/cron.hourly/
Expected behavior
No errors.
Actual behavior
Components
nethserver-hotsync
See also
This happens because mysql is not running (correct), so we don't have to check and clean cdr.
@gsanchietti @Stell0 is correct that this file is called "daily_cdr_cleanup" but it is into cron.hourly folder?
The text was updated successfully, but these errors were encountered: