JimDuskes
commented
6 years ago Same here. ROS 2.2.0 won’t start on CentOS 7
I’ve followed the installation instructions on the Realm website many times with no luck. I’m installing it on a Linode.com CentOS 7 VM.
Using 'npm start’ in my app’s folder, outputs the following: (formatting, such as partial crossing out of lines, was added by github)
my-ros-app@1.0.0 start /home/tony/BOTH npm run build && node dist/index.js "BOTH"
my-ros-app@1.0.0 build /home/tony/BOTH rm -rf dist; ./node_modules/.bin/tsc
sh: ./node_modules/.bin/tsc: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! my-ros-app@1.0.0 build: rm -rf dist; ./node_modules/.bin/tsc
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the my-ros-app@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/tony/.npm/_logs/2017-12-14T17_37_49_609Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-ros-app@1.0.0 start: npm run build && node dist/index.js "BOTH"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-ros-app@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/tony/.npm/_logs/2017-12-14T17_37_49_631Z-debug.log
This is the content of /home/tony/.npm/_logs/2017-12-14T17_37_49_609Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/home/tony/.nvm/versions/node/v8.9.3/bin/node',
1 verbose cli '/home/tony/.nvm/versions/node/v8.9.3/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using npm@5.6.0
3 info using node@v8.9.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle my-ros-app@1.0.0~prebuild: my-ros-app@1.0.0
6 info lifecycle my-ros-app@1.0.0~build: my-ros-app@1.0.0
7 verbose lifecycle my-ros-app@1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle my-ros-app@1.0.0~build: PATH: /home/tony/.nvm/versions/node/v8.9.3/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/tony/BOT$
9 verbose lifecycle my-ros-app@1.0.0~build: CWD: /home/tony/BOTH
10 silly lifecycle my-ros-app@1.0.0~build: Args: [ '-c', 'rm -rf dist; ./node_modules/.bin/tsc' ]
11 info lifecycle my-ros-app@1.0.0~build: Failed to exec build script
12 verbose stack Error: my-ros-app@1.0.0 build: rm -rf dist; ./node_modules/.bin/tsc
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.rm -rf dist; ./node_modules/.bin/tsc
23 error spawn ENOENT
24 error Failed at the my-ros-app@1.0.0 build script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
The is the content of /home/tony/.npm/_logs/2017-12-14T17_37_49_631Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/home/tony/.nvm/versions/node/v8.9.3/bin/node',
1 verbose cli '/home/tony/.nvm/versions/node/v8.9.3/bin/npm',
1 verbose cli 'start',
1 verbose cli 'BOTH' ]
2 info using npm@5.6.0
3 info using node@v8.9.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle my-ros-app@1.0.0~prestart: my-ros-app@1.0.0
6 info lifecycle my-ros-app@1.0.0~start: my-ros-app@1.0.0
7 verbose lifecycle my-ros-app@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle my-ros-app@1.0.0~start: PATH: /home/tony/.nvm/versions/node/v8.9.3/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/tony/BOT$
9 verbose lifecycle my-ros-app@1.0.0~start: CWD: /home/tony/BOTH
10 silly lifecycle my-ros-app@1.0.0~start: Args: [ '-c', 'npm run build && node dist/index.js "BOTH"' ]
11 silly lifecycle my-ros-app@1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle my-ros-app@1.0.0~start: Failed to exec start script
13 verbose stack Error: my-ros-app@1.0.0 start: npm run build && node dist/index.js "BOTH"
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.npm run build && node dist/index.js "BOTH"
22 error Exit status 1
23 error Failed at the my-ros-app@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
After days of trying to get this to work, any help would be appreciated.
bigfish24
ozmaat
raudabaugh
codegrue
revolter
I was not able to run ROS after installing it.
Goals
Install ROS on CentOS Linux 7.4 and start ROS with npm start
Expected Results
After the command"ros init my-app" , "npm start" would run ROS
Actual Results
I get the following error after running "npm start"
`my-ros-app@1.0.0 start /home/user1/realmapp
sh: ./node_modules/.bin/tsc: No such file or directory npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! my-ros-app@1.0.0 build:
rm -rf dist; ./node_modules/.bin/tscnpm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the my-ros-app@1.0.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/user1/.npm/_logs/2017-12-13T15_28_45_808Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! my-ros-app@1.0.0 start:
npm run build && node dist/index.jsnpm ERR! Exit status 1 npm ERR! npm ERR! Failed at the my-ros-app@1.0.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/user1/.npm/_logs/2017-12-13T15_28_45_824Z-debug.log`
Steps to Reproduce
Also tried installing with npm "install -g realm-object-server"
I don't get any error but an "undefined" is added at the end of line as below after the command runs.
"Installing dependencies... A little patience is good.undefined"
Version of Realm and Tooling
Logs
systemctl status realm-object-server.service
Dec 13 11:14:22 dom systemd[1]: Started Realm Object Server. Dec 13 11:14:22 dom systemd[1]: Starting Realm Object Server... Dec 13 11:14:23 dom realm-object-server[26823]: read configuration from /etc/realm/configuration.yml. Dec 13 12:09:48 dom systemd[1]: Stopping Realm Object Server... Dec 13 12:09:48 dom systemd[1]: Stopped Realm Object Server. Warning: realm-object-server.service changed on disk. Run 'systemctl daemon-reload' to reload units.sudo journalctl -u realm-object-server.service
Dec 13 11:14:22 dom systemd[1]: Started Realm Object Server. Dec 13 11:14:22 dom systemd[1]: Starting Realm Object Server... Dec 13 11:14:23 dom realm-object-server[26823]: read configuration from /etc/realm/configuration.yml. Dec 13 12:09:48 dom systemd[1]: Stopping Realm Object Server... Dec 13 12:09:48 dom systemd[1]: Stopped Realm Object Server.cat /var/log/realm-object-server.log
No log after running the neither ros-init or npm startAttaching logs from npm/logs after the running - npm start log2.txt log1.txt
Thank you