Reference taken from this Article ! Script to Create Read-Only user: CREATE ROLE Read_Only_User WITH LOGIN PASSWORD ‘Test1234’ NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION VALID UNTIL ‘infinity’; Assign permission to this read only user: GRANT CONNECT ON DATABASE YourDatabaseName TO Read_Only_User; GRANT USAGE ON SCHEMA public TO Read_Only_User; GRANT SELECT ON ALL TABLES IN SCHEMA public … Read more
[26729.124569] Write(10): 2a 00 03 96 5a b0 00 00 08 00 [26729.124576] end_request: I/O error, dev sda, sector 60185264 [26729.125298] Buffer I/O error on device sda2, logical block 4593494 [26729.125986] lost page write due to I/O error on sda2 For me, that’s pretty strong evidence that your /dev/sda is on its way out. You … Read more
Those permissions should be all that’s needed for the mysqldump. Since you’ve granted LOCK TABLES, and it’s erroring on LOCK TABLES, seems like the permissions are inconsistent. Have you run a FLUSH PRIVILEGES?
I just recently ran into this problem and solved it by rebooting but after further investigation it appears that issuing the following command might fix it. echo running > /sys/block/device-name/device/state I think you might want to look at look at section 25.14.4: Changing the Read/Write State of an Online Logical Unit in this document, however, … Read more
‘Read-only file system’ error indicates that the file system is exported as read only. The rw mount option tells client that ‘WRITE’ is allowed to be sent to the server. On regular unix systems, check /etc/exports file: /NFS2 172.x.y.z(rw) on appliances, check the documentation to export as read-write.