cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Mobility Services Engine - Failed to get the status for process at port 7555

1689
Views
0
Helpful
0
Comments

 

Introduction

In case you face an issue with a clean install of MSE on Hyper-V. Initial setup goes through fine until it tries to start the services.

[root@JHBVMSE ~]# /etc/init.d/msed start
Starting MSE Platform  

Starting Apache HTTPD Server
Apache Server is already running. Skipping restart.
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process...
Started Admin process.
Starting database ..............
Database started successfully. Starting framework and services ...................................................MSE startup not completed yet. Please check back later with getserverinfo command.

If you leave it for a while and then try running the getservinfo command you will get the following output.

[root@JHBVMSE ~]# getserverinfo
Health Monitor is running
Retrieving MSE Services status.
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Checking status of service at port 7555
Failed to get the status for process at port 7555

Scenario 2

Another user faced exact similar issue but running on a VMWare ESXi host, not Hyper V.

He checked the RAM (11GB) and CPU (8 Cores) but still receive an error when starting the service or after completing setup

ERROR: Error in connecting to MSE Platform. Make sure MSE is up and running

Have attempted multiple times to stop/start the services using /opt/mse/msed start/stop and have rebooted the server completely.

Solution

Typically on new installs, services fail due to hardware support, not meeting the requirements for that install. Other reasons is changing the hardware configuration after an install.

The above mentioned solution was verified by user as he mentioned "That should have been the first thing I checked. Our VM administrator only gave it 4GB RAM. Upped that to 8GB and it works perfectly".

Source

This document is created from the following discussion

https://supportforums.cisco.com/discussion/12200041/mobility-services-engine

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards