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.

Sign up for GitHub

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

Jump to bottom

Connectivity error while in session with PicoStill #190

Open
marcchabot opened this issue Jan 12, 2021 · 17 comments
Open

Connectivity error while in session with PicoStill #190

marcchabot opened this issue Jan 12, 2021 · 17 comments

Comments

@marcchabot
Copy link

I am unable to successfully complete a distillation because every 5-10 minutes or so, Z will give me a "Connectivity error" and alarm go on. I manually have to select Reconnect. It will reconnect but 5-10 minutes later same thing again.

Any fix for this?

Thank you.
@wiltdavi
Copy link
Contributor

I saw a similar behavior but it ran hours without an issue in my case so I just reconnected and continued. I did not get any logs so I did not open an issue for it. If you can reproduce it so quickly can you provided logs of the issue?

What is your setup? I was using a RPi 3 Model B with a Wi-Fi connection to the Z.

@tmack8001
Copy link
Collaborator

For some reason the Z has more wifi and/or network stability issues than any other device (surprising to me). If you have an ethernet port (or you can get a $10-15 USB<->ethernet adapter) I'd encourage anyone to go that route until this can be determined what the underlying issues are.

@marcchabot
Copy link
Author

marcchabot commented Jan 12, 2021 via email

@wiltdavi
Copy link
Contributor

@tmack8001 I tried to use the Ethernet connect to the Z but I was not able to get the PicoStill to start a session properly in this configuration. I was going to look into the logs but I have not done that yet. Should it work for the Z to connect to the PicoStill over Wi-Fi while the Z is connected to the RPi over Ethernet?

@tmack8001
Copy link
Collaborator

Not sure I have both connected over WiFi here with no issues so far 🤞 just trying to reproduce what others have mentioned.

We bridge the two interfaces (ap0 and eth0) explicitly as the ascii diagram on my blog post showed so they are still on the same network. The Z doesn't connect "WiFi" to the Still as then it would need to disconnect from out wireless network, but rather communicates to it via the network they both are attached to by IP address I'm fairly certain.

@tmack8001
Copy link
Collaborator

@marcchabot if you could restart and update the server (no need to power down use the option in system in the navbar).

I recently added a better logs experience. Use that to then post the nginx error log to this ticket would be helpful.

@marcchabot
Copy link
Author

marcchabot commented Jan 12, 2021 via email

@tmack8001
Copy link
Collaborator

@marcchabot don't think GitHub attached files from an email properly all the time. Best to do that via the website instead

@marcchabot
Copy link
Author

marcchabot commented Jan 12, 2021 via email •
edited
Loading

@tmack8001
Copy link
Collaborator

No @marcchabot I haven't gotten those, you can email them over to me as well if that is easier for you.

@tmack8001
Copy link
Collaborator

tmack8001 commented Jan 12, 2021 •
edited
Loading

or wait yea actually I see it now there is a link to the file in the latest commit I missed 🤦‍♂️. Or at least only the nginx.error.log

@tmack8001
Copy link
Collaborator

tmack8001 commented Jan 12, 2021 •
edited
Loading

As I suspected there are some communication failures between 2 pieces of technology within the server:

2021/01/12 09:25:08 [error] 411#411: *1 connect() failed (111: Connection refused) while connecting to upstream, 
client: 192.168.72.115, server: www.picobrew.com, request: "PUT /Vendors/input.cshtml?type=ZState&token=<token> HTTP/1.1", 
upstream: "http://127.0.0.1:8080/Vendors/input.cshtml?type=ZState&token=<token>", host: "www.picobrew.com"

However when I see this it only occurs right at server startup if I catch one process not fully started yet (or after doing a server update and restart task). Can you confirm if this is an ongoing problem even after the website of the raspberrypi server stabilizes after startup? If you can view the index page http://raspberrypi/ I classify that as stabilized.

I see you say this happens now every 20 minutes do you restart any electronics when this happens (the Z, the raspberrypi, or the PicoStill)?

@marcchabot
Copy link
Author

This is an ongoing problem. Rightr now, it's beeping every 5 mins or so. I gave plenty of time to the server to boot. I don't have to reatart anything, just select "try to reconnect" but 5 mins (10 if I'm lucky) I'll have that same error agasin. Here is todays' error log.

Thanks
nginx.error.log

@marcchabot
Copy link
Author

Could it be that Z is switching from ETH to Wifi and then giving me Connectivity error? Couldtry to disable Z wifi (by giving wrong password to PICOBREW AP so it stays on ethernet and not wifi?

@tmack8001
Copy link
Collaborator

@marcchabot I had another theory about what was going on, but unfortunately that error log shows that isn't the case. I had a suspicion that nginx (the http and https proxy in front of our server) is switching between ipv4 and ipv6 internally for talking to the python+flask service port, however all the upstream timeouts in that error log weren't from the Z unit itself and instead from your browser is which not great, but ok.

Could you also upload the flask+server logs? I want to put to rest any assumption that there was an error in the server vs having unstable connection to the server.

When you run non PicoStill sessions do you have issues (drain, rinse, brew, etc)? Should see a fairly frequent data log show up on the brew graphs with no visible gap of data being reported. Data is reported every minute or so should be obvious if there is any loss of connectivity.

When ethernet is enabled on the Z I'm fairly certain it takes user action to switch back to WiFi via the settings menu of the Z.

@marcchabot
Copy link
Author

Here is the other log you need.

As I'm just starting using your Pico server, I don't know if Z behavior is different with non-Still tasks. Will do some more tests and report back to you.
picobrew_pico.log

@tmack8001
Copy link
Collaborator

Ok in this I also don't see any reported errors. However, that doesn't necessarily mean anything either.

Jan 14 13:42:14 raspberrypi rc.local[386]: 127.0.0.1 - - [14/Jan/2021 13:42:14] "PUT /Vendors/input.cshtml?type=ZState&token=<z-uid> HTTP/1.0" 200 -
Jan 14 13:43:37 raspberrypi rc.local[386]: 127.0.0.1 - - [14/Jan/2021 13:43:37] "PUT /Vendors/input.cshtml?type=ZState&token=<z-uid> HTTP/1.0" 200 -
Jan 14 13:43:59 raspberrypi rc.local[386]: 127.0.0.1 - - [14/Jan/2021 13:43:59] "GET /API/PicoStill/getFirmwareAddress?uid=<still-uid>&version=0.0.30 HTTP/1.0" 200 -
Jan 14 13:44:17 raspberrypi rc.local[386]: 127.0.0.1 - - [14/Jan/2021 13:44:17] "POST /Vendors/input.cshtml?type=StillRequest&token=<z-uid> HTTP/1.0" 200 -
Jan 14 13:44:25 raspberrypi rc.local[386]: 127.0.0.1 - - [14/Jan/2021 13:44:25] "POST /Vendors/input.cshtml?type=StillRequest&token=<z-uid> HTTP/1.0" 200 -

What this log tells me though is that you didn't actually start a session just went through the clean acknowledgements. Did you start the session? If you did there should be some session log requests from the Z followed by minutely data log points in the graph of the water heating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tmack8001 @marcchabot @wiltdavi