Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: SQLITE_ERROR since v24.12 #548

Open
1 task done
bladecell opened this issue Jan 10, 2025 · 5 comments
Open
1 task done

[Bug]: SQLITE_ERROR since v24.12 #548

bladecell opened this issue Jan 10, 2025 · 5 comments
Labels
bug Something isn't working

Comments

@bladecell
Copy link

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Hey I am running this service on UNRAID for more than a year and started getting SQLITE_ERROR when starting container, which fails. The error is present on version 24.12 and 25.1., I can start the version 24.11. without any issue.

What error did you receive?

Checking if there are any migrations to run for direction "up"...

/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9
        this[cppdb].exec(sql);
                    ^
SqliteError: no such column: password
    at Database.exec (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9:14)
    at WrappedDatabase.exec (file:///app/src/db.js:30:20)
    at Migration.up (file:///app/migrations/1718889148000-openid.js:4:24)
    at next (/app/node_modules/migrate/lib/migrate.js:35:45)
    at /app/node_modules/migrate/lib/migrate.js:71:9
    at /app/node_modules/migrate/lib/set.js:84:5
    at FSReqCallback.oncomplete (node:fs:192:23) {
  code: 'SQLITE_ERROR'
}

Node.js v18.20.5
Checking if there are any migrations to run for direction "up"...

/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9
        this[cppdb].exec(sql);
                    ^
SqliteError: no such column: password
    at Database.exec (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9:14)
    at WrappedDatabase.exec (file:///app/src/db.js:30:20)
    at Migration.up (file:///app/migrations/1718889148000-openid.js:4:24)
    at next (/app/node_modules/migrate/lib/migrate.js:35:45)
    at migrate (/app/node_modules/migrate/lib/migrate.js:76:3)
    at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3)
    at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8)
    at file:///app/src/migrations.js:23:23
    at /app/node_modules/migrate/index.js:62:5
    at /app/node_modules/migrate/lib/load-migrations.js:97:7 {
  code: 'SQLITE_ERROR'
}

Node.js v18.20.5
Checking if there are any migrations to run for direction "up"...

/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9
        this[cppdb].exec(sql);
                    ^
SqliteError: no such column: password
    at Database.exec (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9:14)
    at WrappedDatabase.exec (file:///app/src/db.js:30:20)
    at Migration.up (file:///app/migrations/1718889148000-openid.js:4:24)
    at next (/app/node_modules/migrate/lib/migrate.js:35:45)
    at migrate (/app/node_modules/migrate/lib/migrate.js:76:3)
    at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3)
    at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8)
    at file:///app/src/migrations.js:23:23
    at /app/node_modules/migrate/index.js:62:5
    at /app/node_modules/migrate/lib/load-migrations.js:97:7 {
  code: 'SQLITE_ERROR'
}

Node.js v18.20.5

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

@bladecell bladecell added the bug Something isn't working label Jan 10, 2025
@bladecell bladecell changed the title [Bug]: SQLITE_ERROR from v24.12 [Bug]: SQLITE_ERROR since v24.12 Jan 10, 2025
@Epitaffio
Copy link

Same here

@TheQuickestFox
Copy link

Also experiencing this issue.

@TheQuickestFox
Copy link

Small progress:

I did manage to get it to boot on 25.1 (from a clean database, so without my data) when I enforced that all files were on /mnt/cache/appdata instead of /mnt/user/appdata.

I don't currently have the time to mess about forcing a copy of my database/user data over to cache to continue testing. But I wonder if this is a permissions issue for the array?

@Ijackedupmycode
Copy link

Same issue,
hosting on unraid
downgraded now im locked out

@elephantgrenades
Copy link

This issue is covered in #521. I'm on unraid and followed the fix within - all's good again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants