jatpat / phpliteadmin

Automatically exported from code.google.com/p/phpliteadmin
0 stars 0 forks source link

Database is locked #256

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Won't let me add, delete or update a row in the database. 

What is the expected output? What do you see instead?
It should correctly add, edit or delete that specific row. 

What version of the product are you using? On what operating system? Which
Database Extension (PDO/SQLiteDatabase/SQLiteDatabase3 - see Database
structure-tab in phpLiteAdmin)?
PDO

Please provide any additional information below.

Original issue reported on code.google.com by rosemary...@gmail.com on 4 Jul 2014 at 8:52

GoogleCodeExporter commented 9 years ago
Do you get any error message? Does the tab on the left say [r] or [rw] next to 
your database?

Is the database file writeable? Have you checked the rights of the file? Tried 
chmod 777 or chown www-data:www-data?

Original comment by crazy4ch...@gmail.com on 4 Jul 2014 at 10:41

GoogleCodeExporter commented 9 years ago
It says [rw] next to my database. 

Original comment by rosemary...@gmail.com on 7 Jul 2014 at 5:08

GoogleCodeExporter commented 9 years ago
I was able to fix the issue by exporting the contents of the database, deleting 
it and the recreating, importing. No system file permissions were changed.

Original comment by straterp...@gmail.com on 7 Jul 2014 at 5:17

GoogleCodeExporter commented 9 years ago
Was there any error message before when you tried to change the database?
Perhaps some other program opened the DB, got a lock and crashed without 
unlocking the DB?

Original comment by crazy4ch...@gmail.com on 7 Jul 2014 at 5:20

GoogleCodeExporter commented 9 years ago
There isn't another program accessing that file and I even tried rebooting 
apache to clear the lock with no success. The only error was that the DB was 
locked.

Original comment by straterp...@gmail.com on 7 Jul 2014 at 5:30

GoogleCodeExporter commented 9 years ago
I don't know how I could reproduce this and I think it is rather a problem of a 
db in a corrupted state than a problem of phpLiteAdmin.
Therefore closing the issue.

Original comment by crazy4ch...@gmail.com on 27 Dec 2014 at 11:28