Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

NEWS

js-controller 2 jetzt für alle im Stable

apollon77 last edited by

iobroker war sauber gestoppt davor? Keine Prozesse mehr gelaufen?
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

ja

ist immernoch gestoppt
1 Reply Last reply
Reply Quote 0
apollon77 last edited by

Und was genau kommt als Fehler wnen Du wieder neu starten willst?
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

sudo iobroker start keine fehler kommt nix
M 1 Reply Last reply
Reply Quote 0
M
Motsche1 @Motsche1 last edited by

erst bei sudo iobroker start admin
1 Reply Last reply
Reply Quote 0
apollon77 last edited by

Fehler im Logfile? /opt/iobroker/log/...
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

also im moment kann er nicht starten da kein js controler da ist

das log ist seit 40 min nix neues drin hab aber vor 10 min versucht zu starten
M 1 Reply Last reply
Reply Quote 0
M
Motsche1 @Motsche1 last edited by

@Motsche1 ich lösch mal die log und installiere js neu mom
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

alsoinstallation geht nur mit

npm install iobroker.js-controller

dann hab ich wieder 1.5.14 drauf und iobroker laüft
1 Reply Last reply
Reply Quote 0

Motsche1

und dann hab ich im log fplgenden fehler wenn ich starte

2019-12-27 17:47:54.478  - [31merror[39m: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
2019-12-27 17:47:54.480  - [31merror[39m: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
    at Object.openSync (fs.js:443:3)
    at Object.writeFileSync (fs.js:1194:35)
    at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2024:16)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

apollon77 @Motsche1 last edited by

@Motsche1 Installation Fixer ... siehe FAQ!

Ansonsten mach mal

npm install iobroker.js-controller@2.1.1
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

hab ich beides schon durch --- selbes ergebnis
1 Reply Last reply
Reply Quote 0
apollon77 @Motsche1 last edited by

@Motsche1 Immer dieser Fehler mit dem "Flatten"?

Ruf mal nach install der 2.1.1 bitte manuell "iobroker setup first" auf.

Und immer noch: Was steht im ioBroker Logfile?
1 Reply Last reply
Reply Quote 0

Motsche1

@apollon77 said in js-controller 2 jetzt für alle im Stable:

iobroker setup first

Iobroker setup first

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

und log file hatte ich schon gepostet aber gern nochmal

2019-12-27 17:55:09.310  - [31merror[39m: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
2019-12-27 17:55:09.314  - [31merror[39m: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
    at Object.openSync (fs.js:443:3)
    at Object.writeFileSync (fs.js:1194:35)
    at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2024:16)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
2019-12-27 17:55:09.318  - [32minfo[39m: iobroker _restart
2019-12-27 17:55:09.745  - [32minfo[39m: iobroker Starting node restart.js
2019-12-27 17:55:09.768  - [32minfo[39m: iobroker exit 0
2019-12-27 17:55:09.809  - [32minfo[39m: admin.0 starting. Version 3.6.12 in /opt/iobroker/node_modules/iobroker.admin, node: v10.18.0
2019-12-27 17:55:09.870  - [32minfo[39m: admin.0 requesting all states
2019-12-27 17:55:09.870  - [32minfo[39m: admin.0 requesting all objects
2019-12-27 17:55:11.485  - [32minfo[39m: admin.0 received all objects
2019-12-27 17:55:11.501  - [33mwarn[39m: admin.0 No repository source configured
2019-12-27 17:55:11.524  - [32minfo[39m: admin.0 http server listening on port 8081
2019-12-27 17:55:11.524  - [32minfo[39m: admin.0 Use link "http://localhost:8081" to configure.
2019-12-27 17:55:19.324  - [32minfo[39m: host.rockpro64 force terminating
2019-12-27 17:55:19.324  - [32minfo[39m: Adapter admin still running
2019-12-27 17:55:20.218  - [32minfo[39m: host.rockpro64 instance system.adapter.sonoff.0 started with pid 26841
2019-12-27 17:55:20.399  - [32minfo[39m: admin.0 terminating http server on port 8081
2019-12-27 17:55:21.905  - [32minfo[39m: admin.0 terminating http server on port 8081

apollon77 last edited by

Und jetzt bitte mal log von dem Install direkt per npm mit der 2.1.1
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

also 2.1.1 install und dann noch mal in die log schauen
1 Reply Last reply
Reply Quote 0

Motsche1

iobroker log nix drin also neuer eintrag

in der npm log steht

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'install',
1 verbose cli   'iobroker.js-controller@2.1.1' ]
2 info using npm@6.13.4
3 info using node@v10.18.0
4 verbose npm-session 64667189d8460ead
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://registry.npmjs.org/iobroker.js-controller 325ms (from cache)
8 silly pacote version manifest for iobroker.js-controller@2.1.1 fetched in 347ms
9 timing stage:loadCurrentTree Completed in 11475ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 136ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2548ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule iobroker.js-controller@2.1.1 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/decache 124ms (from cache)
18 silly pacote range manifest for decache@^4.5.1 fetched in 129ms
19 silly resolveWithNewModule decache@4.5.1 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/semver 145ms (from cache)
21 silly pacote range manifest for semver@^6.3.0 fetched in 152ms
22 silly resolveWithNewModule semver@6.3.0 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/respjs 288ms (from cache)
24 http fetch GET 304 https://registry.npmjs.org/readline-sync 294ms (from cache)
25 silly pacote range manifest for respjs@^4.2.0 fetched in 300ms
26 silly resolveWithNewModule respjs@4.2.0 checking installable status
27 silly pacote range manifest for readline-sync@^1.4.10 fetched in 308ms
28 silly resolveWithNewModule readline-sync@1.4.10 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/mime 319ms (from cache)
30 http fetch GET 304 https://registry.npmjs.org/node-forge 322ms (from cache)
31 http fetch GET 304 https://registry.npmjs.org/chokidar 345ms (from cache)
32 silly pacote range manifest for mime@^2.4.4 fetched in 347ms
33 silly resolveWithNewModule mime@2.4.4 checking installable status
34 silly pacote range manifest for node-forge@^0.9.1 fetched in 351ms
35 silly resolveWithNewModule node-forge@0.9.1 checking installable status
36 http fetch GET 304 https://registry.npmjs.org/event-stream 363ms (from cache)
37 silly pacote range manifest for chokidar@^3.3.0 fetched in 373ms
38 silly resolveWithNewModule chokidar@3.3.1 checking installable status
39 http fetch GET 304 https://registry.npmjs.org/ioredis 372ms (from cache)
40 http fetch GET 304 https://registry.npmjs.org/iobroker.objects-redis 386ms (from cache)
41 http fetch GET 304 https://registry.npmjs.org/socket.io-client 223ms (from cache)
42 http fetch GET 304 https://registry.npmjs.org/socket.io 264ms (from cache)
43 silly pacote range manifest for event-stream@^4.0.1 fetched in 417ms
44 silly resolveWithNewModule event-stream@4.0.1 checking installable status
45 silly pacote range manifest for ioredis@^4.14.1 fetched in 427ms
46 silly resolveWithNewModule ioredis@4.14.1 checking installable status
47 silly pacote range manifest for iobroker.objects-redis@^1.2.8 fetched in 444ms
48 silly resolveWithNewModule iobroker.objects-redis@1.2.13 checking installable status
49 silly pacote version manifest for socket.io-client@2.3.0 fetched in 280ms
50 silly resolveWithNewModule socket.io-client@2.3.0 checking installable status
51 silly pacote version manifest for socket.io@2.3.0 fetched in 322ms
52 silly resolveWithNewModule socket.io@2.3.0 checking installable status
53 http fetch GET 304 https://registry.npmjs.org/winston 217ms (from cache)
54 http fetch GET 304 https://registry.npmjs.org/tar 229ms (from cache)

Motsche1 @Motsche1

5377 warn enoent ENOENT: no such file or directory, open '/home/pi/package.json'
5378 verbose enoent This is related to npm not being able to find a file.
5379 warn pi No description
5380 warn pi No repository field.
5381 warn pi No README data
5382 warn pi No license field.
5383 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
5384 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   linux
5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: arm64
5386 verbose stack Error: iobroker.js-controller@2.1.1 install: `node iobroker.js setup first`
5386 verbose stack Exit status 25
5386 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
5386 verbose stack     at EventEmitter.emit (events.js:198:13)
5386 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
5386 verbose stack     at ChildProcess.emit (events.js:198:13)
5386 verbose stack     at maybeClose (internal/child_process.js:982:16)
5386 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
5387 verbose pkgid iobroker.js-controller@2.1.1
5388 verbose cwd /home/pi
5389 verbose Linux 4.4.192-rockchip64
5390 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.js-controller@2.1.1"
5391 verbose node v10.18.0
5392 verbose npm  v6.13.4
5393 error code ELIFECYCLE
5394 error errno 25
5395 error iobroker.js-controller@2.1.1 install: `node iobroker.js setup first`
5395 error Exit status 25
5396 error Failed at the iobroker.js-controller@2.1.1 install script.
5396 error This is probably not a problem with npm. There is likely additional logging output above.
5397 verbose exit [ 25, true ]

apollon77 @Motsche1 last edited by

@Motsche1 sagte in js-controller 2 jetzt für alle im Stable:

5377 warn enoent ENOENT: no such file or directory, open '/home/pi/package.json'

startest du das npm install im richtigen verzeichnis? Muss /opt/iobroker sein! Nicht /home/pi
1 Reply Last reply
Reply Quote 0
M
Motsche1 last edited by

@apollon77 said in js-controller 2 jetzt für alle im Stable:

/opt/iobroker

ja schon
1 Reply Last reply
Reply Quote 0

Support us

714
Online

31.7k
Users

79.6k
Topics

1.3m
Posts

74

556

134779

Log in to reply

1
2
3
4
5
27
28

1 / 28