Messages écrits par Jerry Lau

Hello everyone.

Running moodle version 3.6.x on redhat 7.6 64-bit with php 7.2.x and MySQL 5.7

During a restore, this error came up and where can I start to troubleshoot this for this course?

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AMD qq.surveyid = '3345'' at line 1
SELECT qrr.* FROM mdl_questionnaire_question qq INNER JOIN mdl_questionnaire_response_rank qrr ON qq.id = qrr.question_id WHERE qq.type_id = ? AND qrr.rankvalue >= ? AMD qq.surveyid = ?
[array (
0 => 8,
1 => 0,
2 => 3345,
)]
Error code: dmlreadexception
Stack trace:
  • line 486 of /lib/dml/moodle_database.php: dml_read_exception thrown
  • line 1186 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
  • line 1038 of /mod/questionnaire/classes/question/rate.php: call to mysqli_native_moodle_database->get_recordset_sql()
  • line 406 of /mod/questionnaire/backup/moodle2/restore_questionnaire_stepslib.php: call to mod_questionnaire\question\rate::move_all_nameddegree_choices()
  • line 410 of /backup/util/plan/restore_structure_step.class.php: call to restore_questionnaire_activity_structure_step->after_execute()
  • line 113 of /backup/util/plan/restore_structure_step.class.php: call to restore_structure_step->launch_after_execute_methods()
  • line 181 of /backup/util/plan/base_task.class.php: call to restore_structure_step->execute()
  • line 210 of /backup/moodle2/restore_activity_task.class.php: call to base_task->execute()
  • line 178 of /backup/util/plan/base_plan.class.php: call to restore_activity_task->execute()
  • line 168 of /backup/util/plan/restore_plan.class.php: call to base_plan->execute()
  • line 339 of /backup/controller/restore_controller.class.php: call to restore_plan->execute()
  • line 224 of /backup/util/ui/restore_ui.class.php: call to restore_controller->execute_plan()
  • line 135 of /backup/restore.php: call to restore_ui->execute()


Moyenne des évaluations  -

Hello everyone.

We have decided to move/migrate our existing Moodle 3.6.x platform in-house to service provider instead.

This is a good thing as this gives us a chance to clean things up.

We need some feedback / recommendations on the best way of doing the migration.

What is reasonably fast, safe and efficient way that we could transfer over courses that have been identified by our users that want to keep and migrate their courses, so that we don’t have to do it one-by-one manually?

If we move the entire database, that defeats the purpose of  clean-up before migration as a our database is large. We want to do this before migration.

What about settings and configurations? Can we just "migrate" them? I think this should be easier as all settings are in the database and can be migrated and restored at the new platform, no?

Recommendations?

Thanks!






Moyenne des évaluations  -

Hello folks

We are running version 3.6.x on a RHEL 7.6 64-BIT, PHP 7.7.2 and MySQL 5.7

Our external database enrolment was working great in previous versions 3.4.x but now we noticed that the enrolments are missing enrolments.

I read this and there is a subtle difference now I think

https://docs.moodle.org/37/en/External_database_enrolment#Synchronising_external_database_enrolments_.28scheduled_task_and_deprecated_script.29

Do users have to EXIST or created in moodle for this to work? In previous moodle versions, if a user does not exist but has a record in the external enrolment database and sychronized, Moodle would automatically create that account regardless if they exist in Moodle or not in the user table.

So do they have to exist before the synchronization script is called?

I am using the "/path/to/moodle/enrol/database/cli/sync.php"  just past midnight once a day.

What am I doing wrong and what areas should I check (and how to check) that my settings are okay?

Thanks

Jerry




Moyenne des évaluations  -