[Ovmsdev] Server v2 hang / crash / ?
Michael Balzer
dexter at expeedo.de
Mon Mar 19 06:54:53 HKT 2018
Greg & Steve,
that's again mDNS. My module has now, without mDNS, been running for over four hours with many reconnects and no problems at all.
There is an mDNS fix upstream esp-idf, but I don't think that is related to our issue: c68fd9d54535f8123b2f63d1061114eff9f77c1b
We need to update esp-idf, but it's too late now for the first factory image. Better just exclude mDNS for now.
I've pushed my workaround for the AP mode startup in OvmsServerV2::NetUp() -- it works, but as Mark said, we certainly need to revise the network init procedures.
I'm off for today. Besides the mDNS issue I think we've got a very usable first release.
Regards,
Michael
Am 18.03.2018 um 23:32 schrieb Greg D.:
> So, the stuck v2 server occurred again. Went off to so some other things, came back to find it wasn't connected. Stopped and started, but the start never
> returned. I toggled the wifi hotspot that it was connected through (confirmed on the hotspot side), but it never reconnected. Disconnecting and reconnecting
> the simple_monitor; still no prompt, no response to the keyboard. Presume it's stuck in a loop somewhere, with the lights turned out. No idea how to get its
> attention at this point, to find out what it's doing...
>
> Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
> I (4161) wifi: n:1 1, o:1 0, ap:1 1, sta:1 0, prof:1
> I (4821) wifi: state: init -> auth (b0)
> I (4831) wifi: state: auth -> auth (4a0)
> I (5821) wifi: state: auth -> init (2)
> I (5821) wifi: n:1 0, o:1 1, ap:1 1, sta:1 0, prof:1
> I (11451) simcom: State timeout, transition to 2
> I (11451) simcom: State: Enter PoweringOn state
> I (11451) simcom: Power Cycle
> I (12611) housekeeping: System considered stable (free: 41816 bytes)
> I (13281) wifi: n:1 1, o:1 0, ap:1 1, sta:1 0, prof:1
> I (13291) wifi: state: init -> auth (b0)
> I (13301) wifi: state: auth -> assoc (0)
> I (13311) wifi: state: assoc -> run (10)
> I (13381) wifi: connected with gregnet3, channel 1
> I (14401) event: sta ip: 192.168.43.49, mask: 255.255.255.0, gw: 192.168.43.1
> I (14401) netmanager: Set DNS#0 9.9.9.9
> I (14401) netmanager: Set DNS#1 8.8.8.8
> I (14401) netmanager: Interface priority is st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
> I (14401) time: Starting SNTP client
> I (14411) ovms-mdns: Restarting MDNS service
> I (14441) esp32wifi: WiFi UP with SSID: gregnet3, MAC: 30:ae:a4:37:1b:64, IP: 192.168.43.49, mask: 255.255.255.0, gw: 192.168.43.1
> I (17571) simcom: State: Enter PoweredOn state
> I (37471) simcom: State: Enter MuxStart state
> I (37471) gsm-mux: Start MUX
> I (37481) gsm-mux: Channel #0 is open
> I (37491) gsm-mux: Channel #1 is open
> I (37491) gsm-mux: Channel #2 is open
> I (37501) gsm-mux: Channel #3 is open
> I (37511) gsm-mux: Channel #4 is open
> I (38451) simcom: State: Enter NetWait state
> I (48471) simcom: CREG Network Registration: RegisteredRoaming
> I (49451) simcom: State: Enter NetStart state
> I (50491) simcom: PPP Connection is ready to start
> I (51451) simcom: State: Enter NetMode state
> I (51451) gsm-ppp: Initialising...
> I (54551) gsm-ppp: StatusCallBack: None
> I (54551) gsm-ppp: status_cb: Connected
> I (54551) gsm-ppp: our_ipaddr = 10.170.146.142
> I (54551) gsm-ppp: his_ipaddr = 10.64.64.64
> I (54561) gsm-ppp: netmask = 255.255.255.255
> I (54561) gsm-ppp: our6_ipaddr = ::
> I (54561) netmanager: Set DNS#0 9.9.9.9
> I (54561) netmanager: Set DNS#1 8.8.8.8
> I (54561) netmanager: Interface priority is st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
> I (54561) time: Starting SNTP client
> I (54561) ovms-mdns: Restarting MDNS service
> W (682451) simcom: 3 minutes since last MUX rx frame - assume MUX has failed
> I (682451) gsm-ppp: Shutting down (soft)...
> I (682451) netmanager: Interface priority is st1 (192.168.43.49/255.255.255.0 <http://192.168.43.49/255.255.255.0> gateway 192.168.43.1)
> I (682451) time: Restarting SNTP client
> I (682451) ovms-server-v2: Network is reconfigured, so disconnect network connection
> I (682451) ovms-mdns: Restarting MDNS service
> OVMS >
> OVMS >
> OVMS > server v2 status
> Starting
> OVMS > server v2 stop
> Stopping OVMS Server V2 connection (oscv2)
> OVMS > server v2 status
> OVMS v2 server has not been started
> OVMS > server v2 start
> Launching OVMS Server V2 connection (oscv2)
>
> --- exit ---
> greg at linux-0rpb:~/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3> make simple_monitor
> --- forcing DTR inactive
> --- forcing RTS inactive
> --- Miniterm on /dev/ttyUSB0 115200,8,N,1 ---
> --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
>
>
>
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180318/34c89143/attachment.htm>
More information about the OvmsDev
mailing list