egghelp/eggheads community

Psig + Eggdrop = timeout

2011-07-23T09:40:30-04:00

I fixed the issue, by another way but now with more logs i have no choice, I'll do that..

Thank you (many month later).

Statistics: Posted by fizz — Sat Jul 23, 2011 9:40 am

Psig + Eggdrop = timeout

2011-02-21T19:27:31-04:00

Pisg takes a while to parse that amount of logfiles, it does that everytime and will get slower and slower when the logfiles grow larger or get more, yes, that's normal. The solution is to not run pisg from eggdrop, but make it run every day or something via crontab. Eggdrop blocks in [exec] until the command it executes finishes, there are methods to execute stuff "in the background" - piped open or bgexec or exec with &, but I'd recommend not running pisg from eggdrop at all, crontab should suit your needs:

See http://www.df7cb.de/projects/pisg/pisg/scripts/crontab or similar

Statistics: Posted by thommey — Mon Feb 21, 2011 7:27 pm

Psig + Eggdrop = timeout

2011-02-21T19:11:24-04:00

Hi,

I have an Eggdrop with Pisg.
Eggdrop works fine, but while Pisg analyze logs, it freeze completely.
There is only 1years of log (700.000 lines), 1 file by day.

After each pisg analyze (env 1minute), Eggdrop stops responding (freeze) for another 3 or 5 minutes Oo
Sometime I have a ping timeout...

And when I launch Pisg by myself (./psig), It happens the same thing.
So I think its not directly due to Eggdrop but Pisg (I saw 99% CPU for perl, during psig running)

Have you same issue ?
If yes, how do you can keep many years of logging ?
Why Eggdrop does not respond, when I run Psig manually ?
Why Eggdrop continues to freeze when Psig finished ?

Its a VM with this configuration :
OS : Debian 6
Eggdrop : 1.6.20
Pisg : 0.72
Proc : Xeon E5520 (2 Virtual Processors)
MEM : 2Go
HD : 10Go
Log : 700K lines 34Mo

Thank you,
F.

Statistics: Posted by fizz — Mon Feb 21, 2011 7:11 pm