Closed bastianh closed 8 years ago
Hi @bastianh, sorry to hear about this problem.
Firstly, I've made changes in 1735071f3d6b2ae905caf7842df777a36096851c to prevent the crash and instead show regex used for matching and the underlying error code.
Would you be able to pull down these changes and run znc --debug
and see what message you get when receiving a message?
Regards,
Kyle
sure .. I only got the crash about once a day but I'll keep it running with debug enabled and check the log
I found something in the logs
[2015-10-14 19:02:39.358315] (dafire/bastion) IRC -> ZNC [:Urist_Mcflyship[SRNE]!DirkJohnwood@thebastion.info PRIVMSG #lounge :it'll be 5 hours]
[2015-10-14 19:02:39.358447] Caught regex error '2' from '\.bLeebe\.[2BAD\._\.]\.b'.
I guess it's because this irc server uses/allows [
and ]
in the nickname?
@bastianh These should be escaped correctly but looks like they're not. Could you let me know what your IRC nickname is, and which keywords you have configured for mentions in Palaver. One of them looks something like Leebe.[2BAD].
from this error message.
the nick is Leebe[2BAD_]
(no dots). it's assigned from the server based on the usergroup in that community.
I have not configured any additional keywords.
Thanks for your help.
Looks like older versions of GCC have some significant problems with regex. GCC 4.9 or later should solve most regex related problems. According to the GCC 4.9 release notes (https://gcc.gnu.org/gcc-4.9/changes.html).
I think you'll need to upgrade to a more modern compiler and rebuild ZNC, and the module with it.
I've added checks for when you build the module and mentioned this in the README now (https://github.com/cocodelabs/znc-palaver/commit/e9b61749e7d84c3672d7eba53eb94a0788c28d1d).
Hi, when I'm using the znc-palaver plugin znc is crashing short after the last client disconnected with message:
the backtrace:
I have tried znc 1.6.1 and current github master.