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

Error: Could not locate the bindings file. #19

Closed
1Dilva opened this issue Feb 1, 2023 · 7 comments
Closed

Error: Could not locate the bindings file. #19

1Dilva opened this issue Feb 1, 2023 · 7 comments
Assignees
Labels
type: bug Something isn't working

Comments

@1Dilva
Copy link

1Dilva commented Feb 1, 2023

Hey, running this on a Pebblehost service. The bot worked ONCE then it never worked again I reset files deleted everything reinstalled no hope I was hoping to get some help here. Console vvvv I also contacted them and they said "we don't support SQLite" but that makes no sense because the bot worked once and there should be a fix around it. I hope you are still active here and I hope I get some help thanks


01.02 09:36:01 [Bot] /Bot3/node_modules/bindings/bindings.js:135
01.02 09:36:01 [Bot] throw err;
01.02 09:36:01 [Bot] ^
01.02 09:36:01 [Bot] Error: Could not locate the bindings file. Tried:
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/build/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/build/Debug/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/build/Release/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/out/Debug/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/Debug/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/out/Release/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/Release/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/build/default/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/compiled/16.17.0/linux/x64/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node
01.02 09:36:01 [Bot] → /Bot3/node_modules/better-sqlite3/lib/binding/node-v93-linux-x64/better_sqlite3.node
01.02 09:36:01 [Bot] at bindings (/Bot3/node_modules/bindings/bindings.js:126:9)
01.02 09:36:01 [Bot] at new Database (/Bot3/node_modules/better-sqlite3/lib/database.js:48:64)
01.02 09:36:01 [Bot] at Object. (/Bot3/node_modules/quick.db/src/index.js:7:15)
01.02 09:36:01 [Bot] at Module._compile (node:internal/modules/cjs/loader:1126:14)
01.02 09:36:01 [Bot] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
01.02 09:36:01 [Bot] at Module.load (node:internal/modules/cjs/loader:1004:32)
01.02 09:36:01 [Bot] at Function.Module._load (node:internal/modules/cjs/loader:839:12)
01.02 09:36:01 [Bot] at Module.require (node:internal/modules/cjs/loader:1028:19)
01.02 09:36:01 [Bot] at require (node:internal/modules/cjs/helpers:102:18)
01.02 09:36:01 [Bot] at Object. (/Bot3/node_modules/quick.db/index.js:7:18) {
01.02 09:36:01 [Bot] tries: [
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/build/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/build/Debug/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/build/Release/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/out/Debug/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/Debug/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/out/Release/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/Release/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/build/default/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/compiled/16.17.0/linux/x64/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node',
01.02 09:36:01 [Bot] '/Bot3/node_modules/better-sqlite3/lib/binding/node-v93-linux-x64/better_sqlite3.node'
01.02 09:36:01 [Bot] ]
01.02 09:36:01 [Bot] }
01.02 09:36:01 [PebbleHost Loader] File ./Bot3/index.js stopped

@PetyXbron
Copy link
Owner

Check yours quick.db version with the command npm list quick.db.
Downgrading quick.db to 7.1.3 should fix the issue.
You can use this console command when the process is off: npm i [email protected] --save --save-exact

@PetyXbron
Copy link
Owner

Also, did you run the command npm install before running the project?

@1Dilva
Copy link
Author

1Dilva commented Feb 1, 2023

The quick.db version is already 7.1.3 and yes I have run the npm install command

@PetyXbron
Copy link
Owner

Yeah, it worked once because the first run of the bot does not require SQLite, then it needs.
SQLite is a solution for saving the message ID of statusCH. As the Console vvvv (Pebblehost service?) support said, they are not supporting SQLite and that, unfortunately, you cannot use the statusCH feature.
I will try to find another solution for saving the message ID of statusCH.

@PetyXbron
Copy link
Owner

Also, I would suggest that you consider using another hosting service.

@1Dilva
Copy link
Author

1Dilva commented Feb 1, 2023

No it worked the first time like everything was fine on the test server then I had to move it to the main server it started bugging so I deleted the files and installed everything again and that's when it all started breaking. But I mean it's all good is there another way I can save msg id of statusCH without sqlite? the service has MySQL. And I can't exactly switch services either I have always been with them and I have 2 other bots running currently on the service. If you are able to help me make the statusCH work another way that would be great if not it's all good I can figure something else out

@1Dilva
Copy link
Author

1Dilva commented Feb 1, 2023

by first time I mean like I was able to restart the bot multiple times changing configs and everything then the second I reset the files so it can work on the other server it broke

@PetyXbron PetyXbron self-assigned this Apr 10, 2023
@PetyXbron PetyXbron added the type: bug Something isn't working label Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants