@glasfaser
Na toll
Strg + C
10 mal versucht und geht nicht
aber jetzt geht es auf einmal,
danke

@glasfaser
iob logs --watch | uniq

wie hält man das denn an?

@glasfaser
Deshalb ja ich dussel, ich kann es nicht mehr nachvollziehen,
es kann sein.

@thomas-braun said in BSB-LAN Adapter Funktioniert nach iobroker update nicht.:

iob logs --watch | uniq

login as: pi
pi@192.168.33.23's password:
Linux iobroker-2 6.1.29-v8+ #1652 SMP PREEMPT Wed May 24 14:46:55 BST 2023 aarch                                                                                                                               64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon May 29 11:20:27 2023 from 192.168.33.17

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set                                                                                                                                a new password.

pi@iobroker-2:~ $ iob logs --watch | uniq
2023-05-29 12:33:58.226  - error: bsblan.0 (13225) Error: Parse Error: Invalid header value char
2023-05-29 12:33:58.227  - error: bsblan.0 (13225) RequestError: Error: Parse Error: Invalid header value char
    at new RequestError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:14:15)
    at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
    at Request.emit (node:events:513:28)
    at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:877:8)
    at ClientRequest.emit (node:events:525:35)
    at Socket.socketOnData (node:_http_client:551:9)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2023-05-29 12:33:58.227  - debug: bsblan.0 (13225) Reset Timer
2023-05-29 12:34:00.009  - info: bsblan.0 (13225) Scheduled restart.
2023-05-29 12:34:00.010  - info: bsblan.0 (13225) cleaned everything up...
2023-05-29 12:34:00.056  - info: bsblan.0 (13225) terminating
2023-05-29 12:34:00.058  - info: bsblan.0 (13225) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-05-29 12:34:00.597  - info: host.iobroker-2 instance system.adapter.bsblan.0 scheduled normal terminated and will be restarted on schedule.
2023-05-29 12:34:00.597  - info: host.iobroker-2 Restart adapter system.adapter.bsblan.0 because enabled
2023-05-29 12:34:01.628  - info: host.iobroker-2 instance system.adapter.bsblan.0 started with pid 13240
2023-05-29 12:34:03.492  - debug: bsblan.0 (13240) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-05-29 12:34:03.532  - debug: bsblan.0 (13240) Objects client ready ... initialize now
2023-05-29 12:34:03.536  - debug: bsblan.0 (13240) Objects create System PubSub Client
2023-05-29 12:34:03.537  - debug: bsblan.0 (13240) Objects create User PubSub Client
2023-05-29 12:34:03.566  - debug: bsblan.0 (13240) Objects client initialize lua scripts
2023-05-29 12:34:03.576  - debug: bsblan.0 (13240) Objects connected to redis: 127.0.0.1:9001
2023-05-29 12:34:03.599  - debug: bsblan.0 (13240) Redis States: Use Redis connection: 127.0.0.1:9000
2023-05-29 12:34:03.610  - debug: bsblan.0 (13240) States create System PubSub Client
2023-05-29 12:34:03.611  - debug: bsblan.0 (13240) States create User PubSub Client
2023-05-29 12:34:03.628  - debug: bsblan.0 (13240) States connected to redis: 127.0.0.1:9000
2023-05-29 12:34:03.752  - info: bsblan.0 (13240) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.bsblan, node: v18.16.0, js-controller: 4.0.24
2023-05-29 12:34:03.825  - debug: bsblan.0 (13240) Schedule restart: */30 * * * * *
2023-05-29 12:34:03.894  - info: bsblan.0 (13240) Values found: 700
2023-05-29 12:34:03.897  - debug: bsblan.0 (13240) Fetch values ...
2023-05-29 12:34:03.984  - info: bsblan.0 (13240) Setup new objects (700) ...
2023-05-29 12:34:05.398  - error: bsblan.0 (13240) Error: Parse Error: Invalid header value char
2023-05-29 12:34:05.399  - error: bsblan.0 (13240) RequestError: Error: Parse Error: Invalid header value char
    at new RequestError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:14:15)
    at plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
    at Request.emit (node:events:513:28)
    at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:877:8)
    at ClientRequest.emit (node:events:525:35)
    a

@fischerjedd
ist bei Firefox nicht eingestellt

@fischerjedd
wegen automatische Übersetzung englisch - deutsch

@glasfaser
ich meinte, das Verhalten ist dasselbe, selber Fehler

@thomas-braun
Ich habe es mal in Firefox gestartet
alles das selbe

@fischerjedd
Nächstes Problem

In CodeTags, damit man das auch lesen kann.

Ich mache hier gerade eine Fortbildung

@glasfaser
Super erklärt, jetzt habe ich dussel es auch kapiert.