# Asterisk logs disappearing after reboot

**URL:** <https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194>\
**Category:** AllStarLink\
**Created:** [November 14, 2026, 10:47pm UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194 "2026-11-14T22:47:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\
**Post date:** [November 14, 2026, 10:47pm UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/1 "2026-11-14T22:47:30Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![W5GLE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w5gle/32/4480_2.png) [@W5GLE](https://community.allstarlink.org/u/W5GLE)\
**Post date:** [November 14, 2026, 11:15pm UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/2 "2026-11-14T23:15:54Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 11:30pm UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/3 "2026-11-14T23:30:47Z")

</div>

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".

---

<div class="post-metadata">

**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\
**Post date:** [November 15, 2026, 12:10am UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/4 "2026-11-15T00:10:28Z")

</div>

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".

---

<div class="post-metadata">

**Author:** ![N5TIN](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/82dd89/32.png) [@N5TIN](https://community.allstarlink.org/u/N5TIN)\
**Post date:** [November 15, 2026, 5:05pm UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/5 "2026-11-15T17:05:51Z")

</div>

Another option if you just want to archive old logs is to look at logrotate. You could have it archive logs elsewhere, like a thumb drive on /mnt/usb

Steve

---

<div class="post-metadata">

**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\
**Post date:** [November 16, 2026, 1:23am UTC](https://community.allstarlink.org/t/asterisk-logs-disappearing-after-reboot/25194/6 "2026-11-16T01:23:21Z")

</div>

I may have misspoken.

I almost never look at the logs for my repeater site nodes, which run on Raspberry Pi units, as there has not been any real need to date. For one reason or another I actually looked at a few of them yesterday after performing upgrades, and noticed that the folder was purged upon reboot.

I usually review the logs for my hub nodes, which run on cloud VPS machines. They are in fact retaining logs after updates and reboots, and logrotate is indeed doing it's thing, as the folder contains zipped archives of older logs.

I can only assume a VPS installation sets up the log operation differently than a Pi appliance installation.

Sorry for the false alarm.

Eric  
K2CB
