Can't connect to my local rshake with SWARM

hyvernaud · May 13, 2026, 3:52am

Hi,
I updated my SWARM configuration to access the Rshake network with FDSNWS. But I’m having trouble connecting to my local Rshake with SWARM. Here is the list of my configured servers
server=RS net;wsc:AM||||3600|1000|https://data.raspberryshake.org/fdsnws/dataselect/1/query|https://data.raspberryshake.org/fdsnws/station/1/query
server=EarthScope DMC;sls:rtserve.iris.washington.edu:18000
server=GEONET;wsc:NZ|*|10|HHZ|3600|1000|FDSNWS - Dataselect
server=AVO Winston;wws:pubavo1.wr.usgs.gov:16022:10000:1
server=myshake;wws:192.168.178.36:16032:15000:1

but when trying to connect to my shake

2026-05-12 05:39:53 ERROR - Error connecting to 192.168.178.36:16032 in WWSClient. (java.net.ConnectException)

The IP address is good
Envoi d’une requête ‘Ping’ 192.168.178.36 avec 32 octets de données :
Réponse de 192.168.178.36 : octets=32 temps=1 ms TTL=64
Réponse de 192.168.178.36 : octets=32 temps<1ms TTL=64
Réponse de 192.168.178.36 : octets=32 temps<1ms TTL=64
Réponse de 192.168.178.36 : octets=32 temps=1 ms TTL=64

Statistiques Ping pour 192.168.178.36:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 0ms, Maximum = 1ms, Moyenne = 0ms

regards,
Olivier

Stormchaser · May 13, 2026, 9:17pm

Hello Olivier,

Thank you for the detailed troubleshooting you’ve already done.

I’ve checked my SWARM Shake connection, and my configuration file is basically the same as yours, excluding the different Shake IP, naturally.

You probably have already tried, but you still get this issue after rebooting both Shake and computer you’re trying to connect from?

hyvernaud · May 13, 2026, 9:23pm

Yes, indeed, I rebooted both RF737 and RC78F Shakes and computer

Stormchaser · May 13, 2026, 9:33pm

All right. Then, on the computer you are using SWARM on, could you open Windows PowerShell and then execute the following?

Test-NetConnection -ComputerName 192.168.178.36 -Port 16032

This will tell us if we can communicate with the required port.

hyvernaud · May 14, 2026, 3:48am

Hi StormChaser ,

PS C:\Users\xxxxxxxxxx> Test-NetConnection -ComputerName 192.168.178.36 -Port 16032 AVERTISSEMENT : TCP connect to (192.168.178.36 : 16032) failed
ComputerName : 192.168.178.36
RemoteAddress : 192.168.178.36
RemotePort : 16032
InterfaceAlias : Ethernet
SourceAddress : 192.168.178.21
PingSucceeded : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False

It seems the connection to port 16032 failed. I don’t know how to open it.

regards,
Olivier

Stormchaser · May 14, 2026, 1:22pm

Hello again Olivier,

All right, thank you for the command output. Indeed, we need to understand why the communication via that port is not working.

Could you download the log files from the Shake (using the Logs button in rs.local/) and send them to me?

hyvernaud · May 14, 2026, 5:49pm

Hi StormChaser,

I have the same issue with my two rshakes : 192.168.178.36 and 192.168.178.25

With the first , no way to obtain the log files : Internal Server Error with the logs button.

“The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.”

With the second, I manage to obtain the log file.
RSH.RF737.2026-05-14T17_43_24.logs.tar (6.6 MB)

regards,
Olivier

Stormchaser · May 14, 2026, 8:08pm

Hello Olivier,

Thank you very much for the Shake logs and for trying on both. I have passed all info to our software team so that they can review it.

In the meantime, could you SSH into the Shake, and execute the following command?

ip addr show

Thank you.

hyvernaud · May 14, 2026, 9:02pm

for 192.168.178.36

myshake@raspberryshake:/opt $ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:6c:c7:8f brd ff:ff:ff:ff:ff:ff
inet 192.168.178.36/24 brd 192.168.178.255 scope global eth0
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:39:92:da brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:20:66:9e:c5 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.2/16 scope global docker0
valid_lft forever preferred_lft forever
inet 169.254.82.46/16 brd 169.254.255.255 scope global docker0
valid_lft forever preferred_lft forever
6: vethc5fa3bd@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 0e:02:d5:df:71:85 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 169.254.47.57/16 brd 169.254.255.255 scope global vethc5fa3bd
valid_lft forever preferred_lft forever
8: veth097d96b@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 26:41:74:81:1b:ae brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet 169.254.46.171/16 brd 169.254.255.255 scope global veth097d96b
valid_lft forever preferred_lft forever
10: veth6b3bfeb@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether ca:03:2b:7e:17:30 brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet 169.254.240.8/16 brd 169.254.255.255 scope global veth6b3bfeb
valid_lft forever preferred_lft forever
myshake@raspberryshake:/opt $

for 192.168.178.25

myshake@raspberryshake:/opt $ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:c5:f7:37 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.25/24 brd 192.168.178.255 scope global eth0
valid_lft forever preferred_lft forever
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:3a:df:76:58 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.2/16 scope global docker0
valid_lft forever preferred_lft forever
inet 169.254.200.152/16 brd 169.254.255.255 scope global docker0
valid_lft forever preferred_lft forever
6: veth5923fb6@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 0a:10:51:02:32:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.92.23/16 brd 169.254.255.255 scope global veth5923fb6
valid_lft forever preferred_lft forever
8: veth2a4ac63@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 52:7a:46:3e:1c:5e brd ff:ff:ff:ff:ff:ff
inet 169.254.234.115/16 brd 169.254.255.255 scope global veth2a4ac63
valid_lft forever preferred_lft forever
10: veth1dbdf10@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether b6:9f:92:02:f8:1d brd ff:ff:ff:ff:ff:ff
inet 169.254.233.79/16 brd 169.254.255.255 scope global veth1dbdf10
valid_lft forever preferred_lft forever
myshake@raspberryshake:/opt $

Stormchaser · May 17, 2026, 7:06pm

Thank you very much for the output Olivier!

I’ve passed it to our software team so that they can take a look at it. I’ll update you when I have news from them.

Stormchaser · May 18, 2026, 3:32pm

Hello again Olivier,

We have a solution for the issue you’ve highlighted. Here it is below:

Copy the attached set-dip script / pgm to the shake, to directory /tmp
Log into the shake via SSH
Execute the following commands:

> cd /tmp
> chmod a+x set-dip
> ./set-dip

3.1. The Shake will automatically reboot
set-dip (53.9 KB)

After the restart is complete, your SWARM installation should be able to acquire data from the Shake again.

Let us know how it goes!

Benjamin · May 20, 2026, 1:58am

Hi, Is this fix only for Olivier’s shake or will it work with anyone? I am also unable to connect to the shake with swarm.

hyvernaud · May 20, 2026, 3:45am

Many thanks to you, stormchaser, and your IT team. I applied your instructions to both Rshake instances, and I can now view my local signals with Swarm again.
Since I’m a bit curious, I’d like to know what the problem was and whether it’s likely to happen again. As a precaution, I’ve kept the set-dip command in the /tmp directory of my Rshakes.

Stormchaser · May 20, 2026, 4:36pm

Hello Benjamin,

Yes, this is a valid fix for any Shaker experiencing the same issue. Once applied, the fix persists, so there is no need to apply it again (unless one reburns the microSD card).

Stormchaser · May 20, 2026, 4:42pm

It was our pleasure hyvernaud, and thank you for bringing this up to our attention.

The cause of the issue was that, for some Shakes, identifying the Docker bridge (an element we use in the Shake OS) IP address could return two IPs, and OWS (responsible for providing data to the helicorder and SWARM) would consequently be unable to start because it was expecting only one.

This solution (which is permanent, no need to reapply it unless you reburn the microSD) sets the Docker IP to a single known value, thus addressing OWS requirements.

As I wrote in the message above, the next Shake OS (when out) will include a permanent fix to this issue, so there will be no need to manually apply it anymore.

Thank you again, and happy Shaking!