• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  1. Home
  2. Wesley Galdino de Farias
  • Profile
  • Following 1
  • Followers 0
  • Topics 1
  • Posts 3
  • Best 0
  • Controversial 0
  • Groups 0

Wesley Galdino de Farias

@Wesley Galdino de Farias

0
Reputation
1
Profile views
3
Posts
0
Followers
1
Following
Joined Sep 23, 2021, 3:13 PM Last Online May 9, 2024, 4:09 PM

Wesley Galdino de Farias Unfollow Follow

Latest posts made by Wesley Galdino de Farias

  • RE: Trigeercmdagent start, but it does not work

    Thanks for your reply, and I'm sorry for the huge delay to reply you.
    You are totally right I was made this 'ground' mistake.

    Thanks

    posted in Instructions
    W
    Wesley Galdino de Farias
    Nov 17, 2021, 7:03 PM
  • RE: Trigeercmdagent start, but it does not work

    I've fixed the problem, but not in elegant way.
    I've changed triggercmdagent service systemd file located in: /etc/systemd/system/triggercmdagent.service

    From this:
    ExecStart=/usr/bin/env node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

    To this:
    ExecStart=/usr/bin/env node /usr/share/triggercmdagent/app/src/agent.js --console >/dev/null 2>/dev/null &

    From now on, it is working good.

    If someone has the reight solution for this problem, I'd like to know. Tks

    posted in Instructions
    W
    Wesley Galdino de Farias
    Oct 15, 2021, 5:01 PM
  • Trigeercmdagent start, but it does not work

    Hi,

    I've installed triggercmdagent, it is start without any erros, but it is not working.

    Bellow, the 'systemctl status triggercmdagent'

    ● triggercmdagent.service - TRIGGERcmd Agent
    Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; vendor preset: enabled)
    Active: active (running) since Fri 2021-10-15 09:59:56 -03; 7s ago
    Main PID: 1996 (node)
    Tasks: 11 (limit: 4435)
    CGroup: /system.slice/triggercmdagent.service
    └─1996 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

    Oct 15 09:59:58 ubuntu env[1996]: Logging in with saved token to run background tasks.
    Oct 15 09:59:58 ubuntu env[1996]: Write backup completed.
    Oct 15 09:59:59 ubuntu env[1996]: |> Now connected to https://www.triggercmd.com.
    Oct 15 09:59:59 ubuntu env[1996]: ___/ For help, see: http://bit.ly/2q0QDpf
    Oct 15 09:59:59 ubuntu env[1996]: (using sails.io.js node SDK @v1.1.13)
    Oct 15 09:59:59 ubuntu env[1996]: Connected at: Fri Oct 15 2021 09:59:59 GMT-0300 (Brasilia Standard Time)
    Oct 15 09:59:59 ubuntu env[1996]: Initiated command removals
    Oct 15 09:59:59 ubuntu env[1996]: Initiated command adds
    Oct 15 09:59:59 ubuntu env[1996]: { message: 'Subscribed to 61697726d340a9001b5131be!' }
    Oct 15 09:59:59 ubuntu env[1996]: { message: 'Subscribed to 61697726d340a9001b5131be!' }

    I've noticed that, when I create a new command, in commands.json file and restart the service, it does not sync with the triggercmd site, but when I start the triggercmd with the --console option, just like that:

    node /usr/share/triggercmdagent/app/src/agent.js --console

    Everything works properly and the new command syncs with the site.

    What I must do to fix this?

    Tks.

    posted in Instructions
    W
    Wesley Galdino de Farias
    Oct 15, 2021, 1:07 PM