On Feb 16, 2:14 pm, Jair Gaxiola <jyr.gaxi...@gmail.com> wrote: > On Thu, Feb 16, 2012 at 1:28 PM, Denmat <tu2bg...@gmail.com> wrote: > > Hi, > > > Is it a read only file system? > > > change from > > purged to present failed: Could not set 'present on ensure: Read-only > > file system - /tmp/puppet20120216-1063-18q7lsz-0 at > > /tmp/vagrant-puppet/manifests/vagrant.pp:15 > > I have of file system read only, > > drwxrwxrwt 3 root root 4096 Feb 16 11:43 . > drwxr-xr-x 22 root root 4096 Jul 21 2011 .. > -rw------- 1 root root 2799 Feb 16 11:49 puppet20120216-1053-1p4uxc-0 > -rw------- 1 vagrant vagrant 191 Feb 16 11:43 vagrant-network-entry > -rw-r--r-- 1 root root 283 Feb 16 11:43 vagrant-network-interfaces > drwxr-xr-x 4 root root 4096 Feb 16 11:43 vagrant-puppet > vagrant@lucid32:~$ > drwxr-xr-x 4 root root 4096 Feb 16 11:43 . > drwxrwxrwt 3 root root 4096 Feb 16 11:43 .. > drwxr-xr-x 1 vagrant vagrant 102 Feb 16 11:49 manifests > drwxr-xr-x 1 vagrant vagrant 238 Feb 15 15:23 modules-0 > vagrant@lucid32:~$ ls -al /tmp/vagrant-puppet/manifests > total 8 > drwxr-xr-x 1 vagrant vagrant 102 Feb 16 11:49 . > drwxr-xr-x 4 root root 4096 Feb 16 11:43 .. > -rw-r--r-- 1 vagrant vagrant 1444 Feb 16 10:32 vagrant.pp > > I run sudo dpkg --configure -a from console returns: > > dpkg: unable to access dpkg status area: Read-only file system
You have misunderstood Denmat's question, though it was really a statement presented in question form. Your tools are telling you that the *filesystem* is read-only. That has nothing to do with the permission bits for individual files, and everything to do with how the filesystem in question (apparently the root filesystem on the affected node) is mounted. You will find, I predict, that you cannot modify the filesystem by any means, including such trivial commands as "touch /tmp/foo". Since it seems unlikely to be itentional for the root filesystem to be monuted read-only during normal system operation, you should do two things: 1) Figure out why it is mounted read-only 2) Fix the problem and remount the filesystem read-write You might be able to achieve all that by simply rebooting the system (cleanly, if possible). For what it's worth, the only time I have ever had a filesystem unexpectedly transition from read/write to read-only happened when the system detected filesystem errors during normal operation. It remounted the filesystem read-only to prevent (further) filesystem damage. I quickly discovered that the system had a failing memory module, which was probably the root cause of the episode. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
