Closed sebthebert closed 11 years ago
Date: 2011-11-05 00:46:03 Author: sebthebert
Ok,
it's probably related to changes I made in octo_parser & octo_uparser in the last release...
So can you just send me the Service (your_service.xml file) and some log samples that are supposed to match by mail (octo.devel@gmail.com).
I want to reproduce your bug on my server to see exactly what's going on...
I'm waiting for your data.
Date: 2011-11-05 18:49:05 Author: hollstein
I also experienced the same thing using Octopussy v1.0-rc4 in the past. It occoured rarely and I resolved that issue simply by removing the messages either by timestamp or line selection. That can be a time consuming task however! I further assume (just a thought) that it has to do with the time a specific logline resides within the "Unknown" directory in coherence with recent Octopussy (device) refreshs or (deamon) restarts.
Date: 2011-11-17 01:18:24 Author: sebthebert
Fixed in Octopussy revision 529: http://syslog-analyzer.svn.sourceforge.net/viewvc/syslog-analyzer?view=revision&revision=529
and release 1.0.1 !
Date: 2011-11-17 01:18:24 Author: sebthebert
As you asked in ticket 3432668, I open a new ticket about the bug I'm experiencing.
When I add a new service with the log wizard, the related messages stay in the unknown messages list. I can only delete them manually.
I'm 100% sure that the service is matching my messages because I used the search function on the message, and the wizard found me a matching service.
I tried to re-install Octopussy a lot of times, I'm always experiencing this. I tried on Debian 6.0 and Debian 6.0.3, same results. On the same configuration, I have no problem with Octopussy rc5, it only occurs with rc6.
Do not hesitate to ask me if you want more information, or if you want me to test something specific on my server.