Hello all,
The problem is solved, I will write info, maybe it can help someone.
It all started when I changed the database colation (I made the mistake that Moodle was not in maintenance mode, and students were working on Moodle while the script was making changes). I'm not sure if this could create duplicates in the Moodle database?
Solution:
I exported the database with the --insert-ignore option (to avoid exporting duplicates), created the new database, and then imported the previously exported database.
After I imported the database without duplicates and started the update again, it works. At the moment everything is working and there seems to be no problems.
I hope this will be helpful to others with the same problem.
Sincerely Jeff
The problem is solved, I will write info, maybe it can help someone.
It all started when I changed the database colation (I made the mistake that Moodle was not in maintenance mode, and students were working on Moodle while the script was making changes). I'm not sure if this could create duplicates in the Moodle database?
Solution:
I exported the database with the --insert-ignore option (to avoid exporting duplicates), created the new database, and then imported the previously exported database.
After I imported the database without duplicates and started the update again, it works. At the moment everything is working and there seems to be no problems.
I hope this will be helpful to others with the same problem.
Sincerely Jeff