system check fails after upgrading joomla/moodle/joomdle

Good morning Anthony,

I am upgrading a customer's Joomla/Moodle site and have the following issue.
After upgrading Joomla (from 3.10.8 to 3.10.11) and Moodle (from 3.9.13 to 4.1+) the system check on the Joomdle Web Services fails. The reason would be that the Joomdle versions differ from each other. However, you can see in the picture that they do match.
The other lines in the system check are green. The result in this case is that users in Joomla can see their courses but have to log in twice.
Do you have any idea what could be going on here?

php version we are using: 7.4.33

Hi Peter.

I don't think I have seen this message before when the versions are the same.
Also, when showing that message, usually everything still works fine. So maybe there's a different problem and the system check is not detecting it properly....
You can try putting some debug in the code to see if you get more info:
File: administrator/components/com_joomdle/helpers/content.php
Line: 1154, after: $response = JoomdleHelperContent::call_method_debug ('system_check');
Add: print_R ($response);

And post the results.

The respons is:


Array ( [joomdle_auth] => 1 [mnet_auth] => 1 [joomdle_configured] => 1 [test_data] => It works [release] => 2.0.0 )

Antonio,

A difference in php settings between old and new server is that certain functions are disabled. In Joomla / system information / tab relevant php settings:

Disabled Functions: exec,system,passthru,shell_exec,proc_close,proc_open,dl,popen,show_source,posix_kill,posix_mkfifo,posix_getpwuid,posix_setpgid,posix_setsid,posix_setuid,posix_setgid,posix_seteuid,posix_setegid,posix_uname

Is one or more of these functions needed for the Joomdle component?

No, those functions are not needed.

But I see something very odd in your debug output:
[release] => 2.0.0

So, it is returning 2.0.0 even if you showed me that you have 2.0.4 installed. Please double check that you are really connecting to the Moodle site you are checking, because I don't understand how it can return 2.0.0 if 2.0.4 is installed.

I think I understand what is happening. We are testing the migration on another server (different IP address, same db credentials). For the test, we modified the local host file to arrive at the correct IP. Joomdle, whilst linking with Moodle (same server), probably does not take this into account and searches on the existing server?

Yes, that's what's happening: you are connecting to the live Moodle site.

> For the test, we modified the local host file to arrive at the correct IP.

Do you mean in your computer? Joomdle will need it in the server host file, as that's what it will use when connecting Joomla/Moodle.

In general, I think it is better to test the updates a on a testing environment with different URLs, changing Joomdle configuration after setting up the copy from the live sites. This is less prone to errors.

You're right offcourse. But there where so many links ...

We'll change it in the host file on the server for now. Thanks for the quick responses!

Regards,
Peter

Just to let you know,

I changed the host file on the server but that didn't go as expected. Another error appeared: Unexpected error: 23000021: ERRORCODE: accessexception.

What i did was changing the webservice protocol to REST in Joomla and Moodle and that worked => All green

Good to know that you got it working.

As for the accessexception: maybe is related to using the same token as the live site....
My recommendation for testing upgrades is issuing new tokens too, to make sure you are not connection to the live site.