Jair Gaxiola
2012-Feb-16 19:03 UTC
[Puppet Users] Could not set present on ensure: Read-only file system
Hi,
I try install python-psycopg2 with other packages, when run apt-get -y
update returns the errors:
err: /Stage[main]/Etc/Package[build-essential]/ensure: 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
err: /Stage[main]/Etc/Package[python-psycopg2]/ensure: change from
purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install python-psycopg2'' returned 100:
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Python::Gunicorn/File[/var/log/gunicorn]/ensure:
change from absent to directory failed: Could not set ''directory on
ensure: Read-only file system - /var/log/gunicorn at
/tmp/vagrant-puppet/modules-0/python/manifests/gunicorn.pp:11
notice: /Stage[main]/Python::Gunicorn/File[/var/run/gunicorn]/ensure: created
err: /Stage[main]/Python::Venv/Package[python-virtualenv]/ensure:
change from purged to present failed: Execution of ''/usr/bin/apt-get
-q -y -o DPkg::Options::=--force-confold install python-virtualenv''
returned 100: W: Not using locking for read only lock file
/var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Group[puppet]/ensure: change from absent to present failed:
Could not create group puppet: Execution of ''/usr/sbin/groupadd
puppet'' returned 1:
err: /Stage[main]/Etc/Package[libcurl3-dev]/ensure: change from purged
to present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install libcurl3-dev'' returned 100: W:
Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Etc/Package[curl]/ensure: change from purged to
present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install curl'' returned 100: W: Not
using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Monit/Package[monit]/ensure: change from purged to
present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install monit'' returned 100: W: Not
using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
notice: /Stage[main]/Monit/File[/etc/default/monit]: Dependency
Package[monit] has failures: true
warning: /Stage[main]/Monit/File[/etc/default/monit]: Skipping because
of failed dependencies
notice: /Stage[main]/Monit/File[/etc/monit/monitrc]: Dependency
Package[monit] has failures: true
warning: /Stage[main]/Monit/File[/etc/monit/monitrc]: Skipping because
of failed dependencies
notice: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Dependency
Package[monit] has failures: true
warning: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Skipping
because of failed dependencies
notice: /Stage[main]/Monit/Service[monit]: Dependency Package[monit]
has failures: true
warning: /Stage[main]/Monit/Service[monit]: Skipping because of failed
dependencies
err: /Stage[main]/Etc/Package[git-doc]/ensure: change from purged to
present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install git-doc'' returned 100: W: Not
using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Etc/Package[libcurl4-gnutls-dev]/ensure: change from
purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install libcurl4-gnutls-dev'' returned
100: W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Dev/Exec[apt-get -y update]/returns: change from
notrun to 0 failed: /usr/bin/apt-get -y update returned 100 instead of
one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:62
err: /Stage[main]/Dev/Exec[apt-get -y make]/returns: change from
notrun to 0 failed: /usr/bin/apt-get -r make upgrade returned 100
instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:70
err: /Stage[main]/Dev/Exec[apt-get -y upgrade]/returns: change from
notrun to 0 failed: /usr/bin/apt-get -y upgrade returned 100 instead
of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:66
err: /Stage[main]/Nginx/Package[nginx]/ensure: change from purged to
present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install nginx'' returned 100: W: Not
using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
notice: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]: Dependency
Package[nginx] has failures: true
warning: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]: Skipping
because of failed dependencies
notice: /Stage[main]/Nginx/Service[nginx]: Dependency Package[nginx]
has failures: true
warning: /Stage[main]/Nginx/Service[nginx]: Skipping because of failed
dependencies
notice: /Stage[main]/Nginx/File[/etc/logrotate.d/nginx]: Dependency
Package[nginx] has failures: true
warning: /Stage[main]/Nginx/File[/etc/logrotate.d/nginx]: Skipping
because of failed dependencies
notice: /Stage[main]/Nginx/File[/etc/nginx/mime.types]: Dependency
Package[nginx] has failures: true
warning: /Stage[main]/Nginx/File[/etc/nginx/mime.types]: Skipping
because of failed dependencies
err: /Stage[main]/Etc/Package[git-core]/ensure: change from purged to
present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install git-core'' returned 100: W: Not
using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
notice: /Stage[main]/Nginx/File[/etc/nginx/sites-enabled/default]:
Dependency Package[nginx] has failures: true
warning: /Stage[main]/Nginx/File[/etc/nginx/sites-enabled/default]:
Skipping because of failed dependencies
err: /Stage[main]/Python::Dev/Package[python-dev]/ensure: change from
purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install python-dev'' returned 100: W:
Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: /Stage[main]/Etc/Package[libxslt-dev]/ensure: change from purged
to present failed: Execution of ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install libxslt-dev'' returned 100: W:
Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run ''sudo dpkg --configure
-a'' to correct the problem.
err: Failed to apply catalog: Read-only file system -
/var/lib/puppet/state/state.yaml
err: Could not save last run local report: Read-only file system -
/var/lib/puppet/state/last_run_summary.yaml
err: /File[/var/lib/puppet/rrd]/ensure: change from absent to
directory failed: Could not set ''directory on ensure: Read-only file
system - /var/lib/puppet/rrd
err: Could not send report: Got 1 failure(s) while initializing:
change from absent to directory failed: Could not set ''directory on
ensure: Read-only file system - /var/lib/puppet/rrd
The line 15 is ensure => installed
class etc {
package {
["python-psycopg2", "git-core",
"build-essential", "git-doc",
"ufw", "libcurl3-dev",
"libcurl4-gnutls-dev", "libxslt-dev",
"curl", "libxml2-dev" ]:
ensure => installed;
}
}
class dev {
exec { ''apt-get -y update'':
command => ''/usr/bin/apt-get -y update''
}
exec { ''apt-get -y upgrade'':
command => ''/usr/bin/apt-get -y upgrade''
}
exec { ''apt-get -y make'':
command => ''/usr/bin/apt-get -r make upgrade''
}
class {
etc: ;
}
}
Any suggestions?
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Denmat
2012-Feb-16 19:28 UTC
Re: [Puppet Users] Could not set present on ensure: Read-only file system
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:15Try doing a remount on / with rw. Also check if you can do a manual install of the package once you confirm you can right to the file system. On 17/02/2012, at 6:03, Jair Gaxiola <jyr.gaxiola@gmail.com> wrote:> Hi, > > I try install python-psycopg2 with other packages, when run apt-get -y > update returns the errors: > > err: /Stage[main]/Etc/Package[build-essential]/ensure: 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 > > err: /Stage[main]/Etc/Package[python-psycopg2]/ensure: change from > purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install python-psycopg2'' returned 100: > W: Not using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Python::Gunicorn/File[/var/log/gunicorn]/ensure: > change from absent to directory failed: Could not set ''directory on > ensure: Read-only file system - /var/log/gunicorn at > /tmp/vagrant-puppet/modules-0/python/manifests/gunicorn.pp:11 > > notice: /Stage[main]/Python::Gunicorn/File[/var/run/gunicorn]/ensure: created > > err: /Stage[main]/Python::Venv/Package[python-virtualenv]/ensure: > change from purged to present failed: Execution of ''/usr/bin/apt-get > -q -y -o DPkg::Options::=--force-confold install python-virtualenv'' > returned 100: W: Not using locking for read only lock file > /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Group[puppet]/ensure: change from absent to present failed: > Could not create group puppet: Execution of ''/usr/sbin/groupadd > puppet'' returned 1: > > err: /Stage[main]/Etc/Package[libcurl3-dev]/ensure: change from purged > to present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install libcurl3-dev'' returned 100: W: > Not using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Etc/Package[curl]/ensure: change from purged to > present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install curl'' returned 100: W: Not > using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Monit/Package[monit]/ensure: change from purged to > present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install monit'' returned 100: W: Not > using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > notice: /Stage[main]/Monit/File[/etc/default/monit]: Dependency > Package[monit] has failures: true > > warning: /Stage[main]/Monit/File[/etc/default/monit]: Skipping because > of failed dependencies > > notice: /Stage[main]/Monit/File[/etc/monit/monitrc]: Dependency > Package[monit] has failures: true > > warning: /Stage[main]/Monit/File[/etc/monit/monitrc]: Skipping because > of failed dependencies > > notice: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Dependency > Package[monit] has failures: true > > warning: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Skipping > because of failed dependencies > > notice: /Stage[main]/Monit/Service[monit]: Dependency Package[monit] > has failures: true > > warning: /Stage[main]/Monit/Service[monit]: Skipping because of failed > dependencies > > err: /Stage[main]/Etc/Package[git-doc]/ensure: change from purged to > present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install git-doc'' returned 100: W: Not > using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Etc/Package[libcurl4-gnutls-dev]/ensure: change from > purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install libcurl4-gnutls-dev'' returned > 100: W: Not using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Dev/Exec[apt-get -y update]/returns: change from > notrun to 0 failed: /usr/bin/apt-get -y update returned 100 instead of > one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:62 > > err: /Stage[main]/Dev/Exec[apt-get -y make]/returns: change from > notrun to 0 failed: /usr/bin/apt-get -r make upgrade returned 100 > instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:70 > > err: /Stage[main]/Dev/Exec[apt-get -y upgrade]/returns: change from > notrun to 0 failed: /usr/bin/apt-get -y upgrade returned 100 instead > of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:66 > > err: /Stage[main]/Nginx/Package[nginx]/ensure: change from purged to > present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install nginx'' returned 100: W: Not > using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > notice: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]: Dependency > Package[nginx] has failures: true > > warning: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]: Skipping > because of failed dependencies > > notice: /Stage[main]/Nginx/Service[nginx]: Dependency Package[nginx] > has failures: true > > warning: /Stage[main]/Nginx/Service[nginx]: Skipping because of failed > dependencies > > notice: /Stage[main]/Nginx/File[/etc/logrotate.d/nginx]: Dependency > Package[nginx] has failures: true > > warning: /Stage[main]/Nginx/File[/etc/logrotate.d/nginx]: Skipping > because of failed dependencies > > notice: /Stage[main]/Nginx/File[/etc/nginx/mime.types]: Dependency > Package[nginx] has failures: true > > warning: /Stage[main]/Nginx/File[/etc/nginx/mime.types]: Skipping > because of failed dependencies > > err: /Stage[main]/Etc/Package[git-core]/ensure: change from purged to > present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install git-core'' returned 100: W: Not > using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > notice: /Stage[main]/Nginx/File[/etc/nginx/sites-enabled/default]: > Dependency Package[nginx] has failures: true > > warning: /Stage[main]/Nginx/File[/etc/nginx/sites-enabled/default]: > Skipping because of failed dependencies > > err: /Stage[main]/Python::Dev/Package[python-dev]/ensure: change from > purged to present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install python-dev'' returned 100: W: > Not using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: /Stage[main]/Etc/Package[libxslt-dev]/ensure: change from purged > to present failed: Execution of ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install libxslt-dev'' returned 100: W: > Not using locking for read only lock file /var/lib/dpkg/lock > E: dpkg was interrupted, you must manually run ''sudo dpkg --configure > -a'' to correct the problem. > > > err: Failed to apply catalog: Read-only file system - > /var/lib/puppet/state/state.yaml > > err: Could not save last run local report: Read-only file system - > /var/lib/puppet/state/last_run_summary.yaml > > err: /File[/var/lib/puppet/rrd]/ensure: change from absent to > directory failed: Could not set ''directory on ensure: Read-only file > system - /var/lib/puppet/rrd > > err: Could not send report: Got 1 failure(s) while initializing: > change from absent to directory failed: Could not set ''directory on > ensure: Read-only file system - /var/lib/puppet/rrd > > The line 15 is ensure => installed > > class etc { > package { > ["python-psycopg2", "git-core", "build-essential", "git-doc", > "ufw", "libcurl3-dev", > "libcurl4-gnutls-dev", "libxslt-dev", "curl", "libxml2-dev" ]: > ensure => installed; > } > } > > class dev { > exec { ''apt-get -y update'': > command => ''/usr/bin/apt-get -y update'' > } > > exec { ''apt-get -y upgrade'': > command => ''/usr/bin/apt-get -y upgrade'' > } > > exec { ''apt-get -y make'': > command => ''/usr/bin/apt-get -r make upgrade'' > } > class { > etc: ; > } > } > > > Any suggestions? > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Jair Gaxiola
2012-Feb-16 20:14 UTC
Re: [Puppet Users] Could not set present on ensure: Read-only file system
On Thu, Feb 16, 2012 at 1:28 PM, Denmat <tu2bgone@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:15I 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 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jcbollinger
2012-Feb-17 13:55 UTC
[Puppet Users] Re: Could not set present on ensure: Read-only file system
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 systemYou 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Jair Gaxiola
2012-Feb-17 17:01 UTC
Re: [Puppet Users] Re: Could not set present on ensure: Read-only file system
Is work with run apt-get update first. Thanks a lot. On Fri, Feb 17, 2012 at 7:55 AM, jcbollinger <John.Bollinger@stjude.org> wrote:> > > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- SIN ETIQUETAS.[ PUNTO ] http://flavors.me/jyr http://pythoncocoa.com http://opentumblr.com -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.