cad XML-RPC response parsing failure: -510

Hi,

Upgraded one of my M370 clusters from 12.7.2 to 12.7.2 U1 today. This time from the cloud interface.

Now i see this geting logget every 5 seconds from the cluster:
2022-01-05 21:40:31 Webshop-HA2 cad XML-RPC response parsing failure: -510 - 135464-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:07 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 209744-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:12 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 211298-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:18 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 212861-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:24 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 214056-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:29 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 214824-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:45:35 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 226071-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:48:10 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 257249-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:48:16 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 258096-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug
2022-01-05 21:48:21 Webshop-HA1 cad XML-RPC response parsing failure: -510 - 258657-byte supposed UTF-8 string is not valid UTF-8. UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff3) Debug

/Robert

Comments

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @[email protected]
    Please check your policy and user names to ensure there's not any special characters (anything that isn't UTF-8.)
    The cluster (cad process) is trying to sync the configs between each other and is failing to do so because something in the config isn't valid.

    -James Carson
    WatchGuard Customer Support

  • edited January 6

    @james.carson

    I can for sure say, there is only valid UTF-8 characters in my configuration.
    The error message came the same second the upgrade started.

    This morning when i checked the cluster the error message is gone. Searching in Dimension and cloud logging do not even shows these error logs, so it seems it has not been logged. Very odd.

    If i force a cluster sync, it completes without errors:

    CLI: cluster sync configuration
    2022-01-06 08:50:30 Webshop-HA1 systemd System backup succeeded msg_id="5501-0020" Event
    2022-01-06 08:50:31 Webshop-HA2 systemd Device normal restore from server image initiated msg_id="5501-000B" Event
    2022-01-06 08:50:31 Webshop-HA2 systemd Device normal restore from server image succeeded msg_id="5501-0021" Event

    It looks as a error starting from when the update is started from the Cloud and not WSM?

    /Robert

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Could very well be -- I'd need to see a support file from the firewall to track down what is potentially going wrong.

    The specific error you were seeing suggests -something- was trying to push a character into the system that it didn't like.

    If it's coming from the cloud, I suspect it's related to international character support, which WSM/PM/FSM don't really support. There were some beta builds that would just display those characters as unicode ? or x boxes instead of nothing.

    -James Carson
    WatchGuard Customer Support

  • @james.carson

    I´ll grab a support file on the next cluster i upgrade if i see the same error message.

    /robert

Sign In to comment.