Title: Interpreting this error Last modified: January 22, 2025 --- # Interpreting this error * Resolved [sino27](https://wordpress.org/support/users/sino27/) * (@sino27) * [1 year, 4 months ago](https://wordpress.org/support/topic/interpreting-this-error/) * So I moved a website from one folder into another. During the final extraction this is the message I was presented with: DATABASE ERROR: ‘You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘mysqldump: Deprecated program name. It will be removed in a future release, u…’ at line 3′[SQL=/* DUPLICATOR-LITE( MYSQL-DUMP BUILD MODE) MYSQL SCRIPT CREATED ON : 2025-01-22 18:20:15 */ * mysqldump: Deprecated program name. It will be removed in a future release, use‘/ usr/bin/mariadb-dump’ ins…] * DATABASE ERROR: ‘Variable ‘time_zone’ can’t be set to the value of ‘NULL” [SQL =/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;…]I think I understand first error. The first error is about the deprecated mysqldump command. This is just a warning indicating that MariaDB recommends using mariadb-dump instead of mysqldump in the future. This error by itself should not affect the functionality of my site is that correct? I am using MariaDB 11.4.4What I am worried about is the second error. Can you explain this to me? In my mind the problem occurs when the time zone on the source server differs from the time zone on the destination server. The duplicator tries to set the time zone as it was on the source server, but in the migration process, this value sometimes becomes NULL. But my destination server is same as source server. * So I am interpreting this as that the duplicator when creating packages always creates a completely new SQL dump, treating the process as if you were doing a full migration to a new server. In the dump creation process, the plugin does not take into account that the destination environment is identical to the original( which is fine). So it’s trying to reset system variables that actually already exist in my MariaDB environment ?? Is that it? I don’t remember this error happening before. Note that website on destination folder works perfectly 100% normal, no issue whatsoever. All is fine I am just worried should or could this give me error down the road in the future? I don’t want ending in broken website. Therefore I ask for clarification of the error. Is it safe to ignore or something needs to be done on the server itself?Regards Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Support [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * (@mohammedeisa) * [1 year, 4 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18262169) * Hello [@sino27](https://wordpress.org/support/users/sino27/) , * Thanks for reaching out to us. * Currently, I’m discussing this topic with the team. Please wait and I will get back to you as soon as possible. * Thanks! * Plugin Support [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * (@mohammedeisa) * [1 year, 4 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18268580) * Hi [@sino27](https://wordpress.org/support/users/sino27/) , * We haven’t heard back from you in a few days, so I’m going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation. * Thanks!  * Thread Starter [sino27](https://wordpress.org/support/users/sino27/) * (@sino27) * [1 year, 4 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18269106) * I don’t understand your last comment? You said to me “Please wait and I will get back to you as soon as possible.” and now your few days later your last comment is “We haven’t heard back from you in a few days, so I’m going to go ahead and close this thread for now.” – is this automatic timed message or you are trolling me? Why is this “Resolved” ? - This reply was modified 1 year, 4 months ago by [Yui](https://wordpress.org/support/users/fierevere/). - This reply was modified 1 year, 4 months ago by [sino27](https://wordpress.org/support/users/sino27/). * Thread Starter [sino27](https://wordpress.org/support/users/sino27/) * (@sino27) * [1 year, 3 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18308247) * So what happened with your response? It’s been 3 weeks since you reported you are discussing this with your team. * Thread Starter [sino27](https://wordpress.org/support/users/sino27/) * (@sino27) * [1 year, 3 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18346898) * I am still waiting for your answer. I don’t understand why you won’t comment it. You said you will. More then a month passed since then and you are active here. You said you are commenting with your team and that you will get back to me. Why don’t you want to respond to me? * Plugin Support [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * (@mohammedeisa) * [1 year, 3 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18353424) * Hi [@sino27](https://wordpress.org/support/users/sino27/) , * Please accept my apologies for this mistake. I marked this topic as resolved by mistake. * After discussing the second error with the team, their provided me with the following feedback: * The error “DATABASE ERROR: ‘Variable ‘time_zone’ can’t be set to the value of‘ NULL” indicates that the database engine doesn’t allow setting the “NULL” as a value for the column in the problem. If you have access to the website where you create the backup, please open the database through PHPMyadmin, and change the default value of that column to another value that works with the database engine. For example, you can use CURRENT_TIMESTAMP as a default value for this column. * Please note that the problem might be with other columns. So you may need to repeat this process for all the columns. * I hope this helps, and pleas accept my apologies for closing the ticket mistakenly and for the late reply. * Thanks. * Plugin Support [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * (@mohammedeisa) * [1 year, 3 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18353441) * Hi [@sino27](https://wordpress.org/support/users/sino27/) , * Can you please let us know what are version of the database engines used in the source and destination websites? * I’m looking forward to hearing back from you. * Thanks! * Thread Starter [sino27](https://wordpress.org/support/users/sino27/) * (@sino27) * [1 year, 3 months ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18353508) * Thank you for your solution. All fine, apology accepted. Mark as resolved please and keep up the good work. * Plugin Support [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * (@mohammedeisa) * [1 year ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18488154) * Hi [@sino27](https://wordpress.org/support/users/sino27/) , * Sorry again for the late reply, I lost this topic somehow. * I’m happy that I could help you resolve your issue, this is a great news. * Please don’t hesitate to open a new topic in you need help, I’m happy to assist you. * Thanks! Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Interpreting this error’ is closed to new replies. * ![](https://ps.w.org/duplicator/assets/icon-256x256.png?rev=2906985) * [Duplicator - Backups & Migration Plugin - Cloud Backups, Scheduled Backups, & More](https://wordpress.org/plugins/duplicator/) * [Frequently Asked Questions](https://wordpress.org/plugins/duplicator/#faq) * [Support Threads](https://wordpress.org/support/plugin/duplicator/) * [Active Topics](https://wordpress.org/support/plugin/duplicator/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/duplicator/unresolved/) * [Reviews](https://wordpress.org/support/plugin/duplicator/reviews/) * 14 replies * 2 participants * Last reply from: [mohammedeisa](https://wordpress.org/support/users/mohammedeisa/) * Last activity: [1 year ago](https://wordpress.org/support/topic/interpreting-this-error/#post-18488154) * Status: resolved