This post is more than 5 years old
68 Posts
0
1318
Cleaning DD4500 schedule - default not working?
Hi,
i am implementing several DD4500 Systems at a customer location the last days. My customer saw a strange beahvior in the cleaning schedule. Default is at tuesday 6 AM but it was running at 3 PM. I checked time and date Settings running correct, and did not find any Problems regarding time servers or system time.
System is running firmware 5.4.0.8
Did anyone else see such a behavior with a DD and this firmware?
I will open a call in the meantime and will keep you informed
Regards,
Patric
PatrickBetts
116 Posts
0
January 23rd, 2014 14:00
Patric,
If you are on a 4500 with 5.4.0.8 and the Timezone was changed after install, you will need to reboot it for the change to take effect. It will show you the changed timezone when you run "config show timezone" but look at the uptime. If it hasn't been rebooted that change is not actually set yet.
ble1
14.3K Posts
0
January 22nd, 2014 07:00
I haven't seen it (not running 5.4), but did customer see cleaning was still running or that it kicked off at that time? Also, do you know what TZ is set on the box?
PatricJ
68 Posts
0
January 23rd, 2014 03:00
It is set to Europe/Berlin as it should be.
ble1
14.3K Posts
1
January 23rd, 2014 04:00
Check filesys clean show config to see current setting and and filesys clean status to see when it ended up last time. If configuration was not changed, you can check logs and see what happened at the time when this was supposed to work. As test, to reproduce it, you can set schedule to be today at the time when you can monitor it and see if it gets executed and what do CLI and GUI report.
PatricJ
68 Posts
0
January 23rd, 2014 07:00
Hi,
i will give it a try. I also asked the customer to check which backup Jobs were running at this time to get an overview how much the System was used at the cleaning schedule time.
ble1
14.3K Posts
0
January 23rd, 2014 13:00
Patric, if this is your customer, you most likely have their autosupport bundles so you could check from those.
PatricJ
68 Posts
1
January 24th, 2014 10:00
Rebooting again was the solution. Changing time and date Settings do not restart the ntp Service. Thanks for your help
PatrickBetts
116 Posts
0
January 24th, 2014 10:00
Dynamox,
From the 5.4 Initial Config Guide which can be found here (Page 21)
https://my.datadomain.com/custom-view/doc/appliance/5.4.x/DDOS_5.4_Initial_Config_Guide.pdf
dynamox
20.4K Posts
0
January 24th, 2014 10:00
ouch
dynamox
20.4K Posts
0
January 24th, 2014 10:00
have to reboot to change time zone ?
PatrickBetts
116 Posts
0
January 24th, 2014 10:00
Patric,
Glad to hear it's working now! Thank you for the update.
Anonymous
274.2K Posts
1
January 24th, 2014 11:00
Dynamox,
Per KB Article 1019
https://my.datadomain.com/download/kb/all/Timezone_Change_Require_Reboot.html
A reboot is required because of possible mismatches for log entries. But, more importantly, jobs run under cron (asups, cleaning, repl throttle changes, snapshots) will continue to run on the old time zone schedule until a reboot is performed.
Patric’s cleaning issue is an example.