FastAGI did not start after VM Reboot

FreePBX Installation / Upgrade
1

Hi,

I was wondering that some incoming calls did not work as expected. Analyzing the Asterisk log show that FollowMe did not work, because FastAGI failed. An ss -lntp | grep 4573 confirmed that.

I have rebooted the FreePBX VM yesterday because of a Debian Kernel update. It seems that the FastAGI failed to start during the boot phase. Unfortunately no one has seen this issue - no emails, no warning visible in the FreePBX dashboard.

A simple fwconsole restart solved the situation.

As FastAGI seems to run under node, I’m not sure if this message I found in the syslog during the reboot is related:

2026-01-21T14:56:43.511243+01:00 pbx fwconsole[1313]: The process “runuser ‘asterisk’ -s ‘/bin/bash’ -c ‘cd /var/www/html/admin/modules/pm2/node && mkdir -p /home/asterisk/.pm2 && mkdir -p /var/www/html/admin/modules/pm2/node/logs && export HOME=/home/asterisk && export PM2_HOME=/home/asterisk/.pm2 && export ASTLOGDIR=/var/log/asterisk && export ASTVARLIBDIR=/var/lib/asterisk && export PATH=$HOME/.node/bin:$PATH && export NODE_PATH=$HOME/.node/lib/node_modules:$NODE_PATH && export MANPATH=$HOME/.node/share/man:$MANPATH && /var/www/html/admin/modules/pm2/node/node_modules/pm2/bin/pm2 jlist’” exceeded the timeout of 60 seconds.

Has anyone an idea why that stuff did not start well after the reboot?

2

Did you upgrade the node packages from Debian repos ?

There’s been some recent discussion about this in another topic Security Upgradable Packages Kept Back.

3

No, I didn’t. The packages are still on hold here.

I guess that 60 seconds timeout is a bit tough after reboot. It does not happen with an “fwconsole restart”. Looks like timing for me, I think it does not make it always within this time when the load pressure is high (during cold startup).

I’ve added a 30 seconds delay to the freepbx service in the service file to shift that “timeout” more out of the load pressure. I’ll see if this helps at the next Kernel update.

4

Curious if it is networking that is not coming online quickly, or if throwing more resources at the VM resolves the issue, e.g., RAM, CPU, etc.