[SOLVED] Oned failed to start error

Community Support
1

Hi,

I’m stuck with this error and can’t figure out the base problem. When running the command “one start” as root i get the error.

“oned failed to start”

I’ve already changed permissions on /var/log/one to the user “oneadmin”.

On the logs I see this error:

Sun Nov 6 02:31:28 2016 [Z0][ReM][E]: Req:8832 UID:- HostPoolInfo result FAILURE [HostPoolInfo] User couldn’t be authenticated, aborting call.

Also, I’m facing this error. Aprox. every minut this appears on the terminal, which seems the frontend trying to connect to the node as root:

Thanks.

2

Also, the output of the command “service opennebula status” shows:

● opennebula.service - OpenNebula Cloud Controller Daemon
Loaded: loaded (/lib/systemd/system/opennebula.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 02:24:23 CET; 9min ago
Process: 22988 ExecStop=/bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE)
Process: 22922 ExecStart=/usr/bin/oned -f (code=exited, status=0/SUCCESS)
Process: 22915 ExecStartPre=/usr/sbin/logrotate -s /tmp/logrotate.state -f /etc/logrotate.d/opennebula (code=exited, status=0/SUCCESS)
Process: 22911 ExecStartPre=/bin/chown oneadmin:oneadmin /var/log/one (code=exited, status=0/SUCCESS)
Process: 22908 ExecStartPre=/bin/mkdir -p /var/log/one (code=exited, status=0/SUCCESS)
Main PID: 22922 (code=exited, status=0/SUCCESS)

Nov 06 02:24:21 frontend systemd[1]: Starting OpenNebula Cloud Controller Daemon…
Nov 06 02:24:21 frontend systemd[1]: Started OpenNebula Cloud Controller Daemon.
Nov 06 02:24:23 frontend systemd[1]: opennebula.service: Control process exited, code=exited status=1
Nov 06 02:24:23 frontend systemd[1]: Stopped OpenNebula Cloud Controller Daemon.
Nov 06 02:24:23 frontend systemd[1]: opennebula.service: Unit entered failed state.
Nov 06 02:24:23 frontend systemd[1]: opennebula.service: Failed with result ‘exit-code’.

3

Solved. It was a problem with Gems version.

4

How did you solve it?