1. Home
  2. Support
Article - CS278792

Error "main process exited, code=exited, status=1/FAILURE" when attempting to start a native linux deployment of ThingWorx Analytics

Modified: 24-Sep-2020   


Applies To

  • ThingWorx Analytics 8.1 to 8.5

Description

  • Unable to start ThingWorx Analytics on linux (CentOS , Ubuntu)
  • <ThingWorxAnalyticsServer>/bin/twas.sh status reports the following for each microservices:
systemd[1]: Started ThingWorx Analytics - Data Microservice.
systemd[1]: Starting ThingWorx Analytics - Data Microservice...
systemd[1]: twas-data-ms.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: twas-data-ms.service: control process exited, code=exited status=1
systemd[1]: Unit twas-data-ms.service entered failed state.
systemd[1]: twas-data-ms.service failed.
  • Installation process was successful
  • journalctl -xe reports
Started ThingWorx Analytics - Data Microservice.
Starting ThingWorx Analytics - Data Microservice...
Error: Unable to access jarfile XXXX/ThingWorxAnalyticsServer/standalone_jars/data-ms.jar
  • in release 8.5.x install.log file shows
Error running /bin/systemctl start twas-zookeeper: Job for twas-zookeeper.service failed because the control process exited with error code. See "systemctl status twas-zookeeper.service" and "journalctl -xe" for details.
...
Get http://localhost:8900/async/versioninfo: dial tcp 127.0.0.1:8900: connect: connection refused
Get http://localhost:8900/async/versioninfo: dial tcp 127.0.0.1:8900: connect: connection refused
This is a printer-friendly version of Article 278792 and may be out of date. For the latest version click CS278792