I just noticed on a number of my nodes, that as of version Asterisk 22.10.1+asl3-3.10.8-1.deb13, a system reboot results in the \var\log\asterisk folder empty of archived logs, and messages.log only goes back as far as the time of the reboot.
Did something change with the latest updates?
Kinda makes it hard to go back and troubleshoot an issue if/when a reboot is required to restore operation. Or is there a flag/variable that now needs to be set as of the latest update?
This has been default for a while now, if you prefer to keep the logs comment the lines in /etc/fstab so they are not on the tmpfs and they will be preserved!
All of the write-heavy locations like /var/log, /tmp/, etc. have been volatile tmpfs volumes since day 1 of the ASL3 Appliance. Definitely not something that "just happened".
Strange.... I could have sworn that the messages.log file was being retained at reboot. Especially with all the reboots I was having to do with the "Exceptionally long voice queue length error messages".