On Thu, Aug 5, 2010 at 4:22 PM, Aaron Cooper <[email protected]> wrote:

>  Thanks Jochen,
>
> Does your cron script check for errors, or is it just running a Repair each
> time? A repair on each table seems to be rather intensive on the server even
> for just one DB.
>

just checking for "uptime" of the specific function.

KR, Jochen



>
> A
>
> ----- Original Message -----
> *From:* Jochen Daum <[email protected]>
> *To:* [email protected]
> *Sent:* Thursday, August 05, 2010 1:20 PM
> *Subject:* Re: [phpug] MySQL automated maintenance/notifications
>
> Hi,
>
> of many sites we manage or host, only 2 of them get corruption of MySQL
> tables. It is easiest to either build a custom test script that runs with
> cron or buy a web monitoring service for the same purpose. If it involves
> notifying by text message, the web monitoring services appear always the
> easiest and cheapest way.
>
> Kind Regards,
>
> Jochen Daum
>
> Chief Automation Officer
> Automatem Ltd
>
> Phone: 09 630 3425
> Mobile: 021 567 853
> Email: [email protected]
> Skype: jochendaum
> Website: www.automatem.co.nz
> http://twitter.com/automatem
> http://nz.linkedin.com/in/automatem
> http://www.xing.com/go/invite/3425509.181107
> http://www.aucklandbusinessnetworking.co.nz
>
>
> On Thu, Aug 5, 2010 at 1:16 PM, Aaron Cooper <[email protected]>wrote:
>
>>  Hi all,
>>
>> We just had a case where a table in a MySQL 5 database was "flagged as
>> stopped" and needed to be repaired. We only discovered this as a certain
>> segment of a site was not functioning correctly.
>>
>> Anyone care to share how they manage either:
>>
>> a) Automated maintenance/repair
>> b) Automated notification of common MySQL table issues
>>
>> Cheers
>> Aaron
>>
>>
>>
>>     [email protected]
>>  mbl: +64 21 577 155
>>  www.zanzomedia.com
>>
>>       The information in this email or any attachment is confidential and
>> may be legally privileged. It is intended solely for the intended recipient.
>> Access to this email by anyone else is unauthorised. If you are not the
>> intended recipient, any disclosure, copying, distribution or any action
>> taken or omitted to be taken in reliance on it, is unauthorised and
>> prohibited. Such action may breach copyright or otherwise be unlawful. If
>> you have received this email in error, please delete and destroy all copies.
>>
>> --
>> NZ PHP Users Group: http://groups.google.com/group/nzphpug
>> To post, send email to [email protected]
>> To unsubscribe, send email to
>> [email protected]<nzphpug%[email protected]>
>
>
> --
> NZ PHP Users Group: http://groups.google.com/group/nzphpug
> To post, send email to [email protected]
> To unsubscribe, send email to
> [email protected]<nzphpug%[email protected]>
>
>  --
> NZ PHP Users Group: http://groups.google.com/group/nzphpug
> To post, send email to [email protected]
> To unsubscribe, send email to
> [email protected]<nzphpug%[email protected]>
>

-- 
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]

Reply via email to