Hello Stromchaser,
The problem I mentioned in my previous post went away without us knowing why.
Currently our shakes are Not Connected:
|Data Producer|:|ON|
|Data Consumer|:|ON|
|Off-line Mode|:|OFF|
|Data Forwarding|:|ON|
|Server Connection|:|Not Connected|
We can ping 144.91.66.87, but the ports 55555-55556 seem to be closed
myshake@raspberryshake:/opt $ nc -zvw5 144.91.66.87 55555
nc: connect to 144.91.66.87 port 55555 (tcp) timed out: Operation now in progress
myshake@raspberryshake:/opt $ nc -zvw5 144.91.66.87 55556
nc: connect to 144.91.66.87 port 55556 (tcp) timed out: Operation now in progress
There was not change of the configuration on our devices. The ISP says these ports related to the IP of our device are open on their network.
Therefore, I would like to ask your help.
Thank you very much once more.
logs (2.9 MB)
1 Like
Hello konstantinos,
Thank you for the new details and the logs from the Shake. It seems that, at first, the Shake cannot find any internet connection:
2024 165 07:13:06: Network detection failed, unable to curl or ping common sites
2024 165 07:13:06: No internet connection found
2024 165 07:13:17: Network detection failed, unable to curl or ping common sites
2024 165 07:13:20: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
However, this seems to solve itself later, as the Shake can find a NTP server for time synchronization without further hassles.
From the results of your port test, it appears that ports 55555 and 55556 are closed. Have you checked if, for any reason, your router configuration has been reset or if the ports have been closed by whatever protocol the router has (there was a case like this in the past)?
Have you also tried turning off the Shake, restarting the router, and then turning on the Shake again to see if anything changes?
As a last resort, you could try to bring your router back to factory settings (there should be a way to do so via the admin panel) and then re-add the port exceptions to see if they now remain.
1 Like
Dear Stormchaser,
Thank you very much for your help.
The router still has the same settings as when the Shake was connected. The router is also programmed to reboot automatically a few times per day. Moreover, I have manually rebooted the Shake (through its web interface) a few times over the last few days, but it remains Not Connected.
Somehow, today, I get this
myshake@raspberryshake:/opt $ nc -zvw5 144.91.66.87 55555
Connection to 144.91.66.87 55555 port [tcp/] succeeded!
myshake@raspberryshake:/opt $ nc -zvw5 144.91.66.87 55556
Connection to 144.91.66.87 55556 port [tcp/] succeeded!
It is difficult to find out what closes and opens these ports. Perhaps there are parts of the network between the Shake and the server that are out of the control of the ISP.
Also, the router often loses the mobile internet connection. Perhaps we can assume that this is why the log has that entry.
Would you recommend programming our Shakes to reboot automatically? Would this help?
Thanks once more.
We appreciate very much your support.
2 Likes
Hello konstantinos,
Yes, the situation appears quite erratic, which generates the service connection discontinuities that you are seeing.
I think that the loss of mobile internet connection you describe could be the reason the ports are “closing” and “opening” again. You could also set up the Shake to reboot daily, and see if this fixes your problem. Here’s a guide on how to do it:
To use a more familiar crontab editor in sudo, execute this after logging into the Shake:
sudo EDITOR=nano crontab -e
You will then get an empty file; this is OK. Copy and paste the following (after copying, a single right-click on the black screen should be enough):
0 2 * * * /sbin/shutdown -r now
Then save and exit the crontab editor with Ctrl+X , then Y to confirm, and finally Enter .
To check that the crontab has been modified successfully, you can see its contents with:
sudo crontab -l
Also, in case you’re not familiar with cronjob syntax, here’s a summarized explanation:
Each part has a specific meanig, allowing you to schedule tasks on a recurring basis.
0 2 * * * - This part of the line specifies when the cron job will run.
0 - Minute (0-59)2 - Hour (0-23, where 2 refers to 2 AM)* - Day of the month (1-31)* - Month (1-12)* - Day of the week (0-7, where both 0 and 7 represent Sunday)
/sbin/shutdown - This is the command that is being scheduled.-r - This is an option for the shutdown command and it stands for reboot.now specifies that the shutdown and reboot should happen immediately.
So, the entire line 0 2 * * * /sbin/shutdown -r now schedules a reboot at 2 AM every day.