Problem: During the earlier disk-full incident, the agent’s local cache files got truncated to 0 bytes while trying to write to a full disk:<\/p>\n\n\n\n
The agent kept limping along until the reboot, then failed to start at all because it couldn’t parse an empty state file \u2014 and since the service has no auto-restart configured, it just sat failed from then on.<\/p>\n\n\n\n
Fix \u2014 moved the corrupted files aside (not deleted) and restarted the service:<\/p>\n\n\n\n
sudo mkdir -p \/usr\/local\/ltechagent\/corrupt-backup-20260813
sudo mv \/usr\/local\/ltechagent\/state \/usr\/local\/ltechagent\/state_old \/usr\/local\/ltechagent\/corrupt-backup-20260813\/
sudo mv \/usr\/local\/ltechagent\/monitors\/* \/usr\/local\/ltechagent\/corrupt-backup-20260813\/
sudo systemctl restart ltechagent.service<\/p>\n\n\n\n
The agent’s actual identity\/config (agent_config) was untouched \u2014 only the runtime state cache was corrupted \u2014 so on restart it rebuilt fresh state using its existing registration and reconnected to pams.pahosted.com.au without needing a reinstall.<\/p>\n\n\n\n
Let me know if you still want Restart=on-failure added to the unit file so it self-heals if this happens again.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Problem: During the earlier disk-full incident, the agent’s local cache files got truncated to 0 bytes while trying to write to a full disk: The agent kept […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9814","post","type-post","status-publish","format-standard","hentry","category-research"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t