Mobility Services Engine

[ishtak1974]

Hey guys,

I'm having 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 I leave it for a while and then try running the getservinfo command I 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

Any ideas?

[Scott Fella · Accepted 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.  If your meeting the requirements and still having issues in a new install, then your best bet is to open a TAC case. 

[ishtak1974]

That should haved been the first thing I checked. Our VM administrator only gave it 4GB RAM. Upped that to 8GB and it works perfectly.

[evangkaverman]

I have had the exact same issue, but running on a VMWare ESXi host, not Hyper V.

I have 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.

Any help appreciated.

[rcsu-it]

I had a similar error after 'upgrading' manually (not via Prime) from factory 7.4 on the 3355 to latest 7.6 image using the .db.tar file method.  I guess I'll try the fresh install method next which is deleting all of the /opt directories indicated in the release notes.  If that doesn't work it looks like a call to TAC is inevitable.  Good thing I still have another one to try the Prime Infrastructure upgrade method.

Any thoughts would be appreciated.

[abroysin17232]

Pregunta sobre el MSE, quiero para los servicios para volverlos a arrancar y validar si se sincroniza mi MSE con el Prime , ya intente con estes comando: [root @ MSE ~] # /etc/init.d/msed stop

Pero al verificar nuevamente el status veo que no se paro el servicio de Apache, algun comando para  parar el servicio manualmente e intentar si funciona sincronizarlo nuevamente, ojala me puedan ayudar.

saludos