H
Homarr4w ago
Edo

Issue trying to install with Helm

After installing Homarr using the traditional method, I get the following error in my deployment:
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
/app/migrate/node_modules/better-sqlite3/lib/database.js:65
throw new TypeError('Cannot open database because the directory does not exist');
^
TypeError: Cannot open database because the directory does not exist
at new Database (/app/migrate/node_modules/better-sqlite3/lib/database.js:65:9)
at Object.<anonymous> (/app/migrate/migrate.ts:12:16)
at Module._compile (node:internal/modules/cjs/loader:1255:14)
at Module.m._compile (/app/migrate/node_modules/ts-node/src/index.ts:1618:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
at Object.require.extensions.<computed> [as .ts] (/app/migrate/node_modules/ts-node/src/index.ts:1621:12)
at Module.load (node:internal/modules/cjs/loader:1113:32)
at Function.Module._load (node:internal/modules/cjs/loader:960:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at phase4 (/app/migrate/node_modules/ts-node/src/bin.ts:649:14)
error Command failed with exit code 1.
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
/app/migrate/node_modules/better-sqlite3/lib/database.js:65
throw new TypeError('Cannot open database because the directory does not exist');
^
TypeError: Cannot open database because the directory does not exist
at new Database (/app/migrate/node_modules/better-sqlite3/lib/database.js:65:9)
at Object.<anonymous> (/app/migrate/migrate.ts:12:16)
at Module._compile (node:internal/modules/cjs/loader:1255:14)
at Module.m._compile (/app/migrate/node_modules/ts-node/src/index.ts:1618:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
at Object.require.extensions.<computed> [as .ts] (/app/migrate/node_modules/ts-node/src/index.ts:1621:12)
at Module.load (node:internal/modules/cjs/loader:1113:32)
at Function.Module._load (node:internal/modules/cjs/loader:960:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at phase4 (/app/migrate/node_modules/ts-node/src/bin.ts:649:14)
error Command failed with exit code 1.
I've tried downgrading to Homarr version 0.15.2 and no success. Any ideas? I'm also getting this error in the log:
https://next-auth.js.org/errors#client_fetch_error Unexpected token 'I', "Internal S"... is not valid JSON {
error: {
message: `Unexpected token 'I', "Internal S"... is not valid JSON`,
stack: `SyntaxError: Unexpected token 'I', "Internal S"... is not valid JSON\n` +
' at JSON.parse (<anonymous>)\n' +
' at parseJSONFromBytes (/app/node_modules/next/dist/compiled/undici/index.js:2:4905)\n' +
' at successSteps (/app/node_modules/next/dist/compiled/undici/index.js:2:4473)\n' +
' at /app/node_modules/next/dist/compiled/undici/index.js:2:65581\n' +
' at node:internal/process/task_queues:140:7\n' +
' at AsyncResource.runInAsyncScope (node:async_hooks:206:9)\n' +
' at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)\n' +
' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)',
name: 'SyntaxError'
},
url: 'http://homarr-5ccbf47785-h7xkn:7575/api/auth/session',
message: `Unexpected token 'I', "Internal S"... is not valid JSON`
}
https://next-auth.js.org/errors#client_fetch_error Unexpected token 'I', "Internal S"... is not valid JSON {
error: {
message: `Unexpected token 'I', "Internal S"... is not valid JSON`,
stack: `SyntaxError: Unexpected token 'I', "Internal S"... is not valid JSON\n` +
' at JSON.parse (<anonymous>)\n' +
' at parseJSONFromBytes (/app/node_modules/next/dist/compiled/undici/index.js:2:4905)\n' +
' at successSteps (/app/node_modules/next/dist/compiled/undici/index.js:2:4473)\n' +
' at /app/node_modules/next/dist/compiled/undici/index.js:2:65581\n' +
' at node:internal/process/task_queues:140:7\n' +
' at AsyncResource.runInAsyncScope (node:async_hooks:206:9)\n' +
' at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)\n' +
' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)',
name: 'SyntaxError'
},
url: 'http://homarr-5ccbf47785-h7xkn:7575/api/auth/session',
message: `Unexpected token 'I', "Internal S"... is not valid JSON`
}
Thank you.
Solution:
Use this command with this file : helm upgrade homarr oben01/homarr --namespace homarr --create-namespace --values=values.yaml...
Jump to solution
21 Replies
Cakey Bot
Cakey Bot4w ago
Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
odah
odah4w ago
Hello @Edo could u please provide your values files ? which chart are u using ?
Edo
EdoOP4w ago
Hi. I’m using all the defaults provided in oben01/homarr
odah
odah4w ago
Could u please provide the values files?!
Edo
EdoOP4w ago
Sorry, i’m new to Helm. I’m not using any custom parameters. I’m just using the default install from the repo. Could you explain?
odah
odah4w ago
Which command are u running ?!
Edo
EdoOP4w ago
helm repo add oben01 https://oben01.github.io/charts/ helm repo update helm install homarr oben01/homarr
oben01 Helm Charts
A collection of Helm charts.
odah
odah4w ago
What’s the output of this command : Kubectl get storageclass
Edo
EdoOP4w ago
Give me 10-15 min, let me access my cluster
❯ k get storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 8d
❯ k get storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 8d
Could it be the volume expansion being set to false?
odah
odah4w ago
I’ll send u all the needed command i’ll get to u in 1hour
Solution
odah
odah4w ago
Use this command with this file : helm upgrade homarr oben01/homarr --namespace homarr --create-namespace --values=values.yaml
Edo
EdoOP4w ago
That worked! Thank you!! Can you explain how providing these values fixed it?
odah
odah4w ago
Database need a mounted volume to be working Good news could u please mark your question as solved please 🙂
Edo
EdoOP4w ago
I thought that installing from the default values.yaml provides this for us
odah
odah4w ago
it is not enabled by default
Edo
EdoOP4w ago
so when we do the helm install command without providing any parameters, it does not use this file by default? https://github.com/oben01/charts/blob/main/charts/homarr/values.yaml
GitHub
charts/charts/homarr/values.yaml at main · oben01/charts
Contribute to oben01/charts development by creating an account on GitHub.
odah
odah4w ago
https://github.com/oben01/charts/blob/main/charts/homarr/values.yaml#L160 the values that u provided in the helm command will override only the persitence section which create a pvc to hold data permanently
GitHub
charts/charts/homarr/values.yaml at main · oben01/charts
Contribute to oben01/charts development by creating an account on GitHub.
Edo
EdoOP4w ago
ohhh, the default values are false, so you changed it to true, correct?
odah
odah4w ago
Yes
Edo
EdoOP4w ago
thank you, i'm still learning haha. i appreciate the explanation
odah
odah4w ago
u welcome. Happy helming
Want results from more Discord servers?
Add your server