View Issue Details

IDProjectCategoryView StatusLast Update
0004561unrealircdpublic2016-09-30 13:53
Reportermagic000 Assigned Totmcarthur  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version4.0.1 
Summary0004561: Error logs get filled up with an unexplained error message
DescriptionSeemingly every 30 seconds several lines of the following error are added to the error.log, which makes it both unusable since it is spammed with this message and grows very fast several hundred KB a minute. This is occurring only when the flag "errors" is used.

[Thu Jan 28 19:25:18 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:25:48 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:25:48 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:25:48 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:26:18 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:26:18 2016] - [BUG?] kevent returned 2
[Thu Jan 28 19:26:18 2016] - [BUG?] kevent returned 2

This is occurring in a FreeBSD 10.2 jail. No misbehaviour of the ircd process has been observed, i.e. the server is working as usual despite the error log getting filled with the above stated message.
Steps To ReproduceRunning 4.0.1 as usual with flag "errors" added under the log block.
Additional Information4.0.1 is compiled with remote includes.
3rd party modules

Activities

syzop

2016-01-30 10:37

administrator   ~0019079

Travis: since you have already been working on the kevent I/O engine for hours, fixing nenolod's bugs, this one is for you :D

tmcarthur

2016-02-07 21:06

reporter   ~0019095

Having a look - if everything else appears to be working this is likely a false alarm or an unexpected return code that does not indicate an error in our code but just a quirk in the kqueue engine. I'll fully investigate though to validate that is the case.

syzop

2016-02-29 11:05

administrator   ~0019102

Travis: It was reproducible for you? Did you find & fix the issue?

magic000

2016-03-07 00:56

reporter   ~0019125

I am too looking forward to having this resolved. Currently running without the error log and that's hardly optimal. Thanks for your reminder, Syzop.

syzop

2016-03-11 14:28

administrator   ~0019135

Ok, I'm not going to delay the 4.0.2 release for this, it has been a month already. I've now silenced these errors, they will only appear when compiled with DEBUGMODE. I'm not sure if it's the right move but since you say it works otherwise well, and Travis says too, I'm going for that for now..

Travis: can you still look into this?

magic000

2016-03-11 15:29

reporter   ~0019136

If only i will be able to use error log and do so via syslog, I am all good. No awkward behavior observed of any other sort, as said, and i've been running 4.0.1 for over a month now.

syzop

2016-03-11 17:39

administrator   ~0019137

Last edited: 2016-03-11 17:40

Thanks for the information. I've released 4.0.2 which includes the necessary changes. I'm leaving this bug open until Travis has looked fully into the issue.

magic000

2016-03-19 18:57

reporter   ~0019141

Last edited: 2016-03-19 18:58

Syslog logging works as expected in 4.0.2. Thanks for the fix.

syzop

2016-09-30 13:53

administrator   ~0019433

The warning was removed a few versions ago and I looked at this myself while debugging another issue. The error pops up when trying to delete a write notification event (from the SSL code path). It's completely harmless, though it would be even better if we save ourselves the unnecessary function call. Not really important.

Issue History

Date Modified Username Field Change
2016-01-30 10:21 magic000 New Issue
2016-01-30 10:35 syzop Assigned To => tmcarthur
2016-01-30 10:35 syzop Status new => assigned
2016-01-30 10:37 syzop Note Added: 0019079
2016-02-07 21:06 tmcarthur Note Added: 0019095
2016-02-29 11:05 syzop Note Added: 0019102
2016-03-07 00:56 magic000 Note Added: 0019125
2016-03-11 14:28 syzop Note Added: 0019135
2016-03-11 15:29 magic000 Note Added: 0019136
2016-03-11 17:39 syzop Note Added: 0019137
2016-03-11 17:40 syzop Note Edited: 0019137
2016-03-11 17:40 syzop Note Edited: 0019137
2016-03-19 18:57 magic000 Note Added: 0019141
2016-03-19 18:58 magic000 Note Edited: 0019141
2016-09-30 13:53 syzop Note Added: 0019433
2016-09-30 13:53 syzop Status assigned => closed
2016-09-30 13:53 syzop Resolution open => fixed