@Russ That seems to have done it! I think my mistake was mostly running it as a standard user. When I switched to root and ran node agent.js --console, it did prompt me to input the token. After that I was able to restart the service and now when I check status, it always shows as active.
Thanks for your help.
@Russ Sorry I didn't specify. I'm running Debian headless inside Proxmox. I think the problem might actually be that the service is repeatedly crashing after start up. When I run doas systemctl status triggercmdagent I get this:
× triggercmdagent.service - TRIGGERcmd Agent
Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2024-05-18 17:05:02 EDT; 7min ago
Duration: 389ms
Process: 2757 ExecStart=/usr/bin/env node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData (code=exited, status=0/SUCCESS)
Main PID: 2757 (code=exited, status=0/SUCCESS)
CPU: 385ms
May 18 17:05:02 core-services systemd[1]: triggercmdagent.service: Deactivated successfully.
May 18 17:05:02 core-services systemd[1]: triggercmdagent.service: Scheduled restart job, restart counter is at 6.
May 18 17:05:02 core-services systemd[1]: Stopped triggercmdagent.service - TRIGGERcmd Agent.
May 18 17:05:02 core-services systemd[1]: triggercmdagent.service: Start request repeated too quickly.
May 18 17:05:02 core-services systemd[1]: triggercmdagent.service: Failed with result 'start-limit-hit'.
May 18 17:05:02 core-services systemd[1]: Failed to start triggercmdagent.service - TRIGGERcmd Agent.
Running
doas systemctl reset-failed triggercmdagent
doas systemctl start triggercmdagent
doas systemctl status triggercmdagent
gives me what I think is the expected output at first:
● triggercmdagent.service - TRIGGERcmd Agent
Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; preset: enabled)
Active: active (running) since Sat 2024-05-18 17:17:22 EDT; 113ms ago
Main PID: 2860 (node)
Tasks: 7 (limit: 2307)
Memory: 15.7M
CPU: 102ms
CGroup: /system.slice/triggercmdagent.service
└─2860 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData
But then checking status again right after gives me this again:
× triggercmdagent.service - TRIGGERcmd Agent
Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2024-05-18 17:17:23 EDT; 2s ago
Duration: 406ms
Process: 2860 ExecStart=/usr/bin/env node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData (code=exited, status=0/SUCCESS)
Main PID: 2860 (code=exited, status=0/SUCCESS)
CPU: 388ms
May 18 17:17:22 core-services systemd[1]: triggercmdagent.service: Deactivated successfully.
May 18 17:17:23 core-services systemd[1]: triggercmdagent.service: Scheduled restart job, restart counter is at 5.
May 18 17:17:23 core-services systemd[1]: Stopped triggercmdagent.service - TRIGGERcmd Agent.
May 18 17:17:23 core-services systemd[1]: triggercmdagent.service: Start request repeated too quickly.
May 18 17:17:23 core-services systemd[1]: triggercmdagent.service: Failed with result 'start-limit-hit'.
May 18 17:17:23 core-services systemd[1]: Failed to start triggercmdagent.service - TRIGGERcmd Agent.
Do you have any advice on how to fix the crashes?
Hi,
I've got the tcmd cli tool installed, and I tried installing triggercmdagent (headless, both foreground app and daemon), and either way, it doesn't seem to recognize when I edit the /root/.TRIGGERcmdData/commands.json file. When I run "tcmd --list", it only shows the "Gnome Editor" command that comes by default, and none of the ones I added. I even removed the Gnome Editor command and that one still shows up.
Restarting triggercmdagent (app or daemon) as well as the machine itself seems to have no effect.