Truenas Jail running IOBROKER - Modbus adapter not working

SailorMax

Cadet
Joined
Oct 24, 2014
Messages
7
Hello and Happy 2022,
I'm running iobroker in a Truenas jail (12.2 release p11). All updates done. Iobroker is basically running, except for the modbus adapter. Error messages are:


QuelleZeit
debugNachricht
host.freenas-iobroker2022-01-02 16:36:49.223infoRestart adapter system.adapter.modbus.0 because enabled
host.freenas-iobroker2022-01-02 16:36:49.223errorinstance system.adapter.modbus.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.freenas-iobroker2022-01-02 16:36:49.223errorCaught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:84:21)
host.freenas-iobroker2022-01-02 16:36:49.223errorCaught by controller[0]: at doListen (node:net:1505:7)
host.freenas-iobroker2022-01-02 16:36:49.223errorCaught by controller[0]: at listenInCluster (node:net:1367:12)
host.freenas-iobroker2022-01-02 16:36:49.223errorCaught by controller[0]: at Server.setupListenHandle [as _listen2] (node:net:1302:21)
host.freenas-iobroker2022-01-02 16:36:49.222errorCaught by controller[0]: Error: listen EACCES: permission denied 192.168.178.50:502
modbus.png

modbus.0
2022-01-02 16:36:49.199warnTerminated (UNCAUGHT_EXCEPTION): Without reason
modbus.png

modbus.0
2022-01-02 16:36:49.198infoterminating
modbus.png

modbus.0
2022-01-02 16:36:49.184errorException-Code: EACCES: listen EACCES: permission denied 192.168.178.50:502
modbus.png

modbus.0
2022-01-02 16:36:49.184errorError: listen EACCES: permission denied 192.168.178.50:502 at Server.setupListenHandle [as _listen2] (node:net:1302:21) at listenInCluster (node:net:1367:12) at doListen (node:net:1505:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)
modbus.png

modbus.0
2022-01-02 16:36:49.183erroruncaught exception: listen EACCES: permission denied 192.168.178.50:502
modbus.png

modbus.0
2022-01-02 16:36:49.021infoState value to set for "modbus.0.info.connection" has to be type "string" but received type "number"

The .xx.50 IP is iobroker which want's to talk to the modbus instance with port 502 on IP 192.168.178.11 (small plc).

I have another instance of iobroker running under debian on another machine which is working perfectly fine with the modbus adapter.

With my limitted UNIX knowledge, this sounds like a rights/permissions/closed port/you name it problem.

Any thoughts??

regards Matthias
 
Top