Ask Your Question
1

chardev: opening backend "file" failed: Permission denied

asked 2013-06-21 12:05:26 -0500

Sam W. gravatar image

updated 2013-06-21 13:11:25 -0500

Hi all,

I had my cluster working on a single node. glance images and nova instances are stored on an nfs mount.

I added two more nodes and enabled live-migration.

Now when I try to start to an instance I get:

nova-scheduler.log - libvirtError: internal error Process exited while reading console log output: chardev: opening backend "file" failed: Permission denied

Here is the traceback from nova-compute.log: http://pastie.org/pastes/8066860/text

I have seen references online to this error, but no solutions. Does anyone know what may be causing and better yet, how to fix it?

Thanks, Sam

=== edit ===

Here is some more information. I am using Ubuntu 12.04 LTS, I have turned off apparmor.

Here is my export/mount:

export: /data/os-grizzly   10.57.0.0/255.255.0.0(rw,no_root_squash,no_subtree_check)

mount: dedup:/big_pool/os-grizzly on /os-grizzly type nfs (rw,noatime,nolock,tcp,bg,intr,hard,addr=10.54.90.10)

root@test1:/# find /os-grizzly -type d | xargs ls -l -d
drwxr-xr-x 4 root   root   4 Jun 21 13:39 /os-grizzly
drwxr-xr-x 3 glance glance 3 Jun  3 10:25 /os-grizzly/glance
drwxr-x--- 2 glance glance 4 Jun 19 15:41 /os-grizzly/glance/images
drwxr-xr-x 3 nova   nova   3 Jun 21 13:39 /os-grizzly/nova
drwxr-xr-x 4 nova   nova   5 Jun 21 13:13 /os-grizzly/nova/instances
drwxr-xr-x 2 nova   nova   4 Jun 19 15:42 /os-grizzly/nova/instances/_base
drwxr-xr-x 2 nova   nova   6 Jun 19 15:42 /os-grizzly/nova/instances/locks

root@test1:/# grep -RE "^[^#]" /etc/libvirt/*.conf
/etc/libvirt/libvirtd.conf:listen_tls = 0
/etc/libvirt/libvirtd.conf:listen_tcp = 1
/etc/libvirt/libvirtd.conf:unix_sock_group = "libvirtd"
/etc/libvirt/libvirtd.conf:unix_sock_rw_perms = "0770"
/etc/libvirt/libvirtd.conf:auth_unix_ro = "none"
/etc/libvirt/libvirtd.conf:auth_unix_rw = "none"
/etc/libvirt/libvirtd.conf:auth_tcp = "none"
/etc/libvirt/qemu.conf:dynamic_ownership = 0
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-06-21 14:45:09 -0500

Sam W. gravatar image

When all else fails, reboot.

That seemed to fix that error. Onto the next one.

Thanks all that took the time to read this post.

edit flag offensive delete link more

Comments

P.S. I can not answer my own question because I do not have enough points.

Sam W. gravatar imageSam W. ( 2013-06-21 14:45:48 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2013-06-21 12:05:26 -0500

Seen: 753 times

Last updated: Jun 21 '13