I'm trying to create a new app with Meteor (this is the first time I've used it on this computer).
When I try and start a new app:
meteor create simple-todos
I'm getting the following error and creating the app fails:
{ [Error: SQLITE_CANTOPEN: unable to open database file]
stack: [Getter] }
And below that I get some other errors:
Error: SQLITE_CANTOPEN: unable to open database file
at Object.Future.wait (/Users/Jack/.meteor/packages/meteor-tool/.1.1.4.2l3p0l++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
I can't find other people having this same issue, so I'm a bit in the dark as to how to debug or fix. Pointers as to how to debug / fix this would be really helpful.
It may be a permission error.
In order to fix this issue, you could try to adjust the permission by running this command:
sudo chown -R $USER ~/.meteor
Related
I am trying to run the collection-examples-as near example but when I run yarn deploy it gives me the following error
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: ENOENT: no such file or directory, open './contract.wasm'
[Error: ENOENT: no such file or directory, open './contract.wasm'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './contract.wasm'
}
error Command failed with exit code 1.
I think the error is it can't find the path to ./contract.wasm so I run yarn build the I tried to deploy it again using yarn deploy but I got another error which is:
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: Can not sign transactions for account dev-1637744501224-6323200 on network
default, no matching key pair found in
InMemorySigner(MergeKeyStore(UnencryptedFileSystemKeyStore(/home/rasha/.near-
credentials), UnencryptedFileSystemKeyStore(/home/rasha/collection-examples-
as/neardev))).
{
type: 'KeyNotFound',
context: undefined
}
any help or suggestions?
There's an issue with old versions of near-cli and dev-deploy.
As a workaround, you can try running the latest cli directly from your terminal:
near dev-deploy --wasmFile="./contract.wasm" -f
Just check that you installed the latest version of near-cli, currently 2.2.0. You can check your version with near --version.
Be sure to run yarn build first, so you'll have the compiled contract.wasm file.
Note: When you run yarn deploy, it uses the old near-cli version defined in package.json. (probably some old version like 1.6.0)
You might also want to check this GitHub issue (dev-deploy error): https://github.com/near/create-near-app/issues/1408
I have implemented it in my local and works well. But when I moved the changes to the window server it's giving the below error
Failed to launch Base! [0402/075840.212:ERROR:os_crypt_win.cc(70)] Failed to encrypt: The system cannot find the file specified. (0x2)\r\n[0402/075840.212:FATAL:headless_browser_main_parts.cc(103)] Check failed: OSCrypt::Init(local_state_.get()). \r\nBacktrace:\r\n\tIsSandboxedProcess [0x00007FFC31341842+705042]\r\n\tIsSandboxedProcess [0x00007FFC312C39A2+189298]\r\n\tIsSandboxedProcess [0x00007FFC312D2AF8+251080]\r\n\tIsSandboxedProcess [0x00007FFC312D39E0+254896]\r\n\tRelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFC32B12123+12980755]\r\n\tRelaunchChromeBrowserWithNewCommandLineIfNeeded [0x00007FFC32B11E8D+12980093]\r\n\tovly_debug_event [0x00007FFC2F905929+16331561]\r\n\tovly_debug_event [0x00007FFC2FCC5B17+20264215]\r\n\tovly_debug_event [0x00007FFC2F904675+16326773]\r\n\tovly_debug_event [0x00007FFC2F9073BE+16338366]\r\n\tIsSandboxedProcess [0x00007FFC31DB7DB7+11675527]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC3125A837+8179991]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC3125B5AD+8183437]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC3125B20C+8182508]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC3125A1BD+8178333]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC3125A53A+8179226]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC31294D1A+8418810]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC31294BDC+8418492]\r\n\tCrashForExceptionInNonABICompliantCodeRange [0x00007FFC312949E7+8417991]\r\n\tChromeMain [0x00007FFC2E971238+408]\r\n\tOrdinal0 [0x00007FF6E8CF26B8+9912]\r\n\tOrdinal0 [0x00007FF6E8CF1A41+6721]\r\n\tGetHandleVerifier [0x00007FF6E8E3AF42+904642]\r\n\tBaseThreadInitThunk [0x00007FFC68F113F2+34]\r\n\tRtlUserThreadStart [0x00007FFC6AB054F4+52]\r\n\r\n
Can anyone please advise what should be the fix for the above error message?
We had the same error with default browser:
Failed to launch browser! [0428/113352.960:ERROR:os_crypt_win.cc(70)] Failed to encrypt
As #hardkoded suggested, using the revision 851527 we could launch the browser. Thank you!
When I trying to upgrade my application error occurs.enter image description here
What is the Solution for it ??
I can't able to fix this error .
Plz give me the solution ...
Please, make sure that:
The user 'odoo' is the owner of your DB. In any case:
ALTER DATABASE <db_name> OWNER TO odoo;
You have all the dependencies installed, in particular less. In any case:
sudo npm install -g less less-plugin-clean-css
i want to add a user conversation function in my app, but i am having problems installing the talk functionality. i have downloaded the project from github, but i was unable to use it because of this two errors
Warning: require(C:\xampp\htdocs\tok\bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in C:\xampp\htdocs\tok\bootstrap\autoload.php on line 17
Fatal error: require(): Failed opening required 'C:\xampp\htdocs\tok\bootstrap/../vendor/autoload.php' (include_path='C:\xampp\php\PEAR') in C:\xampp\htdocs\tok\bootstrap\autoload.php on line 17. is there a way out of???
does anyone know how use the talk functionality by nahid??
You just need to run the following in the project folder:
Composer Install
Here is a question with a similar issue that might help you get to the root cause: (possible duplicate question)
Laravel 5 Failed opening required bootstrap/../vendor/autoload.php
I'm trying to get my meteor app up and running, but I don't understand the error that its throwing at all, which is:
/Users/ten3/.meteor/packages/meteor- tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
throw(ex);
^
Error: EACCES, unlink '/Users/ten3/Desktop/git/ten/website/prospect-recovery/prospect-recovery/.meteor/local/db/mongod.lock'
at Object.Future.wait (/Users/ten3/.meteor/packages/meteor-tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
at /tools/fs/files.js:1331:28
at Object.wrapper [as unlink] (/tools/fs/files.js:1334:20)
at findMongoAndKillItDead (/tools/runners/run-mongo.js:318:11)
at launchOneMongoAndWaitForReadyForInitiate (/tools/runners/run-mongo.js:400:7)
at launchMongo (/tools/runners/run-mongo.js:656:7)
at [object Object]._.extend._startOrRestart (/tools/runners/run-mongo.js:756:19)
at [object Object]._.extend.start (/tools/runners/run-mongo.js:714:10)
at /tools/runners/run-all.js:168:26
- - - - -
I'm running a shell script before I try to run a local copy of my meteor app. It supposed to stop my application from interacting with other APIs. When I run the script (I'm on a mac) through my terminal, it returns '0' which as I read means that there are zero errors. I know that the error message is guiding me to certain lines of code, but I don't understand why I would change them if my co-worker could get his copy up and running. He is running his application on a windows computer. Thank you. I'm pretty new to this.
It was a permission error just as #thatgibbyguy first suggested. I was able to run it buy using sudo meteor to override the permission restrictions. I wasn't about to remove my mongod.lock file since that my coworker had the file and was able to get it up and running.