2

I can remember creating this file but it disapeard. But not completely:

root@XXX:/etc/vz/conf# ls -al
total 0
drwxr-x--- 2 root www-data 0 Okt  1 16:04 .
drwxr-x--- 2 root www-data 0 Okt  1 16:04 ..

root@XXX:/etc/vz/conf# touch 1030.conf
touch: cannot touch `1030.conf': File exists

root@warp1:/etc/vz/conf# echo blah > 1030.conf
-bash: 1030.conf: File exists

root@warp1:/etc/vz/conf# rm 1030.conf
rm: cannot remove `1030.conf': No such file or directory

System is Debian7 / Proxmox:

Linux warp1 2.6.32-24-pve #1 SMP Fri Sep 13 07:29:30 CEST 2013 x86_64 GNU/Linux

What is causing this and how can I get my file back / get rid of it and how do I debug sth. like this? Thanks!

Scheintod
  • 391
  • 1
  • 5
  • 17

1 Answers1

2

The file exists on another node in your cluster and Proxmox checks for that. You need to do something like:

mv /etc/pve/nodes/[node1]/openvz/whatever.conf /etc/pve/nodes/[node2]/openvz

to move the config to a different node.

seumasmac
  • 332
  • 2
  • 7
  • Brilliant. I wasn't event aware that I'm running a cluster. Just wantet to use the proxmox kernel because debian 7 doesn't include openvz kernels anymore. – Scheintod Oct 01 '13 at 16:27
  • Looking at the directory you mentioned I see that the root of the problem seems to be that I've renamed my host and this was recognised as new node. – Scheintod Oct 01 '13 at 16:28
  • Do you know what to do if I don't want this feature or what exactly is doing this? – Scheintod Oct 01 '13 at 16:30
  • I'm not sure there's anything you can do to make it more like a single machine. But perhaps it's worthy of a separate question; I'm not really a proxmox expert! – seumasmac Oct 01 '13 at 16:34