How To / General

Resyncronisation after desasterrecovery

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 6 days ago #1 by StefanGros
Resyncronisation after desasterrecovery was created by StefanGros
After an Ransomware attack i had to recreate my website from an older backup. I had to reinstall moodle and im port there an old db too. Now ich get "Web services error: array_key_exists(): Argument #2 ($array) must be of type array, null given" when it try to sync or change PW in Joomla. Is there a way to "resync" joomla and moodle

Please Log in or Create an account to join the conversation.

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 6 days ago #2 by StefanGros
Replied by StefanGros on topic Resyncronisation after desasterrecovery
If i switch from RRST to CML-RPC o get Call to undefined function xmlrpc_encode_request()

Please Log in or Create an account to join the conversation.

More
9 months 5 days ago #3 by Antonio Durán
Replied by Antonio Durán on topic Resyncronisation after desasterrecovery
Hi. If you restored old DBs, users should be synced already.

You need to make sure that system check is all green before doing anything else.

Please Log in or Create an account to join the conversation.

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 5 days ago #4 by StefanGros
Replied by StefanGros on topic Resyncronisation after desasterrecovery
Systemcheck is green, but the error persists because the two databases are not from the same date. I disabled userhooks, so my customers dont get the error when trying to change the passwords. I myself have a new PW in joomla but the old one in Moodle. I thought about deleting all moodleusers and let joomdle create them new in moodle.

Please Log in or Create an account to join the conversation.

More
9 months 4 days ago #5 by Antonio Durán
Replied by Antonio Durán on topic Resyncronisation after desasterrecovery
But are the users in Joomla/Moodle/Joomdle in Joomdle.->Users?

You can enable more debugging to try to find out where exactly the error is coming from.

Please Log in or Create an account to join the conversation.

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 3 days ago #6 by StefanGros
Replied by StefanGros on topic Resyncronisation after desasterrecovery
Yes they are and everything looks goo...except that users get those errors when trying to change the password. Afaikt not even everyone. If i delete everyone in moodle (except an admin account). Should i be able to recreate the moodle user accounts from Joomla? Shouldnt this give me a consistant user base in moodle?

Please Log in or Create an account to join the conversation.

More
9 months 2 days ago #7 by Antonio Durán
Replied by Antonio Durán on topic Resyncronisation after desasterrecovery
I would not recommend that: users would lose all progress in Moodle courses. Also, as you don't know the root of the problem, it may not even help.

You say it does not happen to all users. What I would do is test with a user that has the problem, first enabling "Debug system" in Joomla config, to try to get more info about the problem.

Please Log in or Create an account to join the conversation.

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 2 days ago #8 by StefanGros
Replied by StefanGros on topic Resyncronisation after desasterrecovery
I cant anyway since i am logged out from moodle too now Trying to access joomdle users:
Es ist ein Fehler aufgetreten.

0 Call to undefined function xmlrpc_encode_request()

Call Stack
# Function Location
1 () JROOT/administrator/components/com_joomdle/helpers/content.php:54
2 JoomdleHelperContent::get_request() JROOT/administrator/components/com_joomdle/helpers/content.php:165
3 JoomdleHelperContent::call_method_xmlrpc_fgc() JROOT/administrator/components/com_joomdle/helpers/content.php:314
4 JoomdleHelperContent::call_method_xmlrpc() JROOT/administrator/components/com_joomdle/helpers/content.php:294
5 JoomdleHelperContent::call_method() JROOT/administrator/components/com_joomdle/models/users.php:499
6 JoomdleModelUsers->getMoodleUsersNumber() JROOT/administrator/components/com_joomdle/models/users.php:83
7 JoomdleModelUsers->populateState() JROOT/libraries/src/MVC/Model/StateBehaviorTrait.php:59
8 Joomla\CMS\MVC\Model\BaseModel->getState() JROOT/administrator/components/com_joomdle/models/users.php:119
9 JoomdleModelUsers->getStoreId() JROOT/administrator/components/com_joomdle/models/users.php:136
10 JoomdleModelUsers->getItems() JROOT/libraries/src/MVC/View/AbstractView.php:171
11 Joomla\CMS\MVC\View\AbstractView->get() JROOT/administrator/components/com_joomdle/views/users/view.html.php:27
12 JoomdleViewUsers->display() JROOT/libraries/src/MVC/Controller/BaseController.php:697
13 Joomla\CMS\MVC\Controller\BaseController->display() JROOT/administrator/components/com_joomdle/controller.php:50
14 JoomdleController->display() JROOT/libraries/src/MVC/Controller/BaseController.php:730
15 Joomla\CMS\MVC\Controller\BaseController->execute() JROOT/administrator/components/com_joomdle/joomdle.php:28
16 require_once() JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:71
17 Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}() JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:73
18 Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch() JROOT/libraries/src/Component/ComponentHelper.php:361
19 Joomla\CMS\Component\ComponentHelper::renderComponent() JROOT/libraries/src/Application/AdministratorApplication.php:150
20 Joomla\CMS\Application\AdministratorApplication->dispatch() JROOT/libraries/src/Application/AdministratorApplication.php:205
21 Joomla\CMS\Application\AdministratorApplication->doExecute() JROOT/libraries/src/Application/CMSApplication.php:304
22 Joomla\CMS\Application\CMSApplication->execute() JROOT/administrator/includes/app.php:58
23 require_once() JROOT/administrator/index.php:32

Please Log in or Create an account to join the conversation.

  • StefanGros
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
More
9 months 2 days ago #9 by StefanGros
Replied by StefanGros on topic Resyncronisation after desasterrecovery
So since i have no courses where a progress is important i decided to delete the moodle users. What i forgot/didnt know was that the deletion in moodle resultet in the deletion in joomla - a thing that should NEVER EVER happen in my enviroment, since all usermanagemtn is only made in Joomla and not in moodle. So i had to restore the Joomla site from Backup. Just to get the red screen of death in joomla (error 500 - oops something went wrong). I initiated debug mode with littel help, but since i had the idea that joomdle is the killer i disabled all plugins in the database (after another restore) and i was able to access the backend. Now i have to say that i am a bit frightened to enable to plugins again or reinstall joomdle. My priorities are in the stability of the joomla-site so whatever happens in moodle should not kill my joomla site.

Please Log in or Create an account to join the conversation.

More
9 months 2 days ago #10 by Antonio Durán
Replied by Antonio Durán on topic Resyncronisation after desasterrecovery
Sorry to hear that. Joomdle will delete Joomla users when deleting them in Moodle if you have the sync option enabled.

As for your previous message: it seems you left xmlrpc in joomdle settings, instead of going back to REST.

As for the 500 error...You can enable joomdle plugins one by one to find if any of them was causing it... if you restored from the same backup as before, I don't know why this time you are getting these problems.

Please Log in or Create an account to join the conversation.