Issue with Job Composer

Get Help
1

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

image
image671×1150 83.1 KB

Sincerely Kenny Hanson

2

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?

3

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

4

No I don’t think you want to create this file by hand.

5

Hi Jeff, I’m sorry but what do you recommend we do? It seems anything I do crashes the Job Composer. I can save his folders, would deleting his ondemand/* reset his current account and have all new files created?

Kenny

6

Really it’s only that production.sqlite3 file that you need to delete. Wiping the entire directory is a bit overkill - but is an option if you like.

Additionally, there could be something in journalctl, dmesg or from your NFS logs to indicate why that file specifically is unreachable.

7

Deleting that file crashes the job composer.

8

Sorry! I think this is the process you want to follow.

  1. Delete that file
  2. restart the web server (in the help menu)
  3. navigate back to the job composer through the nav bar entry (don’t go directly there)
9

Hi Jeff, I had to wipe out his entire $HOME/ondemand/* folder. He only used Job Composer so I archived that stuff so he could retrieve his 15 scripts or so. Removing just the myjobs on down still crashed the app. It’s working again now :slight_smile:

kENNY