starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #268] Checks awaiting first synchronization #2118

New issue

Closed

opened 2026-03-14 02:37:48 +03:00 by kerem · 9 comments

kerem commented

2026-03-14 02:37:48 +03:00

Owner

Originally created by @JerresonJ on GitHub (Feb 5, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/268

Originally assigned to: @wh1te909 on GitHub.

I've got one agent stuck on "checks awaiting first synchronization"
V 0.4.6 Agent V 1.4.3

I've uninstalled and re-installed this agent but it still gets stuck here. Any pointers?

Originally created by @JerresonJ on GitHub (Feb 5, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/268 Originally assigned to: @wh1te909 on GitHub. I've got one agent stuck on "checks awaiting first synchronization" V 0.4.6 Agent V 1.4.3 I've uninstalled and re-installed this agent but it still gets stuck here. Any pointers?

kerem

2026-03-14 02:37:48 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 02:38:04 +03:00

Author

Owner

@wh1te909 commented on GitHub (Feb 5, 2021):

open cmd as admin and run
"C:\Program Files\TacticalAgent\tacticalrmm.exe" -m runchecks -log debug -logto stdout
will print alot of debug info should see the error there

@wh1te909 commented on GitHub (Feb 5, 2021): open cmd as admin and run ```"C:\Program Files\TacticalAgent\tacticalrmm.exe" -m runchecks -log debug -logto stdout``` will print alot of debug info should see the error there

kerem commented

2026-03-14 02:38:09 +03:00

Author

Owner

@JerresonJ commented on GitHub (Feb 5, 2021):

There was no error there at all. But it still says awaiting first synchronization

==============================================================================

GET  /api/v3/blahblahblah/checkrunner/  HTTP/1.1
HOST   : api.blahblahblah
HEADERS:
        Accept: application/json
        Authorization: Token blahblahblah
        Content-Type: application/json
        User-Agent: go-resty/2.4.0 (https://github.com/go-resty/resty)
BODY   :
***** NO CONTENT *****
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 200 OK
PROTO        : HTTP/1.1
RECEIVED AT  : 2021-02-05T17:23:23.5723231-05:00
TIME DURATION: 135.998ms
HEADERS      :
        Allow: GET, PATCH, HEAD, OPTIONS
        Content-Length: 614
        Content-Type: application/json
        Date: Fri, 05 Feb 2021 22:22:04 GMT
        Referrer-Policy: same-origin
        Server: nginx
        Vary: Origin
        X-Content-Type-Options: nosniff
        X-Frame-Options: DENY
BODY         :
{
   "agent": 12,
   "check_interval": 120,
   "checks": [
      {
         "id": 3,
         "assigned_tasks": [
            {
               "id": 3,
               "enabled": true
            }
         ],
         "script": null,
         "check_type": "eventlog",
         "status": "pending",
         "threshold": null,
         "disk": null,
         "ip": null,
         "script_args": [],
         "timeout": null,
         "svc_name": null,
         "pass_if_start_pending": null,
         "pass_if_svc_not_exist": false,
         "restart_if_stopped": null,
         "log_name": "Application",
         "event_id": 15006,
         "event_id_is_wildcard": false,
         "event_type": "ERROR",
         "event_source": "MSExchangeTransport",
         "event_message": "Exchange Transport service is rejecting messages because available disk space is below",
         "fail_when": "contains",
         "search_last_days": 1,
         "agent": 12
      }
   ]
}
==============================================================================

@JerresonJ commented on GitHub (Feb 5, 2021): There was no error there at all. But it still says awaiting first synchronization ============================================================================== ~~~ REQUEST ~~~ GET /api/v3/blahblahblah/checkrunner/ HTTP/1.1 HOST : api.blahblahblah HEADERS: Accept: application/json Authorization: Token blahblahblah Content-Type: application/json User-Agent: go-resty/2.4.0 (https://github.com/go-resty/resty) BODY : ***** NO CONTENT ***** ------------------------------------------------------------------------------ ~~~ RESPONSE ~~~ STATUS : 200 OK PROTO : HTTP/1.1 RECEIVED AT : 2021-02-05T17:23:23.5723231-05:00 TIME DURATION: 135.998ms HEADERS : Allow: GET, PATCH, HEAD, OPTIONS Content-Length: 614 Content-Type: application/json Date: Fri, 05 Feb 2021 22:22:04 GMT Referrer-Policy: same-origin Server: nginx Vary: Origin X-Content-Type-Options: nosniff X-Frame-Options: DENY BODY : { "agent": 12, "check_interval": 120, "checks": [ { "id": 3, "assigned_tasks": [ { "id": 3, "enabled": true } ], "script": null, "check_type": "eventlog", "status": "pending", "threshold": null, "disk": null, "ip": null, "script_args": [], "timeout": null, "svc_name": null, "pass_if_start_pending": null, "pass_if_svc_not_exist": false, "restart_if_stopped": null, "log_name": "Application", "event_id": 15006, "event_id_is_wildcard": false, "event_type": "ERROR", "event_source": "MSExchangeTransport", "event_message": "Exchange Transport service is rejecting messages because available disk space is below", "fail_when": "contains", "search_last_days": 1, "agent": 12 } ] } ==============================================================================

kerem commented

2026-03-14 02:38:14 +03:00

Author

Owner

@wh1te909 commented on GitHub (Feb 5, 2021):

tacticalrmm.zip

please try same command with this exe. Don't need to replace the exe in program files, just put this exe wherever u want but call it same way with -m runchecks -log debug -logto stdout
this one should print some more debug info and then paste output please

@wh1te909 commented on GitHub (Feb 5, 2021): [tacticalrmm.zip](https://github.com/wh1te909/tacticalrmm/files/5935717/tacticalrmm.zip) please try same command with this exe. Don't need to replace the exe in program files, just put this exe wherever u want but call it same way with `-m runchecks -log debug -logto stdout` this one should print some more debug info and then paste output please

kerem commented

2026-03-14 02:38:19 +03:00

Author

Owner

@JerresonJ commented on GitHub (Feb 5, 2021):

Using the new .exe above.

tacticalrmm.exe -m runchecks -log debug -logto stdout

That had the exact same output as above. There was no additional output.

@JerresonJ commented on GitHub (Feb 5, 2021): Using the new .exe above. ``` tacticalrmm.exe -m runchecks -log debug -logto stdout ``` That had the exact same output as above. There was no additional output.

kerem commented

2026-03-14 02:38:24 +03:00

Author

Owner

@wh1te909 commented on GitHub (Feb 5, 2021):

lol sorry im retarded. bug in event log check with latest agent xD i'll have a new release out shortly with the fix

@wh1te909 commented on GitHub (Feb 5, 2021): lol sorry im retarded. bug in event log check with latest agent xD i'll have a new release out shortly with the fix

kerem commented

2026-03-14 02:38:30 +03:00

Author

Owner

@JerresonJ commented on GitHub (Feb 5, 2021):

LOL - no problem. I'll update when I can. Thanks.

@JerresonJ commented on GitHub (Feb 5, 2021): LOL - no problem. I'll update when I can. Thanks.

kerem commented

2026-03-14 02:38:35 +03:00

Author

Owner

@wh1te909 commented on GitHub (Feb 5, 2021):

tacticalrmm.zip
can you try please with this exe just as a sanity check before i release :)

@wh1te909 commented on GitHub (Feb 5, 2021): [tacticalrmm.zip](https://github.com/wh1te909/tacticalrmm/files/5935780/tacticalrmm.zip) can you try please with this exe just as a sanity check before i release :)

kerem commented

2026-03-14 02:38:40 +03:00

Author

Owner

@JerresonJ commented on GitHub (Feb 5, 2021):

Definitely way more output there and now the interface says checks are passing. So it appears to be fixed in that version of the exe. Looks like it properly searched the event logs that time.

@JerresonJ commented on GitHub (Feb 5, 2021): Definitely way more output there and now the interface says checks are passing. So it appears to be fixed in that version of the exe. Looks like it properly searched the event logs that time.

kerem commented

2026-03-14 02:38:45 +03:00

Author

Owner

@wh1te909 commented on GitHub (Feb 6, 2021):

thanks, released in 1.4.4

@wh1te909 commented on GitHub (Feb 6, 2021): thanks, released in 1.4.4