This evening I connected my new OVMS v3.1 to my laptop and went through the setup wizard. That seemed to go smoothly. I copied over my ssh key and things seemed to be working fine. I installed an SD card so I could do logging if needed, and then unplugged the module to install it in the car. But it didn't come up! After I brought it back to the desk and connected to the laptop again, I see a message on the console that it has factory reset itself. What are the ways to trigger a factory reset? I must have unintentionally hit one. -- Steve
SDCARD factoryreset.txt Hold the program button down for several seconds Command-line Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there? Regards, Mark.
On 20 Jun 2018, at 3:56 PM, Stephen Casner <casner@acm.org> wrote:
This evening I connected my new OVMS v3.1 to my laptop and went through the setup wizard. That seemed to go smoothly. I copied over my ssh key and things seemed to be working fine. I installed an SD card so I could do logging if needed, and then unplugged the module to install it in the car. But it didn't come up!
After I brought it back to the desk and connected to the laptop again, I see a message on the console that it has factory reset itself.
What are the ways to trigger a factory reset? I must have unintentionally hit one.
-- Steve _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Mark, Thanks for the prompt reply.
1. SDCARD factoryreset.txt 2. Hold the program button down for several seconds 3. Command-line
I certainly didn't intentionally do 1 or 3. I do have the module installed in the 3D-printed case for the v3.0 module that I have modified with a plastic button extension that allows me to push the reset button with the module enclosed in the case. (I mentioned this a while back; the extension is the plastic part that performed the same role in a defunct GFCI plug on a hair dryer.) It is conceivable that this extension pushed on the program button instead of the reset button, but that is not likely because of the physical geometry and the button is still working properly as a reset.
Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there?
We don't have any "shutdown" operation to stop the module cleanly, so after the configuration I just unplugged it from the USB cable thereby removing power. Is there some likelihood that /store would not have been stable? As I mentioned, when I brought the module back to my desk after it did not come up in the car, I saw this: W (550) esp32wifi: AutoInit: factory reset detected, starting public AP net 'OVMS' with password 'OVMSinit' A full log via USB is attached in case there might be anything interesting in it. It shows the session where I did the wizard setup initially, then the session where I brought it back and found it back to factory reset, then a third session where I disconnected from power and plugged back in without loss of the config. -- Steve
It's always the missing log… your logs look perfectly normal, no hint of anything going wrong on the first setup. Option 2 can be excluded if you had the SD inserted all the time, as the button status is only checked when no SD is inserted. Regards, Michael Am 20.06.2018 um 21:37 schrieb Stephen Casner:
Mark,
Thanks for the prompt reply.
1. SDCARD factoryreset.txt 2. Hold the program button down for several seconds 3. Command-line I certainly didn't intentionally do 1 or 3. I do have the module installed in the 3D-printed case for the v3.0 module that I have modified with a plastic button extension that allows me to push the reset button with the module enclosed in the case. (I mentioned this a while back; the extension is the plastic part that performed the same role in a defunct GFCI plug on a hair dryer.) It is conceivable that this extension pushed on the program button instead of the reset button, but that is not likely because of the physical geometry and the button is still working properly as a reset.
Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there? We don't have any "shutdown" operation to stop the module cleanly, so after the configuration I just unplugged it from the USB cable thereby removing power. Is there some likelihood that /store would not have been stable?
As I mentioned, when I brought the module back to my desk after it did not come up in the car, I saw this:
W (550) esp32wifi: AutoInit: factory reset detected, starting public AP net 'OVMS' with password 'OVMSinit'
A full log via USB is attached in case there might be anything interesting in it. It shows the session where I did the wizard setup initially, then the session where I brought it back and found it back to factory reset, then a third session where I disconnected from power and plugged back in without loss of the config.
-- Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Michael, Thanks for reviewing the log. Did you notice the part in the second session (second time doing the wizard) where there were multiple instances of this message: W (38852769) webserver: HandleLogin: auth failure for username 'admin' This was while I was successfully logged into the webserver and in one of the wizard steps where the wizard is repeatedly querying for progress. I was able to go to the status page after that without having to authenticate again. This seems strange. Oh, I have an idea: I plugged in my v3.0 module so I could get the ssh key from its config, and it may have brought up AP with the same SSID. I don't know what happens to the client if there are two APs competing in that way. -- Steve On Wed, 20 Jun 2018, Michael Balzer wrote:
It's always the missing log... your logs look perfectly normal, no hint of anything going wrong on the first setup.
Option 2 can be excluded if you had the SD inserted all the time, as the button status is only checked when no SD is inserted.
Regards, Michael
Am 20.06.2018 um 21:37 schrieb Stephen Casner:
Mark,
Thanks for the prompt reply.
1. SDCARD factoryreset.txt 2. Hold the program button down for several seconds 3. Command-line I certainly didn't intentionally do 1 or 3. I do have the module installed in the 3D-printed case for the v3.0 module that I have modified with a plastic button extension that allows me to push the reset button with the module enclosed in the case. (I mentioned this a while back; the extension is the plastic part that performed the same role in a defunct GFCI plug on a hair dryer.) It is conceivable that this extension pushed on the program button instead of the reset button, but that is not likely because of the physical geometry and the button is still working properly as a reset.
Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there? We don't have any "shutdown" operation to stop the module cleanly, so after the configuration I just unplugged it from the USB cable thereby removing power. Is there some likelihood that /store would not have been stable?
As I mentioned, when I brought the module back to my desk after it did not come up in the car, I saw this:
W (550) esp32wifi: AutoInit: factory reset detected, starting public AP net 'OVMS' with password 'OVMSinit'
A full log via USB is attached in case there might be anything interesting in it. It shows the session where I did the wizard setup initially, then the session where I brought it back and found it back to factory reset, then a third session where I disconnected from power and plugged back in without loss of the config.
-- Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
I think the AutoInit: factory reset detected, starting public AP net 'OVMS' with password ‘OVMSinit’ message is perhaps misleading. It isn’t specifically detecting a factory reset. More that the auto/wifi.mode is “ap” (which is the default if that parameter has not been defined), and that auto/wifi.ssid.ap is undefined, and that wifi.ap/OVMS is empty, and that there is no module password defined). I did have one report of a user who could not save his config settings. Supposedly he configured the module, unplugged it, moved it to the car, plugged it in, and it was back to factory defaults. I had him do a ‘module factory reset’ to make sure the config partition was correctly formatted. That solved his problem. But, if it was a config mounting problem we would see that reported in the logs around the point "ovms_main: Mounting CONFIG…”. Yours looks clean. Regards, Mark.
On 21 Jun 2018, at 4:45 AM, Stephen Casner <casner@acm.org> wrote:
Michael,
Thanks for reviewing the log. Did you notice the part in the second session (second time doing the wizard) where there were multiple instances of this message:
W (38852769) webserver: HandleLogin: auth failure for username 'admin'
This was while I was successfully logged into the webserver and in one of the wizard steps where the wizard is repeatedly querying for progress. I was able to go to the status page after that without having to authenticate again. This seems strange.
Oh, I have an idea: I plugged in my v3.0 module so I could get the ssh key from its config, and it may have brought up AP with the same SSID. I don't know what happens to the client if there are two APs competing in that way.
-- Steve
On Wed, 20 Jun 2018, Michael Balzer wrote:
It's always the missing log... your logs look perfectly normal, no hint of anything going wrong on the first setup.
Option 2 can be excluded if you had the SD inserted all the time, as the button status is only checked when no SD is inserted.
Regards, Michael
Am 20.06.2018 um 21:37 schrieb Stephen Casner:
Mark,
Thanks for the prompt reply.
1. SDCARD factoryreset.txt 2. Hold the program button down for several seconds 3. Command-line I certainly didn't intentionally do 1 or 3. I do have the module installed in the 3D-printed case for the v3.0 module that I have modified with a plastic button extension that allows me to push the reset button with the module enclosed in the case. (I mentioned this a while back; the extension is the plastic part that performed the same role in a defunct GFCI plug on a hair dryer.) It is conceivable that this extension pushed on the program button instead of the reset button, but that is not likely because of the physical geometry and the button is still working properly as a reset.
Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there? We don't have any "shutdown" operation to stop the module cleanly, so after the configuration I just unplugged it from the USB cable thereby removing power. Is there some likelihood that /store would not have been stable?
As I mentioned, when I brought the module back to my desk after it did not come up in the car, I saw this:
W (550) esp32wifi: AutoInit: factory reset detected, starting public AP net 'OVMS' with password 'OVMSinit'
A full log via USB is attached in case there might be anything interesting in it. It shows the session where I did the wizard setup initially, then the session where I brought it back and found it back to factory reset, then a third session where I disconnected from power and plugged back in without loss of the config.
-- Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Steve, I guess your browser then received about half of the responses from the old module, so it continuosly switched authentication between the two modules. Regards, Michael Am 20.06.2018 um 22:45 schrieb Stephen Casner:
Michael,
Thanks for reviewing the log. Did you notice the part in the second session (second time doing the wizard) where there were multiple instances of this message:
W (38852769) webserver: HandleLogin: auth failure for username 'admin'
This was while I was successfully logged into the webserver and in one of the wizard steps where the wizard is repeatedly querying for progress. I was able to go to the status page after that without having to authenticate again. This seems strange.
Oh, I have an idea: I plugged in my v3.0 module so I could get the ssh key from its config, and it may have brought up AP with the same SSID. I don't know what happens to the client if there are two APs competing in that way.
-- Steve
On Wed, 20 Jun 2018, Michael Balzer wrote:
It's always the missing log... your logs look perfectly normal, no hint of anything going wrong on the first setup.
Option 2 can be excluded if you had the SD inserted all the time, as the button status is only checked when no SD is inserted.
Regards, Michael
Am 20.06.2018 um 21:37 schrieb Stephen Casner:
Mark,
Thanks for the prompt reply.
1. SDCARD factoryreset.txt 2. Hold the program button down for several seconds 3. Command-line I certainly didn't intentionally do 1 or 3. I do have the module installed in the 3D-printed case for the v3.0 module that I have modified with a plastic button extension that allows me to push the reset button with the module enclosed in the case. (I mentioned this a while back; the extension is the plastic part that performed the same role in a defunct GFCI plug on a hair dryer.) It is conceivable that this extension pushed on the program button instead of the reset button, but that is not likely because of the physical geometry and the button is still working properly as a reset.
Maybe not a factory reset but a corrupt config partition? Can you try to change config. Then reboot. Then check config is still there? We don't have any "shutdown" operation to stop the module cleanly, so after the configuration I just unplugged it from the USB cable thereby removing power. Is there some likelihood that /store would not have been stable?
As I mentioned, when I brought the module back to my desk after it did not come up in the car, I saw this:
W (550) esp32wifi: AutoInit: factory reset detected, starting public AP net 'OVMS' with password 'OVMSinit'
A full log via USB is attached in case there might be anything interesting in it. It shows the session where I did the wizard setup initially, then the session where I brought it back and found it back to factory reset, then a third session where I disconnected from power and plugged back in without loss of the config.
-- Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (3)
-
Mark Webb-Johnson -
Michael Balzer -
Stephen Casner