New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration serveur + blockedlog #13233
Comments
Can you compare the 2 first lines of table llx_blockedlog to see how it is in old database and in new database ? Is there any difference of 11 byte between following fields : If it is similar (check seriously field object_data), can you tell if you change your PHP version. From which version to which version ? Can you compare the timezone of the PHP, and the timezone of the Database. Finally can your run this command lien program on your old environment and on your new one and cut and past results for both: |
Hello eldy, Thank you for your return and your script, here is the result: Old server: #!/usr/bin/env php New server: #!/usr/bin/env php in addition, I changed the time zone in php.ini on the new server with the same as the old one. thank you so much |
Bug
Suite migration un dolibarr v10.0.1 d’un serveur sur un autre, tous les logs inéaltérables précédents sont en rouge (notés corrompus), puis le premier log suivant affiche dans l’infobulle « Le journal archivé semble valide par rapport au précédent mais la chaîne était corrompue auparavant » :
https://www.dolibarr.fr/forum/t/migration-serveur-blockedlog/32094
Environment
The text was updated successfully, but these errors were encountered: