<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, is there any progress or any workaround how to show logs in
sunstone?<br>
<br>
<br>
<div class="moz-cite-prefix">Dne 7.2.2013 12:11, Andreas Calvo Gómez
napsal(a):<br>
</div>
<blockquote cite="mid:51138BD6.7060006@scytl.com" type="cite">Daniel,
<br>
On 06/02/13 14:22, Daniel Molina wrote:
<br>
<blockquote type="cite">On 6 February 2013 12:36, Andreas Calvo
Gómez <a class="moz-txt-link-rfc2396E" href="mailto:andreas.calvo@scytl.com"><andreas.calvo@scytl.com></a> wrote:
<br>
<blockquote type="cite">Daniel,
<br>
<br>
On 06/02/13 12:34, Daniel Molina wrote:
<br>
<blockquote type="cite">On 6 February 2013 12:17, Andreas
Calvo Gómez <a class="moz-txt-link-rfc2396E" href="mailto:andreas.calvo@scytl.com"><andreas.calvo@scytl.com></a>
<br>
wrote:
<br>
<blockquote type="cite">Hi Daniel!
<br>
<br>
On 06/02/13 11:15, Daniel Molina wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
On 1 February 2013 13:05, Andreas Calvo Gómez
<a class="moz-txt-link-rfc2396E" href="mailto:andreas.calvo@scytl.com"><andreas.calvo@scytl.com></a>
<br>
wrote:
<br>
<blockquote type="cite">We have performed a update of
both the OS (CentOS 6.2 to 6.3) and
<br>
OpenNebula
<br>
(3.8.1 to 3.8.3), and are facing some errors that
weren't in the older
<br>
release:
<br>
- Logs can't be viewed from the webUI: selecting the
"VM Log" tab shows
<br>
an
<br>
error message "Log for VM XXX not available".
<br>
</blockquote>
There was a bug in previous releases with the vm log
directory, but it
<br>
should be fixed in 3.8.3. Did you restart the
sunstone-server after
<br>
upgrading?
<br>
</blockquote>
Yes, several times because Sunstone or ONE becomes
unresponsive from time
<br>
to
<br>
time.
<br>
</blockquote>
Is Sunstone running on the same machine as OpenNebula?
<br>
</blockquote>
Yes, we have a frontend with Sunstone and OpenNebula (using
NFS to share the
<br>
common storage).
<br>
</blockquote>
The new vms logs should be in:
<br>
system-wide: LOG_LOCATION + "/vms/#{id}.log"
<br>
self-contained: LOG_LOCATION + "/vms/#{id}/vm.log"
<br>
the former directory was
<br>
system-wide: LOG_LOCATION + "/#{id}.log"
<br>
self-contained: LOG_LOCATION + "/#{id}/vm.log"
<br>
<br>
The logs from vms created in old versions have to be
moved/linked to
<br>
this new directory. I will update the upgrade guide with this
step,
<br>
sorry for the inconvenience..
<br>
</blockquote>
However, logs for new VMs are created under /var/log/one, which I
thought is where ONE is looking to show them.
<br>
<blockquote type="cite">
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">- One node can't establish
network connections: started VMs on one
<br>
specific
<br>
node don't have network connectivity, while they get
the IP address by
<br>
context. All other nodes work fine.
<br>
</blockquote>
Please check the following link:
<br>
<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.opennebula.org/faq#my_vm_is_running_but_i_get_no_answer_from_pings_what_s_wrong">http://wiki.opennebula.org/faq#my_vm_is_running_but_i_get_no_answer_from_pings_what_s_wrong</a>
<br>
<br>
Maybe there is something wrong with the host
configuration.
<br>
</blockquote>
I'll try that link, but all nodes performed the same
update procedure and
<br>
only one is not working.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">- Sunstone/ONE seems to be
stucked from time to time when performing
<br>
large
<br>
operations: as the old version (3.8.1), Sunstone
becomes unresponsive
<br>
and
<br>
it
<br>
is necessary to shut down all applications (one,
sunstone, occi) and
<br>
start
<br>
them again. It usually happens when performing an
operation with a
<br>
large
<br>
set
<br>
of VMs.
<br>
<br>
For all errors, no log in /var/log/one give any hint.
<br>
Is there any other way to try to narrow down the root
source of this
<br>
problems?
<br>
</blockquote>
What are exactly the actions you performed and with how
many vms?
<br>
Could you send us your sched.conf and oned.conf files?
<br>
</blockquote>
When a batch command is executed (usually deleting 50+
VMs), Sunstone or
<br>
ONE
<br>
becomes unresponsive and must be restarted.
<br>
Yes, attached you will find our config files.
<br>
</blockquote>
Can you interact with OpenNebula through the cli, or is
Sunstone the
<br>
only one that becomes unresponsive.
<br>
</blockquote>
Everything becomes unresponsive, but not at the same time.
<br>
When a user performs a large batch operation, the same user
can't run more
<br>
commands, but other users are fine for a while.
<br>
After some time, users can't log into Sunstone and other
services (such as
<br>
OCCI) become unresponsive too.
<br>
<br>
</blockquote>
Could you send us the oned.log part when this operation is
performed
<br>
</blockquote>
I've attached a compressed file with all logs (besides VM related
ones) performing the batch operation.
<br>
Hope it's usefull.
<br>
<blockquote type="cite">
<br>
Cheers
<br>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
</pre>
</blockquote>
<br>
</body>
</html>