NextGen Knowledge Center

Mirth® Connect Engine fails to start up

  • A common cause of this is port conflicts. Check the Logs, you may see something like this: 
    • ERROR 2017-06-23 09:17:22,757 [Main Server Thread] com.mirth.connect.server.Mirth: http.port port is already in use: 8080
ERROR 2017-06-23 09:17:22,758 [Main Server Thread] com.mirth.connect.server.Mirth: https.port port is already in use: 8443
    • Change the "http.port" and "https.port" in your Configuration to ones that aren't already used.
  • Another common cause is database connectivity / problems. If you see this: 
    • ERROR 2017-06-23 09:26:07,888 [Main Server Thread] com.mirth.connect.server.Mirth: Error establishing connection to database, aborting startup. The connection attempt failed.

      It probably means you have an error in your database Configuration settings, or the machine running Mirth® Connect by NextGen Healthcaredoes not have connectivity to the correct IP.

  • If you see an error like this: 
    • ERROR 2017-06-23 09:32:35,405 [Main Server Thread] com.mirth.connect.server.Mirth: Failed to migrate database schema
com.mirth.connect.model.util.MigrationException: Failed to execute script:

      If may mean that you have changed the "database.url" setting correctly, but forgot to also change the "database" setting. For example if you are switching from Derby to PostgreSQL, make sure to change the "database" setting to "postgres".

  • Another possibility is that you have all the database settings correct, but the schema you are trying to connect to doesn't yet exist: 
    • ERROR 2017-06-23 09:35:10,668 [Main Server Thread] com.mirth.connect.server.Mirth: Error establishing connection to database, aborting startup. FATAL: database "mirthdb" does not exist
    • In your database management tool / command line, make sure to create the schema ("mirthdb" by default). Then Mirth® Connect will automatically create all the necessary tables once it starts up.