[one-users] sunstone says : "OpenNebula is not running"
Hector Sanjuan
hsanjuan at opennebula.org
Thu May 3 02:09:57 PDT 2012
I guess then you have to update it as well and restart opennebula and
sunstone.
Hector
En Wed, 02 May 2012 12:42:00 +0200, Guigui 6675636b206f6666
<licks0re at hotmail.com> escribió:
>
> No, I did not update oneadmin password.
>
> oneuser list gives me :
>
> ID GROUP NAME
> AUTH PASSWORD
> 0 oneadmin oneadmin core
> ecb7b4f4ea2fe692223555d6051620a093ca01cb
> 1 oneadmin serveradmin server_c
> 2f4b89c71cba62fddbb709f50943fa33f55ec6f9
>
> Cheers,
> Guillaume
>
>> To: licks0re at hotmail.com
>> Subject: Re: [one-users] sunstone says : "OpenNebula is not running"
>> Date: Wed, 2 May 2012 12:36:29 +0200
>> CC: users at lists.opennebula.org
>> From: hsanjuan at opennebula.org
>>
>> Have you updated oneadmin password too? What is the output of 'oneuser
>> list'?
>>
>> H
>>
>> En Wed, 02 May 2012 12:31:29 +0200, Guigui 6675636b206f6666
>> <licks0re at hotmail.com> escribió:
>>
>> >
>> > Hello Hector,
>> >
>> > Unfortunately, still the same problem. And I'm using this packages
>> from
>> > that repository :|
>> >
>> >
>> >> To: licks0re at hotmail.com
>> >> Subject: Re: [one-users] sunstone says : "OpenNebula is not running"
>> >> Date: Wed, 2 May 2012 11:44:50 +0200
>> >> CC: users at lists.opennebula.org
>> >> From: hsanjuan at opennebula.org
>> >>
>> >> This is probably because you changed the contents of sunstone_auth.
>> For
>> >> that to work you need to to update the password of the serveradmin
>> user
>> >> with the sha1 password (oneuser passwd serveradmin susenebula
>> --sha1).
>> >>
>> >> Im not sure your original problem was a packaging thing, but you
>> could
>> >> also try the opensuse packages from
>> >> http://opennebula.org/software:software
>> >>
>> >> Hector
>> >>
>> >>
>> >> En Wed, 02 May 2012 11:31:48 +0200, Guigui 6675636b206f6666
>> >> <licks0re at hotmail.com> escribió:
>> >>
>> >> >
>> >> > Good morning all,
>> >> >
>> >> > So. I re-did everything from scratch.
>> >> >
>> >> > 1) re-installed the machine with opensuse 12.1
>> >> > 2) re-installed the softwares opennebula & sunstone
>> >> > 3) added the one_auth variable to oneadmin .bashrc profile to avoid
>> >> > confusion with the one_auth file
>> >> >
>> >> > Unfortunately, still the same problem. But now, I see some auth
>> >> problem
>> >> > in the oned.log (at the end of this message)
>> >> >
>> >> > Wed May 2 11:27:39 2012 [ReM][D]: UserPoolInfo method invoked
>> >> >
>> >> > Wed May 2 11:27:39 2012 [ReM][E]: [UserPoolInfo] User couldn't be
>> >> > authenticated, aborting call.
>> >> >
>> >> >
>> >> > Am I confusing something here ? sunstone credentials are the
>> >> credentials
>> >> > given in the sunstone_auth file, am I correct ?
>> >> > (in fact, I set all the passwords to "susenebula"... oneadmin
>> system
>> >> > account, in one_auth file and in sunstone_auth file)
>> >> >
>> >> >
>> >> > To start the services, I do :
>> >> >
>> >> > "sudo - oneadmin"
>> >> > "one start"
>> >> > "sunstone-server start"
>> >> >
>> >> > It gives me no errors. One & sunstone logs at the end of this
>> message.
>> >> >
>> >> > So here are all the revelant config files:
>> >> >
>> >> > one_auth file:
>> >> > oneadmin:susenebula
>> >> >
>> >> > sunstone_auth file:
>> >> > oneadmin:susenebula
>> >> >
>> >> > file rights :
>> >> > -rw-r--r-- 1 oneadmin cloud 20 Jan 27 14:34 one_auth
>> >> > -rw------- 1 oneadmin cloud 20 Jan 27 15:15 sunstone_auth
>> >> >
>> >> > /etc/one/oned.conf
>> >> >
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # OpenNebula Configuration file
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Daemon configuration attributes
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # MANAGER_TIMER: Time in seconds the core uses to evaluate
>> periodical
>> >> > functions.
>> >> > # HOST_MONITORING_INTERVAL and VM_POLLING_INTERVAL can not have
>> >> smaller
>> >> > values
>> >> > # than MANAGER_TIMER.
>> >> > #
>> >> > # HOST_MONITORING_INTERVAL: Time in seconds between host
>> >> monitorization.
>> >> > # HOST_PER_INTERVAL: Number of hosts monitored in each interval.
>> >> > #
>> >> > # VM_POLLING_INTERVAL: Time in seconds between virtual machine
>> >> > monitorization.
>> >> > # (use 0 to disable VM monitoring).
>> >> > # VM_PER_INTERVAL: Number of VMs monitored in each interval.
>> >> > #
>> >> > # VM_DIR: Remote path to store the VM images, it should be shared
>> >> > between all
>> >> > # the cluster nodes to perform live migrations. This variable is
>> the
>> >> > default
>> >> > # for all the hosts in the cluster. VM_DIR IS ONLY FOR THE NODES
>> AND
>> >> > *NOT* THE
>> >> > # FRONT-END
>> >> > #
>> >> > # SCRIPTS_REMOTE_DIR: Remote path to store the monitoring and VM
>> >> > management
>> >> > # scripts.
>> >> > #
>> >> > # PORT: Port where oned will listen for xmlrpc calls.
>> >> > #
>> >> > # DB: Configuration attributes for the database backend
>> >> > # backend : can be sqlite or mysql (default is sqlite)
>> >> > # server : (mysql) host name or an IP address for the MySQL
>> server
>> >> > # port : (mysql) port for the connection to the server.
>> >> > # If set to 0, the default port is used.
>> >> > # user : (mysql) user's MySQL login ID
>> >> > # passwd : (mysql) the password for user
>> >> > # db_name : (mysql) the database name
>> >> > #
>> >> > # VNC_BASE_PORT: VNC ports for VMs can be automatically set to
>> >> > VNC_BASE_PORT +
>> >> > # VMID
>> >> > #
>> >> > # DEBUG_LEVEL: 0 = ERROR, 1 = WARNING, 2 = INFO, 3 = DEBUG
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> > #MANAGER_TIMER = 30
>> >> >
>> >> > HOST_MONITORING_INTERVAL = 600
>> >> > #HOST_PER_INTERVAL = 15
>> >> >
>> >> > VM_POLLING_INTERVAL = 600
>> >> > #VM_PER_INTERVAL = 5
>> >> >
>> >> > #VM_DIR=/srv/cloud/one/var
>> >> >
>> >> > SCRIPTS_REMOTE_DIR=/var/tmp/one
>> >> >
>> >> > PORT = 2633
>> >> >
>> >> > DB = [ backend = "sqlite" ]
>> >> >
>> >> > # Sample configuration for MySQL
>> >> > # DB = [ backend = "mysql",
>> >> > # server = "localhost",
>> >> > # port = 0,
>> >> > # user = "oneadmin",
>> >> > # passwd = "oneadmin",
>> >> > # db_name = "opennebula" ]
>> >> >
>> >> > VNC_BASE_PORT = 5900
>> >> >
>> >> > DEBUG_LEVEL = 3
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Physical Networks configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # NETWORK_SIZE: Here you can define the default size for the
>> virtual
>> >> > networks
>> >> > #
>> >> > # MAC_PREFIX: Default MAC prefix to be used to create the
>> >> > auto-generated MAC
>> >> > # addresses is defined here (this can be overrided by the Virtual
>> >> > Network
>> >> > # template)
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> > NETWORK_SIZE = 254
>> >> >
>> >> > MAC_PREFIX = "02:00"
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Image Repository Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # DEFAULT_IMAGE_TYPE: This can take values
>> >> > # OS Image file holding an operating system
>> >> > # CDROM Image file holding a CDROM
>> >> > # DATABLOCK Image file holding a datablock,
>> >> > # always created as an empty block
>> >> > # DEFAULT_DEVICE_PREFIX: This can be set to
>> >> > # hd IDE prefix
>> >> > # sd SCSI
>> >> > # xvd XEN Virtual Disk
>> >> > # vd KVM virtual disk
>> >> >
>> >>
>> #*******************************************************************************
>> >> > DEFAULT_IMAGE_TYPE = "OS"
>> >> > DEFAULT_DEVICE_PREFIX = "hd"
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Information Driver Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # You can add more information managers with different
>> configurations
>> >> > but make
>> >> > # sure it has different names.
>> >> > #
>> >> > # name : name for this information manager
>> >> > #
>> >> > # executable: path of the information driver executable, can be
>> an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments : for the driver executable, usually a probe
>> >> configuration
>> >> > file,
>> >> > # can be an absolute path or relative to
>> >> $ONE_LOCATION/etc
>> >> > (or
>> >> > # /etc/one/ if OpenNebula was installed in /)
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # KVM Information Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > IM_MAD = [
>> >> > name = "im_kvm",
>> >> > executable = "one_im_ssh",
>> >> > arguments = "-r 0 -t 15 kvm" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # XEN Information Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #IM_MAD = [
>> >> > # name = "im_xen",
>> >> > # executable = "one_im_ssh",
>> >> > # arguments = "xen" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # VMware Information Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #IM_MAD = [
>> >> > # name = "im_vmware",
>> >> > # executable = "one_im_sh",
>> >> > # arguments = "-t 15 -r 0 vmware" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # EC2 Information Driver Manager Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #IM_MAD = [
>> >> > # name = "im_ec2",
>> >> > # executable = "one_im_ec2",
>> >> > # arguments = "im_ec2/im_ec2.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-----------------------------------------------------------------------------
>> >> > # Ganglia Information Driver Manager Configuration
>> >> >
>> >>
>> #-----------------------------------------------------------------------------
>> >> > #IM_MAD = [
>> >> > # name = "im_ganglia",
>> >> > # executable = "one_im_sh",
>> >> > # arguments = "ganglia" ]
>> >> >
>> >>
>> #-----------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # Dummy Information Driver Manager Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #IM_MAD = [ name="im_dummy", executable="one_im_dummy"]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Virtualization Driver Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # You can add more virtualization managers with different
>> >> configurations
>> >> > but
>> >> > # make sure it has different names.
>> >> > #
>> >> > # name : name of the virtual machine manager driver
>> >> > #
>> >> > # executable: path of the virtualization driver executable, can
>> be
>> >> an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments : for the driver executable
>> >> > #
>> >> > # default : default values and configuration parameters for the
>> >> > driver, can
>> >> > # be an absolute path or relative to
>> $ONE_LOCATION/etc
>> >> (or
>> >> > # /etc/one/ if OpenNebula was installed in /)
>> >> > #
>> >> > # type : driver type, supported drivers: xen, kvm, xml
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # KVM Virtualization Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> > # -l <actions[=command_name]> actions executed locally, command
>> >> can be
>> >> > # overridden for each action.
>> >> > # Valid actions: deploy, shutdown, cancel, save, restore,
>> >> > migrate, poll
>> >> > # An example: "-l migrate,poll=poll_ganglia,save"
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > VM_MAD = [
>> >> > name = "vmm_kvm",
>> >> > executable = "one_vmm_exec",
>> >> > arguments = "-t 15 -r 0 kvm",
>> >> > default = "vmm_exec/vmm_exec_kvm.conf",
>> >> > type = "kvm" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # XEN Virtualization Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> > # -l <actions[=command_name]> actions executed locally, command
>> >> can be
>> >> > # overridden for each action.
>> >> > # Valid actions: deploy, shutdown, cancel, save, restore,
>> >> > migrate, poll
>> >> > # An example: "-l migrate,poll=poll_ganglia,save"
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #VM_MAD = [
>> >> > # name = "vmm_xen",
>> >> > # executable = "one_vmm_exec",
>> >> > # arguments = "-t 15 -r 0 xen",
>> >> > # default = "vmm_exec/vmm_exec_xen.conf",
>> >> > # type = "xen" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # VMware Virtualization Driver Manager Configuration
>> >> > # -r number of retries when monitoring a host
>> >> > # -t number of threads, i.e. number of hosts monitored at the
>> same
>> >> > time
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #VM_MAD = [
>> >> > # name = "vmm_vmware",
>> >> > # executable = "one_vmm_sh",
>> >> > # arguments = "-t 15 -r 0 vmware",
>> >> > # default = "vmm_exec/vmm_exec_vmware.conf",
>> >> > # type = "vmware" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # EC2 Virtualization Driver Manager Configuration
>> >> > # arguments: default values for the EC2 driver, can be an
>> absolute
>> >> > path or
>> >> > # relative to $ONE_LOCATION/etc (or /etc/one/ if
>> >> > OpenNebula was
>> >> > # installed in /).
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #VM_MAD = [
>> >> > # name = "vmm_ec2",
>> >> > # executable = "one_vmm_ec2",
>> >> > # arguments = "vmm_ec2/vmm_ec2.conf",
>> >> > # type = "xml" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # Dummy Virtualization Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #VM_MAD = [ name="vmm_dummy", executable="one_vmm_dummy",
>> type="xml" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Transfer Manager Driver Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # You can add more transfer managers with different configurations
>> but
>> >> > make
>> >> > # sure it has different names.
>> >> > # name : name for this transfer driver
>> >> > #
>> >> > # executable: path of the transfer driver executable, can be an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments : for the driver executable, usually a commands
>> >> > configuration file
>> >> > # , can be an absolute path or relative to
>> >> > $ONE_LOCATION/etc (or
>> >> > # /etc/one/ if OpenNebula was installed in /)
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # SHARED Transfer Manager Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > TM_MAD = [
>> >> > name = "tm_shared",
>> >> > executable = "one_tm",
>> >> > arguments = "tm_shared/tm_shared.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # SSH Transfer Manager Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #TM_MAD = [
>> >> > # name = "tm_ssh",
>> >> > # executable = "one_tm",
>> >> > # arguments = "tm_ssh/tm_ssh.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # Dummy Transfer Manager Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #TM_MAD = [
>> >> > # name = "tm_dummy",
>> >> > # executable = "one_tm",
>> >> > # arguments = "tm_dummy/tm_dummy.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # LVM Transfer Manager Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #TM_MAD = [
>> >> > # name = "tm_lvm",
>> >> > # executable = "one_tm",
>> >> > # arguments = "tm_lvm/tm_lvm.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # VMware DataStore Transfer Manager Driver Configuration
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #TM_MAD = [
>> >> > # name = "tm_vmware",
>> >> > # executable = "one_tm",
>> >> > # arguments = "tm_vmware/tm_vmware.conf" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Image Manager Driver Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Drivers to manage the image repository, specialized for the
>> storage
>> >> > backend
>> >> > # executable: path of the transfer driver executable, can be an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments : for the driver executable
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # FS based Image Manager Driver Configuration
>> >> > # -t number of threads, i.e. number of repo operations at the
>> same
>> >> > time
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > IMAGE_MAD = [
>> >> > executable = "one_image",
>> >> > arguments = "fs -t 15" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Hook Manager Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # The Driver (HM_MAD), used to execute the Hooks
>> >> > # executable: path of the hook driver executable, can be an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments : for the driver executable, can be an absolute path
>> or
>> >> > relative
>> >> > # to $ONE_LOCATION/etc (or /etc/one/ if OpenNebula
>> was
>> >> > installed
>> >> > # in /)
>> >> > #
>> >> > # Virtual Machine Hooks (VM_HOOK) defined by:
>> >> > # name : for the hook, useful to track the hook (OPTIONAL)
>> >> > # on : when the hook should be executed,
>> >> > # - CREATE, when the VM is created (onevm create)
>> >> > # - PROLOG, when the VM is in the prolog state
>> >> > # - RUNNING, after the VM is successfully booted
>> >> > # - SHUTDOWN, after the VM is shutdown
>> >> > # - STOP, after the VM is stopped (including VM image
>> >> > transfers)
>> >> > # - DONE, after the VM is deleted or shutdown
>> >> > # - FAILED, when the VM enters the failed state
>> >> > # command : path is relative to $ONE_LOCATION/var/remotes/hook
>> >> > # (self-contained) or to /var/lib/one/remotes/hook
>> >> > (system-wide).
>> >> > # That directory will be copied on the hosts under
>> >> > # SCRIPTS_REMOTE_DIR. It can be an absolute path that
>> >> must
>> >> > exist
>> >> > # on the target host
>> >> > # arguments : for the hook. You can access to VM information
>> with $
>> >> > # - $VMID, the ID of the virtual machine
>> >> > # - $TEMPLATE, the VM template in xml and base64
>> encoded
>> >> > # remote : values,
>> >> > # - YES, The hook is executed in the host where the
>> VM
>> >> was
>> >> > # allocated
>> >> > # - NO, The hook is executed in the OpenNebula server
>> >> > (default)
>> >> > #
>> >> > #
>> >> > # Host Hooks (HOST_HOOK) defined by:
>> >> > # name : for the hook, useful to track the hook (OPTIONAL)
>> >> > # on : when the hook should be executed,
>> >> > # - CREATE, when the Host is created (onehost create)
>> >> > # - ERROR, when the Host enters the error state
>> >> > # - DISABLE, when the Host is disabled
>> >> > # command : path is relative to $ONE_LOCATION/var/remotes/hook
>> >> > # (self-contained) or to /var/lib/one/remotes/hook
>> >> > (system-wide).
>> >> > # That directory will be copied on the hosts under
>> >> > # SCRIPTS_REMOTE_DIR. It can be an absolute path that
>> >> must
>> >> > exist
>> >> > # on the target host.
>> >> > # arguments : for the hook. You can use the following Host
>> >> information:
>> >> > # - $HID, the ID of the host
>> >> > # - $TEMPLATE, the Host template in xml and base64
>> >> encoded
>> >> > # remote : values,
>> >> > # - YES, The hook is executed in the host
>> >> > # - NO, The hook is executed in the OpenNebula server
>> >> > (default)
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> > HM_MAD = [
>> >> > executable = "one_hm" ]
>> >> >
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Fault Tolerance Hooks
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # This hook is used to perform recovery actions when a host fails.
>> The
>> >> > VMs
>> >> > # running in the host can be deleted (use -d option) or resubmitted
>> >> (-r)
>> >> > in
>> >> > # other host
>> >> > # Last argument (force) can be "y", so suspended VMs in the host
>> will
>> >> be
>> >> > # resubmitted/deleted, or "n", so suspended VMs in the host will be
>> >> > ignored
>> >> > #
>> >> > #HOST_HOOK = [
>> >> > # name = "error",
>> >> > # on = "ERROR",
>> >> > # command = "ft/host_error.rb",
>> >> > # arguments = "$HID -r n",
>> >> > # remote = "no" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > # These two hooks can be used to automatically delete or resubmit
>> VMs
>> >> > that reach
>> >> > # the "failed" state. This way, the administrator doesn't have to
>> >> > interact
>> >> > # manually to release its resources or retry the deployment.
>> >> > #
>> >> > #
>> >> > # Only one of them should be uncommented.
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> > #
>> >> > #VM_HOOK = [
>> >> > # name = "on_failure_delete",
>> >> > # on = "FAILED",
>> >> > # command = "/usr/bin/env onevm delete",
>> >> > # arguments = "$VMID" ]
>> >> > #
>> >> > #VM_HOOK = [
>> >> > # name = "on_failure_resubmit",
>> >> > # on = "FAILED",
>> >> > # command = "/usr/bin/env onevm resubmit",
>> >> > # arguments = "$VMID" ]
>> >> >
>> >>
>> #-------------------------------------------------------------------------------
>> >> >
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # Auth Manager Configuration
>> >> >
>> >>
>> #*******************************************************************************
>> >> > # AUTH_MAD: The Driver that will be used to authenticate (authn)
>> and
>> >> > # authorize (authz) OpenNebula requests. If defined OpenNebula will
>> >> use
>> >> > the
>> >> > # built-in auth policies.
>> >> > #
>> >> > # executable: path of the auth driver executable, can be an
>> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
>> >> (or
>> >> > # /usr/lib/one/mads/ if OpenNebula was installed in
>> /)
>> >> > #
>> >> > # arguments :
>> >> > # --authn: list of authentication modules separated by
>> commas,
>> >> if
>> >> > not
>> >> > # defined all the modules available will be enabled
>> >> > # --authz: authorization module
>> >> > #
>> >> > # SESSION_EXPIRATION_TIME: Time in seconds to keep an authenticated
>> >> > token as
>> >> > # valid. During this time, the driver is not used. Use 0 to disable
>> >> > session
>> >> > # caching
>> >> > #
>> >> > # ENABLE_OTHER_PERMISSIONS: Whether or not to enable the
>> permissions
>> >> for
>> >> > # 'other'. Users in the oneadmin group will still be able to change
>> >> > # these permissions. Values: YES or NO
>> >> >
>> >>
>> #*******************************************************************************
>> >> >
>> >> > AUTH_MAD = [
>> >> > executable = "one_auth_mad",
>> >> > arguments = "--authn ssh,x509,ldap,server_cipher,server_x509"
>> >> > # arguments = "--authz quota --authn
>> >> > ssh,x509,ldap,server_cipher,server_x509"
>> >> > ]
>> >> >
>> >> > SESSION_EXPIRATION_TIME = 900
>> >> >
>> >> > #ENABLE_OTHER_PERMISSIONS = "YES"
>> >> >
>> >> >
>> >> > /etc/one/sunstone-server.conf
>> >> >
>> >> > # OpenNebula sever contact information
>> >> > :one_xmlrpc: http://localhost:2633/RPC2
>> >> >
>> >> > # Server Configuration
>> >> > :host: localhost
>> >> > :port: 8080
>> >> >
>> >> > # Authentication driver for incomming requests
>> >> > # sunstone, for OpenNebula's user-password scheme
>> >> > # x509, for x509 certificates based authentication
>> >> > :auth: sunstone
>> >> >
>> >> > # Authentication driver to communicate with OpenNebula core
>> >> > # cipher, for symmetric cipher encryption of tokens
>> >> > # x509, for x509 certificate encryption of tokens
>> >> > :core_auth: cipher
>> >> >
>> >> > # VNC Configuration
>> >> > :vnc_proxy_base_port: 29876
>> >> > :novnc_path:
>> >> >
>> >> > # Default language setting
>> >> > :lang: en_US
>> >> >
>> >> >
>> >> > /var/log/one/oned.log
>> >> >
>> >> > Wed May 2 11:24:38 2012 [ONE][I]: Starting OpenNebula 3.2.1
>> >> > ----------------------------------------
>> >> > OpenNebula Configuration File
>> >> > ----------------------------------------
>> >> > AUTH_MAD=ARGUMENTS=--authn
>> >> > ssh,x509,ldap,server_cipher,server_x509,EXECUTABLE=one_auth_mad
>> >> > DB=BACKEND=sqlite
>> >> > DEBUG_LEVEL=3
>> >> > DEFAULT_DEVICE_PREFIX=hd
>> >> > DEFAULT_IMAGE_TYPE=OS
>> >> > ENABLE_OTHER_PERMISSIONS=YES
>> >> > HM_MAD=EXECUTABLE=one_hm
>> >> > HOST_MONITORING_INTERVAL=600
>> >> > HOST_PER_INTERVAL=15
>> >> > IMAGE_MAD=ARGUMENTS=fs -t 15,EXECUTABLE=one_image
>> >> > IM_MAD=ARGUMENTS=-r 0 -t 15 kvm,EXECUTABLE=one_im_ssh,NAME=im_kvm
>> >> > MAC_PREFIX=02:00
>> >> > MANAGER_TIMER=15
>> >> > NETWORK_SIZE=254
>> >> > PORT=2633
>> >> > SCRIPTS_REMOTE_DIR=/var/tmp/one
>> >> > SESSION_EXPIRATION_TIME=900
>> >> >
>> >>
>> TM_MAD=ARGUMENTS=tm_shared/tm_shared.conf,EXECUTABLE=one_tm,NAME=tm_shared
>> >> > VM_DIR=/var/lib/one/
>> >> > VM_MAD=ARGUMENTS=-t 15 -r 0
>> >> >
>> >>
>> kvm,DEFAULT=vmm_exec/vmm_exec_kvm.conf,EXECUTABLE=one_vmm_exec,NAME=vmm_kvm,TYPE=kvm
>> >> > VM_PER_INTERVAL=5
>> >> > VM_POLLING_INTERVAL=600
>> >> > VNC_BASE_PORT=5900
>> >> > ----------------------------------------
>> >> > Wed May 2 11:24:38 2012 [ONE][I]: Log level:3
>> >> > [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
>> >> > Wed May 2 11:24:38 2012 [ONE][I]: Checking database version.
>> >> > Wed May 2 11:24:38 2012 [VMM][I]: Starting Virtual Machine
>> Manager...
>> >> > Wed May 2 11:24:38 2012 [LCM][I]: Starting Life-cycle Manager...
>> >> > Wed May 2 11:24:38 2012 [VMM][I]: Virtual Machine Manager started.
>> >> > Wed May 2 11:24:38 2012 [LCM][I]: Life-cycle Manager started.
>> >> > Wed May 2 11:24:38 2012 [InM][I]: Starting Information Manager...
>> >> > Wed May 2 11:24:38 2012 [InM][I]: Information Manager started.
>> >> > Wed May 2 11:24:38 2012 [TrM][I]: Starting Transfer Manager...
>> >> > Wed May 2 11:24:38 2012 [DiM][I]: Starting Dispatch Manager...
>> >> > Wed May 2 11:24:38 2012 [TrM][I]: Transfer Manager started.
>> >> > Wed May 2 11:24:38 2012 [HKM][I]: Starting Hook Manager...
>> >> > Wed May 2 11:24:38 2012 [DiM][I]: Dispatch Manager started.
>> >> > Wed May 2 11:24:38 2012 [HKM][I]: Hook Manager started.
>> >> > Wed May 2 11:24:38 2012 [AuM][I]: Starting Auth Manager...
>> >> > Wed May 2 11:24:38 2012 [AuM][I]: Authorization Manager started.
>> >> > Wed May 2 11:24:38 2012 [ImM][I]: Starting Image Manager...
>> >> > Wed May 2 11:24:38 2012 [ImM][I]: Image Manager started.
>> >> > Wed May 2 11:24:38 2012 [ReM][I]: Starting Request Manager...
>> >> > Wed May 2 11:24:38 2012 [ReM][I]: Starting XML-RPC server, port
>> 2633
>> >> ...
>> >> > Wed May 2 11:24:38 2012 [ReM][I]: Request Manager started.
>> >> > Wed May 2 11:24:40 2012 [VMM][I]: Loading Virtual Machine Manager
>> >> > drivers.
>> >> > Wed May 2 11:24:40 2012 [VMM][I]: Loading driver: vmm_kvm
>> (KVM)
>> >> > Wed May 2 11:24:40 2012 [VMM][I]: Driver vmm_kvm loaded.
>> >> > Wed May 2 11:24:40 2012 [InM][I]: Loading Information Manager
>> >> drivers.
>> >> > Wed May 2 11:24:40 2012 [InM][I]: Loading driver: im_kvm
>> >> > Wed May 2 11:24:40 2012 [InM][I]: Driver im_kvm loaded
>> >> > Wed May 2 11:24:40 2012 [TM][I]: Loading Transfer Manager drivers.
>> >> > Wed May 2 11:24:40 2012 [VMM][I]: Loading driver: tm_shared
>> >> > Wed May 2 11:24:40 2012 [TM][I]: Driver tm_shared loaded.
>> >> > Wed May 2 11:24:40 2012 [HKM][I]: Loading Hook Manager driver.
>> >> > Wed May 2 11:24:40 2012 [HKM][I]: Hook Manager loaded
>> >> > Wed May 2 11:24:40 2012 [ImM][I]: Loading Image Manager driver.
>> >> > Wed May 2 11:24:40 2012 [ImM][I]: Image Manager loaded
>> >> > Wed May 2 11:24:40 2012 [AuM][I]: Loading Auth. Manager driver.
>> >> > Wed May 2 11:24:40 2012 [AuM][I]: Auth Manager loaded
>> >> > Wed May 2 11:24:57 2012 [ReM][D]: HostPoolInfo method invoked
>> >> > Wed May 2 11:24:57 2012 [ReM][D]: VirtualMachinePoolInfo method
>> >> invoked
>> >> > Wed May 2 11:24:57 2012 [ReM][D]: AclInfo method invoked
>> >> > Wed May 2 11:25:27 2012 [ReM][D]: HostPoolInfo method invoked
>> >> > Wed May 2 11:25:27 2012 [ReM][D]: VirtualMachinePoolInfo method
>> >> invoked
>> >> > Wed May 2 11:25:27 2012 [ReM][D]: AclInfo method invoked
>> >> > Wed May 2 11:26:56 2012 [ReM][D]: HostPoolInfo method invoked
>> >> > Wed May 2 11:26:57 2012 [ReM][D]: VirtualMachinePoolInfo method
>> >> invoked
>> >> > Wed May 2 11:26:57 2012 [ReM][D]: AclInfo method invoked
>> >> > Wed May 2 11:27:26 2012 [ReM][D]: HostPoolInfo method invoked
>> >> > Wed May 2 11:27:27 2012 [ReM][D]: VirtualMachinePoolInfo method
>> >> invoked
>> >> > Wed May 2 11:27:27 2012 [ReM][D]: AclInfo method invoked
>> >> > Wed May 2 11:27:39 2012 [ReM][D]: UserPoolInfo method invoked
>> >> > Wed May 2 11:27:39 2012 [ReM][E]: [UserPoolInfo] User couldn't be
>> >> > authenticated, aborting call.
>> >> >
>> >> >
>> >> >
>> >> > /var/log/one/sunstone.log
>> >> >
>> >> > == Sinatra/1.3.2 has taken the stage on 8080 for development with
>> >> backup
>> >> > from Thin
>> >> >
>> >> > (and that's all until I stop the sunstone-server.)
>> >> >
>> >> >
>> >> > Again, thanks all for your answers, Olivier, Lehel & Hector :-)
>> >> >
>> >> > Guillaume
>> >> >
>> >> >
>> >> > Date: Wed, 2 May 2012 08:18:55 +0200
>> >> > From: olivier.sallou at codeless.fr
>> >> > To: licks0re at hotmail.com
>> >> > Subject: Re: [one-users] sunstone says : "OpenNebula is not
>> running"
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Le 5/1/12 10:10 AM, Guigui 6675636b206f6666 a écrit :
>> >> >
>> >> > Well, it's on the same machine so I guess it tries to
>> connect
>> >> > localhost, am I wrong?
>> >> >
>> >> >
>> >> > By the way, happy day-off 1st of may ;-)
>> >> >
>> >> >
>> >> > All depends on configuration.
>> >> >
>> >> > If it listens on 127.0.0.1, it will accept connections only on
>> >> this
>> >> > interface. So it sunstone is configured to call oned on
>> current ip
>> >> > instead of 127.0.01 it will fail for example.
>> >> >
>> >> > The listen address and the connection address should exactly be
>> >> the
>> >> > same (or one should listen on 0.0.0.0)
>> >> >
>> >> >
>> >> > Olivier
>> >> >
>> >> >> To: users at lists.opennebula.org
>> >> >> Date: Tue, 1 May 2012 12:28:06 +0200
>> >> >> From: hsanjuan at opennebula.org
>> >> >> Subject: Re: [one-users] sunstone says : "OpenNebula is not
>> running"
>> >> >>
>> >> >> Hi, can you send /var/log/one/sunstone.log. It may have useful
>> info.
>> >> >> Also
>> >> >> check oned.log in case it is an auth problem.
>> >> >>
>> >> >> Hector
>> >> >>
>> >> >> En Tue, 01 May 2012 08:50:58 +0200, Guigui 6675636b206f6666
>> >> >> <licks0re at hotmail.com> escribió:
>> >> >>
>> >> >> >
>> >> >> > Good morning,
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > I'm trying to setup open nebula on an opensuse 12.1
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > I followed this document (which, if you do exactly the steps is
>> NOT
>> >> >> > working at the end):
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > SDB:Cloud OpenNebula - openSUSE
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > The problem is that I can't get sunstone server working. I
>> double
>> >> >> > checked the settings, etc, no way I'll get it to work.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > Sunstone server systematically answers :
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > "OpenNebula is not running"
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > But, I confirm that open nebula IS running, here's a ps -ef |
>> grep
>> >> >> one :
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > oneadmin 3046 1 0 Apr30 pts/0 00:00:05 /usr/bin/oned -f
>> >> >> >
>> >> >> > oneadmin 3064 1 0 Apr30 pts/0 00:00:03
>> /usr/bin/mm_sched
>> >> >> >
>> >> >> > oneadmin 3067 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_vmm_exec.rb -t 15 -r 0 kvm
>> >> >> >
>> >> >> > oneadmin 3077 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_im_exec.rb -r 0 -t 15 kvm
>> >> >> >
>> >> >> > oneadmin 3086 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_tm.rb tm_shared/tm_shared.conf
>> >> >> >
>> >> >> > oneadmin 3099 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_hm.rb
>> >> >> >
>> >> >> > oneadmin 3109 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_image.rb fs -t 15
>> >> >> >
>> >> >> > oneadmin 3118 3046 0 Apr30 pts/0 00:00:00 ruby
>> >> >> > /usr/lib/one/mads/one_auth_mad.rb --authn
>> >> >> > ssh,x509,ldap,server_cipher,server_x509
>> >> >> >
>> >> >> > root 3162 1 0 Apr30 pts/0 00:00:17 ruby
>> >> >> > /usr/lib/one/sunstone/sunstone-server.rb
>> >> >> >
>> >> >> > root 6697 2989 0 08:18 pts/0 00:00:00 grep
>> --color=auto
>> >> one
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > Any clues?
>> >> >> >
>> >> >> > Thanks in advance!
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Hector Sanjuan
>> >> >> OpenNebula Developer
>> >> >> _______________________________________________
>> >> >> Users mailing list
>> >> >> Users at lists.opennebula.org
>> >> >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>> >> >
>> >>
>> >>
>> >> --
>> >> Hector Sanjuan
>> >> OpenNebula Developer
>> >
>>
>>
>> --
>> Hector Sanjuan
>> OpenNebula Developer
>
--
Hector Sanjuan
OpenNebula Developer
More information about the Users
mailing list