J'ai personnellement migré en 5.1 sur mon VPS.
Tout c'est bien passé, mais j'ai maintenant un soucis récurent. Toute les heures, j'ai le service tailwatchd qui est planté ...
Code:
tailwatchd failed @ Fri Jan 21 10:35:37 2011. A restart was attempted automagically.
Service Check Method: [check command] tailwatchd is not running
En regardant les logs de ce programme, voici le message d'erreur :
Code:
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
[2011-01-21 10:35:37 +0100] [main] [STOP Ok] 7447
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch::Utils::Stop] [2011-01-21 10:35:37 +0100] [main] Current process '7447' stopped
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
[2011-01-21 10:35:37 +0100] [main] [START] 27760 1295602561
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Restored /var/log/maillog (size:921802) to 904972 (requested 904972)
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Restored /var/log/exim_mainlog (size:622360) to 417226 (requested 417226)
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Caught up /var/log/maillog to 921802
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Reading back thirty lines of /var/log/maillog starting at 905418
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Restoring /var/log/maillog to catch up position 921802
[2011-01-21 10:35:37 +0100] [Cpanel::TailWatch] [INFO] Restored /var/log/maillog to position 921802
install_driver(mysql) failed: Can't load '/usr/local/lib/perl5/site_perl/5.8.8/x86_64-linux/auto/DBD/mysql/mysql.so' for module DBD::mysql: /usr/lib64/libmysqlclient.so.15: version `libmysqlclient_15' not found (required by /usr/local/l$
at /usr/local/lib/perl5/site_perl/5.8.8/x86_64-linux/DBD/mysql.pm line 14
Compilation failed in require at (eval 11) line 3.
Perhaps a required shared library or dll isn't installed where expected
at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 252
Je pense donc que cette erreur est lié, mais je n'ai pas encore ouvert un ticket, je continu à chercher une solution ...