05-19-2021 01:08 PM
Wondering if any one might have insight of why and what the following means in the trapsd.log for a few systems that have yet to automaticly update themselves to 7.3.2 (Also find if in console, and set the agent to upgrade, its still reflecting 7.3.1)
Saw the following in the trapsd.log when generating a support file.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {common:LibTrapsCommon:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed converting JSON='null' to protobuf message with 3: : Root element must be a message.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed to convert json = [null] to proto, error=3
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Error downloading content, error code 3
Also seeing regular repeating instances of:
"XDR Agent failed to upgrade from version 7.3.1.20981 to version 7.3.2.26319 on xxxxxxxx"
In Agents Audit Logs for this and 4 other systems that are currently reflected as "Connected" in Status, but not yet upgraded themselves and have not since yesterday when 1000+ endpoints did.
06-30-2021 08:46 AM
@KRisselada wrote:Wondering if any one might have insight of why and what the following means in the trapsd.log for a few systems that have yet to automaticly update themselves to 7.3.2 (Also find if in console, and set the agent to upgrade, its still reflecting 7.3.1)
Saw the following in the trapsd.log when generating a support file.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {common:LibTrapsCommon:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed converting JSON='null' to protobuf message with 3: : Root element must be a message.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed to convert json = [null] to proto, error=3
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Error downloading content, error code 3
Also seeing regular repeating instances of:
"XDR Agent failed to upgrade from version 7.3.1.20981 to version 7.3.2.26319 on xxxxxxxx"In Agents Audit Logs for this and 4 other systems that are currently reflected as "Connected" in Status, but not yet upgraded themselves and have not since yesterday when 1000+ endpoints did.
Hi @KRisselada ,
This appears to a bug in the upgrade process, which would require analysis of a tech support file by our Support team. Did you happen to route to them via the Customer Support Portal to get details as to why this was occurring?
06-30-2021 08:46 AM
@KRisselada wrote:Wondering if any one might have insight of why and what the following means in the trapsd.log for a few systems that have yet to automaticly update themselves to 7.3.2 (Also find if in console, and set the agent to upgrade, its still reflecting 7.3.1)
Saw the following in the trapsd.log when generating a support file.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {common:LibTrapsCommon:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed converting JSON='null' to protobuf message with 3: : Root element must be a message.
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Failed to convert json = [null] to proto, error=3
2021/05/19T11:57:41.002-07:00 <Error> xxxxxxxxxx [19832:6520 ] {trapsd:AgentAction:591bda4f237e4e0b872fd035e106bcee(InstallUpdate):} Error downloading content, error code 3
Also seeing regular repeating instances of:
"XDR Agent failed to upgrade from version 7.3.1.20981 to version 7.3.2.26319 on xxxxxxxx"In Agents Audit Logs for this and 4 other systems that are currently reflected as "Connected" in Status, but not yet upgraded themselves and have not since yesterday when 1000+ endpoints did.
Hi @KRisselada ,
This appears to a bug in the upgrade process, which would require analysis of a tech support file by our Support team. Did you happen to route to them via the Customer Support Portal to get details as to why this was occurring?
07-22-2021 06:43 AM
thanks @gjenkins we moved beyond 7.3.x and didn't get a case raised. But will keep in mind, if see something like this next time
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
