cluster.conf.new: Permission denied

mfaure

New Member
Hello,

I'm trying to setup Unicast and modifying /etc/pve/cluster.conf with the instructions from http://pve.proxmox.com/wiki/Fencing#General_HowTo_for_editing_the_cluster.conf, but I can't copy the file:

Code:
# cp /etc/pve/cluster.conf /etc/pve/cluster.conf.new
cp: cannot create regular file `/etc/pve/cluster.conf.new': Permission denied

I can't even create a single empty file

Code:
# touch dummy-file
touch: cannot touch `dummy-file': Permission denied

Here are the rights on the files:
Code:
# ls -al
total 5
drwxr-x---  2 root www-data    0 Jan  1  1970 .
drwxr-xr-x 91 root root     4096 Dec 28 10:32 ..
-r--r-----  1 root www-data  294 Dec 27 20:11 cluster.conf
-r--r-----  1 root www-data  155 Jan  1  1970 .clusterlog
-rw-r-----  1 root www-data    2 Jan  1  1970 .debug
lr-xr-x---  1 root www-data    0 Jan  1  1970 local -> nodes/proxmox9
-r--r-----  1 root www-data  242 Jan  1  1970 .members
lr-xr-x---  1 root www-data    0 Jan  1  1970 openvz -> nodes/proxmox9/openvz
lr-xr-x---  1 root www-data    0 Jan  1  1970 qemu-server -> nodes/proxmox9/qemu-server
-r--r-----  1 root www-data  205 Jan  1  1970 .rrd
-r--r-----  1 root www-data  256 Jan  1  1970 .version
-r--r-----  1 root www-data   18 Jan  1  1970 .vmlist

What am I missing ?
 
This thread is very old but I ran into the same issue and I don't see a viable solution for this thread so I will post my solution in case someone has same issue and even for my future self ;).

In proxmox7 the /etc/pve/ directory is lock by proxmox so no actions can be made.
to unlock it
Bash:
systemctl stop pve-cluster
# At this point I think we can directly modify /etc/pve/corosync.conf
# but I will follow the suggested Proxmox wiki procedure
cp /etc/pve/corosync.conf /etc/pve/corosync.conf.new
cp /etc/pve/corosync.conf /etc/pve/corosync.conf.bak
nano /etc/pve/corosync.conf.new
mv /etc/pve/corosync.conf.new /etc/pve/corosync.conf
systemctl start pve-cluster

I hope it helps
 
This thread is very old but I ran into the same issue and I don't see a viable solution for this thread so I will post my solution in case someone has same issue and even for my future self ;).

In proxmox7 the /etc/pve/ directory is lock by proxmox so no actions can be made.
to unlock it
Bash:
systemctl stop pve-cluster
# At this point I think we can directly modify /etc/pve/corosync.conf
# but I will follow the suggested Proxmox wiki procedure
cp /etc/pve/corosync.conf /etc/pve/corosync.conf.new
cp /etc/pve/corosync.conf /etc/pve/corosync.conf.bak
nano /etc/pve/corosync.conf.new
mv /etc/pve/corosync.conf.new /etc/pve/corosync.conf
systemctl start pve-cluster

I hope it helps

This is totaly wrong.
After you stop the cluster there is nothing to edit in /etc/pve
 
To modify corosync file :
Bash:
nano /etc/corosync/corosync.conf
once the modifications have been made :
Bash:
systemctl restart pve-cluster
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!