I have a user who ran smack into a wall with the Job Composer. It’s the very same issue as this old link from 5 years ago… OOD 1.7.0 Job Composer issue - corrupted SQLite3 database? .
I did remove the database and the page blew up on him, attaching picture below. I’ve dug through the logs, I cycled his nginx_pun, I can’t get him back into the composer.
I hope y’all have some advice for me :).See you in two weeks? GRIN
Sincerely Kenny Hanson
Yea I/O disk error is pretty generic. I’d maybe try to copy the db file and interact with it through the sqlite3 command to see if you can replicate on the CLI.
Beyond that - maybe it’s a drive issue? Maybe just bad luck hitting some bad NFS blocks? In any case, your remediation of removing the file is the right way to go. Or perhaps you can pull a backup from last week/before this starting happening?
Oh boy, if it’s a disk error… I personally think people just don’t close out of their browsers properly. I’ve been warning them for years. Should I just have sqlite3 create the file if I can’t rebuild it?
Thanks Jeff! Kenny
No I don’t think you want to create this file by hand.
