Hallo Tester.
-
Hallo BF,
ich habe an dem Testszenario mal heimlich still und leise teilgenommen und die neuen Versionen auf einer Backupmaschine installiert.
nun habe ich das alles ein paar Tage beobachtet bevor ich hier schreibe.
- Die Installation selbst ging glatt über die Bühne.
Meine Konfiguration ist wie folgt:
Linux castor 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux
v0.12.14
2.15.1
-
Ich verwende für die Historisierung der Daten den sql Adapter, der die Daten auf eine getrennte Synology mit mysql schreibt. Auch hier nach der Installation, zumindest glaube ich das, keine Auffälligkeiten.
-
Ich habe nun das logging von Verbrauchsdaten des B-Control Adapters aktiviert, der im 500ms Rhythmus alle Sensoren ausliest.
In der Konfiguration des Logging eines Datenpunktes ->"Table" kann man das auch verfolgen.
- ABER: Unter "CHART" gibt es leider absolut nichts zu sehen. Auch der Versuch die Datenpunkte über rickcharts oder flot anzuzeigen geht nicht. Es ist, als würden die Daten zwar in die DB geloggt werden, aber der Rückweg zum Anzeigen der Daten nicht funktionieren.
Ich weiss nicht ob das nun ein Bug ist, oder ich einfach etwas übersehen habe zu aktivieren. Bräuchte da mal etwas unterstützung.
-
Und noch ein Nachsatz:
Ich habe mal den sql Adapter auf debug Level gestellt. Der Wirft Nachrichten raus, von denen ich mal glaube, dass er damit absolut nichts am hut haben dürfte:
Kurzer Ausschnitt:
! sql.0 11 10:44:32.036 debug inMem message * b-control-em.1.Backofen_0001201210250699
! sql.0 11 10:44:32.011 debug sql.0 INSERT INTO iobroker.ts_number (id, ts, val, ack, _from, q) VALUES(5, 1462956262006, 28.7, 0, 5, 0);
! sql.0 11 10:44:31.923 debug sql.0 INSERT INTO iobroker.ts_number (id, ts, val, ack, _from, q) VALUES(51, 1462956269764, 7.7, 0, 1, 0);
! sql.0 11 10:44:31.900 debug inMem message * b-control-em.2.Till_0001201210230069
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.uptime
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memHeapUsed
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memHeapTotal
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memRss
! sql.0 11 10:44:31.414 debug inMem message * system.adapter.javascript.0.connected
! sql.0 11 10:44:31.414 debug inMem message * system.adapter.javascript.0.alive
! sql.0 11 10:44:31.307 debug inMem message * node-red.0.consumption.geschirrspueler
! sql.0 11 10:44:31.306 debug inMem message * b-control-em.1.Geschirrspueler_0001201210250681
! sql.0 11 10:44:31.167 debug inMem message * node-red.0.consumption.waschmaschine
! sql.0 11 10:44:31.164 debug inMem message * b-control-em.2.Waeschetrockner_0001201210230072
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.level
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.b
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.g
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.r
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.reachable
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.colormode
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.alert
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.ct
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.xy
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.effect
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.sat
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.hue
! sql.0 11 10:44:31.044 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.bri
! sql.0 11 10:44:31.044 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.on
! sql.0 11 10:44:30.999 debug inMem message * hue.0.HeinzelHue.Till_Decke_1/2.level
! sql.0 11 10:44:30.999 debug inMem message * hue.0.HeinzelHue.Till_Decke_1/2.b
Die b-control-Messages sind korrekt, aber ich weiss nicht woher der sql.0 die Nchrichten von hue oder anderen nimmt. Da hab ich kein Logging aktiviert.Bin etwas ratlos.
-
Und noch ein Nachsatz:
Ich habe mal den sql Adapter auf debug Level gestellt. Der Wirft Nachrichten raus, von denen ich mal glaube, dass er damit absolut nichts am hut haben dürfte:
Kurzer Ausschnitt:
! sql.0 11 10:44:32.036 debug inMem message * b-control-em.1.Backofen_0001201210250699
! sql.0 11 10:44:32.011 debug sql.0 INSERT INTO iobroker.ts_number (id, ts, val, ack, _from, q) VALUES(5, 1462956262006, 28.7, 0, 5, 0);
! sql.0 11 10:44:31.923 debug sql.0 INSERT INTO iobroker.ts_number (id, ts, val, ack, _from, q) VALUES(51, 1462956269764, 7.7, 0, 1, 0);
! sql.0 11 10:44:31.900 debug inMem message * b-control-em.2.Till_0001201210230069
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.uptime
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memHeapUsed
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memHeapTotal
! sql.0 11 10:44:31.419 debug inMem message * system.adapter.javascript.0.memRss
! sql.0 11 10:44:31.414 debug inMem message * system.adapter.javascript.0.connected
! sql.0 11 10:44:31.414 debug inMem message * system.adapter.javascript.0.alive
! sql.0 11 10:44:31.307 debug inMem message * node-red.0.consumption.geschirrspueler
! sql.0 11 10:44:31.306 debug inMem message * b-control-em.1.Geschirrspueler_0001201210250681
! sql.0 11 10:44:31.167 debug inMem message * node-red.0.consumption.waschmaschine
! sql.0 11 10:44:31.164 debug inMem message * b-control-em.2.Waeschetrockner_0001201210230072
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.level
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.b
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.g
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.r
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.reachable
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.colormode
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.alert
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.ct
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.xy
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.effect
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.sat
! sql.0 11 10:44:31.059 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.hue
! sql.0 11 10:44:31.044 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.bri
! sql.0 11 10:44:31.044 debug inMem message * hue.0.HeinzelHue.Till_Decke_2/2.on
! sql.0 11 10:44:30.999 debug inMem message * hue.0.HeinzelHue.Till_Decke_1/2.level
! sql.0 11 10:44:30.999 debug inMem message * hue.0.HeinzelHue.Till_Decke_1/2.b
Die b-control-Messages sind korrekt, aber ich weiss nicht woher der sql.0 die Nchrichten von hue oder anderen nimmt. Da hab ich kein Logging aktiviert.Bin etwas ratlos. `
Ich glaube, ich habe so was eingebaut, dass falls mehr als 50 States geloggt wird, dann werden alle Nachrichten an sql weitergeleitet und da entscheiden, ob geloggt werden muss. Damit Controller nicht 100 oder 1000 vergleiche macht und damit das System ausbremmst. -
Hallo BF,
ich habe an dem Testszenario mal heimlich still und leise teilgenommen und die neuen Versionen auf einer Backupmaschine installiert.
nun habe ich das alles ein paar Tage beobachtet bevor ich hier schreibe.
- Die Installation selbst ging glatt über die Bühne.
Meine Konfiguration ist wie folgt:
Linux castor 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux
v0.12.14
2.15.1
-
Ich verwende für die Historisierung der Daten den sql Adapter, der die Daten auf eine getrennte Synology mit mysql schreibt. Auch hier nach der Installation, zumindest glaube ich das, keine Auffälligkeiten.
-
Ich habe nun das logging von Verbrauchsdaten des B-Control Adapters aktiviert, der im 500ms Rhythmus alle Sensoren ausliest.
In der Konfiguration des Logging eines Datenpunktes ->"Table" kann man das auch verfolgen.
- ABER: Unter "CHART" gibt es leider absolut nichts zu sehen. Auch der Versuch die Datenpunkte über rickcharts oder flot anzuzeigen geht nicht. Es ist, als würden die Daten zwar in die DB geloggt werden, aber der Rückweg zum Anzeigen der Daten nicht funktionieren.
Ich weiss nicht ob das nun ein Bug ist, oder ich einfach etwas übersehen habe zu aktivieren. Bräuchte da mal etwas unterstützung. `
Hast du auch flot upgedatet und dann "iobroker upload flot" geschrieben? -
Bingo!!! Das Upload flot hast gebracht!
Vielen Dank!!!
-
Bitte alle Pakete (besonders: SQL, JS-Controller, Flot, Admin) updaten, so wie oben beschreiben ist. Es gibt da Änderungen.
-
erledigt.
Beim Update vom js-controller die Meldungen:
$ sudo npm install https://github.com/ioBroker/ioBroker.js-controller/tarball/master --production [sudo] Passwort für michael: npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0\. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. | [...]Und im Log sind die SQL Fehler erhalten geblieben:
sql.0 12 16:23:13.293 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(11, 1463062982278, 42.5, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:13.293 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(10, 1463062982277, 999.22, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:03.302 error sql.0 Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(15, 1463062982277, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:03.301 error sql.0 Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(6, 1463062982277, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:22:05.322 error Cannot delete DELETE FROM ts_number WHERE id=8 AND ts < 1461853320320;: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_string (id, ts, val, ack, _from, q) VALUES(5, 1463062917661, 'stabil', 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(15, 1463062917661, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(6, 1463062917661, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:54.618 error Cannot delete DELETE FROM ts_number WHERE id=2 AND ts < 1461853260616;: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:54.295 info enabled logging of javascript.1.WIFFI.Arbeitszimmer.wz_azimutUmgebung, wie oben beschrieben:
ubuntu 16.04
npm 2.15.1
node 4.4.4
-
erledigt.
Beim Update vom js-controller die Meldungen:
$ sudo npm install https://github.com/ioBroker/ioBroker.js-controller/tarball/master --production [sudo] Passwort für michael: npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0\. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. | [...]Und im Log sind die SQL Fehler erhalten geblieben:
sql.0 12 16:23:13.293 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(11, 1463062982278, 42.5, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:13.293 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(10, 1463062982277, 999.22, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:03.302 error sql.0 Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(15, 1463062982277, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql.0 12 16:23:03.301 error sql.0 Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(6, 1463062982277, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:22:05.322 error Cannot delete DELETE FROM ts_number WHERE id=8 AND ts < 1461853320320;: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_string (id, ts, val, ack, _from, q) VALUES(5, 1463062917661, 'stabil', 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(15, 1463062917661, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:58.668 error Cannot insert INSERT INTO ts_bool (id, ts, val, ack, _from, q) VALUES(6, 1463062917661, 0, 0, 3, 0);: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:54.618 error Cannot delete DELETE FROM ts_number WHERE id=2 AND ts < 1461853260616;: Error: SQLITE_BUSY: database is locked sql-0 12 16:21:54.295 info enabled logging of javascript.1.WIFFI.Arbeitszimmer.wz_azimutUmgebung, wie oben beschrieben:
ubuntu 16.04
npm 2.15.1
node 4.4.4 `
Danke. Kannst du nur sql updaten? Noch mal
-
ubuntu 16.04
npm 2.15.1
node 4.4.4
Danke. Kannst du nur sql updaten? Noch mal :)erledigt.
sql.0 13 02:53:18.213 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(12, 1463100788209, 20.9, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.210 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(11, 1463100788194, -17.9, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.207 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(10, 1463100788193, 1001.09, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.205 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(9, 1463100788191, 0.11, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.202 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(8, 1463100788190, 30.5, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.200 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(13, 1463100788190, 30.2, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql.0 13 02:53:18.198 error sql.0 Cannot insert INSERT INTO ts_number (id, ts, val, ack, _from, q) VALUES(7, 1463100788188, 98, 0, 3, 0);: Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: ts_number.id, ts_number.ts sql-0 13 02:53:09.201 warn Cannot get index of "javascript.1.WIFFI.Arbeitszimmer.wz_motion_left": Error: SQLITE_BUSY: database is locked sql-0 13 02:53:09.201 error Cannot select SELECT id, type FROM datapoints WHERE name='javascript.1.WIFFI.Arbeitszimmer.wz_motion_left';: Error: SQLITE_BUSY: database is locked sql-0 13 02:53:08.173 info enabled logging of javascript.1.WIFFI.Arbeitszimmer.wz_azimutioBroker Versionen:
root@ubuntu-1604-dev:/opt/iobroker# ./iobroker update update done Adapter "web" : 1.4.3 , installed 1.4.3 Adapter "rickshaw" : 0.3.1 , installed 0.4.0 [Updateable] Adapter "sql" : 0.1.2 , installed 0.3.1 [Updateable] Controller "js-controller" : 0.8.10 , installed 0.8.10 Adapter "javascript" : 2.0.6 , installed 2.0.6 Adapter "history" : 0.2.1 , installed 0.4.0 [Updateable] Adapter "fritzbox" : 0.2.1 , installed 0.2.1 Adapter "flot" : 1.0.0 , installed 1.2.0 [Updateable] Adapter "admin" : 1.0.3 , installed 1.1.1 [Updateable] -
erledigt
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.1root@RPi2-1:/opt/iobroker# ps -A | grep " io.*" 713 ? 01:48:02 iobroker.js-con 722 ? 01:00:08 io.admin.0 727 ? 00:51:32 io.sql.0 732 ? 00:06:08 io.web.0 743 ? 00:50:16 io.history.0 1276 ? 00:48:06 io.javascript.0root@RPi2-1:/opt/iobroker# node node_modules/iobroker.js-controller/iobroker.js update
! update done
! Adapter "zwave" : 0.2.5
! Adapter "yr" : 1.0.1 , installed 1.0.1
! Adapter "yamaha" : 0.1.5
! Adapter "wolf" : 0.1.0
! Adapter "web" : 1.4.3 , installed 1.4.3
! Adapter "weatherunderground": 0.1.0
! Adapter "vis-timeandweather": 1.1.0
! Adapter "vis-rgraph" : 0.0.2
! Adapter "vis-plumb" : 0.1.6
! Adapter "vis-metro" : 1.0.0
! Adapter "vis-lcars" : 1.0.0
! Adapter "vis-keyboard" : 0.0.2
! Adapter "vis-justgage" : 0.4.1 , installed 0.4.1
! Adapter "vis-jqui-mfd" : 0.1.0
! Adapter "vis-hqwidgets" : 1.0.0
! Adapter "vis-google-fonts": 0.1.0
! Adapter "vis-fancyswitch": 1.0.0
! Adapter "vis-colorpicker": 0.1.3
! Adapter "vis-bars" : 0.1.1
! Adapter "vis" : 0.9.4 , installed 0.9.4
! Adapter "vcard" : 0.0.6
! Adapter "text2command" : 1.0.0
! Adapter "terminal" : 0.1.2
! Adapter "telegram" : 0.2.4
! Adapter "starline" : 0.1.5
! Adapter "sonos" : 0.1.8
! Adapter "squeezebox" : 0.1.0
! Adapter "samsung" : 0.0.10
! Adapter "rpi" : 0.0.4
! Adapter "rickshaw" : 0.3.1 , installed 0.4.0 [Updateable]
! Adapter "pushover" : 0.1.1
! Adapter "pushbullet" : 0.0.11
! Adapter "piface" : 0.0.50
! Adapter "phantomjs" : 0.1.2
! Adapter "owfs" : 0.0.2
! Adapter "onkyo" : 0.2.0
! Adapter "occ" : 0.2.4
! Adapter "tvspielfilm" : 0.2.2 , installed 0.1.0 [Updateable]
! Adapter "sql" : 0.1.2 , installed 0.2.0 [Updateable]
! Adapter "socketio" : 1.4.0
! Adapter "simple-api" : 1.1.0
! Adapter "scenes" : 0.2.5
! Adapter "sayit" : 0.3.17
! Adapter "s7" : 0.2.4
! Adapter "ping" : 1.1.1
! Adapter "noolite" : 0.0.1
! Adapter "node-red" : 1.0.0
! Adapter "mysensors" : 0.2.3
! Adapter "mqtt" : 1.0.2
! Adapter "modbus" : 0.3.10
! Adapter "mobile" : 0.4.1
! Adapter "miele" : 0.0.12
! Adapter "megad" : 1.2.0
! Adapter "knx" : 0.2.10
! Controller "js-controller" : 0.8.10 , installed 0.8.10
! Adapter "javascript" : 2.0.6 , installed 2.0.6
! Adapter "influxdb" : 0.1.2
! Adapter "icons-ultimate-png": 0.1.0
! Adapter "icons-open-icon-library-png": 0.1.3
! Adapter "icons-mfd-svg" : 0.1.2
! Adapter "icons-mfd-png" : 0.1.2
! Adapter "icons-material-svg": 0.1.0
! Adapter "icons-material-png": 0.1.0
! Adapter "icons-icons8" : 0.0.1
! Adapter "icons-addictive-flavour-png": 0.1.0
! Adapter "ical" : 1.1.1
! Adapter "hmm" : 1.0.1
! Adapter "homekit" : 0.1.4
! Adapter "hue" : 0.5.3
! Adapter "hm-rpc" : 1.1.3
! Adapter "hm-rega" : 0.3.7
! Adapter "history" : 0.2.1 , installed 0.4.0 [Updateable]
! Adapter "harmony" : 0.5.5
! Adapter "geofency" : 0.1.4
! Adapter "fritzbox" : 0.2.1
! Adapter "feiertage" : 0.3.2 , installed 0.3.2
! Adapter "flot" : 1.0.0 , installed 1.2.0 [Updateable]
! Adapter "email" : 0.1.2
! Adapter "dwd" : 2.0.3 , installed 2.0.3
! Adapter "cul" : 0.0.4
! Adapter "chromecast" : 1.0.6
! Adapter "b-control-em" : 0.1.1
! Adapter "artnet" : 0.0.3
! Adapter "admin" : 1.0.3 , installed 1.1.1 [Updateable]root@RPi2-1:/opt/iobroker# node node_modules/iobroker.js-controller/iobroker.js stop Stopping iobroker controller daemon... iobroker controller daemon stopped. Exit code for "killall.sh": 0root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.js … all/master --production
! npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
! npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
! /
! > iobroker.js-controller@0.8.10 install /opt/iobroker/node_modules/iobroker.js-controller
! > node lib/setup.js setup first
! iobroker.js-controller@0.8.10 node_modules/iobroker.js-controller
! ├── mime@1.3.4
! ├── daemonize2@0.4.2
! ├── adm-zip@0.4.7
! ├── ncp@2.0.0
! ├── semver@4.3.6
! ├── node.extend@1.1.5 (is@3.1.0)
! ├── node-schedule@1.0.0 (long-timeout@0.0.2, cron-parser@1.1.0)
! ├── winston@2.2.0 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8, isstream@0.1.2, async@1.0.0, pkginfo@0.3.1, colors@1.0.3)
! ├── yargs@3.32.0 (decamelize@1.2.0, camelcase@2.1.1, y18n@3.2.1, window-size@0.1.4, cliui@3.2.0, os-locale@1.4.0, string-width@1.0.1)
! ├── winston-daily-rotate-file@1.0.1 (winston@2.1.1)
! ├── socket.io@1.4.6 (has-binary@0.1.7, debug@2.2.0, socket.io-parser@2.2.6, socket.io-adapter@0.4.0, engine.io@1.6.9)
! ├── socket.io-client@1.4.6 (to-array@0.1.4, component-emitter@1.2.0, indexof@0.0.1, component-bind@1.0.0, backo2@1.0.2, object-component@0.0.3, has-binary@0.1.7, debug@2.2.0, socket.io-parser@2.2.6, parseuri@0.0.4, engine.io-client@1.6.9)
! ├── request@2.72.0 (aws-sign2@0.6.0, tunnel-agent@0.4.3, forever-agent@0.6.1, oauth-sign@0.8.2, is-typedarray@1.0.0, caseless@0.11.0, stringstream@0.0.5, aws4@1.4.1, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.0, tough-cookie@2.2.2, node-uuid@1.4.7, qs@6.1.0, combined-stream@1.0.5, mime-types@2.1.11, form-data@1.0.0-rc4, hawk@3.1.3, bl@1.1.2, http-signature@1.1.1, har-validator@2.0.6)
! ├── prompt@1.0.0 (revalidator@0.1.8, pkginfo@0.4.0, colors@1.1.2, read@1.0.7, winston@2.1.1, utile@0.3.0)
! ├── tar.gz@1.0.3 (commander@2.9.0, bluebird@2.10.2, tar@2.2.1, chai@3.5.0, fstream@1.0.9, mocha@2.4.5, mout@0.11.1)
! └── npm@2.15.5root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.ad … all/master --production
! iobroker.admin@1.1.1 node_modules/iobroker.admin
! ├── connect-flash@0.1.1
! ├── xtend@4.0.1
! ├── passport-local@1.0.0 (passport-strategy@1.0.0)
! ├── cookie-parser@1.4.1 (cookie-signature@1.0.6, cookie@0.2.3)
! ├── passport@0.2.2 (pause@0.0.1, passport-strategy@1.0.0)
! ├── express-session@1.13.0 (cookie-signature@1.0.6, utils-merge@1.0.0, on-headers@1.0.1, cookie@0.2.3, parseurl@1.3.1, depd@1.1.0, crc@3.4.0, uid-safe@2.0.0, debug@2.2.0)
! ├── body-parser@1.15.1 (content-type@1.0.2, bytes@2.3.0, depd@1.1.0, on-finished@2.3.0, raw-body@2.1.6, http-errors@1.4.0, qs@6.1.0, debug@2.2.0, iconv-lite@0.4.13, type-is@1.6.12)
! ├── express@4.13.4 (escape-html@1.0.3, cookie-signature@1.0.6, utils-merge@1.0.0, merge-descriptors@1.0.1, methods@1.1.2, vary@1.0.1, content-type@1.0.2, parseurl@1.3.1, cookie@0.1.5, fresh@0.3.0, content-disposition@0.5.1, etag@1.7.0, range-parser@1.0.3, serve-static@1.10.2, array-flatten@1.1.1, path-to-regexp@0.1.7, depd@1.1.0, qs@4.0.0, on-finished@2.3.0, finalhandler@0.4.1, debug@2.2.0, proxy-addr@1.0.10, send@0.13.1, type-is@1.6.12, accepts@1.2.13)
! ├── socket.io@1.4.6 (has-binary@0.1.7, debug@2.2.0, socket.io-parser@2.2.6, socket.io-adapter@0.4.0, engine.io@1.6.9, socket.io-client@1.4.6)
! └── request@2.72.0 (aws-sign2@0.6.0, tunnel-agent@0.4.3, oauth-sign@0.8.2, forever-agent@0.6.1, caseless@0.11.0, is-typedarray@1.0.0, stringstream@0.0.5, aws4@1.4.1, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.0, tough-cookie@2.2.2, node-uuid@1.4.7, qs@6.1.0, combined-stream@1.0.5, mime-types@2.1.11, form-data@1.0.0-rc4, bl@1.1.2, hawk@3.1.3, http-signature@1.1.1, har-validator@2.0.6)nun SQL (mit einigen Hinweisen)
root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.sql/tarball/master –production
! -
! > sqlite3@3.1.3 install /opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3
! > node-pre-gyp install –fallback-to-build
! make: Entering directory '/opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/build'
! ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3090100/sqlite3.c
! TOUCH Release/obj.target/deps/action_before_build.stamp
! CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3090100/sqlite3.o
! AR(target) Release/obj.target/deps/sqlite3.a
! COPY Release/sqlite3.a
! CXX(target) Release/obj.target/node_sqlite3/src/database.o
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginOpen(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:143:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginClose(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:227:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginExec(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:505:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginLoadExtension(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:605:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! CXX(target) Release/obj.target/node_sqlite3/src/node_sqlite3.o
! CXX(target) Release/obj.target/node_sqlite3/src/statement.o
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginPrepare(node_sqlite3::Database::Baton*)’:
! ../src/statement.cc:118:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! In file included from ../src/statement.cc:6:0:
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginBind(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:322:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Bind);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginGet(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:370:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Get);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginRun(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:438:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Run);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginAll(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:504:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(All);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginEach(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:601:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Each);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginReset(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:724:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Reset);
! ^
! SOLINK_MODULE(target) Release/obj.target/node_sqlite3.node
! COPY Release/node_sqlite3.node
! COPY /opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/lib/binding/node-v46-linux-arm/node_sqlite3.node
! TOUCH Release/obj.target/action_after_build.stamp
! make: Leaving directory '/opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/build'
! iobroker.sql@0.3.1 node_modules/iobroker.sql
! ├── mysql@2.10.2 (bignumber.js@2.1.4, readable-stream@1.1.14)
! ├── pg@4.5.5 (packet-reader@0.2.0, pg-connection-string@0.1.3, generic-pool@2.1.1, buffer-writer@1.0.1, semver@4.3.6, pg-types@1.11.0, pgpass@0.0.3)
! ├── sql-client@0.7.0 (argf@0.0.1, optimist@0.6.1, inote-util@0.8.1)
! ├── mssql@3.3.0 (generic-pool@2.4.2, promise@7.1.1, tedious@1.14.0)
! └── sqlite3@3.1.3 (nan@2.2.1)root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.hi … all/master --production
iobroker.history@0.4.0 node_modules/iobroker.history
root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.fl ... all/master --production
iobroker.flot@1.2.0 node_modules/iobroker.flot
root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.ri ... all/master --production
iobroker.rickshaw@0.4.0 node_modules/iobroker.rickshaw
root@RPi2-1:/opt/iobroker# node node_modules/iobroker.js-controller/iobroker.js start
Starting iobroker controller daemon... iobroker controller daemon started. PID: 9525 root@RPi2-1:/opt/iobroker# ps -A | grep " io.*" 9525 ? 00:00:14 iobroker.js-con 9534 ? 00:00:12 io.admin.0 9539 ? 00:00:10 io.sql.0 9548 ? 00:00:07 io.web.0 9553 ? 00:00:05 io.history.0 9597 ? 00:00:06 io.javascript.0Gruß
Jürgen
-
==> /opt/iobroker/log/iobroker.2016-05-13.log <== 2016-05-13 06:17:48.426 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.icon';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.438 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.icon": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.441 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.text';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.442 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.text": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.573 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.precipitation_level';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.574 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.precipitation_level": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:51.144 - info: feiertage.0 starting. Version 0.3.2 in /opt/iobroker/node_modules/iobroker.feiertage 2016-05-13 06:17:51.937 - info: host.RPi2-1 instance system.adapter.feiertage.0 terminated with code 0 (OK) 2016-05-13 06:18:02.398 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='feiertage.0.heute.boolean';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:18:02.401 - warn: sql.0 Cannot get index of "feiertage.0.heute.boolean": Error: SQLITE_BUSY: database is locked -
==> /opt/iobroker/log/iobroker.2016-05-13.log <== 2016-05-13 06:17:48.426 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.icon';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.438 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.icon": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.441 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.text';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.442 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.text": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.573 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='yr.0.forecast.day0.precipitation_level';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:48.574 - warn: sql.0 Cannot get index of "yr.0.forecast.day0.precipitation_level": Error: SQLITE_BUSY: database is locked 2016-05-13 06:17:51.144 - info: feiertage.0 starting. Version 0.3.2 in /opt/iobroker/node_modules/iobroker.feiertage 2016-05-13 06:17:51.937 - info: host.RPi2-1 instance system.adapter.feiertage.0 terminated with code 0 (OK) 2016-05-13 06:18:02.398 - error: sql.0 Cannot select SELECT id, type FROM datapoints WHERE name='feiertage.0.heute.boolean';: Error: SQLITE_BUSY: database is locked 2016-05-13 06:18:02.401 - warn: sql.0 Cannot get index of "feiertage.0.heute.boolean": Error: SQLITE_BUSY: database is locked ```` `Danke. Noch mal updaten (nur sql reicht.)
-
root@RPi2-1:/home/pi# cd /opt/iobroker/
root@RPi2-1:/opt/iobroker# node node_modules/iobroker.js-controller/iobroker.js stop Stopping iobroker controller daemon... iobroker controller daemon stopped. Exit code for "killall.sh": 0root@RPi2-1:/opt/iobroker# sudo npm install https://github.com/ioBroker/ioBroker.sql/tarball/master –production
! -
! > sqlite3@3.1.3 install /opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3
! > node-pre-gyp install –fallback-to-build
! make: Entering directory '/opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/build'
! ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3090100/sqlite3.c
! TOUCH Release/obj.target/deps/action_before_build.stamp
! CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3090100/sqlite3.o
! AR(target) Release/obj.target/deps/sqlite3.a
! COPY Release/sqlite3.a
! CXX(target) Release/obj.target/node_sqlite3/src/database.o
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginOpen(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:143:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginClose(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:227:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginExec(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:505:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginLoadExtension(node_sqlite3::Database::Baton*)’:
! ../src/database.cc:605:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! CXX(target) Release/obj.target/node_sqlite3/src/node_sqlite3.o
! CXX(target) Release/obj.target/node_sqlite3/src/statement.o
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginPrepare(node_sqlite3::Database::Baton*)’:
! ../src/statement.cc:118:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! In file included from ../src/statement.cc:6:0:
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginBind(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:322:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Bind);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginGet(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:370:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Get);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginRun(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:438:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Run);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginAll(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:504:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(All);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginEach(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:601:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Each);
! ^
! ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginReset(node_sqlite3::Statement::Baton*)’:
! ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable]
! int status = uv_queue_work(uv_default_loop(),
! ^
! ../src/statement.cc:724:5: note: in expansion of macro ‘STATEMENT_BEGIN’
! STATEMENT_BEGIN(Reset);
! ^
! SOLINK_MODULE(target) Release/obj.target/node_sqlite3.node
! COPY Release/node_sqlite3.node
! COPY /opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/lib/binding/node-v46-linux-arm/node_sqlite3.node
! TOUCH Release/obj.target/action_after_build.stamp
! make: Leaving directory '/opt/iobroker/node_modules/iobroker.sql/node_modules/sqlite3/build'
! iobroker.sql@0.3.2 node_modules/iobroker.sql
! ├── mysql@2.10.2 (bignumber.js@2.1.4, readable-stream@1.1.14)
! ├── pg@4.5.5 (packet-reader@0.2.0, pg-connection-string@0.1.3, generic-pool@2.1.1, buffer-writer@1.0.1, semver@4.3.6, pg-types@1.11.0, pgpass@0.0.3)
! ├── sql-client@0.7.0 (argf@0.0.1, optimist@0.6.1, inote-util@0.8.1)
! ├── mssql@3.3.0 (generic-pool@2.4.2, promise@7.1.1, tedious@1.14.0)
! └── sqlite3@3.1.3 (nan@2.2.1)
! root@RPi2-1:/opt/iobroker#root@RPi2-1:/opt/iobroker# node node_modules/iobroker.js-controller/iobroker.js start Starting iobroker controller daemon... iobroker controller daemon started. PID: 10400 -
Frage:
Ist der Test nun abgeschlossen?
Gruß
Jürgen
-
ich denke ja.
Es gibt noch influxdb, was auch getestet werden muss.
Nächste Woche werde ich dann alles veröffentlichen.
-
ich denke ja.
Nächste Woche werde ich dann alles veröffentlichen. `
Danke für die Rückmeldung.
Das bedeutet ist sollte bis nächste Woche mit der Installation des SQL-Adaptern auf meinem neuen Produktiv-System (DS412+) noch warten.
Gruß
Jürgen
-
Moin zusammen,
bzgl. SQL-Adapter und mySQL-DB teste ich gerade einen Anbieter, der hosted SQL (MS-SQL und auch mySQL) anbietet.
Keinen "Ärger" mit Backup, Last, usw. - und das für kleines Geld (wie ich finde)
Schaut selber : http://www.ecs-webhosting.de/de/cloud-m … osting.htm
Gruß,
Eric
