NEWS
Iobroker.js-controller@1.2.7 - kein syslog mehr
-
Hallo,
nachdem Update kommt nur noch
2018-03-10 22:35:09.850 - error: Caught by controller[0]: Syslog configured, but not installed!mit der Version vorher lief alles stabil.
winston, winston-syslog sind im /opt/iobroker installiert (2.4.1 und 2.0)
-
Wenn das wirklich fehlen sollte, geht denn ein
Mit einem fehlenden Syslog hatte ich keine Probleme.
Enrico
Edit: Vergiss es, ich habe so ein Modul nicht finden können in der ioBroker Installation. :?
-
Lustig, dass ihr Beide schonmal eine ähnliche Diskussion hattet :D :D
-
wenn man
cd /opt/iobroker npm i winston-syslog@1.2.6 iobroker restartausführt.. Hilft das? `
Nein (habe grade auf 1.3.0 upgedatet):
Ich habe die Datei logger.js im Unterverzeichnis lib angepaßt um einen Fehler zu sehen:
/* jshint -W097 */// jshint strict:false /*jslint node: true */ 'use strict'; var winston = require('winston'); var DailyRotateFile = require('winston-daily-rotate-file'); var fs = require('fs'); var path = require('path'); var os = require('os'); var tools = require(__dirname + '/tools.js'); var SysLog; var hostname = tools.getHostName(); try { SysLog = require('winston-syslog').Syslog; } catch (ex) { console.error('No syslog support'); console.error(ex); console.error('No syslog support'); }host.zotac 2018-03-13 13:27:47.460 error Caught by controller[3]: Syslog configured, but not installed! host.zotac 2018-03-13 13:27:47.460 error Caught by controller[2]: No syslog support host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at Function.Module._load (module.js:497:3) code: 'MODULE_NOT_FOUND' } host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at tryModuleLoad (module.js:505:12) host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at Module.load (module.js:565:32) host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at Object.Module._extensions..js (module.js:663:10) host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at Module._compile (module.js:652:30) host.zotac 2018-03-13 13:27:47.460 error Caught by controller[1]: at Object. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/winston-syslog/lib/winston-syslog.js:15:28) host.zotac 2018-03-13 13:27:47.459 error Caught by controller[1]: at require (internal/module.js:11:18) host.zotac 2018-03-13 13:27:47.459 error Caught by controller[1]: at Module.require (module.js:596:17) host.zotac 2018-03-13 13:27:47.459 error Caught by controller[1]: at Function.Module._load (module.js:474:25) host.zotac 2018-03-13 13:27:47.459 error Caught by controller[1]: at Function.Module._resolveFilename (module.js:547:15) host.zotac 2018-03-13 13:27:47.459 error Caught by controller[1]: { Error: Cannot find module 'triple-beam' host.zotac 2018-03-13 13:27:47.454 error Caught by controller[0]: No syslog supportErst:
/opt/iobroker/node_modules/iobroker.js-controller# npm i winston-syslog@1.2.6/opt/iobroker/node_modules/iobroker.js-controller# npm i winston-syslog@1.2.6 > unix-dgram@0.2.3 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/unix-dgram > node-gyp rebuild gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR make: Entering directory '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/unix-dgram/build' CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o SOLINK_MODULE(target) Release/obj.target/unix_dgram.node COPY Release/unix_dgram.node make: Leaving directory '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/unix-dgram/build' npm notice save winston-syslog is being moved from dependencies to optionalDependencies npm notice created a lockfile as package-lock.json. You should commit this file. + winston-syslog@1.2.6 added 13 packages from 33 contributors and updated 1 package in 15.001sDann lief der Logger wieder.
Meine Einstellungen im iobroker json:
"log": { "level": "info", "maxDays": 30, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null }, "syslog1": { "type": "syslog", "enabled": true, "host": "192.168.1.13", "host_comment": "The host running syslogd, defaults to localhost.", "port": "514", "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP ).", "protocol": "udp4", "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "path": "", "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facility_comment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).", "app_name_comment": "The name of the application (Default: process.title).", "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)." } } -
Ich nehme alles frühere zurück und behaupte das Gegenteil :-))
Ja mit 1.3.0 vom js-controller geht es mit Syslog nur mit winston-syslog 1.2.6 :-(
Die Dependency vom js.contrtoller ist an sich: "winston-syslog": "^1.2.6"
(als optionalDependency)
-
Hallo, ich habe den js.controller 1.3.0 am laufen, ohne Probleme.
npm list gibt mir dabei folgende Versionen aus.
!
│ ├─┬ winston@2.4.1 │ │ ├── async@1.0.0 │ │ ├── colors@1.0.3 │ │ ├── cycle@1.0.3 │ │ ├── eyes@0.1.8 │ │ ├── isstream@0.1.2 deduped │ │ └── stack-trace@0.0.10 │ ├─┬ winston-daily-rotate-file@1.7.2 │ │ └── mkdirp@0.5.1 deduped │ ├─┬ winston-syslog@2.0.0 │ │ ├── cycle@1.0.3 deduped │ │ ├── glossy@0.1.7 │ │ └─┬ unix-dgram@0.2.3 │ │ ├── bindings@1.1.1 │ │ └── nan@2.3.5 !Es scheint auch winston-syslog 2.0.0 zu gehen.
Mein System läuft ohne Fehlermeldungen und das Syslog läuft auch.
mfg. Fred
Support us
630
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge