[Ovmsdev] Network stuck?

[Mark Webb-Johnson]

Steve,

That is mg_parse_address in mongoose.c.

Seems to be quite a few conditions can result in ‘cannot parse address’, but not all of them about actually parsing addresses.

Is memory ok? I suggest you use dns ‘8.8.8.8 1.1.1.1’ (rather than relying on access point dns servers), as that will cope better with a network interface switch.

Regards, Mark.

> On 21 Jun 2018, at 12:58 PM, Stephen Casner <casner at acm.org> wrote:
> 
> My OVMS v3.1 has been installed in the car for some hours and now the
> network operations are stuck in some way.  I detected this when I
> found that the app had no status for two hours.  When I connect to the
> USB console, I see the reason:
> 
> I (28236429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (28236429) ovms-server-v2: Status: Connecting...
> W (28254039) ovms-server-v2: Connection failed
> E (28254039) ovms-server-v2: Status: Error: Connection failed
> I (28254239) ovms-server-v2: Status: Disconnected
> I (28273429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (28273429) ovms-server-v2: Status: Connecting...
> W (28290959) ovms-server-v2: Connection failed
> E (28290959) ovms-server-v2: Status: Error: Connection failed
> I (28291159) ovms-server-v2: Status: Disconnected
> 
> And now, as I look, a variation:
> 
> I (28527429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (28527429) ovms-server-v2: Status: Connecting...
> E (28533869) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
> E (28533869) ovms-server-v2: Status: Error: Connection failed
> I (28547429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (28547429) ovms-server-v2: Status: Connecting...
> E (28553979) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
> E (28553979) ovms-server-v2: Status: Error: Connection failed
> 
> OVMS# network status
> Interface#3: pp3 (ifup=1 linkup=1)
>  IPv4: 10.170.41.247/255.255.255.255 gateway 10.64.64.64
> 
> Interface#2: ap2 (ifup=1 linkup=1)
>  IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1
> 
> Interface#1: st1 (ifup=1 linkup=1)
>  IPv4: 192.168.1.82/255.255.255.0 gateway 192.168.1.254
> 
> DNS: 192.168.1.254
> 
> Default Interface: st1 (192.168.1.82/255.255.255.0 gateway 192.168.1.254)
> OVMS# wifi status
> Power: on
> Mode: Access-Point + Client mode
> 
> STA SSID: Revelstoke
>  MAC: 30:ae:a4:43:9c:28
>  IP: 192.168.1.82/255.255.255.0
>  GW: 192.168.1.254
> 
> AP SSID: US33
>  MAC: 30:ae:a4:43:9c:29
>  IP: 192.168.4.1
>  AP Stations: 0
> 
> Anything else to look at before I reset?  The module does respond to
> ping, but not to the web browser nor ssh on the STA wifi.
> 
>                                                        -- Steve
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev