Hi all
We received a report of a computer where installing the 5.1.9 agent didn’t result in a normal report, and the monitoring agent was hung trying to run.
Our subscriber noticed our agent in Activitiy Monitor - called monitoring_client_error_logger and killed that process.
He’s sent in a .zip of /Library/MonitoringClient which should have all the logs we need, and we are investigating.
Historically, similar experiences have pointed to a problem on the computer itself, but it’s too early to rule out a problem with the agent.
If you happen to see anything similar, please don’t hesitate to reach out to https://support.watchmanmonitoring.com
We’ll update this post once we know more.
-Allen Hancock
We’ve isolated the problem to certain cases where the hourly logger runs into an issue reading the Teamviewer log files.
Symptoms of a computer with a related problem would the following
- Has stopped reporting on or near March 26th
- Was on version 5.1.8 of the client
- Is otherwise known to be running.
We’ll have more information soon, and will update this thread again.
If you have any questions please contact us via our support center
Thank you.
-Allen Hancock
Good evening all,
A brief follow up on this report. We’ve tweaked the related code in the 5.1.9 client, however no “smoking gun” was found. Our search for similarly effected computers turned up with just one potential case, however a reinstall of 5.1.9 fixed that as well.
Work progresses with our 5.2 agent, which promises improved logging of failures like this, and will do away with sporadic Disk IO errors.
As always, we look forward to hearing from you with any questions, concerns, or feature requests.
Best,
-Allen Hancock
This topic is now closed.