OpenVZ Forum


Home » General » Support » /dev/null permission denied
Re: /dev/null permission denied [message #51041 is a reply to message #24676] Mon, 06 January 2014 11:54 Go to previous message
narcisgarcia is currently offline  narcisgarcia
Messages: 41
Registered: May 2009
Member
I'm running Debian 7 containers in Debian 7 HN host (Linux 2.6.32-openvz-042stab084.14-amd64), and found this problem, but not inmediately to container's boot: after several hours (or days).

This command inside the container solves me the problem for some minutes:
chmod a+rw /dev/null

But after those minutes the null device comes back to bad permissions crw-r--r--

Now I've tried this at the hardware node:
ContainerID=777
vzctl set $ContainerID --devnodes null:rw --save
vzctl stop $ContainerID
vzctl start $ContainerID


But after some time, trying to use bash-completion (pressing TAB on a terminal), I see the same problem:
Quote:
-bash: /dev/null: Permission denied
bash: _upvars: `-a2': invalid number specifier


I'M SORRY;
At this moment I think that a customized script re-created the "file" /dev/null when doesn't find it with "test -f":
rm -f $MyFile
echo "MyData" > $MyFile

BUT the strange OpenVZ behaviour is that this operation seems to spread to all other containers: one container re-creates /dev/null and all others' have this device modified.


Narcis Garcia

[Updated on: Tue, 07 January 2014 09:54]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Unable to fork: Cannot allocate memory but websites loading
Next Topic: Force date shift in VM
Goto Forum:
  


Current Time: Mon Aug 12 15:18:51 GMT 2024

Total time taken to generate the page: 0.02864 seconds