Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsAccording to article "Overview of Qlik Sense logs when one User initiates a Session ID by opening an application in the Hub"
Usually the AuditActivity_Proxy log is related to when a user gets a Session ID. The web socket connection is opened right after it.
Command=Get session;Result=200;ResultText=Success fe87b122-8979-45d4-9c37-3c39ce704045
However, there could be a situation where the logs show multiple entries of session ID 0 as below
Command=Get session;Result=200;ResultText=Success 0 0 0
This log entry is not normal, the frequency can only be controlled by identifying why are there so many sessions trying to get established ?
Usually as below when a valid session gets established it is followed by the app access web Socket connection.
When session id is showing 0, this indicates to an automated task polling / connecting to the proxy server without any action, in most situations this is a NLB load balancer poll doing server heartbeat check with the wrong URL, server IP or host name.
The NLB polling to monitor availability shows that it is configured with wrong URL such as https://<serverIP>/
The heartbeat check URL should be be changed to: https://server.domain.com/engine/healthcheck/ and NOT https://<serverIP>/
More information at:
https://help.qlik.com/en-US/sense-developer/June2018/Subsystems/EngineAPI/Content/GettingSystemInformation/HealthCheckStatus.htm
---------------------------------------------------------------------------------------------------------------------------------------------
Expected logs
Sequence# ProductVersion Timestamp Hostname Id Description ProxySessionId ProxyPackageId RequestSequenceId UserDirectory UserId ObjectId ObjectName Service Origin Context Command Result Message Id2
4 11.11.0.0 20170321T215736.774+0100 QlikServer1 4f3ec3ce-604b-4fad-930c-6c5d3c417112 Command=Get session;Result=200;ResultText=Success fe87b122-8979-45d4-9c37-3c39ce704045 bcce5b5b-a2e5-455c-9a36-f3fe076b03e3 0 DOMAIN qvservice 0 Not available Proxy AppAccess /qps/user?targeturi=http:%2f%2fqlikserver1.domain.local%2fhub%2f Get session:HandleRequest 200 Handle connection request 4f3ec3ce-604b-4fad-930c-6c5d3c417112
5 11.11.0.0 20170321T215743.567+0100 QlikServer1 1fcb5c5c-15f5-40a6-bd54-0819643cd197 Command=Open connection;Result=0;ResultText=Success fe87b122-8979-45d4-9c37-3c39ce704045 0e6278ad-ffff-4d6c-9d66-af84a1596d78 0 DOMAIN qvservice c3ed4e49-dc98-4ff8-b140-f3d945236197 Not available Proxy AppAccess /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197 Open connection 0 Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36' 1fcb5c5c-15f5-40a6-bd54-0819643cd197
------------------------------
Issue in logs: Why are there so many calls with session ids = 0 ?
333394 11.34.2.0 20180821T082207.364+1200 qlikserver1.domain.local 600e7221-a7cf-4a45-8c03-a76946bec4bc Command=Get session;Result=200;ResultText=Success 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available /qps/user Get session:HandleRequest 200 Handle connection request 600e7221-a7cf-4a45-8c03-a76946bec4bc
333395 11.34.2.0 20180821T082207.582+1200 qlikserver1.domain.local 6dac5c1c-200b-42d6-89d2-9453ebe059f2 Command=Get session;Result=200;ResultText=Success 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available /qps/user Get session:HandleRequest 200 Handle connection request 6dac5c1c-200b-42d6-89d2-9453ebe059f2
333396 11.34.2.0 20180821T082208.286+1200 qlikserver1.domain.local 707fa5e8-5063-4471-85e2-9c371e38cf63 Command=Get session;Result=200;ResultText=Success 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available /qps/user Get session:HandleRequest 200 Handle connection request 707fa5e8-5063-4471-85e2-9c371e38cf63
333397 11.34.2.0 20180821T082211.676+1200 qlikserver1.domain.local 1fb555f9-d96c-401d-ab82-3255a5d73efe Command=Get session;Result=200;ResultText=Success 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available /qps/user Get session:HandleRequest 200 Handle connection request 1fb555f9-d96c-401d-ab82-3255a5d73efe
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us