Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loxone Adapter (IOB) not connect with Miniserver #191

Closed
Sinus1986 opened this issue Oct 3, 2021 · 50 comments
Closed

Loxone Adapter (IOB) not connect with Miniserver #191

Sinus1986 opened this issue Oct 3, 2021 · 50 comments

Comments

@Sinus1986
Copy link

Failure: instance system.adapter.loxone.0 terminated due to SIGBUS
Unbenannt

Whats the problem?
Can someone help me?

@Marcwi15
Copy link

Marcwi15 commented Oct 7, 2021

I have the same Problem.
image

When i add http:// or https:// in the Hostname field least i get two green lights:
image
image
But still getting failure:
image

Any news or Ideas? It worked 2 weeks ago without any problems.

iobroker Version is: v5.1.25
nodejs Version: v12.22.6

@UncleSamSwiss
Copy link
Owner

Can you please provide additional information about your Loxone Miniserver and your ioBroker installation?

Version numbers, your configuration (except for the password of course).

@Cheeseyo
Copy link

Cheeseyo commented Oct 7, 2021

Hi, here my configuration, if you need more information let me know.

IO Broker Details

PlatformBetriebssystem:linux
Architektur:arm
CPUs:4
Geschwindigkeit:1500 MHz
Modell:ARMv7 Processor rev 3 (v7l)
RAM:1.8 GB
System-Betriebszeit:20:10:52
Node.js:v12.22.6
NPM:6.14.15
Datenträgergröße:28.9 GB
Festplatte frei:26.9 GB
Adapter-Anzahl:441
Betriebszeit:20:22:29
Aktive Instanzen:7
Pfad:/opt/iobroker/
Adminagent: 5.1.25
Loxone Agent: 2.2.3

Miniserver Details:

Typ:Miniserver Gen. 1
Version:12.1.7.16

Network:

IP-Range:192.168.2.0/24
IP-IOBroker: 192.168.2.11
IP-Miniserver: 192.168.2.4:80
IP-Router: 192.168.2.1
IP-DNS: 192.168.2.11

Loxone Adapter configured with only IP-Adress 192.168.2.4 results in:
grafik

Loxone Adapter configured with Hostname results in:
grafik

Loxone WebInterface ist working with credentials stored in the Adapter.

@UncleSamSwiss
Copy link
Owner

Have any of you done any updates recently? Other adapters or your OS or NodeJS or anything else?

@Cheeseyo
Copy link

Cheeseyo commented Oct 7, 2021

No, i startet from scratch.

  • Writing image '021-05-07-raspios-buster-armhf-lite.img' to SD-Card
  • doing update and upgradge
  • checking, no node installed
  • installing node and iobroker from https://www.iobroker.net/#de/download

Tried also the raspi image on the iobroker website, but it did not work.

@Sinus1986
Copy link
Author

Hi, no. I have set up my raspi completely newm. No backups implemented. I just downloaded the loxone adapter and tried to get it online, but without success.

@UncleSamSwiss
Copy link
Owner

UncleSamSwiss commented Oct 7, 2021

Can any of you please set the adapter to "debug" and then restart it and then post those logs here?

@Cheeseyo
Copy link

Cheeseyo commented Oct 7, 2021

Ok, here my logs. With Adapter configuration IP-Adress and Hostname.

iobroker_loxone_ip.txt
iobroker_loxone_hostname.txt

@theflamez
Copy link

Hi! I have the issue. Miniserver gen.2

@UncleSamSwiss
Copy link
Owner

Please, everybody who has the problem: provide all details about your system. It doesn't help at all to tell me that you have the same issue without telling me what's your environment and perhaps how/when the issue occured. Software usually doesn't fail without any changes to the systems involved.

@geritsch
Copy link

geritsch commented Oct 7, 2021

I installed this on a pi4 the day before yesterday.

curl -sLf https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs

curl -sLf https://iobroker.net/install.sh | bash -

nodejs had already been deleted

warn.txt
debug.txt

this was my first attempt to get it done. without success
https://www.allroundbastler.de/projekte/problem-loxone-miniserver-gen-2-verbindet-sich-nicht-mit-iobroker/?v=fa868488740a

@Sinus1986
Copy link
Author

Sinus1986 commented Oct 7, 2021

Here an overview about the debug results:

2021-10-07 21:27:48.370 - debug: loxone.0 (24193) Objects client ready ... initialize now
--
2021-10-07 21:27:48.372 - debug: loxone.0 (24193) Objects create System PubSub Client
2021-10-07 21:27:48.374 - debug: loxone.0 (24193) Objects create User PubSub Client
2021-10-07 21:27:48.375 - debug: loxone.0 (24193) Objects client initialize lua scripts
2021-10-07 21:27:48.399 - debug: loxone.0 (24193) Objects connected to redis: 127.0.0.1:9001
2021-10-07 21:27:48.412 - info: host.raspberrypi "system.adapter.loxone.0" disabled
2021-10-07 21:27:48.413 - info: host.raspberrypi stopInstance system.adapter.loxone.0 (force=false, process=true)
2021-10-07 21:27:48.410 - debug: loxone.0 (24193) objectDB connected
2021-10-07 21:27:48.413 - debug: loxone.0 (24193) Redis States: Use Redis connection: 127.0.0.1:9000
2021-10-07 21:27:48.421 - info: host.raspberrypi stopInstance system.adapter.loxone.0 send kill signal
2021-10-07 21:27:48.424 - debug: loxone.0 (24193) States create System PubSub Client
2021-10-07 21:27:48.426 - debug: loxone.0 (24193) States create User PubSub Client
2021-10-07 21:27:48.441 - debug: loxone.0 (24193) States connected to redis: 127.0.0.1:9000
2021-10-07 21:27:48.442 - debug: loxone.0 (24193) statesDB connected
2021-10-07 21:27:48.551 - debug: loxone.0 (24193) Plugin sentry Initialize Plugin (enabled=true)
2021-10-07 21:27:48.625 - error: loxone.0 (24193) adapter disabled
2021-10-07 21:27:48.632 - debug: loxone.0 (24193) Plugin sentry destroyed
2021-10-07 21:27:48.633 - warn: loxone.0 (24193) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
2021-10-07 21:27:49.202 - info: host.raspberrypi instance system.adapter.loxone.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
2021-10-07 21:27:54.161 - info: host.raspberrypi "system.adapter.loxone.0" enabled
2021-10-07 21:27:54.230 - info: host.raspberrypi instance system.adapter.loxone.0 started with pid 24204
2021-10-07 21:27:55.563 - debug: loxone.0 (24204) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-10-07 21:27:55.601 - debug: loxone.0 (24204) Objects client ready ... initialize now
2021-10-07 21:27:55.604 - debug: loxone.0 (24204) Objects create System PubSub Client
2021-10-07 21:27:55.605 - debug: loxone.0 (24204) Objects create User PubSub Client
2021-10-07 21:27:55.607 - debug: loxone.0 (24204) Objects client initialize lua scripts
2021-10-07 21:27:55.628 - debug: loxone.0 (24204) Objects connected to redis: 127.0.0.1:9001
2021-10-07 21:27:55.637 - debug: loxone.0 (24204) objectDB connected
2021-10-07 21:27:55.640 - debug: loxone.0 (24204) Redis States: Use Redis connection: 127.0.0.1:9000
2021-10-07 21:27:55.647 - debug: loxone.0 (24204) States create System PubSub Client
2021-10-07 21:27:55.649 - debug: loxone.0 (24204) States create User PubSub Client
2021-10-07 21:27:55.656 - debug: loxone.0 (24204) States connected to redis: 127.0.0.1:9000
2021-10-07 21:27:55.657 - debug: loxone.0 (24204) statesDB connected
2021-10-07 21:27:55.772 - debug: loxone.0 (24204) Plugin sentry Initialize Plugin (enabled=true)
2021-10-07 21:27:55.855 - info: loxone.0 (24204) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.6, js-controller: 3.3.18
2021-10-07 21:27:55.994 - info: loxone.0 (24204) Miniserver connected
2021-10-07 21:27:56.042 - debug: loxone.0 (24204) sent message: jdev/sys/keyexchange/aceJqA38nYvtgNqp18Sz+qtdxgxKwCkMtoX1mxIxIUFVqdcTvNeKeiEGeeMYnAYzqp8wCSK6OibjDuDlIc0HgEGmnz0T6b6hngAZW64bN7n87jkCaVnCw9cJlsMOB1CLILNqKy/mXMmjKSSviwbSj/wbd25GRVLEFCQ44ALgBT8=
2021-10-07 21:27:56.267 - warn: host.raspberrypi instance system.adapter.loxone.0 terminated due to SIGBUS
2021-10-07 21:27:56.268 - info: host.raspberrypi instance system.adapter.loxone.0 terminated with code NaN ()
2021-10-07 21:27:56.268 - info: host.raspberrypi Restart adapter system.adapter.loxone.0 because enabled

@mattgas
Copy link

mattgas commented Oct 10, 2021

Any news on this? I tried different versions of nodejs (12, 14), admin adapter, javascript adapter and loxone adapter, but the SIGBUS issue remains in any combination.
The issue began on my PI3 after updating several adapters and nodejs. Unfortunately i have no backup...

@UncleSamSwiss
Copy link
Owner

Unfortunately not. I'm on vacation and have no access to a Raspi right now. I hope this issue is not at all related to the adapter but rather some other software. But for now it seems nobody has found the culprit yet.

@Cheeseyo
Copy link

Hi erveryone,

i did some testing and got it running with 'ubuntu-20.04.3-preinstalled-server-arm64+raspi.img' as OS for Raspberry. I think it is not a problem of the apapter.

PlatformBetriebssystem:linux
Architektur:arm64
CPUs:4
Geschwindigkeit:1500 MHz
Modell:unknown
RAM:1.8 GB
System-Betriebszeit:00:20:07
Node.js:v12.22.6
NPM:6.14.15
Datenträgergröße:29.0 GB
Festplatte frei:25.6 GB
Adapter-Anzahl:441
Betriebszeit:00:20:11
Aktive Instanzen:8
Pfad:/opt/iobroker/

Hope it helps...

@theflamez
Copy link

theflamez commented Oct 11, 2021

loxone.0 | 2021-10-11 07:30:41.508 | info | Miniserver connected
loxone.0 | 2021-10-11 07:30:41.293 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.6, js-controller: 3.3.18
host.loxberry | 2021-10-11 07:30:38.199 | info | instance system.adapter.loxone.0 started with pid 1346
host.loxberry | 2021-10-11 07:30:08.158 | info | Restart adapter system.adapter.loxone.0 because enabled
host.loxberry | 2021-10-11 07:30:08.158 | info | instance system.adapter.loxone.0 terminated with code NaN ()
host.loxberry | 2021-10-11 07:30:08.157 | warn | instance system.adapter.loxone.0 terminated due to SIGBUS
loxone.0 | 2021-10-11 07:30:07.992 | info | Miniserver connected
loxone.0 | 2021-10-11 07:30:07.811 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.6, js-controller: 3.3.18
host.loxberry | 2021-10-11 07:30:04.629 | info | instance system.adapter.loxone.0 started with pid 1301
host.loxberry | 2021-10-11 07:29:34.587 | info | Restart adapter system.adapter.loxone.0 because enabled
host.loxberry | 2021-10-11 07:29:34.586 | info | instance system.adapter.loxone.0 terminated with code NaN ()
host.loxberry | 2021-10-11 07:29:34.585 | warn | instance system.adapter.loxone.0 terminated due to SIGBUS
loxone.0 | 2021-10-11 07:29:34.416 | info | Miniserver connected
loxone.0 | 2021-10-11 07:29:34.238 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.6, js-controller: 3.3.18
host.loxberry | 2021-10-11 07:29:31.150 | info | instance system.adapter.loxone.0 started with pid 1161
host.loxberry | 2021-10-11 07:29:01.103 | info | Restart adapter system.adapter.loxone.0 because enabled
host.loxberry | 2021-10-11 07:29:01.102 | info | instance system.adapter.loxone.0 terminated with code NaN ()
host.loxberry | 2021-10-11 07:29:01.100 | warn | instance system.adapter.loxone.0 terminated due to SIGBUS
loxone.0 | 2021-10-11 07:29:00.907 | info | Miniserver connected
loxone.0 | 2021-10-11 07:29:00.717 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.6, js-controller: 3.3.18
host.loxberry | 2021-10-11 07:28:57.622 | info | instance system.adapter.loxone.0 started with pid 1122
host.loxberry | 2021-10-11 07:28:57.468 | info | "system.adapter.loxone.0" enabled

Adapter Version v2.2.3
iobroker Version v5.1.25

PLATFORM: LINUX
RAM: 926 MB
NODE.JS: V12.22.6
NPM: 6.14.15

@UncleSamSwiss
Copy link
Owner

UncleSamSwiss commented Oct 11, 2021

i did some testing and got it running with 'ubuntu-20.04.3-preinstalled-server-arm64+raspi.img' as OS for Raspberry. I think it is not a problem of the apapter.

Hope it helps...

This sounds promising! Thanks for your effort.

For everybody else: can you try with an older Raspi OS image? Or with a lower patch version of NodeJS (e.g. 12.22.5)?

@theflamez
Copy link

Same with 12.22.5

host.loxberry | 2021-10-11 11:02:24.921 | info | Restart adapter system.adapter.loxone.0 because enabled
host.loxberry | 2021-10-11 11:02:24.920 | info | instance system.adapter.loxone.0 terminated with code NaN ()
host.loxberry | 2021-10-11 11:02:24.919 | warn | instance system.adapter.loxone.0 terminated due to SIGBUS
loxone.0 | 2021-10-11 11:02:24.750 | info | Miniserver connected
loxone.0 | 2021-10-11 11:02:24.573 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.5, js-controller: 3.3.18
host.loxberry | 2021-10-11 11:02:21.483 | info | instance system.adapter.loxone.0 started with pid 1548
host.loxberry | 2021-10-11 11:01:51.445 | info | Restart adapter system.adapter.loxone.0 because enabled
host.loxberry | 2021-10-11 11:01:51.444 | info | instance system.adapter.loxone.0 terminated with code NaN ()
host.loxberry | 2021-10-11 11:01:51.443 | warn | instance system.adapter.loxone.0 terminated due to SIGBUS
loxone.0 | 2021-10-11 11:01:51.274 | info | Miniserver connected
loxone.0 | 2021-10-11 11:01:51.099 | info | starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.loxone, node: v12.22.5, js-controller: 3.3.18

I don't want to change raspi image because of other installed plugins

@Cheeseyo
Copy link

Cheeseyo commented Oct 11, 2021

It's funny, i wrote it was working with ubuntu 20.04.3 but today i tried to reproduce it and it now shows the same error. Found that it is working with 64bit only. Maybe it helps.

@Apollon77
Copy link
Contributor

because we research a comparable issue in alexa2 adapter ... can you please check dmesg and /var/log/syslog for entries when the SIGBUS error occurs?

@UncleSamSwiss
Copy link
Owner

We are starting to see similar issues in another adapter. Can somebody please have a look at their dmesg or /var/log/syslog when the error happens? There should be an exception. Please post it including the surrounding messages.

This will also be interesting for @Apollon77

@mattgas
Copy link

mattgas commented Oct 11, 2021

Yes, there is an exception:

Oct 11 19:31:44 raspberrypi bash[542]: ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]
Oct 11 19:31:44 raspberrypi kernel: [35843.789332] Alignment trap: not handling instruction f4430add at [<b6fa4b40>]
Oct 11 19:31:44 raspberrypi kernel: [35843.789341] 8<--- cut here ---
Oct 11 19:31:44 raspberrypi kernel: [35843.789361] Unhandled fault: alignment exception (0xa21) at 0x039f29c6
Oct 11 19:31:44 raspberrypi kernel: [35843.789375] pgd = 858c5790
Oct 11 19:31:44 raspberrypi kernel: [35843.789387] [039f29c6] *pgd=02dea003, *pmd=1ffeb2003

logged on a Pi4 with debian buster, Node.js: v10.24.1, NPM: 6.14.12, admin 4.2.2, javascript 5.2.13.....did some downgrading, but SIGBUS error still occurs.

@Apollon77
Copy link
Contributor

Second case with RPi 4 and such an memory alignment error ... looks more and more like a kernel issue to me

@Cheeseyo
Copy link

I installed raspi OS again, here ist the dmesg. I hope it is the information you need. I just started with raspi and iobroker and i'm not familiar with it. If you need more details, no problem..
dsmeg.txt
.

@UncleSamSwiss
Copy link
Owner

I installed raspi OS again, here ist the dmesg. I hope it is the information you need. I just started with raspi and iobroker and i'm not familiar with it. If you need more details, no problem..
dsmeg.txt
.

But you didn't install ioBroker, I guess. I can't see any error in your file.

@Cheeseyo
Copy link

ok, but it was running and the error showed up in the log. Maybe i did something wrong getting the log. Is there a how to get it?

@Cheeseyo
Copy link

Now i think i got a log for you
syslog.txt
.

@UncleSamSwiss
Copy link
Owner

We are narrowing down the issue.

Is everybody who sees this issue using a Raspberry Pi 4? Please let me know if you use a different device.

@Govraemd
Copy link

Govraemd commented Oct 12, 2021

We are narrowing down the issue.

Is everybody who sees this issue using a Raspberry Pi 4? Please let me know if you use a different device.

Hi, I'm using Pi 2B+
Iobroker is running inside docker on Loxberry

@mattgas
Copy link

mattgas commented Oct 12, 2021 via email

@UncleSamSwiss
Copy link
Owner

Good and bad news: we found the underlying issue, but as of right now it is not yet fixed:
websockets/bufferutil#137

@UncleSamSwiss
Copy link
Owner

UncleSamSwiss commented Oct 13, 2021

We have a temporary workaround for this issue:
https://forum.iobroker.net/post/687830

@UncleSamSwiss
Copy link
Owner

bufferutil version 4.0.5 has been released which fixes this issue.

You might have to uninstall and then reinstall the adapter to get the latest dependency.

@Sinus1986
Copy link
Author

Sinus1986 commented Oct 13, 2021 via email

@UncleSamSwiss
Copy link
Owner

What do you mean by "reinstall"? Did you remove the adapter completely or just the instance?

@Sinus1986
Copy link
Author

Sinus1986 commented Oct 13, 2021 via email

@UncleSamSwiss
Copy link
Owner

Do you have other adapters installed? Some that might also use WebSockets?

If yes, please uninstall all adapters and then reinstall one after the other.

If no, please uninstall ioBroker.loxone and then have a look at /opt/iobroker/node_modules: is there a folder called bufferutil? Please show the entire directory listing of /opt/iobroker/node_modules.

@Sinus1986
Copy link
Author

Sinus1986 commented Oct 13, 2021 via email

@UncleSamSwiss
Copy link
Owner

Please use your browser or the GitHub app on your Android phone and not emails to respond to this thread. There are no screenshots attached and I have to clean up every message you write as it contains the original message and your signature.

@geritsch
Copy link

Everyone is green again and there are no more errors. Now I can start playing around with the miniserver :) THX 👍

@Sinus1986
Copy link
Author

Sorry - attached the screens Screenshot_20211013_211732_com.sonelli.juicessh_edit_272489992856854.jpg

@Sinus1986
Copy link
Author

Screenshot_20211013_212051_com.sonelli.juicessh_edit_272478811169876.jpg

@Sinus1986
Copy link
Author

Screenshot_20211013_212153_com.sonelli.juicessh_edit_272464979278212.jpg

@Sinus1986
Copy link
Author

Screenshot_20211013_212222_com.sonelli.juicessh_edit_272454878398005.jpg

@Sinus1986
Copy link
Author

Screenshot_20211013_211743.jpg

@UncleSamSwiss
Copy link
Owner

@Sinus1986 can you please execute npm ls bufferutil in /opt/iobroker. We should see what other adapter's are using it.

@Sinus1986
Copy link
Author

Here the Screenshot Screenshot_20211014_095758.jpg

@UncleSamSwiss
Copy link
Owner

OK, so please uninstall the adapter again and then execute the command once more. You shouldn't see bufferutil anymore in the output.

@Sinus1986
Copy link
Author

Bufferutil is still there...
I did. Iobroker del loxone in shell, reinstalled loxone adapter...

@Sinus1986
Copy link
Author

Perfect - now I got it.. Thanks for your help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants