on 06 Mar, 2020 09:41 AM
Ok, I've. been trying to upload/paste/link to the logs but your security systems won't allow me.
Bit from the logs it appears to lose connection at some point. (I can't see what time, as the logs aren't timestamped, but this may coincide with increased network activity over my LAN during overnight backups.
The stdout log ends at the connection failure.
Is the agent missing some reconnection logic? After all, transitory network events do occur, but judging from the logs, it didn't try and reconnect and just gave up.
This can be created as a task in task scheduler, and needs to be given admin privileges.
Perhaps the service applet can be improved so that it periodically attempts to reconnect instead of giving up forever? Otherwise, it seems to me that as soon as there is a network outage of a sufficiently long period of time the whole thing just stops without these workarounds.
on 09 Sep, 2022 11:53 AM
I wonder if there can be improvements to the cmdlet for this?
Here is how things currently are, 2.5 years later. This is the output from the host agent on a Mac when I stop the appveyor server service (Windows) for a minute or so, and then start it again.
As you can see, the host agen, never recovers, it stays forever on "Stopping Host Agent connection...".
One has to manually stop/start the service, to enable it to reconnect. Clearly you have put in some disconnection detection and reconnection logic, but it would appear that it isn't working in this case.