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

MacOS: New server not functioning, get "connect: no route to host" error messages #17251

Open
1 task done
b394373 opened this issue Nov 14, 2024 · 13 comments
Open
1 task done

MacOS: New server not functioning, get "connect: no route to host" error messages #17251

b394373 opened this issue Nov 14, 2024 · 13 comments
Assignees
@andig
Labels
bug Something isn't working

Comments

@b394373
Copy link

b394373 commented Nov 14, 2024

Describe the bug

I have a working evcc server setup on an old Mac mini.

When I setup a new server on a new Mac mini M4 on the same network with the same configuration, it doesn't work even though the original server has been stopped.

I get "connect: no route to host" error messages, see log details below.

Steps to reproduce

  1. configured evcc
  2. started evcc
  3. not communicating with charger or meter
    ...

Configuration details

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: ea0538807bbd6a1f1895f7aecaad897d39d117ab3b4be64bd539c4e01e4c3b7a

interval: 30s # control cycle interval

meters:
- type: template
  template: fronius-solarapi-v1 
  usage: grid  
  host: 192.168.188.176  
  user: customer  
  name: grid1
- type: template
  template: fronius-solarapi-v1 
  usage: pv  
  host: 192.168.188.176  
  user: customer  
  name: pv2

chargers:
- type: template
  template: twc3 
  host: 192.168.188.163  
  name: wallbox3

loadpoints:
- title: Garage
  charger: wallbox3
  mode: off

site:
  title: My Home
  meters:
    grid: grid1
    pv:
    - pv2

Log details

[main ] INFO 2024/11/14 09:37:13 evcc 0.131.5
[main ] INFO 2024/11/14 09:37:13 using config file: /etc/evcc.yaml
[db ] INFO 2024/11/14 09:37:13 using sqlite database: /Users/Eugene/.evcc/evcc.db
[main ] INFO 2024/11/14 09:37:14 listening at :7070
[site ] INFO 2024/11/14 09:37:15 site config:
[site ] INFO 2024/11/14 09:37:15 meters: grid ✓ pv ✓ battery ✗
[site ] INFO 2024/11/14 09:37:15 grid: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/14 09:37:15 pv 1: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/14 09:37:15 vehicles:
[site ] INFO 2024/11/14 09:37:15 vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1 ] INFO 2024/11/14 09:37:15 loadpoint 1:
[lp-1 ] INFO 2024/11/14 09:37:15 mode: off
[lp-1 ] INFO 2024/11/14 09:37:15 charger: power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1 ] INFO 2024/11/14 09:37:15 meters: charge ✓
[lp-1 ] INFO 2024/11/14 09:37:15 charge: power ✓ energy ✗ currents ✓
[lp-1 ] DEBUG 2024/11/14 09:37:15 phase timer inactive
[lp-1 ] DEBUG 2024/11/14 09:37:15 pv timer inactive
[lp-1 ] ERROR 2024/11/14 09:37:15 charger enabled: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[site ] DEBUG 2024/11/14 09:37:15 ----
[lp-1 ] ERROR 2024/11/14 09:37:15 charge power: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[lp-1 ] ERROR 2024/11/14 09:37:16 charge currents: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[site ] ERROR 2024/11/14 09:37:17 pv 1 power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host
[site ] DEBUG 2024/11/14 09:37:17 pv power: 0W
[site ] ERROR 2024/11/14 09:37:17 grid power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host
[site ] DEBUG 2024/11/14 09:37:45 ----
[lp-1 ] ERROR 2024/11/14 09:37:45 charge power: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[lp-1 ] ERROR 2024/11/14 09:37:46 charge currents: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[site ] ERROR 2024/11/14 09:37:46 pv 1 power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host
[site ] DEBUG 2024/11/14 09:37:46 pv power: 0W
[site ] ERROR 2024/11/14 09:37:46 grid power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host

What type of operating system are you running?

Linux

Nightly build

  • I have verified that the issue is reproducible with the latest nightly build

Version

Mac-mini-M4 /etc % evcc -v evcc version 0.131.5
@b394373
Copy link
Author

b394373 commented Nov 14, 2024

When I input http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi/ with a browser on the Mac mini M4 I get the following reply;

{
"Body" : {
"Data" : {
"Inverters" : {
"1" : {
"DT" : 102,
"E_Day" : 8503,
"E_Total" : 46116400,
"E_Year" : 11705433,
"P" : 4979
}
},
"Site" : {
"E_Day" : 8503,
"E_Total" : 46116400,
"E_Year" : 11705433,
"Meter_Location" : "grid",
"Mode" : "meter",
"P_Akku" : null,
"P_Grid" : -564.28999999999996,
"P_Load" : -4414.71,
"P_PV" : 4979,
"rel_Autonomy" : 100,
"rel_SelfConsumption" : 88.666599718819043
},
"Version" : "12"
}
},
"Head" : {
"RequestArguments" : {},
"Status" : {
"Code" : 0,
"Reason" : "",
"UserMessage" : ""
},
"Timestamp" : "2024-11-14T08:17:51+10:00"
}
}

@b394373 b394373 closed this as completed Nov 14, 2024
@b394373 b394373 reopened this Nov 14, 2024
@b394373
Copy link
Author

b394373 commented Nov 14, 2024

Sorry, pressed the wrong button

@b394373
Copy link
Author

b394373 commented Nov 14, 2024

And yet when I run the server from the command line, I don't get any errors and it works

Mac-mini-M4 ~ % evcc -c evcc.yaml
[main ] INFO 2024/11/14 13:51:21 evcc 0.131.5
[main ] INFO 2024/11/14 13:51:21 using config file: evcc.yaml
[db ] INFO 2024/11/14 13:51:21 using sqlite database: /Users/Eugene/.evcc/evcc.db
[main ] INFO 2024/11/14 13:51:21 listening at :7070
[site ] INFO 2024/11/14 13:51:24 site config:
[site ] INFO 2024/11/14 13:51:24 meters: grid ✓ pv ✓ battery ✗
[site ] INFO 2024/11/14 13:51:24 grid: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/14 13:51:24 pv 1: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/14 13:51:24 vehicles:
[site ] INFO 2024/11/14 13:51:24 vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1 ] INFO 2024/11/14 13:51:24 loadpoint 1:
[lp-1 ] INFO 2024/11/14 13:51:24 mode: off
[lp-1 ] INFO 2024/11/14 13:51:24 charger: power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1 ] INFO 2024/11/14 13:51:24 meters: charge ✓
[lp-1 ] INFO 2024/11/14 13:51:24 charge: power ✓ energy ✗ currents ✓
[lp-1 ] DEBUG 2024/11/14 13:51:24 phase timer inactive
[lp-1 ] DEBUG 2024/11/14 13:51:24 pv timer inactive
[site ] DEBUG 2024/11/14 13:51:24 ----
[lp-1 ] DEBUG 2024/11/14 13:51:24 charge power: 0W
[lp-1 ] DEBUG 2024/11/14 13:51:24 charge currents: [0.3 0.2 0.1]A
[site ] DEBUG 2024/11/14 13:51:24 pv power: 6700W
[site ] DEBUG 2024/11/14 13:51:24 grid power: -4886W
[site ] DEBUG 2024/11/14 13:51:24 site power: -4886W
[lp-1 ] DEBUG 2024/11/14 13:51:24 charge voltages: [0 0 0]V
[lp-1 ] DEBUG 2024/11/14 13:51:24 charger status: B
[lp-1 ] INFO 2024/11/14 13:51:24 car connected
[lp-1 ] DEBUG 2024/11/14 13:51:24 vehicle api refresh
[lp-1 ] DEBUG 2024/11/14 13:51:24 pv timer elapse
[lp-1 ] DEBUG 2024/11/14 13:51:24 pv timer inactive
[main ] DEBUG 2024/11/14 13:51:24 vehicle status: B (BlueY)
[lp-1 ] INFO 2024/11/14 13:51:24 vehicle updated: unknown -> BlueY
[lp-1 ] DEBUG 2024/11/14 13:51:24 vehicle status: B
[lp-1 ] DEBUG 2024/11/14 13:51:24 vehicle soc: 100%
[lp-1 ] DEBUG 2024/11/14 13:51:24 vehicle soc limit: 100%
[lp-1 ] DEBUG 2024/11/14 13:51:24 vehicle range: 414km
[site ] DEBUG 2024/11/14 13:51:54 ----
[lp-1 ] DEBUG 2024/11/14 13:51:54 charge power: 0W
[lp-1 ] DEBUG 2024/11/14 13:51:54 charge currents: [0.3 0.2 0.1]A
[site ] DEBUG 2024/11/14 13:51:54 grid power: -4853W
[site ] DEBUG 2024/11/14 13:51:54 pv power: 6678W
[site ] DEBUG 2024/11/14 13:51:54 site power: -4853W
[lp-1 ] DEBUG 2024/11/14 13:51:54 vehicle odometer: 47639km
[lp-1 ] DEBUG 2024/11/14 13:51:54 charge voltages: [0 0 0]V
[lp-1 ] DEBUG 2024/11/14 13:51:54 charger status: B
[site ] DEBUG 2024/11/14 13:52:24 ----
[lp-1 ] DEBUG 2024/11/14 13:52:25 charge power: 0W
[lp-1 ] DEBUG 2024/11/14 13:52:25 charge currents: [0.3 0.2 0.1]A
[site ] DEBUG 2024/11/14 13:52:25 pv power: 6676W
[site ] DEBUG 2024/11/14 13:52:25 grid power: -4879W
[site ] DEBUG 2024/11/14 13:52:25 site power: -4879W
[lp-1 ] DEBUG 2024/11/14 13:52:25 charge voltages: [0 0 0]V
[lp-1 ] DEBUG 2024/11/14 13:52:25 charger status: B

@StefanSchoof
Copy link
Contributor

Ist das #16165 (comment)?

@b394373
Copy link
Author

b394373 commented Nov 14, 2024

So, the answer is that the problem is with Apple, awaiting a fix and the workaround is to run evcc in a shell, is that correct?

@andig
Copy link
Member

andig commented Nov 14, 2024

Das wird mit der nächsten Go Version gelöst. Wir upgraden fast immer sofort.

@andig andig closed this as completed Nov 14, 2024
@andig andig added the bug Something isn't working label Nov 14, 2024
@andig andig reopened this Nov 14, 2024
@andig andig self-assigned this Nov 14, 2024
@andig
Copy link
Member

andig commented Nov 14, 2024

Fixed in 039cbf5

@andig andig closed this as completed Nov 14, 2024
@jurgenfd
Copy link

jurgenfd commented Nov 16, 2024 •
edited
Loading

So, the answer is that the problem is with Apple, awaiting a fix and the workaround is to run evcc in a shell, is that correct?

How to easily "run evcc in a shell"? Just install from the tar-ball and run it from a shell. Remove the brew-based version.

@b394373
Copy link
Author

b394373 commented Nov 17, 2024

or simply run the following command;

Mac-mini-M4 ~ % nohup evcc -c evcc.yaml 2>/dev/null &
[1] 81564
Mac-mini-M4 ~ %

@b394373
Copy link
Author

b394373 commented Nov 17, 2024

"039cbf5 MacOS Sequoia: fix network errors" in 0.131.6 still results in "connect: no route to host" errors

[main ] INFO 2024/11/17 15:45:00 evcc 0.131.6
[main ] INFO 2024/11/17 15:45:00 using config file: /Users/Eugene/evcc.yaml
[db ] INFO 2024/11/17 15:45:00 using sqlite database: /Users/Eugene/.evcc/evcc.db
[main ] INFO 2024/11/17 15:45:02 listening at :7070
[site ] INFO 2024/11/17 15:45:04 site config:
[site ] INFO 2024/11/17 15:45:04 meters: grid ✓ pv ✓ battery ✗
[site ] INFO 2024/11/17 15:45:04 grid: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/17 15:45:04 pv 1: power ✓ energy ✗ currents ✗
[site ] INFO 2024/11/17 15:45:04 vehicles:
[site ] INFO 2024/11/17 15:45:04 vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1 ] INFO 2024/11/17 15:45:04 loadpoint 1:
[lp-1 ] INFO 2024/11/17 15:45:04 mode: pv
[lp-1 ] INFO 2024/11/17 15:45:04 charger: power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1 ] INFO 2024/11/17 15:45:04 meters: charge ✓
[lp-1 ] INFO 2024/11/17 15:45:04 charge: power ✓ energy ✗ currents ✓
[lp-1 ] DEBUG 2024/11/17 15:45:04 phase timer inactive
[lp-1 ] DEBUG 2024/11/17 15:45:04 pv timer inactive
[lp-1 ] ERROR 2024/11/17 15:45:04 charger enabled: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[site ] DEBUG 2024/11/17 15:45:04 ----
[lp-1 ] ERROR 2024/11/17 15:45:04 charge power: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[lp-1 ] ERROR 2024/11/17 15:45:05 charge currents: Get "http://192.168.188.163/api/1/vitals": dial tcp 192.168.188.163:80: connect: no route to host
[site ] ERROR 2024/11/17 15:45:06 pv 1 power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host
[site ] DEBUG 2024/11/17 15:45:06 pv power: 0W
[site ] ERROR 2024/11/17 15:45:06 grid power: Get "http://192.168.188.176/solar_api/v1/GetPowerFlowRealtimeData.fcgi": dial tcp 192.168.188.176:80: connect: no route to host
[site ] DEBUG 2024/11/17 15:45:34 ----

@andig andig changed the title New server not functioning, get "connect: no route to host" error messages MacOS: New server not functioning, get "connect: no route to host" error messages Nov 17, 2024
@andig
Copy link
Member

andig commented Nov 17, 2024

Looking it https://github.com/evcc-io/evcc/actions/runs/11871342079/job/33083793728 shows that the release version has been compiled with Go 1.23.3 which seems correct. I'm not sure why this wouldn't work.

Does anybody have an idea? Can we check if the generated binary has the expected properties?

@andig andig reopened this Nov 17, 2024
@StefanSchoof
Copy link
Contributor

From
golang/go#68678 (comment)

For previous releases (Go 1.22 and 1.23), we did a simpler backport, which requires a Go linker flag (-B gobuildid) to generate the UUID.

Is this linker flag set?

@andig
Copy link
Member

andig commented Nov 17, 2024

I wouldn‘t even know how 😮

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andig andig

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andig @StefanSchoof @jurgenfd @b394373