reef-pi connection problem

tutuss · Feb 25, 2021

hello, excuse me in advance for my english. i have a problem. I install reef-pi on a raspberry pi 3+. I use a screen hdmi to see information. I'm connect on localhost with 127.0.0.1. Everything was working well. But after a power cut the raspberry reboot and i'm impossible to reconnect at reef-pi.
I tried 'sudo systemctl status reef-pi.service' but reef-pi is active. ato run but i can't see something.
I tried 'http://localhost ' don't work
chromium say " this site is inaccessible 127.0.0.1 does not allow connection"
i'm thinking of a bug to reef-pi or raspberry
i need help
thank you in advance

Ranjib · Feb 25, 2021

Can you run ‘sudo systemctl restart reef-pi.service’ and see if t resolves. Check the logs for errors and share it here if the problem persist

tutuss · Feb 25, 2021

hi, thanks for your attention
i run 'sudo systemctl restart reef-pi.service' but nothing change. i re-install reef-pi with release but no change.

pi@reef-pi:~ $ sudo systemctl status reef-pi.service
● reef-pi.service - raspberry pi based reef tank controller
Loaded: loaded (/lib/systemd/system/reef-pi.service; enabled; vendor prese
Active: active (running) since Thu 2021-02-25 18:09:32 CET; 9min ago
Main PID: 369 (reef-pi)
Tasks: 13 (limit: 2062)
CGroup: /system.slice/reef-pi.service
└─369 /usr/bin/reef-pi daemon -config /etc/reef-pi/config.yaml

févr. 25 18:18:54 reef-pi reef-pi[369]: 2021/02/25 18:18:54 onTime 0 offTim
févr. 25 18:18:54 reef-pi reef-pi[369]: 2021/02/25 18:18:54 ato-subsystem: se
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 ato-subsystem: se
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 Euipment: 2 On: f
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 onTime 0 offTim
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 ato-subsystem: se
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 ato-subsystem: se
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 Euipment: 2 On: f
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 onTime 0 offTim
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 ato-subsystem: se
lines 1-18/18 (END)

about journal

pi@reef-pi:~ $ sudo journalctl -fu reef-pi.service
-- Logs begin at Thu 2019-02-14 11:11:59 CET. --
févr. 25 18:24:49 reef-pi reef-pi[369]: 2021/02/25 18:24:49 onTime 0 offTime 4096
févr. 25 18:24:49 reef-pi reef-pi[369]: 2021/02/25 18:24:49 ato-subsystem: sensor: flotteur usage: 4
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 ato-subsystem: sensor: flotteur state: 1
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 Euipment: 2 On: false
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 onTime 0 offTime 4096
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 ato-subsystem: sensor: flotteur usage: 4
févr. 25 18:24:51 reef-pi reef-pi[369]: 2021/02/25 18:24:51 ato-subsystem: sensor: flotteur state: 1
févr. 25 18:24:51 reef-pi reef-pi[369]: 2021/02/25 18:24:51 Euipment: 2 On: false
i don't understand

Ranjib · Feb 26, 2021

tutuss said:
hi, thanks for your attention
i run 'sudo systemctl restart reef-pi.service' but nothing change. i re-install reef-pi with release but no change.

pi@reef-pi:~ $ sudo systemctl status reef-pi.service
● reef-pi.service - raspberry pi based reef tank controller
Loaded: loaded (/lib/systemd/system/reef-pi.service; enabled; vendor prese
Active: active (running) since Thu 2021-02-25 18:09:32 CET; 9min ago
Main PID: 369 (reef-pi)
Tasks: 13 (limit: 2062)
CGroup: /system.slice/reef-pi.service
└─369 /usr/bin/reef-pi daemon -config /etc/reef-pi/config.yaml

févr. 25 18:18:54 reef-pi reef-pi[369]: 2021/02/25 18:18:54 onTime 0 offTim
févr. 25 18:18:54 reef-pi reef-pi[369]: 2021/02/25 18:18:54 ato-subsystem: se
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 ato-subsystem: se
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 Euipment: 2 On: f
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 onTime 0 offTim
févr. 25 18:18:55 reef-pi reef-pi[369]: 2021/02/25 18:18:55 ato-subsystem: se
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 ato-subsystem: se
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 Euipment: 2 On: f
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 onTime 0 offTim
févr. 25 18:18:56 reef-pi reef-pi[369]: 2021/02/25 18:18:56 ato-subsystem: se
lines 1-18/18 (END)

about journal

pi@reef-pi:~ $ sudo journalctl -fu reef-pi.service
-- Logs begin at Thu 2019-02-14 11:11:59 CET. --
févr. 25 18:24:49 reef-pi reef-pi[369]: 2021/02/25 18:24:49 onTime 0 offTime 4096
févr. 25 18:24:49 reef-pi reef-pi[369]: 2021/02/25 18:24:49 ato-subsystem: sensor: flotteur usage: 4
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 ato-subsystem: sensor: flotteur state: 1
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 Euipment: 2 On: false
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 onTime 0 offTime 4096
févr. 25 18:24:50 reef-pi reef-pi[369]: 2021/02/25 18:24:50 ato-subsystem: sensor: flotteur usage: 4
févr. 25 18:24:51 reef-pi reef-pi[369]: 2021/02/25 18:24:51 ato-subsystem: sensor: flotteur state: 1
févr. 25 18:24:51 reef-pi reef-pi[369]: 2021/02/25 18:24:51 Euipment: 2 On: false
i don't understand

It means reef-pi is running (Active: active (running)). Looks like your controller is running ato at 1 second check interval, with pca9685 driver (0-4096 ). You should be able to access the web ui. Can you run

Code:

sudo netstat -tulnp

and share the output? This will show all the ports that are in use, and reef-pi should come up with port 80

tutuss · Feb 27, 2021

hello !
pi@reef-pi:~ $ sudo netstat -tulnp
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 2538/vncserver-x11-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 502/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 15794/cupsd
tcp6 0 0 :::5900 :::* LISTEN 2538/vncserver-x11-
tcp6 0 0 :::22 :::* LISTEN 502/sshd
tcp6 0 0 ::1:631 :::* LISTEN 15794/cupsd
udp 0 0 0.0.0.0:68 0.0.0.0:* 451/dhcpcd
udp 0 0 0.0.0.0:631 0.0.0.0:* 15795/cups-browsed
udp 0 0 0.0.0.0:42125 0.0.0.0:* 389/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 389/avahi-daemon: r
udp6 0 0 :::41122 :::* 389/avahi-daemon: r
udp6 0 0 :::5353 :::* 389/avahi-daemon: r

Sorry, i'm not a specialist to servers
I can't connect on localhost and by wifi. The address on browser say 'unable to open page'
I think of a bug of raspberry

tutuss · Mar 2, 2021

Hi! I re-install all. (Raspberry and reef-pi) an it works again. I have access to reef-pi at distance and localhost. I don’t understand where are problems. I hope it won’t start again.

RJDaPirate · Mar 5, 2021

I have also been experiencing the same issue. My Reef Pi is still on the workbench as I add components. Whenever I need to power it off I have to repull and run the github install files. I should have mentioned I am running version 4.1.

Ranjib · Mar 6, 2021

tutuss said:
hello !
pi@reef-pi:~ $ sudo netstat -tulnp
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 2538/vncserver-x11-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 502/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 15794/cupsd
tcp6 0 0 :::5900 :::* LISTEN 2538/vncserver-x11-
tcp6 0 0 :::22 :::* LISTEN 502/sshd
tcp6 0 0 ::1:631 :::* LISTEN 15794/cupsd
udp 0 0 0.0.0.0:68 0.0.0.0:* 451/dhcpcd
udp 0 0 0.0.0.0:631 0.0.0.0:* 15795/cups-browsed
udp 0 0 0.0.0.0:42125 0.0.0.0:* 389/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 389/avahi-daemon: r
udp6 0 0 :::41122 :::* 389/avahi-daemon: r
udp6 0 0 :::5353 :::* 389/avahi-daemon: r

Sorry, i'm not a specialist to servers
I can't connect on localhost and by wifi. The address on browser say 'unable to open page'
I think of a bug of raspberry

I don't see reef-pi in this list. This is a problem. I don't know what's causing this, reef-pi is not listening in port 80, i,e. the Web UI part of reef-pi is not working. Only the controller is running.

Ranjib · Mar 6, 2021

RJDaPirate said:
I have also been experiencing the same issue. My Reef Pi is still on the workbench as I add components. Whenever I need to power it off I have to repull and run the github install files. I should have mentioned I am running version 4.1.

Start a thread if you want to debug this. I would love to assist. But not in this thread.

drnibz · Jun 23, 2021

Ranjib said:
I don't see reef-pi in this list. This is a problem. I don't know what's causing this, reef-pi is not listening in port 80, i,e. the Web UI part of reef-pi is not working. Only the controller is running.

I have the same issue I can't connect to my reef-pi via wifi, can't ssh and I can't ping it. the UI is working when I use pi desktop, and I can connect to the internet.
I tried ‘sudo systemctl restart reef-pi.service' no change
I tried 'sudo netstat -tulnp' reef-pi is listed and listening to port 80

how do I go by troubleshooting this?

thanks!

attiland · Jun 23, 2021

drnibz said:
I have the same issue I can't connect to my reef-pi via wifi, can't ssh and I can't ping it. the UI is working when I use pi desktop, and I can connect to the internet.
I tried ‘sudo systemctl restart reef-pi.service' no change
I tried 'sudo netstat -tulnp' reef-pi is listed and listening to port 80

how do I go by troubleshooting this?

thanks!

Can you ping it when on hard wired?
was it ever working? (Wi-Fi separation or firewall on PI or router)
Does it has a fix IP on Wi-Fi? If so if you set it to DHCP can you ping the new IP? (IP conflict)

drnibz · Jun 23, 2021

attiland said:
Can you ping it when on hard wired?
was it ever working? (Wi-Fi separation or firewall on PI or router)
Does it has a fix IP on Wi-Fi? If so if you set it to DHCP can you ping the new IP? (IP conflict)

It was working before. It’s a PI zero no hard wire (o should of mentioned that)
Let me figure out the IP conflict part and report back
Many thanks

Ranjib · Jun 25, 2021

drnibz said:
I have the same issue I can't connect to my reef-pi via wifi, can't ssh and I can't ping it. the UI is working when I use pi desktop, and I can connect to the internet.
I tried ‘sudo systemctl restart reef-pi.service' no change
I tried 'sudo netstat -tulnp' reef-pi is listed and listening to port 80

how do I go by troubleshooting this?

thanks!

what is the exact output of netstat? is it showing 0.0.0.0 as listening address?

Ranjib · Jun 25, 2021

drnibz said:
It was working before. It’s a PI zero no hard wire (o should of mentioned that)
Let me figure out the IP conflict part and report back
Many thanks

if you can ssh , then reef-pi should be working fine on that IP (assuming netstat shows reef-pi is listening). Can you share the error details in browers, like is it showing time out or just blank page? if its blank page check the javascript console of that browser for the error details (if any).

meanwhile check the reef-pi log (journalctl -u reef-pi.service). for any backend specific errors

Ranjib · Jun 25, 2021

tutuss said:
hello !
pi@reef-pi:~ $ sudo netstat -tulnp
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 2538/vncserver-x11-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 502/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 15794/cupsd
tcp6 0 0 :::5900 :::* LISTEN 2538/vncserver-x11-
tcp6 0 0 :::22 :::* LISTEN 502/sshd
tcp6 0 0 ::1:631 :::* LISTEN 15794/cupsd
udp 0 0 0.0.0.0:68 0.0.0.0:* 451/dhcpcd
udp 0 0 0.0.0.0:631 0.0.0.0:* 15795/cups-browsed
udp 0 0 0.0.0.0:42125 0.0.0.0:* 389/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 389/avahi-daemon: r
udp6 0 0 :::41122 :::* 389/avahi-daemon: r
udp6 0 0 :::5353 :::* 389/avahi-daemon: r

Sorry, i'm not a specialist to servers
I can't connect on localhost and by wifi. The address on browser say 'unable to open page'
I think of a bug of raspberry

reef-pi is not running in your pi. whats the output of

Code:

sudo systemctl status reef-pi.service

and `journalctl -u reef-pi.service`

Ranjib · Jun 25, 2021

RJDaPirate said:
I have also been experiencing the same issue. My Reef Pi is still on the workbench as I add components. Whenever I need to power it off I have to repull and run the github install files. I should have mentioned I am running version 4.1.

are you using kasa driver? If it's reproducible, we should be able to fix it. If it's a bug, this is a very serious issue, but i think we are missing something here, i.e. some other fix is required, outside reef-pi code.

drnibz · Jun 25, 2021

Ranjib said:
if you can ssh , then reef-pi should be working fine on that IP (assuming netstat shows reef-pi is listening). Can you share the error details in browers, like is it showing time out or just blank page? if its blank page check the javascript console of that browser for the error details (if any).

meanwhile check the reef-pi log (journalctl -u reef-pi.service). for any backend specific errors

I got it to work. The issue was a Tinda (range extender) it was always connected to it but not sure why it decided to block it (maybe because it got switched to the secondary node)
Anyways I connect my pi directly to my modem bypassing the range extender and all is good.
Thanks!

frekimed · Jul 12, 2021

I've been having a similar issue for the past few months. It seems to crop up when the raspberry pi cycles for whatever reason. I will get the

Code:

ERR_CONNECTION_REFUSED

or

Code:

DNS_PROBE_FINISHED_NXDOMAIN

error on the webpage. Typically I have been able to get it to resolve by using

Code:

sudo systemctl restart reef-pi.service

, although once recently I had to resort to resetting the database. In all of these instances, I'm able to SSH into the raspberry pi just fine.

Today, resetting the service isn't working. Here was the output I got:

Code:

2021/07/12 15:39:13 ERROR: Failed to initialize i2c. Error: open /dev/i2c-1: no such file or directory
2021/07/12 15:39:13 driver-subsystem: registering driver id: rpi Name: Raspberry Pi
2021/07/12 15:39:13 INFO: equipment subsystem: Finished syncing all equipment
2021/07/12 15:39:13 Successfully started subsystem: equipment
2021/07/12 15:39:13 Successfully started subsystem: ato
2021/07/12 15:39:13 Successfully started subsystem: temperature
2021/07/12 15:39:13 Successfully started subsystem: macro
2021/07/12 15:39:13 Successfully started subsystem: timers
2021/07/12 15:39:13 Successfully started subsystem: system
2021/07/12 15:39:13 reef-pi is up and running
2021/07/12 15:39:13 ERROR: health checker. Failed to load usage. Error: Item 'health_stats' does not exist in bucket 'reef-pi'
2021/07/12 15:39:13 Starting health checker
2021/07/12 15:39:13 Starting http server at: 0.0.0.0:80
Methods: [GET]
2021/07/12 15:39:13 API Doc path: /api/settings
2021/07/12 15:39:13 ERROR: Failed to run http server. Error: listen tcp 0.0.0.0:80: bind: permission denied

Any thoughts? This is a frustrating thing to deal with every few days. I was tempted to try installing Apache to see if that fixed the failed http server issue, but I figured I should just ask first.

Thanks!

attiland · Jul 13, 2021

frekimed said:
I've been having a similar issue for the past few months. It seems to crop up when the raspberry pi cycles for whatever reason. I will get the

Code:

ERR_CONNECTION_REFUSED

or

Code:

DNS_PROBE_FINISHED_NXDOMAIN

error on the webpage. Typically I have been able to get it to resolve by using

Code:

sudo systemctl restart reef-pi.service

, although once recently I had to resort to resetting the database. In all of these instances, I'm able to SSH into the raspberry pi just fine.

Today, resetting the service isn't working. Here was the output I got:

Code:

2021/07/12 15:39:13 ERROR: Failed to initialize i2c. Error: open /dev/i2c-1: no such file or directory 2021/07/12 15:39:13 driver-subsystem: registering driver id: rpi Name: Raspberry Pi 2021/07/12 15:39:13 INFO: equipment subsystem: Finished syncing all equipment 2021/07/12 15:39:13 Successfully started subsystem: equipment 2021/07/12 15:39:13 Successfully started subsystem: ato 2021/07/12 15:39:13 Successfully started subsystem: temperature 2021/07/12 15:39:13 Successfully started subsystem: macro 2021/07/12 15:39:13 Successfully started subsystem: timers 2021/07/12 15:39:13 Successfully started subsystem: system 2021/07/12 15:39:13 reef-pi is up and running 2021/07/12 15:39:13 ERROR: health checker. Failed to load usage. Error: Item 'health_stats' does not exist in bucket 'reef-pi' 2021/07/12 15:39:13 Starting health checker 2021/07/12 15:39:13 Starting http server at: 0.0.0.0:80 Methods: [GET] 2021/07/12 15:39:13 API Doc path: /api/settings 2021/07/12 15:39:13 ERROR: Failed to run http server. Error: listen tcp 0.0.0.0:80: bind: permission denied

Any thoughts? This is a frustrating thing to deal with every few days. I was tempted to try installing Apache to see if that fixed the failed http server issue, but I figured I should just ask first.

Thanks!

Looks like corruption to me. Permissions don’t just change. I might be wrong but at this point I would backup and reinstall and would consider using different memory card or external SSD