On 19 October 2011 00:02, Faarooq Lowe wrote:
> It appears to yield the same level of debugging.
Try running it without strace
--
Daniel Molina
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | @dmamolina
__
El 18/10/11 23:53, Clément Berthelot escribió:
> I realized I couldn't connect from the frontend to the node with SSH
> (connection closed immediately by the node). This is really weird because it
> works perfectly the other way around (from the node to the frontend) not
> asking for any passwor
It appears to yield the same level of debugging.
Here is what we are finding
stat("/usr/local/lib/ruby/1.8/rexml/document.rb", {st_mode=S_IFREG|0644,
st_size=7619, ...}) = 0
open("/usr/local/lib/ruby/1.8/rexml/document.rb", O_RDONLY) = 7
fstat(7, {st_mode=S_IFREG|0644, st_size=7619, ...}) = 0
You could execute virsh list so the daemon should be listening. To me
the error with the iptables could be the cause to that "Unknown
failure". Try flushing iptables.
Also as you could start other VMs try to check the differences, maybe
the virtio drivers or the vnc.
On Tue, Oct 18, 2011 at 11:47
Hey guys,
I'm working on my master thesis which has for subject the evaluation of virtual
firewall in cloud environment. In this optic, I'm trying to create my own cloud
with Xen and OpenNebula. Both the machines I use (Frontend and Node) runs
OpenSUSE 11.4. I followed very closely the document
I think the problem is in the following section of the sunstone-server.rb
begin
result = cloud_auth.auth(request.env, params)
rescue Exception => e
error 500, e.message
end
the exception is captured and is not shown in the login screen, instead you
g
Javier - I did note the following on the hypervisor /var/log/messages on
restart:
Oct 18 11:05:52 localhost libvirtd: 11:05:52.794: error : virRunWithHook:856 :
internal error '/sbin/iptables --table filter --delete INPUT --in-interface
virbr0 --protocol udp --destination-port 69 --jump ACCEPT'
I don't see anything strange in the deployment file and with so little
information from libvirt I would create a new VM with the same
paremeters but without vnc or virtio. I can only see those as the
cause for non descriptive problems.
Also as the libvirt FAQ [1] says check /var/log/messages for s
As requested:
[root@kvm02 10]# cat deployment.1
one-10
4
4194304
hvm
/usr/bin/kvm
[root@kvm02 10]# cat deployment.2
one-10
4
4194304
hvm
/usr/bin/kvm
[root@kvm02 10]# virsh list --inactive
Id Name State
--
Can you send us the deployment files (I can see both deployment.1 and
deployment.2) files? Also go to the node and execute
# virsh list --inactive
as root and check that there are no inactive VMs defined.
Cheers
On Tue, Oct 18, 2011 at 6:28 PM, Ryan Aydelott wrote:
> I am having an issue with
Unfortunately I don't know of any way to stop or recover the failed
migration with OpenNebula or manually.
Rebooting a physical host will basically destroy the running VMs and
most probably the disks will be corrupted.
On Tue, Oct 18, 2011 at 2:34 PM, samuel wrote:
> I add more information so yo
Can you tell me the packages needed to be able to compile/install the
failing gems? I already had rake and gcc for most of the gems but
probably some slipped through my fingers.
2011/10/18 Ruben Diez :
> We had used the /usr/share/one/install_gems script to install gems
>
> Never the less seem
Hi Daniel,
Here is some additional information.
I started the sunstone-server once directly by referencing the ruby
script and used strace
Here is output from that when I attempted to login using x509 credentials?
write(2, "131.225.80.86 - - [18/Oct/2011 1"..., 77131.225.80.86 - -
[18/Oct/2
Hi,
On Tue, 2011-10-18 at 16:41 +0200, Ruben Diez wrote:
> We had used the /usr/share/one/install_gems script to install gems
> Never the less seems that some of them need the corresponded devel c
> library, and fails to install
Could you file a bug report at
http://dev.opennebula.org/projec
Hi,
sorry for the late answer, i missed this one.
So I think that the problem is that Sunstone is not using secure
websockets by default[1]. Therefore websocket connection is trying to
travel through port 80. Since you are tunneling only port 443, it is
impossible for noVNC to contact the proxy o
AUTH_MAD section of oned.conf
AUTH_MAD = [
executable = "/usr/lib/one/mads/one_auth_mad",
#arguments = "--authz quota --authn x509,server"
#arguments = "--authn x509,server"
arguments = "--authn x509, server_auth"
]
sunstone-server.conf
# OpenNebula sever contact information
:on
Hi,
On 18 October 2011 18:24, Faarooq Lowe wrote:
> We are running OpenNebula 3.0 with Sunstone. I am able to use command-line
> launch VMs and to see host, VMs, users, etc.
>
> The sunstone server did launch successfully, however when I attempt to
> login to I get the following message: "Open
Hi,
Just to make sure, please check every item here and report back:
http://wiki.opennebula.org/faq#vnc_console_access_in_sunstone_does_not_work_whats_the_problem
Héctor Sanjuán
OpenNebula Developer
El 17/10/11 18:42, Olivier Sallou escribió:
> Just to give some more info:
>
> manual execution
I am having an issue with bootstrapping an image into a KVM hypervisor, I have
had success with Xen prior to this, but now trying KVM. Some basic info:
OpenNebula 3.0
libvirtd on KVM (Centos 5.6) is 0.8.2
Shared NFS Filesystem
oneadmin account adding to KVM/QEMU groups
onehost successfully monit
All,
We are running OpenNebula 3.0 with Sunstone. I am able to use
command-line launch VMs and to see host, VMs, users, etc.
The sunstone server did launch successfully, however when I attempt to
login to I get the following message: "OpenNebula is not running"
The initial pages come up j
We had used the /usr/share/one/install_gems script to install gems
Never the less seems that some of them need the corresponded devel c
library, and fails to install
We now had install the gems one by one, and these errors appears...
Now the onedb command runs
Thanks a lot for your h
On Tue, 2011-10-18 at 16:00 +0200, Ruben Diez wrote:
> Seems to fail to find a function Perhaps any library is needed??
> We think all the ruby gems are installed, as the documentation explain
I had exactly the same problem with the SQLite DB,
when upgrading from 2.1 -> 3.0, and it was mis
Thank you for your help
After the modification you suggest, this is the output:
oneadmin@onesrv04:/srv/cloud$ onedb upgrade -v
undefined method `fetch' for nil:NilClass
Database schema does not look to be created by OpenNebula: table
user_pool is missing or empty.
Seems to fail to find a
I add more information so you can follow the steps taken and the final
issue.
1)segfault on node 2:
[620617.517308] kvm[28860]: segfault at 420 ip 00413714 sp
7fff9136ea70 error 4 in qemu-system-x86_64[40+335000]
VMs work OK
2)restart libvirt on node 2
/init.d/libvirt-bin restart
I don't see any other reasons why this could fail... Could you edit
/usr/lib/one/ruby/onedb/onedb_backend.rb to output some more info?
Just add the Exception message to the rescue clause in db_exists?
def db_exists?
begin
# User with ID 0 (oneadmin) always exists
Yes: it is populated:
mysql> select * from user_pool where oid=0;
+-+---+--+-+
| oid | user_name | password | enabled |
+-+---+--+-+
| 0 | onea
Yes: it is populated:
mysql> select * from user_pool where oid=0;
+-+---+--+-+
| oid | user_name | password | enabled |
+-+---+--+-+
| 0 | onea
Hi,
Is the DB in the new machine correctly populated?
Can you manually perform a "select * from user_pool where oid=0;" ?
I'm asking because the '-p' option of the mysql commands needs the password
right next to it, without any space; i.e. '-popennebula' instead of '-p
opennebula'
In case any o
Hi:
We are attempt to migrate OpenNebula from 2.1.80 to 3.0
But the new 3.0 OpenNebula was installed in a new machine.
For database migration, we have followed these steps:
1- In the old machine, we made a dump of the database:
mysqldump -h localhost -u oneadmin -p opennebula >opennebula_
hi all,
I'm having an issue with live migration.T here was a running instance on a
node that had a qemu segfault (i've noticed afterwards because the instances
were working).I've tried to live migrate the instance to another node
without problems but the instance remains in MIGRATE state "forever"
Hi,
Thank you very much, Fabian and Carlos, for your help. Things are much more
clear now, I think.
*Sharing the image repository.
If I understood right, the aim with sharing the image repository between the
front-end and the workers is to increase performance by reducing (or
eliminating) the ti
31 matches
Mail list logo