stopped collecting data after updating "guest wlan"

[ronaldn1969]

@bb-Ricardo hope you had a enjoyable Christmas time...

actually I faced the following problem... I changed the name of the guest wlan and afterwards fritzinfluxdb stopped collecting data and the log was flooded with the following message:

ERROR: Failed to write to InfluxDB '192.168.178.34': 400: {"error":"partial write: field type conflict: input field \"wlan3_ssid\" on measurement \"fritzbox\" is type integer, already exists as type string dropped=7"}

It's funny... I changed the name to "01010011000100011001" and now it is recognised as "integer" and not "string" anymore. It only stopped, when I set the old name and restart fritzinlfuxdb.

My workaround by now is, that I set spaces in between... ""0101 0011 0001 0001 1001". But maybe it's possible the you set "wlanX_ssid" as string by default, so that no character is needed.

Best wishes for the new year and thanks for this great project!

Ronald

 INFO: Starting fritzinfluxdb v1.2.0-alpha1 (2022-12-XX)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop
 WARNING: Service 'Cable Info' not applicable for this FritzBox Model Link type 'DSL'
 ERROR: FritzBox Lua request parsing for 'Home Automation' failed: 'NoneType' object is not iterable
 ERROR: Unable to request FritzBox Lua service 'Home Automation', no data returned
 INFO: FritzBox Lua service 'Home Automation' will be disabled.
 INFO: Purging '2239' measurements which are older (2022-12-09 09:37:00+01:00) then the InfluxDB configured retention period

[bb-Ricardo]

Hi @ronaldn1969 ,

sorry for not getting back. Yes I have to add a type to each value in the TR69 configuration.

[bb-Ricardo]

Hey @ronaldn1969: I added the datatype to all TR069 measurements. Can you pull the next-release branch and try again to rename your guest WLAN?

thank you.

[ronaldn1969]

Hi @bb-Ricardo

Before I changed the guest WLAN name, I faced the problem, that fritzinfluxdb v1.2.0 can't write into the existing DB.

 INFO: Starting fritzinfluxdb v1.2.0 (2022-12-23)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop
 INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 

When I switch back to the former version, it's running without problem...

 INFO: Starting fritzinfluxdb v1.1.0 (2022-11-02)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop

I thought, that this could be related to your change. So I droped the database and set up an new one. But still the same...

 INFO: Starting fritzinfluxdb v1.2.0 (2022-12-23)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop
 INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 

BUT, when I let fritzinfluxdb v1.2.0 create the DB, it's running without problem. In this case, I have to drop the DB on my production system, what's not in my interest, and have use your DB retention policy settings.

Last check... droped the DB and start v1.1.0 and let create the DB.

 INFO: Starting fritzinfluxdb v1.1.0 (2022-11-02)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Database 'netzwerk_raw' not found, trying to create it
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop
 ERROR: Failed to write to InfluxDB '192.168.178.35': HTTPConnectionPool(host='192.168.178.35', port=8086): Read timed out. (read timeout=2)
 INFO: Connection to influxDB '192.168.178.35' restored.
 INFO: Flushing '2935' measurements to InfluxDB
 INFO: Purging '510' measurements which are older (2022-01-22 14:10:00+01:00) then the InfluxDB configured retention period

then stopped v1.1.0 and started v1.2.0 and get the same error message

 INFO: Starting fritzinfluxdb v1.2.0 (2022-12-23)
 INFO: Done reading config files
 INFO: Successfully parsed config
 INFO: Connection to InfluxDB 1.8.10 established and database present
 INFO: Successfully established FritzBox TR-069 session
 INFO: Successfully established FritzBox Lua session
 INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
 INFO: Starting main loop
 INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 
 ERROR: Failed to write to InfluxDB '192.168.178.35': 400: 

So it looks like, that the DB structure from the new version is not compatible to old one.

Could you please check if it's possible to ran the change with he "old" DB setup from v1.1.0.

BR
Ronald

[bb-Ricardo]

Hey @ronaldn1969: I just pushed another commit to next-release which should tell you more about the issue.

Can you pull it and run it with the -v option?

sorry for the hassle. Thank you.

[ronaldn1969]

Hi @bb-Ricardo

looks good... ;)

started the new version on existing DB and there was no error message and data shown up in the panel... now will check the WLAN settings...

[ronaldn1969]

@bb-Ricardo it's running well with v1.2.0 on my production system... Thanks a lot!!

v1.1.0: changed the guest WLAN name and got the message:

 ERROR: Failed to write to InfluxDB '192.168.178.34': 400: {"error":"partial write: field type conflict: input field \"wlan3_ssid\" on measurement \"fritzbox\" is type integer, already exists as type string dropped=5"}
 ERROR: Failed to write to InfluxDB '192.168.178.34': 400: {"error":"partial write: field type conflict: input field \"wlan3_ssid\" on measurement \"fritzbox\" is type integer, already exists as type string dropped=5"}
 ERROR: Failed to write to InfluxDB '192.168.178.34': 400: {"error":"partial write: field type conflict: input field \"wlan3_ssid\" on measurement \"fritzbox\" is type integer, already exists as type string dropped=6"}

changed on the production system fritzinfluxdb v1.1.0 to v1.2.0 and got no message...

[bb-Ricardo]

great, thank for the feedback, than I can close this issue.