RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 947149 - logrotate.status: Read-only file system error: could not read state file, will not attempt to write into it.
Summary: logrotate.status: Read-only file system error: could not read state file, wil...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: All
OS: All
unspecified
urgent
Target Milestone: rc
: 6.5
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-01 18:35 UTC by Douglas Schilling Landgraf
Modified: 2014-01-21 19:30 UTC (History)
17 users (show)

Fixed In Version: ovirt-node-3.0.1-2.el6
Doc Type: Bug Fix
Doc Text:
When trying to rotate files manually, an error was generated on logrotate.status: # logrotate /etc/logrotate.d/vdsm error: error creating state file /var/lib/logrotate.status: Read-only file system error: could not read state file, will not attempt to write into it. A bug in the do_filp_open() function caused it to exit early if any write access was requested on a read-only file system. This prevented the opening of device nodes on a read-only file system. With this update, the do_filp_open() has been fixed to no longer exit if a write request is made on a read-only file system.
Clone Of:
Environment:
Last Closed: 2014-01-21 19:30:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC

Description Douglas Schilling Landgraf 2013-04-01 18:35:47 UTC 
Description of problem:

rhev-hypervisor-advanced-6.4-20130321.0

Tried to rotate files manually and I noticed logrotate error about logrotate.status.

# logrotate /etc/logrotate.d/vdsm
error: error creating state file /var/lib/logrotate.status: Read-only file system
error: could not read state file, will not attempt to write into it.

logrotate uses logrotate.status store information about when it last rotated each log file.
Comment 1 haiyang,dong 2013-04-02 07:09:00 UTC 
rhev-h is a read-only file system, so when executing "logrotate /etc/logrotate.d/vdsm" , it will print above error info.

workaround here:
mount -o remount, rw /
Comment 2 Mike Burns 2013-04-02 13:06:55 UTC 
I'm not sure this is as bad as it appears.  logrotate still seems to work even if this file doesn't work.

The fix should be either making the file rw (editing rwtab) or moving the file to another location that is read-write. there is a -s or --state option to specify a different state file location.
Comment 8 Cheryn Tan 2013-11-08 00:34:59 UTC 
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 9 haiyang,dong 2013-11-11 08:40:42 UTC 
Test version:
rhev-hypervisor6-6.5-20131106.0.el6ev.noarch.rpm
ovirt-node-3.0.1-7.el6.noarch
vdsm-4.13.0-0.6.beta1.el6ev.x86_64

Test steps:
1. [root@dhcp-8-136 admin]# cat /etc/rwtab |grep logrotate.status
files	/var/lib/logrotate.status
2. [root@dhcp-8-136 admin]# logrotate /etc/logrotate.d/vdsm

no error info was shown in console, so this bug has been fixed, change it into "VERIFIED".
Comment 11 errata-xmlrpc 2014-01-21 19:30:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0033.html
Note You need to log in before you can comment on or make changes to this bug.