Hi,
We are running two servers (both w2k3, Apache 2.2.4 openssl 0.9.8d, Mysql 5.0.27 - server A is running PHP 5.2.1 and server B 5.2.0)
Both are also running Moodle 1.8.2+ and all environmental checks are coming up as OK.
We have set up Mnet on both as a P2P connection but we can only connect one way. When trying to connect from server A to server B we get the following error:
RPC auth/mnet/user_authorise:Time gap with our moodle site (137 seconds) is greater than the permitted maximum of 15 secondsERROR 6:6:Time gap with our moodle site (137 seconds) is greater than the permitted maximum of 15 seconds
We have double and triple checked all the settings for Mnet and all appear OK - especially as we can connect from Server B to server A with no trouble at all!
Is this is problem with Server A or with Server B Mnet settings?
Is the difference in PHP version affecting this?
Any help on this would be appreciated
Thank you in advance
Damian
Time Gap Error - Peer to Peer
Number of replies: 3Re: Time Gap Error - Peer to Peer
It's exactly what it says: the clocks on the servers are out of sync. Ensure your servers are right-in-sync with the time in the world with ntpd or ntpdate on both, and never look back.
The Mnet protocol has some time-sensitive stuff -- and we saw some "misterious failures" that were cured fixing the time. That's why we check.
Likely FAQ?
The Mnet protocol has some time-sensitive stuff -- and we saw some "misterious failures" that were cured fixing the time. That's why we check.
Likely FAQ?
Re: Time Gap Error - Peer to Peer
Yeap, that was in our case. The time on one of the application server was out 15.5 seconds.
~Robert
Re: Time Gap Error - Peer to Peer
Just an FYI on this, it isn't necessarily the difference in the time on 2 different servers.
We are hosted multiple moodle's on the SAME server and got this time gap error when we tried to do the networking between them.
Same server 'should not' cause a time gap between servers, since only one server
, at least that's what you would think, but the error kept happening.
I found that load_user_capability() was a really slow query, (still looking into why it runs slow when networking) and I think this caused the "time gap" for us.
Since I couldn't find out where to, via moodle admin controls, to change that 15 value I added it to the code in mnet/xmlrpc/client.php right after the "if ($time_offset > 0) {" around line 267, so we have:
$time_offset = $remote_timestamp - $timestamp_send;
if ($time_offset > 0) {
set_config('drift_threshold', 60, 'mnet');
etc...
Probably just a band aid solution but just wanted to throw it out there in case someone else is pulling out their hair over this.
M=
We are hosted multiple moodle's on the SAME server and got this time gap error when we tried to do the networking between them.
Same server 'should not' cause a time gap between servers, since only one server
I found that load_user_capability() was a really slow query, (still looking into why it runs slow when networking) and I think this caused the "time gap" for us.
Since I couldn't find out where to, via moodle admin controls, to change that 15 value I added it to the code in mnet/xmlrpc/client.php right after the "if ($time_offset > 0) {" around line 267, so we have:
$time_offset = $remote_timestamp - $timestamp_send;
if ($time_offset > 0) {
set_config('drift_threshold', 60, 'mnet');
etc...
Probably just a band aid solution but just wanted to throw it out there in case someone else is pulling out their hair over this.
M=