Hi I’m receiving a lot of this errors, how can I fix? Thanks
Dec 18 15:01:25 Debian-bullseye-latest-amd64-base sems[810204]: [810250/yeti:cdr/CdrWriter.cpp:823] ERROR: SQL exception on CdrWriter thread: ERROR: invalid byte sequence for encoding “UTF8”: 0x90
Dec 18 15:01:25 Debian-bullseye-latest-amd64-base sems[810204]: [810250/yeti:cdr/CdrWriter.cpp:643] ERROR: Cant write record to master database
you can ignore it - it caused by some non-utf symbols in invite, usually sent by bots. it fixed in latest versions.
Thank you for your prompt reply, but I think there is no bot because signaling on sip ports is firwalled and whitelisted only by ip. I think it’s related to our own customers…can it be possible?
restarting sems the error has disappeared. I think it was a loop as you said, thanks a lot
Yes, that’s a common UTF8 problem in Yeti-Switch CdrWriter. Even if you only allow certain IPs, strange characters in SIP headers or customer IDs can still set it off. This includes smart quotes, letters from languages other than Latin, or tags that aren’t formatted correctly. A restart clears the loop for a short time, but the long-term solution is either to upgrade to the latest version of sems/Yeti that handles invalid UTF8 well or to filter and normalize incoming strings before they reach the database. If it keeps happening, adding a logging hook to find out which headers or fields are causing the invalid bytes usually helps find the person responsible.
backported auth logs utf8 sanitizer for 1.13.
upgrade to sems-modules-yeti 1.13.109core162