Thanks Jeff, I never thought of that possibility. Is there a way to figure out what the run level was, when it was booted up?
Also I have another update, I could reproduce it consistently on the ATT based AEP conduit now. However I removed the /sbin/angel dependency from my startup scripts, I just use the following
My environment variables in my start scripts.
NAME="TestLoraUplinkPktManager"
APP_LOGDIR="/var/log/app"
# Use MultiTech Provided $APP_DIR environment variable
DAEMON="/usr/bin/node"
DAEMON_ARGS="$APP_DIR/app.js > $APP_LOGDIR/$NAME.log 2>&1"
RUN_DIR=$APP_DIR
START_STOP_DAEMON="/usr/sbin/start-stop-daemon"
PID_FILE="/var/run/$NAME.pid"
My start script for my app. Let me know if you see any concerns with the start script.
$START_STOP_DAEMON --start --background --pidfile "$PID_FILE" --make-pidfile --chdir "$RUN_DIR" --startas /bin/bash -- -c "exec $DAEMON $DAEMON_ARGS"
Even though the application hasn’t started the app-manager believes the application has started successfully, even though there is no app running with that PID as stored in the pid file.
Thanks,
Ajay