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
Manual install of WebThings Gateway master branch on Raspberry Pi OS Bullseye does not start #3069
Comments
@GFPar thanks for reporting. Just to confirm, did you check out the v.1.2.X branch from GitHub to build this? 1.2 has not been released yet and that branch is in a bit of a strange state at the moment (behind both 1.1 and master), so may have some issues. If you want to build yourself I'd recommend you build from the 1.1.X branch, otherwise the pre-built Raspberry Pi image on the website definitely works https://webthings.io/gateway/. |
Hello - thank you for your response. Sorry for my ignorance, but where would i point to the 1.1 branch? Looking at the files that are being extracted from git, it is not obvious where i would extract 1.1 vs. 1.2 Thanks for your help! |
@GFPar OK, given you don't know how to check out the 1.2 branch I will assume you were actually using the master branch (which to be fair does also say version 1.2 in its package.json). You can find the 1.1 source code here https://github.com/WebThingsIO/gateway/tree/v1.1.X To check it out of GitHub you would run:
I'm surprised that the master branch doesn't build on a Pi 3, but it may be the newer version of Raspbian. Our latest Raspberry Pi image is still built on buster. Let me know if 1.1 builds OK for you or if you have the same problem. |
After the 'git clone .... https://....' i ran 'git checkout v1.1.X', but get the message: 'fatal: not a git repository (or any of the parent directions): .git' |
Sorry, you need to switch into the gateway directory first...
|
Hello - sorry for posting earlier, but i tried using the v1.1.x branch with the same result - inability to starting the gateway. The issue is a bit different though. Now, i cam unable set up the domain and register my email on http://localhost:8080/. I have attached the run-app.log file. To see if this was only related to a PI3, i also followed the same steps on a manual built (using the directions on https://github.com/WebThingsIO/gateway) on a Pi4 - to the same result. The gateway fails to start and i am unable to set up the domain. The attached log file is actually from the attempted Pi4 install (i tried multiple domain names and email addresses) - though i have the same issue on the Pi3. Let me know if are any other install logs that may be useful. 2023-02-04 11:50:55.813 INFO : Creating database: /home/pi/.webthings/log/logs.sqlite3 |
@GFPar This looks like a networking problem to me. Are you still having the problem? It's possible that the registration server was experiencing a DNS outage at the time because there were some outages in the past but things have improved recently. If you still get this problem, are you able to reach api.webthings.io from the command line on the pi? E.g.
Are you running in the gateway in a container of any kind? |
Hello - thanks for the response. I was able to successfully create my domain on the webthings.io. However, after rebooting my Pi and running 'npm start' i still get the error message (with the code 137) mentioned at the start of this issue. It is not run in any container. I installed following the instructions in the 'readme file' on an existing Pi (with a new install of the OS). I did this on versions 0.8 and 1.0, and never had any issues. |
OK, so it sounds like the networking problem has resolved itself. A quick web search suggests that Are there any other processes running on the Pi that you could pause while the build finishes? (running |
Thank you for your response. I was able to get the gateway to run using 'node build/app.js' I am able to add ''Add-ons' - however there looks to be an issue with sqlite3. Attached is from the internal error log on the Zigbee module: 2023-03-23 17:08:20.006 INFO : Loading add-on: zigbee-adapter When i go to the referenced directory, it is empty. Don't know if there was an issue with sqlite3 at the time of install. |
Hmm, maybe SQLite failed to compile during the build process? Do you see any errors when building with |
Thank you for the response. I ran 'npm run build'. There were no errors, just 3 warnings about asset size limits. Please see below:
Browserslist: caniuse-lite is outdated. Please run:
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB). WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance. WARNING in webpack performance recommendations: webpack 5.74.0 compiled with 3 warnings in 315117 ms asset service-worker.js 54.3 KiB [emitted] [minimized] (name: service-worker.js)
|
Hmm, looking back over the errors you're seeing, executing the build process which is run by It looks like the I suggest running |
Hello - thanks again for your attention. I re-ran 'npm cl' and do indeed see messages on missing files required for the build. I have included all the output from running that command (sorry, it is long): npm WARN prepare removing existing node_modules/ before installation
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/TryGhost/node-sqlite3/releases/download/v5.1.1/napi-v6-linux-glibc-arm.tar.gz
make: Entering directory '/home/gparise/gateway/node_modules/segfault-handler/build' ::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo ::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’: ::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo ::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
Command failed: /home/gparise/gateway/node_modules/optipng-bin/vendor/optipng --version optipng pre-build test failed
âš Command failed: /home/gparise/gateway/node_modules/jpegtran-bin/vendor/jpegtran -copy none -optimize -outfile /home/gparise/gateway/node_modules/jpegtran-bin/test/fixtures/test-optimized.jpg /home/gparise/gateway/node_modules/jpegtran-bin/test/fixtures/test.jpg âš jpegtran pre-build test failed
Response code 404 (Not Found)
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) added 1804 packages in 1054.934s |
Hello - i have just installed the latest version of Webthings on to a Pi 3+ running Raspbian V11. I installed WebThings using the manual build instructions. I believe everything installed properly.
After i installed i was successfully able to run 'npm start' and could access the web interface locally and successully registered a domain. I proceeded to install the Zigbee App. Unfortunately, none of my Zigbee devices were picked up after i tried to add Things [i did observe the following error: Error: Cannot find module '/home/gparise/.config/nvm/versions/node/v10.24.1/lib/node_modules/gateway-addon/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-arm/node_sqlite3.node']
The problem is that after rebooting the Pi, and starting WebThings using 'npm start'. I get an error message after about 5 minutes. The log is provided below.
Any help on this would be appreciated.
0 info it worked if it ends with ok
1 verbose cli [ '/home/gparise/.config/nvm/versions/node/v10.24.1/bin/node',
1 verbose cli '/home/gparise/.config/nvm/versions/node/v10.24.1/bin/npm',
1 verbose cli 'start' ]
2 info using npm@6.14.12
3 info using node@v10.24.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle webthings-gateway@1.2.0
prestart: webthings-gateway@1.2.0start: webthings-gateway@1.2.06 info lifecycle webthings-gateway@1.2.0
7 verbose lifecycle webthings-gateway@1.2.0
start: unsafe-perm in lifecycle truestart: PATH: /home/gparise/.config/nvm/versions/node/v10.24.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/gparise/gateway/node_modules/.bin:/home/gparise/.config/nvm/versions/node/v10.24.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games8 verbose lifecycle webthings-gateway@1.2.0
9 verbose lifecycle webthings-gateway@1.2.0
start: CWD: /home/gparise/gatewaystart: Args: [ '-c', 'npm run build && node build/app.js' ]10 silly lifecycle webthings-gateway@1.2.0
11 silly lifecycle webthings-gateway@1.2.0
start: Returned: code: 137 signal: nullstart: Failed to exec start script12 info lifecycle webthings-gateway@1.2.0
13 verbose stack Error: webthings-gateway@1.2.0 start:
npm run build && node build/app.js
13 verbose stack Exit status 137
13 verbose stack at EventEmitter. (/home/gparise/.config/nvm/versions/node/v10.24.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/home/gparise/.config/nvm/versions/node/v10.24.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid webthings-gateway@1.2.0
15 verbose cwd /home/gparise/gateway
16 verbose Linux 5.15.84-v7+
17 verbose argv "/home/gparise/.config/nvm/versions/node/v10.24.1/bin/node" "/home/gparise/.config/nvm/versions/node/v10.24.1/bin/npm" "start"
18 verbose node v10.24.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 137
22 error webthings-gateway@1.2.0 start:
npm run build && node build/app.js
22 error Exit status 137
23 error Failed at the webthings-gateway@1.2.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 137, true ]
The text was updated successfully, but these errors were encountered: