# The connpgm and discpgm don’t seem to be working

**URL:** <https://community.allstarlink.org/t/the-connpgm-and-discpgm-don-t-seem-to-be-working/25073>\
**Category:** AllStarLink\
**Tags:** asl3\
**Created:** [October 13, 2026, 11:11pm UTC](https://community.allstarlink.org/t/the-connpgm-and-discpgm-don-t-seem-to-be-working/25073 "2026-10-13T23:11:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![W6DAD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6dad/32/5258_2.png) [@W6DAD](https://community.allstarlink.org/u/W6DAD)\
**Post date:** [October 13, 2026, 11:11pm UTC](https://community.allstarlink.org/t/the-connpgm-and-discpgm-don-t-seem-to-be-working/25073/1 "2026-10-13T23:11:35Z")

</div>

Fresh install of ASL 3 10/6/26

Both commands will not pass node information, , to bash scripts designed to create a log file of connections of disconnections.

As an example, Supermon creates a log (connectlog) of connects and disconnects and is viewable when selecting the “Conection Log” tab. There is no log file created in its respective directory: /var/log/asterisk/ .

Yes I know this is a “third party” program.

Using the examples for programming connpgm and discpgm scripts from the Allstar manual I created the bash scripts and necessary commands for execution.

The Allstar’s example scripts for connect and disconnect work, they create a log file but, the log file is empty. All the necessary ownership and permission and read/write parameters are correct for this log file.

I then went back and manually executed the script used by Supermon by manually adding the necessary info and it correctly wrote the log file.

**w6dad@node62113:/usr/local/sbin/supermon $** sudo ./smlogger 1 62113 54117

The Supermon script works; it creates the log file.

Since the Supermon script works and the Allstar bash script sort of works my conclusion is that when executing the connpmg or discpgm the necessary info need, , is not being passed to either script.

I also have spoken to another Allstar user who noticed that after updating ALS via the cockpit on or around Sept. 15, his connection logging stopped working. My other node using Supermon is working fine, I’ve not updated ASL since June on that node.

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [October 13, 2026, 11:18pm UTC](https://community.allstarlink.org/t/the-connpgm-and-discpgm-don-t-seem-to-be-working/25073/2 "2026-10-13T23:18:45Z")

</div>

The [asl3\_asterisk] 3.10.5 update had a few issues related to `connpgm` and `discpgm`. We believe that these issues have all been addressed in the 3.10.8 update, currently in "beta" testing.

For more info, see : [2026.10.11 - Package Updates - Beta Channel](https://community.allstarlink.org/t/2026-10-11-package-updates-beta-channel/25063)

---

<div class="post-metadata">

**Author:** ![W6NIJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/3d9bf3/32.png) [@W6NIJ](https://community.allstarlink.org/u/W6NIJ)\
**Post date:** [October 14, 2026, 3:09pm UTC](https://community.allstarlink.org/t/the-connpgm-and-discpgm-don-t-seem-to-be-working/25073/3 "2026-10-14T15:09:21Z")

</div>

I had some trouble with duplicate messages a while back but never blank log files on the few nodes that I've personally done. I'm waiting for the fine tuning to get released to update all the nodes and will report back. Thanks everyone.