Gelöst: [Tester] kein Aufruf von http://RPi2-1:8081/#javascript möglich

[derAuge]

2016-05-07 13:37:10.287  - info: host.RPi2-1 object change system.adapter.javascript.0
2016-05-07 13:37:10.289  - info: host.RPi2-1 stopInstance system.adapter.javascript.0
2016-05-07 13:37:10.290  - info: host.RPi2-1 stopInstance system.adapter.javascript.0 killing pid 775
2016-05-07 13:37:10.351  - info: host.RPi2-1 instance system.adapter.javascript.0 terminated with code 0 (OK)
2016-05-07 13:37:12.829  - info: host.RPi2-1 instance system.adapter.javascript.0 started with pid 1040
2016-05-07 13:37:18.313  - info: javascript.0 starting. Version 2.0.6 in /opt/iobroker/node_modules/iobroker.javascript
2016-05-07 13:37:18.366  - info: javascript.0 requesting all states
2016-05-07 13:37:18.375  - info: javascript.0 requesting all objects
2016-05-07 13:37:18.848  - info: javascript.0 received all states
2016-05-07 13:37:19.010  - info: javascript.0 received all objects

[Bluefox]

@derAuge:

2016-05-07 13:37:10.287  - info: host.RPi2-1 object change system.adapter.javascript.0
2016-05-07 13:37:10.289  - info: host.RPi2-1 stopInstance system.adapter.javascript.0
2016-05-07 13:37:10.290  - info: host.RPi2-1 stopInstance system.adapter.javascript.0 killing pid 775
2016-05-07 13:37:10.351  - info: host.RPi2-1 instance system.adapter.javascript.0 terminated with code 0 (OK)
2016-05-07 13:37:12.829  - info: host.RPi2-1 instance system.adapter.javascript.0 started with pid 1040
2016-05-07 13:37:18.313  - info: javascript.0 starting. Version 2.0.6 in /opt/iobroker/node_modules/iobroker.javascript
2016-05-07 13:37:18.366  - info: javascript.0 requesting all states
2016-05-07 13:37:18.375  - info: javascript.0 requesting all objects
2016-05-07 13:37:18.848  - info: javascript.0 received all states
2016-05-07 13:37:19.010  - info: javascript.0 received all objects

```` `  

Wenn du jetzt so was aufrufst:

cd /opt/iobroker
iobroker stop javascript
node node_modules/iobroker.javascript/javascript.js --force --logs

Da sollte es mehr Fehlermeldungen sein.

[derAuge]

@Bluefox:

Wenn du jetzt so was aufrufst:

Code: Alles auswählen

cd /opt/iobroker

iobroker stop javascript

node node_modules/iobroker.javascript/javascript.js –force --logs

Da sollte es mehr Fehlermeldungen sein. `

da startet leider garnichts.

System neu gestartet
` > root@RPi2-1:/opt/iobroker# uname -a && node -v && nodejs -v && npm -v

Linux RPi2-1 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux

v4.4.3

v0.10.29

2.15.1 `

pi@RPi2-1:~ $ su
Passwort:
root@RPi2-1:/home/pi# cd /opt/iobroker/

root@RPi2-1:/opt/iobroker# ps -A | grep " io.*"

root@RPi2-1:/opt/iobroker# ./start.sh
Starting iobroker controller daemon...
iobroker controller daemon started. PID: 713

root@RPi2-1:/opt/iobroker# ps -A | grep " io.*"
  713 ?        00:00:11 iobroker.js-con
  722 ?        00:00:11 io.admin.0
  727 ?        00:00:08 io.sql.0
  732 ?        00:00:07 io.web.0
  743 ?        00:00:05 io.history.0

root@RPi2-1:/opt/iobroker# node node_modules/iobroker.javascript/javascript.js --force --logs

[derAuge]

Lösung:

über den Schalter Admin muss die Anzeige von "Skript" aktiviert werden. Danach geht es

Gruß

Jürgen