GF no longer saves wifi settings?


#1

Has anyone had problems where you have to run setup every time you power on the Glowforge?

My log file entries always start with:
2018-03-09_21:01:59.22180 2 ERROR: unable to read /data/glowforge.conf (2: No such file or directory, src/config.cpp:402)


#2

I think that error is normal and happens very time.

Does the light go teal or are you manually entering setup? If so why?


#3

The Glowforge will never go online. I’ve waited as long as an hour. i have to hold the button to reenter setup on each restart.


#4

This error is actually normal, and can be ignored.

The file it is referring to (/data/glowforge.conf) is used for local override of the read-only configuration file (located at /etc/glowforge.conf).

Most of the wireless logging messages are written to the underlying Linux system logs, which are not (to my knowledge) retrievable by the casual user.


#5

This sounds like a router issue to me; it sounds like the GF is asking for an IP address but the router isn’t responding until the WiFi connection is set up again, though I could be wrong. This is where I would start looking.


#6

Staring at the logs, and comparing to older ones, I can see two things:

  1. The gf is not updating the system clock. The 03-09 fw then starts throwing cert errors (time skew…this is from today 04-18)
    2018-03-09_21:02:02.45364 2634 INFO: net: requesting socket token
    2018-03-09_21:02:02.81107 3032 ERROR: socket token request: http_code=0, result=60 (Peer certificate cannot be authenticated with given CA certificates)
    2018-03-09_21:02:02.82465 3036 WARNING: net: failed to receive token
    2018-03-09_21:02:05.77909 6000 INFO: net: requesting socket token
    2018-03-09_21:02:06.05005 6271 ERROR: socket token request: http_code=0, result=60 (Peer certificate cannot be authenticated with given CA certificates)
    2018-03-09_21:02:06.06389 6274 WARNING: net: failed to receive token
    2018-03-09_21:02:09.03355 9251 INFO: net: requesting socket token
    2018-03-09_21:02:09.30629 9527 ERROR: socket token request: http_code=0, result=60 (Peer certificate cannot be authenticated with given CA certificates)

Or maybe: (this is a little odd, the gf will fire up and allow cuts after rerunning setup).
2018-03-09_21:03:00.99204 61213 ERROR: hw: Coolant flow failure (broken pump) (src/hw_task_messages.cpp:112)
2018-03-09_21:03:01.00523 61216 INFO: hw: error flag set: fault:coolant_flow_fault:set (45)
2018-03-09_21:03:01.00527 61221 INFO: coolant_flow_controller_peripheral: Entering pump state 1
2018-03-09_21:03:01.00529 61225 INFO: coolant_flow_controller_peripheral: Pump on
2018-03-09_21:03:01.53243 61294 INFO: net: requesting socket token


#7

Does your WiFi connection use a captive portal? Meaning - when you connect, you are directed to a page to sign in before you can use the network.

The message indicates that it is trying to connect to the service, but the SSL certificate used by the server to secure the connection is not one that it recognizes as valid.


#8

Nope. The funky thing is that I’m using Lumas which means: A: mesh. B: no debug logs. I do get a status page which tells me when each dhcp client last connected. I’ll try to verify if Luma thinks it handed out a mac address. I don’t see any dhcp lease info on the GF side until after I push the reset button.

On the older firmware, I do see the GF will update its clock at this point. (because while the local clock is more than a month out of date, TLS shouldn’t work. ) The 01-09 older firmware detects the skew and syncs time.

2018-01-09_18:54:27.00799 2746 DEBUG: hw: /dev/watchdog opened, timeout is 60 sec
2018-01-09_18:54:27.00802 2746 INFO: audio_peripheral: Unable to play sound /glowforge/sound/boot
2018-01-09_18:54:27.00803 2747 INFO: net: requesting socket token
2018-01-09_18:54:27.69207 3435 INFO: clock skew detected, updating system time from server response timestamp
2018-02-06_23:12:32.01366 3436 INFO: system time updated
2018-02-06_23:12:32.01368 3439 INFO: socket token request: http_code=200, result=0 (OK)

The current fw does not:

2018-03-09_21:02:02.45362 2623 DEBUG: hw: /dev/watchdog opened, timeout is 60 sec
2018-03-09_21:02:02.45363 2633 INFO: audio_peripheral: Unable to play sound /glowforge/sound/boot
2018-03-09_21:02:02.45364 2634 INFO: net: requesting socket token
2018-03-09_21:02:02.81107 3032 ERROR: socket token request: http_code=0, result=60 (Peer certificate cannot be authenticated with given CA certificates)
2018-03-09_21:02:02.82465 3036 WARNING: net: failed to receive token
2018-03-09_21:02:05.77909 6000 INFO: net: requesting socket token


#9

Can you see in the logs what version of firmware you are running?


#10

Thanks for reaching out.

I see you already emailed us about this and we’re working on it there, so I’m going to close this topic.


#11