Инсталляция под Linux
-
после переустановки линукс, назначение прав не помогает…........
izum@izum-eM350:/opt/iobroker$ cd /opt izum@izum-eM350:/opt$ sudo mkdir iobroker izum@izum-eM350:/opt$ sudo chmod 777 /opt/iobroker izum@izum-eM350:/opt$ sudo npm install iobroker ```` `Устанавливать надо в /opt/iobroker, а не в /opt
З.Ы. Вообще код какой то странный))
Уже находишься в izum@izum-eM350:/opt/iobroker$
но при этом переходишь в cd /opt
потом создаешь уже существующую директорию sudo mkdir iobroker
Разбиритесь что куда скопировать, перейти, установить…
-
после переустановки линукс, назначение прав не помогает…........
izum@izum-eM350:/opt/iobroker$ cd /opt izum@izum-eM350:/opt$ sudo mkdir iobroker izum@izum-eM350:/opt$ sudo chmod 777 /opt/iobroker izum@izum-eM350:/opt$ sudo npm install iobroker ```` `Устанавливать надо в /opt/iobroker, а не в /opt
З.Ы. Вообще код какой то странный))
Уже находишься в izum@izum-eM350:/opt/iobroker$
но при этом переходишь в cd /opt
потом создаешь уже существующую директорию sudo mkdir iobroker
Разбиритесь что куда скопировать, перейти, установить… `
Находясь в /opt/iobroker я удалял до этого папку iobroker , по этому возвращался в /opt/
-
Попробуй так, что напишет
cd /opt/iobroker sudo npm install iobroker.js-controller ```` `izum@izum-eM350:/opt/iobroker$ sudo npm cache clean izum@izum-eM350:/opt/iobroker$ sudo npm install iobroker.js-controller > ws@0.5.0 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_modules/engine.io/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) / > ws@0.4.31 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) npm WARN deprecated object-keys@0.2.0: Please update to the latest object-keys > ws@0.4.31 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/iobroker.admin/node_modules/socket.io/node_modules/engine.io/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) > ws@0.4.31 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/iobroker.admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) - > iobroker.js-controller@0.5.15 install /opt/iobroker/node_modules/iobroker.js-controller > node lib/setup.js setup first sh: 1: node: not found npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! iobroker.js-controller@0.5.15 install: `node lib/setup.js setup first` npm ERR! Exit status 127 npm ERR! npm ERR! Failed at the iobroker.js-controller@0.5.15 install script. npm ERR! This is most likely a problem with the iobroker.js-controller package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node lib/setup.js setup first npm ERR! You can get their info via: npm ERR! npm owner ls iobroker.js-controller npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.16.0-23-generic npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker.js-controller" npm ERR! cwd /opt/iobroker npm ERR! node -v v0.10.25 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /opt/iobroker/npm-debug.log npm ERR! not ok code 0 izum@izum-eM350:/opt/iobroker$ -
node.js не доступен по команде "node"
Что происходит если в консоли написать?
izum@izum-eM350:/opt$ node -
node.js не доступен по команде "node"
Что происходит если в консоли написать?
izum@izum-eM350:/opt$ node ```` `izum@izum-eM350:~$ izum@izum-eM350:/opt$ node bash: izum@izum-eM350:/opt$: Нет такого файла или каталога izum@izum-eM350:~$ /opt$ node bash: /opt$: Нет такого файла или каталога izum@izum-eM350:~$ -
Создай ссылку на "node" с помощью команды "sudo ln -s /usr/bin/nodejs /usr/bin/node"
-
Создай ссылку на "node" с помощью команды "sudo ln -s /usr/bin/nodejs /usr/bin/node" `
izum@izum-eM350:/opt/iobroker$ sudo npm install iobroker.js-controller > ws@0.5.0 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_modules/engine.io/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) make: вход в каталог «/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build» CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished COPY Release/bufferutil.node CXX(target) Release/obj.target/validation/src/validation.o SOLINK_MODULE(target) Release/obj.target/validation.node SOLINK_MODULE(target) Release/obj.target/validation.node: Finished COPY Release/validation.node make: выход из каталога «/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build» npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.25","npm":"1.4.21"}) > ws@0.4.31 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws > (node-gyp rebuild 2> builderror.log) || (exit 0) make: вход в каталог «/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/build» CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished COPY Release/bufferutil.node CXX(target) Release/obj.target/validation/src/validation.o SOLINK_MODULE(target) Release/obj.target/validation.node SOLINK_MODULE(target) Release/obj.target/validation.node: Finished COPY Release/validation.node make: выход из каталога «/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/build» > iobroker.js-controller@0.5.15 install /opt/iobroker/node_modules/iobroker.js-controller > node lib/setup.js setup first creating conf/iobroker.json object system.certificates created object system.repositories created object system.config created object enum.rooms created object system.group.user created object system.group.administrator created object _design/system created object system.user.admin created object system.meta.uuid created install adapter admin object system.adapter.admin created create instance admin object system.adapter.admin.0.uptime created object system.adapter.admin.0.memRss created object system.adapter.admin.0.memHeapTotal created object system.adapter.admin.0.memHeapUsed created object system.adapter.admin.0.connected created object system.adapter.admin.0.alive created object system.adapter.admin.0 created iobroker.js-controller@0.5.15 node_modules/iobroker.js-controller ├── daemonize2@0.4.2 ├── mime@1.2.11 ├── node-schedule@0.1.13 ├── ncp@0.6.0 ├── node.extend@1.0.10 (is@0.3.0) ├── adm-zip@0.4.7 ├── yargs@1.2.6 (minimist@0.1.0) ├── request@2.38.0 (json-stringify-safe@5.0.0, forever-agent@0.5.2, aws-sign2@0.5.0, qs@0.6.6, oauth-sign@0.3.0, stringstream@0.0.4, tunnel-agent@0.4.0, node-uuid@1.4.3, mime-types@1.0.2, form-data@0.1.4, http-signature@0.10.1, tough-cookie@0.12.1, hawk@1.1.1) ├── tar.gz@0.1.1 (commander@1.1.1, tar@0.1.20, fstream@0.1.31) ├── socket.io@1.2.1 (debug@0.7.4, has-binary-data@0.1.3, socket.io-adapter@0.3.1, socket.io-parser@2.2.2, engine.io@1.4.3) ├── winston@0.7.3 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8, colors@0.6.2, async@0.2.10, pkginfo@0.3.0, request@2.16.6) ├── socket.io-client@1.2.1 (to-array@0.1.3, indexof@0.0.1, component-bind@1.0.0, debug@0.7.4, object-component@0.0.3, component-emitter@1.1.2, has-binary@0.1.5, parseuri@0.0.2, socket.io-parser@2.2.2, engine.io-client@1.4.3) └── npm@2.3.0 izum@izum-eM350:/opt/iobroker$Вроде ошибок нет ,но http://localhost:8081/ не открывается.
-
node iobroker start -
node iobroker start ```` `izum@izum-eM350:/opt/iobroker$ node iobroker start /opt/iobroker/iobroker:1 (function (exports, require, module, __filename, __dirname) { node node_module ^^^^^^^^^^^^ SyntaxError: Unexpected identifier at Module._compile (module.js:439:25) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:902:3 izum@izum-eM350:/opt/iobroker$ cd izum@izum-eM350:~$ node iobroker start /home/izum/iobroker:1 (function (exports, require, module, __filename, __dirname) { node node_module ^^^^^^^^^^^^ SyntaxError: Unexpected identifier at Module._compile (module.js:439:25) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:902:3 izum@izum-eM350:~$ node --version v0.10.25 -
node /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js start
-
node /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js start `
Ура, все завелось! Спасибо вам за ваше терпение и отзывчивость)) -
Изюм установил js-controller
Дай еще команду
sudo nmp install iobroker
После успешной установки
sudo init 6
355_img_0820.png -
Изюм установил js-controller
Дай еще команду
sudo nmp install iobroker
После успешной установки
sudo init 6 `
Не получилось….izum@izum-eM350:/opt/iobroker$ sudo npm install iobroker npm ERR! not a package /tmp/npm-2695-nnDOKRW5/1426781950654-0.42539166775532067/tmp.tgz - > iobroker@0.5.1 install /opt/iobroker/node_modules/iobroker > node lib/setup.js npm install iobroker.js-controller --production --silent --prefix "/opt/iobroker/node_modules/iobroker/lib/../../../" npm install iobroker.admin --production --silent --prefix "/opt/iobroker/node_modules/iobroker/lib/../../../" Write "./iobroker start" to start the ioBroker Non-critical error: EACCES, permission denied '/usr/bin/iobroker' iobroker@0.5.1 node_modules/iobroker └── yargs@1.2.6 (minimist@0.1.0) izum@izum-eM350:/opt/iobroker$ -
"npm install iobroker" выполнится только если не существует папка "/opt/iobroker/iobroker-data". То есть устанавливается только на чистую систему.
-
"npm install iobroker" выполнится только если не существует папка "/opt/iobroker/iobroker-data". То есть устанавливается только на чистую систему. `
То есть у меня сейчас не до конца установленный iobroker?? -
-
Что-то у меня не ролучается установить ioBroker . Такое пишет
root@xbmc:/opt/iobroker# npm install iobroker
npm WARN cannot run in wd iobroker@0.5.5 node lib/setup.js (wd=/opt/iobroker/node_modules/iobroker)
iobroker@0.5.5 node_modules/iobroker
└── yargs@1.2.6 (minimist@0.1.0)
root@xbmc:/opt/iobroker# init 6
root@xbmc:/opt/iobroker#
-
А что такое WD? Название машины?
4733_dok_1_meta_ordner.docx
4733_daten_neq1512381.docx -
А что такое WD? Название машины? `
Да нет , это что-то от nodejs . Хотя когда делаю : root@xbmc:/opt/iobroker# npm install iobroker.js-controllerустанавливается ,но в конце пишет ошибки :
npm ERR! Linux 3.2.0-4-686-pae npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.js-controller" npm ERR! node v0.12.7 npm ERR! npm v2.14.0 npm ERR! code ELIFECYCLE npm ERR! iobroker.js-controller@0.7.9 install: `node lib/setup.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@0.7.9 install script 'node lib/setup.js setup first'. npm ERR! This is most likely a problem with the iobroker.js-controller package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node lib/setup.js setup first npm ERR! You can get their info via: npm ERR! npm owner ls iobroker.js-controller npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/iobroker/npm-debug.log root@xbmc:/opt/iobroker# root@xbmc:/opt/iobroker# -
устанавливается ,но в конце пишет ошибки `
У меня тоже при установке ошибки:> iobroker@0.5.5 install /opt/iobroker/node_modules/iobroker > node lib/setup.js npm install iobroker.js-controller --production --prefix /opt/iobroker /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:121 objects.getObject(obj._id, function (err, _obj) { ^ TypeError: Cannot read property 'getObject' of undefined at dbSetup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:121:20) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:189:13 at Object.States.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2095:82) at null._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemServer.js:179:26) at Timer.listOnTimeout (timers.js:119:15) npm ERR! Linux 3.4.108-bananapi npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.js-controller" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.7 npm ERR! npm v2.11.3 npm ERR! code ELIFECYCLE npm ERR! iobroker.js-controller@0.7.9 install: `node lib/setup.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@0.7.9 install script 'node lib/setup.js setup first'. npm ERR! This is most likely a problem with the iobroker.js-controller package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node lib/setup.js setup first npm ERR! You can get their info via: npm ERR! npm owner ls iobroker.js-controller npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/iobroker/node_modules/iobroker/npm-debug.log Cannot install as normal user. Try sudo... sudo npm install iobroker.js-controller --production --prefix /opt/iobroker npm install iobroker.admin --production --prefix /opt/iobroker Write "./iobroker start" to start the ioBroker Auto-start was enabled. Write "update-rc.d -f iobroker.sh remove" to disable auto-start iobroker is started. Go to "http://ip-addr:8081" to open the admin UI. iobroker@0.5.5 node_modules/iobroker └── yargs@1.2.6 (minimist@0.1.0) root@bananapi:/opt/iobroker#Только файла /opt/iobroker/node_modules/iobroker/npm-debug.log не нашел…
Видимо появление этой ошибки - нормально при установке на линукс...
Все таки система "криво" устанавливается, не запускается админка, в логе ошибки:
!
2015-08-22 11:31:42.603 - info: host.bananapi ioBroker.js-controller version 0.7.9 js-controller starting 2015-08-22 11:31:42.632 - info: host.bananapi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-08-22 11:31:42.637 - info: host.bananapi hostname: bananapi 2015-08-22 11:31:42.638 - info: host.bananapi ip addresses: 192.168.69.20 fe80::17:5ff:fe01:d974 2015-08-22 11:31:42.722 - info: inMem-states listening on port 9000 2015-08-22 11:31:42.786 - info: inMem-objects listening on port 9001 2015-08-22 11:31:42.819 - info: host.bananapi InMemoryDB connected 2015-08-22 11:31:42.860 - error: host.bananapi _design/system missing - call node iobroker.js setup !
Попытка запустить вручную, ругается на конфиг admin.0root@bananapi:~# nodejs /opt/iobroker/node_modules/iobroker.admin/admin.js 2015-08-22 12:16:00.184 - error: admin.0 invalid config root@bananapi:~#Запустился только io.js-controller:
50_pic_148.jpg
