improper CRC checksums

[mcfnord]

I just noticed a new, occasional error:

"CRC mismatch in received message"

https://github.com/softins/jamulus-php/blob/master/servers.php#L648

Looks like a Jamulus server is producing packets with improper CRC checksums.

The recurrence seems very low, perhaps once every ten minutes.

I'm not sure how to learn more. Maybe logging at a debug level could reveal the server address.

[softins]

Interesting. Either a bug in the server sending, or in the PHP validation. Does it happen with all three back-ends? Do you have any clue which directory list it's in?
I could add some debug to my Linode back-end, and/or you could to the SF one.

[softins]

I have updated servers.php with commit 4cde755 so that most errors are no longer fatal with die(), but instead log the error, including the ip and port number, and continue after discarding the message.

Depending on server configuration, the error log will probably be in /var/log/php-fpm/.

The London Linode back-end is now using this code.

[mcfnord]

Logging it and making it non-fatal are both great moves. Guess I should monitor that log. I only draw from my back-end, so I can't compare results. I logged 43 instances, and tried to determine the directory, but couldn't. The pattern stopped about 12 hours ago, so I'll close this for now.

[mcfnord]

Heads up! I've seen 5 today:

CRC mismatch in received message

Still don't know which directory. Not sure I'm running your latest bits. I have another issue where my log gets a zillion of these:

[26-Mar-2023 00:07:42] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

... because I do send 7 requests at once.

Maybe if you're bored you can look at your logs for the CRC mismatch origin.

[softins]

Yes, I can see two in the logs on my London Linode back-end:

# fgrep CRC *
www-error.log:[28-Mar-2023 00:19:40 Europe/London] CRC mismatch in received message from 96.32.215.92:39059
www-error.log:[30-Mar-2023 01:30:55 Europe/London] CRC mismatch in received message from 96.32.215.92:47288

That IP is somewhere in Colorado, but at this moment there is no server registered with that IP to any directory.

[mcfnord]

Could also be Georgia. Curious there are two different ports.