PCoIP Management Console Enterprise Edition 2.x getting error message - Waiting for the server to start

Rate this Article
Average: 1 (1 vote)

August 27, 2018

Last modified: 09/19/2023, 12:32 pm

Knowledge Base Article Tutorial Management Console

This message is displayed anytime the daemon and console stop communicating with each other. There are a number of reasons why, please review the three scenarios below.

 

Scenario 1 - DNS A record is missing

One issue has been tracked to lack of a DNS "A" record for the PCoIP Management Console. We have found that many users are setting up the PCoIP Management Console using a static IP address and not configuring an "A" record in their DNS server.

If you get this message "waiting for server to start" when trying to log into the web interface of the PCoIP Management Console please ensure you have the DNS "A" record set for the PCoIP Management Console. Optionally also set a "PTR" record for the PCoIP Management Console.

If using DHCP these records may be automatically created for you depending on you DHCP server configuration.

Viewing the daemon log file you will see the daemon has stopped and as soon as you start the daemon it stops again. The console is trying to talk to the daemon and since the daemon is stopped the message "waiting for server to start" is being displayed.

 

Scenario 2 - Change of host name but DNS A record not updated

The host name of the PCoIP Management Console has been changed and a corresponding DNS record has not been setup. Ensure you have set up a DNS "A" record for the host name of the PCoIP Management Console.

Check the hosts file located in folder /etc

You can also review Why is the database restore not working in PCoIP Management Console 2.2.0? for some additional information on the hosts file.

 

Scenario 3 - Self signed certificate

Self signed certificated have been uploaded to the PCoIP Management Console as soon as you are prompted to login the PCoIP Management Console displays a message "Waiting for server to start" also if you were using PCoIP Management Console 2.1.0 in Standard Edition you now notice the PCoIP Management Console is showing Enterprise Edition. This one is a little more complicated to resolve since you cannot gain access to the web interface to Revert Self-Signed Certificates. For this you will have to SSH into the PCoIP Management Console and change your login to root (su) by default there is no password for root so the first time you log in you will have to set a password (su passwd).

Change to the following directory /opt/teradici/cert/backups

At the prompt type the following commands and confirm to overwrite the existing file:

cp /opt/teradici/cert/backups/keystore.self_signed /opt/daemon/src/main/resources/daemon.keystore
cp /opt/teradici/cert/backups/keystore.self_signed /opt/jetty/etc/keystore

You will need to restart the jetty and daemon services:

/etc/init.d/jetty restart
/etc/init.d/mcdaemon restart

Go back to the web interface and refresh the page to log into the MC. At this point the MC will be running with the Teradici self signed certs.

 

Scenario 4 - Insufficient RAM

The RAM default of 12 GB has been lowered to 4 GB during the .ova Management Console 3.0 deployment.

Increase RAM to 12 GM before .ova deployment.

 

Scenario 5 - Missed step on changing host name

In our Administrator's Guide for PCoIP Management Console Enterprise Edition 2.x we omitted a step required when changing the host name. Many users have modified the host name only to find out that when they try to log into the web interface of the Management Console (MC) they now receive an error message - "Waiting for the server to start."

You need to also add the following to the top of your /etc/hosts file:

mymc  (This will be the hostname of your MC)

Your /etc/hosts file should now look like this:

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 mymc
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 mymc

 

Full instructions are:

To modify hosts file you can use nano or vi......

  1. Use nano to edit /etc/hosts file: 
    # nano /etc/hosts
  2. At the end of both the IPv4 & IPv6 enter the host name of your Management Console. Your file should look like below:
127.0.0.1       localhost       localhost.localdomain   localhost4      localhost4.localdomain4 mymc
::1     localhost       localhost.localdomain   localhost6      localhost6.localdomain6 mymc

3. Press Ctrl X to exit

4. When prompted to "Save modified buffer" answer Y

5. Enter the following at the command line to restart the Management Console daemon:

sudo /etc/init.d/network restart

 

See also:

Why is the database restore not working in PCoIP Management Console 2.2.0?

 

Pertains to:
  • PCoIP Management Console 2.0.0
  • PCoIP Management Console 2.0.1
  • PCoIP Management Console 2.0.2
  • PCoIP Management Console 2.1.0
  • PCoIP Management Console 2.1.1
  • PCoIP Management Console 2.2.0
  • PCoIP Management Console 2.3.0
  • PCoIP Management Console 2.4.0
  • PCoIP Management Console 2.5.1