[one-users] [HostPoolInfo] User couldn't be authenticated, aborting call.
Nelson Mimura Gonzalez
nelsonspbr at gmail.com
Tue Oct 5 08:38:43 PDT 2010
Hi all,
I had previously installed OpenNebula 1.2 from packages repository (via
apt-get) and besides some minor issues everything went fine, both at
front-end and node. I'm using Ubuntu 10.04.
Now I'm installing OpenNebula 2.0 RC1. I downloaded the package
(opennebula_1.9.90-1_i386.deb) and the first problem I had was a error
message, something about "chmod" or "chown" and an entry
"oneadmin:oneadmin". I added this group to "/etc/groups" and then things
started working.
I configured the drivers and so on (file "/etc/one/oned.conf") and the
service starts ("sudo one start"), then I added one host:
$ onehost create node01 im_xen vmm_xen tm_nfs
It's added and I can see it:
$ onehost show 0
HOST 0
INFORMATION
ID: 0
NAME: node01
CLUSTER: default
*STATE: INIT *
IM_MAD: im_xen
VM_MAD: vmm_xen
TM_MAD: tm_nfs
HOST
SHARES
MAX MEM: 0
USED MEM (REAL): 0
USED MEM (ALLOCATED) : 0
MAX CPU: 0
USED CPU (REAL): 0
USED CPU (ALLOCATED): 0
RUNNING VMS: 0
MONITORING INFORMATION
But I noticed that OpenNebula is not able to gather information about the
node:
Tue Oct 5 12:12:29 2010 [ONE][I]: Init OpenNebula Log system
Tue Oct 5 12:12:29 2010 [ONE][I]: Log Level: 3
[0=ERROR,1=WARNING,2=INFO,3=DEBUG]
Tue Oct 5 12:12:29 2010 [ONE][I]: ----------------------------------------
Tue Oct 5 12:12:29 2010 [ONE][I]: OpenNebula Configuration File
Tue Oct 5 12:12:29 2010 [ONE][I]: ----------------------------------------
Tue Oct 5 12:12:29 2010 [ONE][I]:
----------------------------------
DB=BACKEND=sqlite
DEBUG_LEVEL=3
DEFAULT_DEVICE_PREFIX=hd
DEFAULT_IMAGE_TYPE=OS
HM_MAD=EXECUTABLE=one_hm
HOST_MONITORING_INTERVAL=600
IMAGE_REPOSITORY_PATH=/var/lib/one//images
IM_MAD=ARGUMENTS=xen,EXECUTABLE=one_im_ssh,NAME=im_xen
MAC_PREFIX=02:00
MANAGER_TIMER=15
NETWORK_SIZE=254
PORT=2633
SCRIPTS_REMOTE_DIR=/tmp/one
TM_MAD=ARGUMENTS=tm_nfs/tm_nfs.conf,EXECUTABLE=one_tm,NAME=tm_nfs
VM_DIR=/var/lib/one/
VM_HOOK=ARGUMENTS=$VMID,COMMAND=image.rb,NAME=image,ON=DONE
VM_MAD=ARGUMENTS=xen,DEFAULT=vmm_sh/vmm_sh_xen.conf,EXECUTABLE=one_vmm_sh,NAME=vmm_xen,TYPE=xen
VM_POLLING_INTERVAL=600
VNC_BASE_PORT=5000
----------------------------------
Tue Oct 5 12:12:29 2010 [ONE][I]: Bootstraping OpenNebula database.
Tue Oct 5 12:12:29 2010 [VMM][I]: Starting Virtual Machine Manager...
Tue Oct 5 12:12:29 2010 [LCM][I]: Starting Life-cycle Manager...
Tue Oct 5 12:12:29 2010 [VMM][I]: Virtual Machine Manager started.
Tue Oct 5 12:12:29 2010 [InM][I]: Starting Information Manager...
Tue Oct 5 12:12:29 2010 [InM][I]: Information Manager started.
Tue Oct 5 12:12:29 2010 [LCM][I]: Life-cycle Manager started.
Tue Oct 5 12:12:29 2010 [TrM][I]: Starting Transfer Manager...
Tue Oct 5 12:12:29 2010 [TrM][I]: Transfer Manager started.
Tue Oct 5 12:12:29 2010 [DiM][I]: Starting Dispatch Manager...
Tue Oct 5 12:12:29 2010 [DiM][I]: Dispatch Manager started.
Tue Oct 5 12:12:29 2010 [ReM][I]: Starting Request Manager...
Tue Oct 5 12:12:29 2010 [ReM][I]: Request Manager started.
Tue Oct 5 12:12:29 2010 [ReM][I]: Starting XML-RPC server, port 2633 ...
Tue Oct 5 12:12:29 2010 [HKM][I]: Starting Hook Manager...
Tue Oct 5 12:12:29 2010 [HKM][I]: Hook Manager started.
Tue Oct 5 12:12:31 2010 [VMM][I]: Loading Virtual Machine Manager drivers.
Tue Oct 5 12:12:31 2010 [VMM][I]: Loading driver: vmm_xen (XEN)
Tue Oct 5 12:12:31 2010 [VMM][I]: Driver vmm_xen loaded.
Tue Oct 5 12:12:31 2010 [InM][I]: Loading Information Manager drivers.
Tue Oct 5 12:12:31 2010 [InM][I]: Loading driver: im_xen
Tue Oct 5 12:12:31 2010 [InM][I]: Driver im_xen loaded
Tue Oct 5 12:12:31 2010 [TM][I]: Loading Transfer Manager drivers.
Tue Oct 5 12:12:31 2010 [VMM][I]: Loading driver: tm_nfs
Tue Oct 5 12:12:31 2010 [TM][I]: Driver tm_nfs loaded.
Tue Oct 5 12:12:31 2010 [HKM][I]: Loading Hook Manager driver.
Tue Oct 5 12:12:31 2010 [HKM][I]: Hook Manager loaded
Tue Oct 5 12:12:41 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:12:43 2010 [ReM][D]: HostEnable method invoked
Tue Oct 5 12:13:00 2010 [ReM][D]: HostPoolInfo method invoked
*Tue Oct 5 12:13:00 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.*
Tue Oct 5 12:13:30 2010 [ReM][D]: HostPoolInfo method invoked
*Tue Oct 5 12:13:30 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.*
Another interesting fact is that when I start the "one" service and
(re)enable the node, after some time I receive the following message on
console:
The authenticity of host 'node01 (172.20.5.47)' can't be established.
RSA key fingerprint is a5:a7:90:5e:ad:5f:56:91:eb:37:fc:64:92:a5:47:1c.
Are you sure you want to continue connecting (yes/no)?
If I write "yes" and proceed, I get infinite "y" characters printed on my
screen. Then if I stop that and check the log again:
Tue Oct 5 12:20:19 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:20:19 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.*
Tue Oct 5 12:20:30 2010 [InM][I]: Monitoring host node01 (0)
Tue Oct 5 12:20:30 2010 [InM][I]: Command execution fail:
/tmp/one/im/run_probes xen
Tue Oct 5 12:20:30 2010 [InM][I]: STDERR follows.
Tue Oct 5 12:20:30 2010 [InM][I]: Host key verification failed.
Tue Oct 5 12:20:30 2010 [InM][I]: ExitCode: 255
Tue Oct 5 12:20:30 2010 [InM][E]: Error monitoring host 0 : MONITOR FAILURE
0 Could not monitor host node01.*
Tue Oct 5 12:20:48 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:20:48 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
Tue Oct 5 12:21:18 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:21:18 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
Tue Oct 5 12:21:48 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:21:48 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
Tue Oct 5 12:21:55 2010 [VMM][I]: --Mark--
Tue Oct 5 12:21:55 2010 [InM][I]: --Mark--
Tue Oct 5 12:22:17 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:22:17 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
Tue Oct 5 12:22:48 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:22:48 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
Tue Oct 5 12:23:17 2010 [ReM][D]: HostPoolInfo method invoked
Tue Oct 5 12:23:17 2010 [ReM][E]: [HostPoolInfo] User couldn't be
authenticated, aborting call.
After some time the host acquire an ERROR state:
HOST 0
INFORMATION
ID: 0
NAME: node01
CLUSTER: default
*STATE: ERROR*
IM_MAD: im_xen
VM_MAD: vmm_xen
TM_MAD: tm_nfs
HOST
SHARES
MAX MEM: 0
USED MEM (REAL): 0
USED MEM (ALLOCATED) : 0
MAX CPU: 0
USED CPU (REAL): 0
USED CPU (ALLOCATED): 0
RUNNING VMS: 0
MONITORING INFORMATION
I had a previous installation of OpenNebula at the node and everything was
working fine, so I don't think is a node-side problem. I also configured
passwordless access (and checked that) to node, both using my user and
"oneadmin".
Do you have any ideas about what is happening? I feel there's a silly
mistake somewhere...
Some questions:
1) When I installed the package, what is the password chosen for "oneadmin"
user?
2) Is this the password that has to be in plain text at file "one_auth"?
3) Is there any problem if I change that password?
I'm seriously thinking about reinstalling the OS (wouldn't be big deal) and
a) trying to reinstall OpenNebula package; b) or compiling the source and
doing things manually, but I'd like to hear your suggestions first.
Thanks in advance,
Nelson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20101005/30355ceb/attachment-0002.htm>
More information about the Users
mailing list