| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Jordi you where correct
VLM was totally corrupt, reasons
unknown, 24 hours of sleepless work to restore 6 V servers to full
working order again. Time to finally sleep.
Issue closed
On 9/10/07, Jordi Prats <jprats@xxxxxxxx> wrote:
Hi Mike,
If it isn't a permissions issue, I would try to fsck the filesystem. Do
you have SELinux enabled? It use to be a pain in the ass.
best regards,
Jordi
Mike Johnson wrote:
> We needed to reboot our Xen server after 201 days of uptime after making
> some very minor hard drive adjucements. As far as we can tell nothing
> major changed yet we can't launch out xend here is what the debug log says.
>
>
> All of our clients websites are down until we can resolve this issue.
>
> Thank you for any help anyone can offer
>
> root@ffvi:~# tail -f /var/log/xen/xend-debug.log
> Exception in thread Thread-2:
> Traceback (most recent call last):
> File "threading.py", line 460, in __bootstrap
>
self.run()
> File "/usr/lib/python/xen/xend/XendMonitor.py", line 220, in run
> for domid, cputimes in self._get_cpu_stats().items():
> File "/usr/lib/python/xen/xend/XendMonitor.py", line 198, in
> _get_cpu_stats
> for domain in self.xc.domain_getinfo():
> Error: (13, 'Permission denied')
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
>
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home