• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

new commands aren't showing up on

General Discussion
2
6
355
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    Richard Rico
    last edited by Sep 30, 2024, 4:35 AM

    hello, I've tried using both the gui & text editor. new commands are not showing up when I use the app or the web app to view triggers. only 1 shows up. Im running ubuntu 24.x lts

    1 Reply Last reply Reply Quote 0
    • R
      Richard Rico
      last edited by Sep 30, 2024, 4:46 AM

      I ran the install script to get the service installed, got this when I tried to restart it:

      • list itemtriggercmdagent.service: Start request repeated too quickly

      • triggercmdagent.service: Failed with result 'start-limit-hit'

      • Failed to start triggercmdagent.service - TRIGGERcmd Agent.

      R 1 Reply Last reply Sep 30, 2024, 9:38 PM Reply Quote 0
      • R
        Russ @Richard Rico
        last edited by Sep 30, 2024, 9:38 PM

        @Richard-Rico, can you send me the output of this command?

        systemctl status triggercmdagent
        

        I wonder if you installed the background service while you were root. If you do that, it will use your /root/.TRIGGERcmdData folder. Generally, you want to run it like this while logged in as your user so it will use your regular user's data folder:

        sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh
        

        Either way the actual service/daemon will run as root, so the difference is which data folder it will use.

        The reason it's only giving you one command is the background agent adds/removes/runs background commands, and the foreground agent adds/removes/runs background commands.

        Look at your ~/.TRIGGERcmdData/commands.json to see which commands are background vs. foreground commands.

        Russell VanderMey

        R 2 Replies Last reply Oct 1, 2024, 2:59 AM Reply Quote 0
        • R
          Richard Rico @Russ
          last edited by Oct 1, 2024, 2:59 AM

          @Russ said in new commands aren't showing up on:

          systemctl status triggercmdagent output is below:

          rrico@localhoe:~/Downloads/keys-0930/test$ systemctl status triggercmdagent
          × triggercmdagent.service - TRIGGERcmd Agent
          Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; preset: enabled)
          Active: failed (Result: start-limit-hit) since Mon 2024-09-30 01:14:16 EDT; 21h ago
          Duration: 154ms
          Process: 1866618 ExecStart=/usr/bin/env node /usr/lib/triggercmdagent/resources/app/src/daemon.js --run /root/.TRIGGERcmdData (code=exited, status=0/SUCCESS)
          Main PID: 1866618 (code=exited, status=0/SUCCESS)
          CPU: 196ms

          Sep 30 01:14:16 localhoe systemd[1]: triggercmdagent.service: Scheduled restart job, restart counter is at 5.
          Sep 30 01:14:16 localhoe systemd[1]: triggercmdagent.service: Start request repeated too quickly.
          Sep 30 01:14:16 localhoe systemd[1]: triggercmdagent.service: Failed with result 'start-limit-hit'.
          Sep 30 01:14:16 localhoe systemd[1]: Failed to start triggercmdagent.service - TRIGGERcmd Agent.

          1 Reply Last reply Reply Quote 0
          • R
            Richard Rico @Russ
            last edited by Oct 1, 2024, 3:11 AM

            @Russ said in new commands aren't showing up on:

            systemctl status triggercmdagent

            its working now!!! I think what happened was that I originally installed this as root. To fix I did this:
            I uninstalled the background service using the tray icon & simply reinstalled it using the icon. This is my out put now:

            systemctl status triggercmdagent
            ● triggercmdagent.service - TRIGGERcmd Agent
            Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; preset: enabled)
            Active: active (running) since Mon 2024-09-30 23:07:55 EDT; 40s ago
            Main PID: 2344132 (node)
            Tasks: 15 (limit: 18707)
            Memory: 73.8M (peak: 90.6M)
            CPU: 420ms
            CGroup: /system.slice/triggercmdagent.service
            └─2344132 node /usr/lib/triggercmdagent/resources/app/src/daemon.js --run /home/rrico/.TRIGGERcmdData

            Sep 30 23:07:55 localhoe env[2344132]: Write backup completed.
            Sep 30 23:07:55 localhoe env[2344132]: |> Now connected to https://www.triggercmd.com.
            Sep 30 23:07:55 localhoe env[2344132]: ___/ For help, see: http://bit.ly/2q0QDpf
            Sep 30 23:07:55 localhoe env[2344132]: (using sails.io.js node SDK @v1.2.1)
            Sep 30 23:07:55 localhoe env[2344132]: Connected at: Mon Sep 30 2024 23:07:55 GMT-0400 (Eastern Daylight Time)
            Sep 30 23:07:55 localhoe env[2344132]: Initiated command removals
            Sep 30 23:07:55 localhoe env[2344132]: Initiated command adds
            Sep 30 23:07:55 localhoe env[2344132]: { message: 'Subscribed to 66fa0390a3b76800139976ac!' }
            Sep 30 23:07:55 localhoe env[2344132]: { message: 'Subscribed to 66fa0390a3b76800139976ac!' }
            Sep 30 23:07:55 localhoe env[2344132]: Added update-nonprod

            R 1 Reply Last reply Oct 1, 2024, 12:15 PM Reply Quote 0
            • R
              Russ @Richard Rico
              last edited by Oct 1, 2024, 12:15 PM

              @Richard-Rico, awesome, good job. I'll suggest that in the future. That's a simple way to fix it.

              Russell VanderMey

              1 Reply Last reply Reply Quote 0
              2 out of 6
              • First post
                2/6
                Last post