I have read the variety of issues in other posts on this connection issue and have tried them all. I can ping into the github updating directory, so firewall does not seem like an issue. I was accessing just fine, then tried to enable a static IP in settings (gear); this failed and defaulted back to DHCP. However, since that attempt, it has not wanted to connect to server. Data producer and data consumer as well as data forwarding are all ON. Attached is the log file. See if it is helpful in showing what I need to do. I was going to re-install the entire program, but decided to try asking first. -Mario (AM.SDE97)
RSH.RDE97.2025-01-08T10_18_32.logs.tar (3.3 MB)
1 Like
Hello Mario, and welcome to the community!
Thank you for the logs from your Shake. Indeed, the instrument cannot find a network while it is booting up, as shown in these lines:
2025 008 10:17:22: Network detection failed, unable to curl or ping common sites
2025 008 10:17:22: No internet connection found
2025 008 10:17:22: Network detection failed, unable to curl or ping common sites
Could I then please ask you to log into the Shake via SSH (if needed, instructions on how to do so can be found here: How to access your Raspberry Shake’s computer via ssh), execute the following two commands:
cat /etc/dhcpcd.confcat /etc/resolv.conf
and post their output here? Thank you!
Here is output for these two commands:
myshake@raspberryshake:/opt $ cat /etc/dhcpcd.conf
interface eth0
static domain_name_servers=8.8.8.8
static ip_address=192.168.2.228/
static routers=
static domain_name_servers=192.168.2.1
A sample configuration for dhcpcd.
See dhcpcd.conf(5) for details.
Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
Inform the DHCP server of our hostname for DDNS.
Use the hardware address of the interface for the Client ID.
clientid
or
Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid
Persist interface configuration when dhcpcd exits.
persistent
Rapid commit support.
Safe to enable by default because it requires the equivalent option set
on the server to actually work.
option rapid_commit
A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
Most distributions have NTP support.
option ntp_servers
Respect the network MTU.
Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
A ServerID is required by RFC2131.
require dhcp_server_identifier
Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
A hook script is provided to lookup the hostname if not set by the DHCP
server, but it should not be run by default.
#nohook loo
denyinterfaces wlan0myshake@raspberryshake:/opt $ cat /etc/resolv.conf
Generated by resolvconf
nameserver 192.168.2.1
nameserver 8.8.4.4
nameserver 180.76.76.76
Hello SRAF, thank you for the files.
The issue is that there is no specified static router, and the Shake cannot find the proper gateway to reach the wider internet.
To fix this, open the file again with:
sudo nano /etc/dhcpcd.conf
Then fill in the static router line with your router gateway address (it should be the same IP address as the line below, but check with your local configuration to be sure).
Save the file with the sequence:
Ctrl+X, Y, Enter
To make sure those changes took hold, restart the service with:
sudo service dhcpcd restart
Check the output file with:
nano /etc/resolv.conf
Lastly, restart the shake with sudo reboot.
Now, your Shake should be able to connect. If not, then download the new log, copy the new output from the dhcpcd and resolv files, and post all here.
Thank you.
That did it!! Thank you. One last question before I close this thread (let me know if I need to start new threat for this)… I have this installed on a 500 GB SSD drive that is attached to the RS but it appears to be only still using the internal mini card; On the system info it says Disk Usage is 12% - 25.0 Gb available. How do I make the entire 500 GB from the SSD available for data storage? -Mario
1 Like
Great to read that Mario. You’re more than welcome!
We can continue here, no worries. Regarding your SSD drive, you’ll have to “tell” the Shake OS to start using this new storage. Otherwise, the instrument will continue to use the standard microSD card.
We have a guide for external USB storage drives here: How to mount a USB to store the waveform archive; maybe you can adapt it so that your Shake recognizes and starts to use the SSD you’ve connected.