Page 1 of 2
Invalid payload in message. [Solved]
Posted: Mon 03 Oct 2022 2:58 pm
by Mapantz
Never seen this error before:
Code: Select all
2022-10-03 12:03:06.205 WLL broadcast: Invalid payload in message. Percentage good packets 100.00% - (1,375575)
Code: Select all
2022-10-03 12:03:42.207 WLL broadcast: Invalid payload in message. Percentage good packets 99.97% - (104,375589)
104 of those in 36 seconds.
Re: Invalid payload in message.
Posted: Mon 03 Oct 2022 6:31 pm
by mcrossley
MX checks the multicast contents, and if it does not start with
Rejects the data with that message.
If you switch on data logging it should dump out what was actually received.
Re: Invalid payload in message.
Posted: Wed 30 Nov 2022 1:25 am
by Mapantz
Got nailed with this again
https://postimg.cc/ZBhTtHZw
I don't enable the debug, because I don't know when its going to happen.
Re: Invalid payload in message.
Posted: Wed 30 Nov 2022 11:21 am
by mcrossley
It would make sense to log the received data for these errors, I'll add that into the next build. You may then have something to either point to the error source, or to report back to Davis.
Re: Invalid payload in message.
Posted: Wed 30 Nov 2022 8:37 pm
by Mapantz
Cheers Mark.
Had a bunch more this afternoon. It's all rather weird.
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 3:50 pm
by Mapantz
And again..
I had logging on this time.
20221201-135833.zip
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 5:27 pm
by mcrossley
Interesting that the string sent starts with "STR_BCAST", so it does look like the WLL is in a bit of mess.
That is followed by some null chars then "RQ1.0.0"
I'll report this to the Davis dev who looks after the WLL firmware and see what he says...
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:00 pm
by Mapantz
Thanks Mark.
I've noticed that the number of these errors is increasing. I only restarted CMX an hour ago, and there's already been 132.
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:18 pm
by mcrossley
I have had a reply from Davis, it looks unlikely that this is coming from the WLL.
An internet search shows that some printers (or printer software embedded in an IOS(?) app) broadcasts on the same port as the WLL (22222) and uses a string starting with "STR_BCAST" - see:
https://github.com/mprinter/mprinter-io ... ter.m#L154
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:28 pm
by Mapantz
Oh dear.
Nothing is this house is Apple, so it must be from another house?!
I cannot be the only one to suffer this issue, surely?
So there's no way to stop this happening?
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:34 pm
by mcrossley
If you look at the log, the WLL broadcasts are still coming in every 2.5 seconds, but there are bursts of these spurious messages.
No printer on your network then?
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:35 pm
by Mapantz
mcrossley wrote: ↑Thu 01 Dec 2022 6:34 pm
If you look at the log, the WLL broadcasts are still coming in every 2.5 seconds, but there are bursts of these spurious messages.
No printer on your network then?
Nope, no printer here.
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 6:43 pm
by mcrossley
It could be a process of detective work, was any other network attached device switched on, or accessed at the time the messages came in?
Re: Invalid payload in message.
Posted: Thu 01 Dec 2022 10:06 pm
by Mapantz
It's getting worse.
Nothing is being switched on or accessed.
There's no way I'll be able to solve this.
Something I have noticed; The LAN light comes on and flashes when the errors start occurring.
Re: Invalid payload in message.
Posted: Fri 02 Dec 2022 8:05 am
by rogerthn
I did have intermittent disturbances on my LAN and the likely culprit was the PSU on one switch. When the switch finally gave up the 12V PSU voltage was less than 5V.