This post is more than 5 years old
2 Posts
0
146402
September 4th, 2013 10:00
vFoglight 6.6.1 - ERROR: Failed to exec embedded database process
Hello,
I use vFoglight since 1,5 years successfully on Linux (Ubuntu 12.04, I know, it's not supported ).
Today I have rebooted the server und vFoglight don't work. The embedded mySQL-Database
cannot be start with the fms start (fms --daemon). I've found the following errors in the ManagementServerlogs:
| 2013-09-04 12:36:09.919 INFO | [main] com.quest.nitro.service.ServiceMBeanUtil - Database Lifecycle Service Starting... |
| 2013-09-04 12:36:10.294 INFO | [main] com.quest.nitro.db.EmbeddedDatabaseManager - Starting up the embedded database... |
2013-09-04 12:36:10.306 ERROR [main] QcnUtil/src/unix/qcn_message_unix - (internal error) Could not connect socket for message transmission to /tmp/QcnProcessRunner-236164eeefd265647258c4d174c8644e.msg: Connection refused
2013-09-04 12:36:10.306 ERROR [main] com.quest.nitro.db.EmbeddedDatabaseManager - Cant run command: {0}
java.io.IOException: Could not transmit inter-launcher communications message. Check the logs for more information.
| at com.quest.common.launcher.message.MessageHandler.sendMessage(Native Method) | |
| at com.quest.common.launcher.runner.ProcessRunner.sendMessage(ProcessRunner.java:398) | |
| at com.quest.common.launcher.runner.ProcessRunner.execInternal(ProcessRunner.java:275) | |
| at com.quest.common.launcher.runner.ProcessRunner.exec(ProcessRunner.java:210) | |
| at com.quest.nitro.db.EmbeddedDatabaseManager.run(EmbeddedDatabaseManager.java:407) | |
| at com.quest.nitro.db.EmbeddedDatabaseManager.runAndWait(EmbeddedDatabaseManager.java:390) | |
| at com.quest.nitro.db.EmbeddedDatabaseManager.startup(EmbeddedDatabaseManager.java:438) | |
| at com.quest.nitro.service.embeddeddb.EmbeddedDbService.startService(EmbeddedDbService.java:48) |
I stopped the service fms und delete all .msg files in /tmp, but the start don't work.
Can you help me
Best regards
Maik
maikw
2 Posts
1
September 5th, 2013 13:00
Hi Thomas,
yes, the fms was started as root.
The Problem is now solved, an other program is expected to block any ports.
I've stop the process "dovecot" (a mail server) and then vFog started without
problems. If dovecot starts before vFog, then vFog will not start, it works the
other way around. Very strange. F*** upstart, I want my System V Init back.
Best regard
Maik
DELL-Thomas B
171 Posts
0
September 5th, 2013 13:00
Are you by chance running as root?