I am testing a SSO / (RSA) MFA login with the auth_saml2 plugin with autocreation of the user in Moodle. The first time this login via SSO / (RSA) MFA works fine, the user is created in Moodle. When I login the second time, I get an error in Moodle:
auth_saml2: saml_login_complete user 'Username' can't be autocreated as email 'user@x.com' is taken
Without using RSA MFA the SSO works fine in both login situations, what could be the cause of the error of duplicate email address?
Alain Raap
المواضيع التي نشرها Alain Raap
Moodle in English -> General help -> Redis keyspace misses -> Re: Redis keyspace misses
بواسطة - Alain Raap
I'm using Moodle 4.5.4 now and I still see this problem with Redis and the high number of keyspace misses.
When I change the Connection timeout value to zero (0) again, the problem seems over. Anyone who had the
same problem with this Redis setting? After the change, the connection timeout is set to 3 seconds by Moodle itself again.
When I change the Connection timeout value to zero (0) again, the problem seems over. Anyone who had the
same problem with this Redis setting? After the change, the connection timeout is set to 3 seconds by Moodle itself again.
Moodle in English -> General help -> Redis keyspace misses -> Re: Redis keyspace misses
بواسطة - Alain Raap
This morning I looked at the Redis instance of the Moodle MUC cachestore, and the problem was back.
Low hits percentage again.
Moodle in English -> Hardware and performance -> PHP 8.3 support -> Re: PHP 8.3 support
بواسطة - Alain Raap
When you run your site in debug mode, you can see where the plugins fail with deprecation errors or other php errors.
That's how we found the plugins that have problems with the new PHP version. Moodle itself runs fine on this version.
That's how we found the plugins that have problems with the new PHP version. Moodle itself runs fine on this version.
Hi Andrei,
Performance can be optimized by using caching, caching and caching, for PHP the Zend Opcache, for session and Moodle MUC Redis, for the database InnoDB (load your database in memory). It all fits together when tuned in a way that you find your bottlenecks in your Moodle stack. It took us a lot of time, but we see that every new LTS version asks for a good performance test. Redis 'untestable' means that there is no test configuration found in [your site]/admin/settings.php?section=cachestore_redis_settings, configure it there and you can run the tests. But, as Howard mentioned, it's not a really good test to find out your Redis performance. You could try the Redis benchmark on the server, but that only gives you a view of the server itself, and not when a lot of clients cache their data in Redis. There is a plugin you can install to see some stats of Redis: https://moodle.org/plugins/tool_redis
I hope this gives you a little insight, feel free to contact me if I can help you, as we run almost the same stack.
Performance can be optimized by using caching, caching and caching, for PHP the Zend Opcache, for session and Moodle MUC Redis, for the database InnoDB (load your database in memory). It all fits together when tuned in a way that you find your bottlenecks in your Moodle stack. It took us a lot of time, but we see that every new LTS version asks for a good performance test. Redis 'untestable' means that there is no test configuration found in [your site]/admin/settings.php?section=cachestore_redis_settings, configure it there and you can run the tests. But, as Howard mentioned, it's not a really good test to find out your Redis performance. You could try the Redis benchmark on the server, but that only gives you a view of the server itself, and not when a lot of clients cache their data in Redis. There is a plugin you can install to see some stats of Redis: https://moodle.org/plugins/tool_redis
I hope this gives you a little insight, feel free to contact me if I can help you, as we run almost the same stack.