On 10/2/09 16:58, Ivan Voras wrote:
> Valentin Bud wrote:
>
>
>> I noticed that it is already at 1GB. Now my problem is how can i avoid this
>> in the future because
>> on that production server mysql is crucial or in case it happens how ca I be
>> the first to know
>> of that problem?
>>
>
On Tuesday 10 February 2009 07:58:31 Ivan Voras wrote:
> Valentin Bud wrote:
> > I noticed that it is already at 1GB. Now my problem is how can i avoid
> > this in the future because
> > on that production server mysql is crucial or in case it happens how ca I
> > be the first to know
> > of that p
Valentin Bud wrote:
>
> I noticed that it is already at 1GB. Now my problem is how can i avoid this
> in the future because
> on that production server mysql is crucial or in case it happens how ca I be
> the first to know
> of that problem?
If you examine the mysql-server script in /usr/local/e
Hello community,
Today I had for the first time this problem with mysql on a production
server.
The following start flowing in the mysql-err.log
090210 9:12:17 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
1676280 bytes)
Doing a top resulted in mysql eating up about 2GB of memory of
