Bug 1341008

Summary: Error: Unable to open database for writing: Permission denied
Product: [Fedora] Fedora EPEL Reporter: Mohamed Magdy <s3cur1ty1>
Component: vnstatAssignee: Adrian Reber <adrian>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: el6CC: adrian, matt.castelein
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-30 14:56:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mohamed Magdy 2016-05-31 05:52:28 UTC 
This happens for every installation, the database files deployed as root but it must be deployed as vnstat user, the fix would be

chown vnstat: /var/lib/vnstat/*

OS: CentOS 6 & 7
Comment 1 Matt Castelein 2018-08-08 14:46:57 UTC 
Same here, EL7.
Comment 2 Ben Cotton 2020-11-05 16:47:32 UTC 
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Comment 3 Matt Castelein 2020-11-06 15:08:12 UTC 
Looks like this is fixed in EPEL8.
Comment 4 Ben Cotton 2020-11-30 14:56:44 UTC 
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 5 JensonRoya 2023-12-19 11:20:33 UTC Comment hidden (spam)