DBC:Errors/DBC-E005: Difference between revisions
Jump to navigation
Jump to search
Page 
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:DBCollect]] | |||
{{error | [DBC-E005] IOerror retrieving <file>: <message>}} | {{error | [DBC-E005] IOerror retrieving <file>: <message>}} | ||
| Line 12: | Line 13: | ||
If these files are 'pseudo' files (such as in /sys, /proc etc) the permissions will be reset to normal at the first reboot. | If these files are 'pseudo' files (such as in /sys, /proc etc) the permissions will be reset to normal at the first reboot. | ||
{{PrevNext|DBC:Errors/DBC-E004|DBC:Errors/DBC-E006}} | |||
Latest revision as of 15:31, 10 October 2024
[DBC-E005] IOerror retrieving <file>: <message>
This happens if DBcollect cannot read a file as part of the collected data.
It is related to DBC:Errors/DBC-E004 depending on the Python version.
Solution:
Some systems have non-standard security policies, preventing dbcollect to read these files. It may be undesirable to change the permissions with chmod. In these cases you can use file access control lists to set an ACL permission without changing the basic permissions.
The command is setfacl -m u:oracle:- <file(s)> - assuming the database user under which dbcollect runs is oracle.
If these files are 'pseudo' files (such as in /sys, /proc etc) the permissions will be reset to normal at the first reboot.
Page