Error: when handling rolled log files

[fatinfazrizanor]

Hi,

When opening hub/qmc, the page is load slow, so i read the proxy log file to recognize the issue. 

I found this error 

"Error when handling rolled log files 

and 

Proxy REST Time-out at Proxy.Communication.Rest.ProxyRestClient.CallSync[TR](String restCommand, RESTMethod method, Object jsonObject, IDictionary`2 additionalHeaders)"

What is this error means? is it show the cause of the performance/slow issue in hub & qmc?

Regard,

FT

[TauseefKhan]

Hi @fatinfazrizanor,

As the error messages and given image, it appears there are two primary issues contributing to the slow loading of the Qlik Sense Hub and QMC (Management Console).

1- Error when handling rolled log files:

This error suggests that there could be issues with how log files are being rolled over. Log file rolling is a process to archive old log entries to separate files to prevent the main log file from becoming too large, which can degrade performance. If this process encounters problems, it might delay the logging mechanism and consequently affect the performance of the system.

2- Proxy REST Time-out at Proxy.Communication.Rest.ProxyRestClient.CallSyncTR:

This error indicates that the Proxy REST client experienced a timeout while trying to make a synchronous call. This could mean that the server is not responding within the expected time frame, possibly due to high load or internal communication inefficiencies within the server infrastructure.
Both these issues can indeed contribute to performance degradation when accessing the Hub and QMC.

Check with this below Solutions :
Review Log Management Settings:

Assess the configuration settings for log file handling, including size limits and rollover criteria. If the settings are set too low, consider increasing them to reduce the frequency of rollovers. Also, ensure that there is adequate disk space and that the disk performance is not a bottleneck.
Increase Proxy REST Timeout:

As indicated by the error, the Proxy REST client's timeout could be too short for the current server response times. Increasing the timeout setting may help. You can adjust this parameter in the service's configuration files or through the QMC under service cluster settings.
Performance and Resource Checks:

Conduct a thorough check of the server's resources (CPU, Memory, Disk I/O, Network) to identify any bottlenecks or resource contention issues that might be causing slow responses.
Additionally, ensure that the Qlik Sense services are operating optimally and consider restarting services if necessary to clear any transient issues.

Consult Logs for Additional Insights:

Further delve into other system and Qlik Sense logs beyond the proxy logs to gain more insights into potential issues or recurring patterns that could be affecting system performance.

Update and Patch System:

Ensure that your Qlik Sense installation is up-to-date with the latest patches and updates. Occasionally, performance issues can be related to software bugs that are resolved in newer releases.

[fatinfazrizanor]

Hi Tauseef Khan, thank you for your response. 

I would like to know what is the cause of the issues? For your information, this is multinode environment and there is no internet connection in the servers. Is it related to ports? or any other related cause? 

For now we stuck to identify the cause and how to solve this issue. Thanks for your help.

Regards,

FT

[TauseefKhan]

The error indicated in your log file, "Error when handling rolled log files" and "Proxy REST Time-out at Proxy.Communication.Rest.ProxyRestClient.CallSync[TR]", is a significant clue that there might be issues with the Qlik Sense Proxy Service or its communication with other Qlik services, especially when handling logging operations.

I hope you have checked with this step: Restart the Qlik Sense Proxy Service and the Qlik Sense Repository Service to update their states. After restarting, please check the logs for any persistent errors or warnings.

As your Qlik Sense environment is multi-node and without internet access, and considering the nature of the error, it is important to check several potential causes as mentioned above and port also.

Port Configurations: Ensure that all required ports for intra-node and inter-node communication are open and properly configured. For the Qlik Sense Proxy Service (QPS), essential ports include 443 (HTTPS), 4242 (QRS REST API), and others like 4747 (Engine), 4899 (Printing), 4243 (REST API), etc. Verify that these ports are not blocked by any firewalls within your environment.

Qlik Sense Services Status: Confirm that all critical Qlik Sense services (such as the Qlik Sense Repository Service, Proxy Service, Engine Service) are up and running on each node. Check their logs for any errors or warnings that could point to issues.

Log Management: The error regarding "handling rolled log files" suggests there might be a problem with log rotation or retention settings. Ensure the log directory has sufficient disk space and that the log settings are configured correctly to avoid log file corruption or excessive size.

Network Connectivity: A multinode environment requires proper network connectivity between nodes. Use ping or telnet to verify connectivity between nodes on relevant ports. If network issues are detected, address them with your IT/network team.

[fatinfazrizanor]

Hi TauseefKhan,

 Log Management: The error regarding "handling rolled log files" suggests there might be a problem with log rotation or retention settings. Ensure the log directory has sufficient disk space and that the log settings are configured correctly to avoid log file corruption or excessive size.'

for this point, is this log management related with qlik sense log file? Could i know where is the log setting being configured?

Regards,

FT

[TauseefKhan]

Logs are essential for troubleshooting, monitoring, and maintaining the health of your Qlik Sense environment.
Common log files include:
Proxy Logs: These contain information related to user access, authentication, and communication between components.

Engine Logs: These capture details about app reloads, data connections, and calculations.

Repository (QRS) Logs: These track Qlik Sense Repository Service (QRS) activities, such as app
publishing and user management.

Scheduler Logs: These provide insights into scheduled tasks and reloads.

The log files are typically stored in the following directory:
C:\ProgramData\Qlik\Sense\Log

Within this directory, you’ll find subfolders for each service (e.g., Proxy, Engine, Repository, Scheduler), and each service has its own log files.