Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Contact
Find Answers
Join Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Get Support
Have a Question?
Search Qlik's Support knowledge database or request assisted support for your highly complex issues.
Submit a Case
Talk with a Representative
Critical Issues
Experiencing a serious product issue? Please Contact us by phone. Click here to view phone numbers and hours by region.
Contact UsWelcome Guest
Installed Qlik Products
My Environments
Log your environments to ensure faster and more targeted troubleshooting.
View Available Licenses
My Licenses
Understand your licenses to help you maximize your experience.
Knowledge
Qlik Sense - Node is offline - Failed to retrieve service status from 'http://Servername:4444/status/' (Unable to connect to the remote server)
Article Number: 000055934 | Last Modified: 2020/02/12Description
In Qlik Sense Management Console (QMC) under Nodes, a specific Rim node status is offline.
The Repository Trace System logs (By default C:\Programdata\Qlik\Sense\Log\Repository\Trace\) the following error is registered:
...
Failed to retrieve service status from 'http://ServerName:4444/status/' (Unable to connect to the remote server)
...
Environment:
The Repository Trace System logs (By default C:\Programdata\Qlik\Sense\Log\Repository\Trace\) the following error is registered:
...
Failed to retrieve service status from 'http://ServerName:4444/status/' (Unable to connect to the remote server)
...
Environment:
- Qlik Sense Enterprise, all versions
Cause
To get the service status from the Rim node, the Central node needs to make request to the Rim node which is supposed to be listening on port 4444.
Resolution
Possible points of failure:
- The Rim node is not listening on the port 4444. The command netstat -bano | findstr 4444 on the Rim server to determine if listening. Otherwise, restarting the services on the Rim node might help. Follow the order documented under Manual Start and Stop order of Qlik Sense services
- The communication between the Central node and the Rim node via port 4444 is blocked. You can use this article to determine that How To Check Open Ports Using PowerShell
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.