severity 344519 normal
tags 344519 - moreinfo
thanks
hi eppie,
On Tue, Jan 03, 2006 at 09:37:44PM +0100, Eppie 1305 wrote:
> I've done some more testing and it seems that it wasn't Cacti.
>
> adding a variable thread_cache_size > 0 in my.cnf did the trick for me.
>
> This bug can be closed.
th
Hello,
I've done some more testing and it seems that it wasn't Cacti.
adding a variable thread_cache_size > 0 in my.cnf did the trick for me.
This bug can be closed.
Regards,
Epco
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC
i'll need some more information if you would like to have help with
resolving this. here are a few questions off the top of my head:
- what version of mysql?
mysql Ver 12.22 Distrib 4.0.24, for pc-linux-gnu (i386)
- remote mysql server or local?
local
- what's in my.cnf?
grep -v '#' my.cnf
Processing commands for [EMAIL PROTECTED]:
> tags 344519 unreproducible moreinfo
Bug#344519: Reload cacti graph page generates mysql zombie process for every
graph
There were no tags set.
Tags added: unreproducible, moreinfo
> thanks
Stopping processing here.
Please contact me if yo
tags 344519 unreproducible moreinfo
thanks
hi epco,
i'll need some more information if you would like to have help with
resolving this. here are a few questions off the top of my head:
- what version of mysql?
- remote mysql server or local?
- what's in my.cnf?
- how many devices (and what kind
Package: cacti
Version: 0.8.6c-7sarge2
Severity: critical
Justification: breaks the whole system
When I do a reload of the cacti graph page, I see that there is a zombie mysql
daemon process created for every graph shown.
In the end this results in over 1000 zombie processes and mysql server can
6 matches
Mail list logo