01-13-2021 07:48 AM
Hi
I have seen TFTP restarts in the first few minutes of Jan 1st on atleast 3 different 12.5.1 clusters, although luckily no Cores and TFTP restarted on each node. Similar events are also seen in the Syslog and TFTP logs pointing to this bug. However the bug lists than only 11.5 SU versions are affected. Should TFTP restart each new year (are DST dates recalculated) or is this the bug and we have to wait either for a new SU or ES?
Thanks
Solved! Go to Solution.
01-13-2021 03:27 PM
ctftp restart is expected to rebuild DST files for the year.
ctftp failing to start after stop and producing core file has only been observed on 11.5 versions to this point and is unexpected.
01-13-2021 03:27 PM
ctftp restart is expected to rebuild DST files for the year.
ctftp failing to start after stop and producing core file has only been observed on 11.5 versions to this point and is unexpected.
01-01-2022 08:52 PM - edited 01-01-2022 08:53 PM
I saw this across a few 12.5.1 clients on January 1st 2022 shortly after midnight.
no core dump files
the cisco tftp service stopped from Cisco syslog then failed to start, service failure syslog , reason unsuccessful completion. Then it started fine on its own.
the sdl trace files didn't have much either
01-10-2023 05:10 PM - edited 01-10-2023 05:11 PM
Agree, I also experience the same on the Janury 1st 2023, cucm 12.5.1 and no core dump file
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide