This is similar to bug https://github.com/Luxoft/Twister/issues/188 .
Twister User Guide 0.11 under heading "6 > How to install/upgrade the framework" mentions recommended configuration as below:
Recommended requirements (1 CE and 10 users with 50 EPs in total):
Dual Core CPU
2GB RAM
10GB HDD (at least to store all of the log reports)
A compatible 50 users setup of Twister is made following the above specification.
After some 15 users have started, the setup is found to be failing in updating the UI Log panel with the execution logs, though they get updated in LIVE log in "/home/user/twister/.twister_cache".
The warning captured in server_log.log is as follows:
WARNING CeFs.py: 571: _usr_service Cannot reuse read User Service for user: result expired.
Later, the new users are unable to start execution. The server_log.log informs that execution status is "Running" but the usr_log.log stalls with "Connecting to Central Engine" message.
TWISTER_PATH is set to /home/USER/twister.
This is similar to bug https://github.com/Luxoft/Twister/issues/188 . Twister User Guide 0.11 under heading "6 > How to install/upgrade the framework" mentions recommended configuration as below: Recommended requirements (1 CE and 10 users with 50 EPs in total): Dual Core CPU 2GB RAM 10GB HDD (at least to store all of the log reports)
A compatible 50 users setup of Twister is made following the above specification. After some 15 users have started, the setup is found to be failing in updating the UI Log panel with the execution logs, though they get updated in LIVE log in "/home/user/twister/.twister_cache". The warning captured in server_log.log is as follows: WARNING CeFs.py: 571: _usr_service Cannot reuse read User Service for
user
:result expired
.Later, the new users are unable to start execution. The server_log.log informs that execution status is "Running" but the usr_log.log stalls with "Connecting to Central Engine" message. TWISTER_PATH is set to /home/USER/twister.