Unable to perform request to 'http://192.168.178.1/data.lua'

Question

Unable to perform request to 'http://192.168.178.1/data.lua'

Closed this issue a year ago · 6 comments

Hi,
i've installed it till 15 minutes ago but I can't get some data.
The Box is 7590 with FW 7.50 and it is connected at DSL
The InfluxDB ist created and the user has all rights
At the start everything looks fine, but then i get Erros and no Data in my DB
I hope you can help me.
`
2023-05-02 23:33:41,823 - INFO: Starting fritzinfluxdb v1.2.1 (2023-01-26)
2023-05-02 23:33:41,825 - INFO: Done reading config files
2023-05-02 23:33:41,908 - INFO: Successfully parsed config
2023-05-02 23:33:41,932 - INFO: Connection to InfluxDB 1.8.10 established and database present
2023-05-02 23:33:47,263 - INFO: Successfully established FritzBox TR-069 session
2023-05-02 23:33:47,763 - INFO: Successfully established FritzBox Lua session
2023-05-02 23:33:47,764 - INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
2023-05-02 23:33:47,764 - INFO: Starting main loop
2023-05-02 23:33:50,039 - INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
2023-05-02 23:34:06,844 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:06,844 - ERROR: Unable to request FritzBox Lua service 'Active network hosts', no data returned
2023-05-02 23:34:06,844 - INFO: FritzBox Lua service 'Active network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:33:50,039 - INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
2023-05-02 23:34:06,844 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:06,844 - ERROR: Unable to request FritzBox Lua service 'Active network hosts', no data returned
2023-05-02 23:34:06,844 - INFO: FritzBox Lua service 'Active network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:34:16,850 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:16,851 - ERROR: Unable to request FritzBox Lua service 'Passive network hosts', no data returned
2023-05-02 23:34:16,851 - INFO: FritzBox Lua service 'Passive network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:34:26,857 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:26,858 - ERROR: Unable to request FritzBox Lua service 'System Stats', no data returned
2023-05-02 23:34:26,858 - INFO: FritzBox Lua service 'System Stats (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:33:47,764 - INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (DSL) - FW: 7.50
2023-05-02 23:33:47,764 - INFO: Starting main loop
2023-05-02 23:33:50,039 - INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
2023-05-02 23:34:06,844 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:06,844 - ERROR: Unable to request FritzBox Lua service 'Active network hosts', no data returned
2023-05-02 23:34:06,844 - INFO: FritzBox Lua service 'Active network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:33:50,039 - INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL'
2023-05-02 23:34:06,844 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:06,844 - ERROR: Unable to request FritzBox Lua service 'Active network hosts', no data returned
2023-05-02 23:34:06,844 - INFO: FritzBox Lua service 'Active network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:34:16,850 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:16,851 - ERROR: Unable to request FritzBox Lua service 'Passive network hosts', no data returned
2023-05-02 23:34:16,851 - INFO: FritzBox Lua service 'Passive network hosts (Fritz!OS 7.29 - latest)' will be disabled.
2023-05-02 23:34:26,857 - ERROR: Unable to perform request to 'http://192.168.178.1/data.lua': HTTPConnectionPool(host='192.168.178.1', port=80): Read timed out. (read timeout=10)
2023-05-02 23:34:26,858 - ERROR: Unable to request FritzBox Lua service 'System Stats', no data returned
2023-05-02 23:34:26,858 - INFO: FritzBox Lua service 'System Stats (Fritz!OS 7.29 - latest)' will be disabled.
^C2023-05-02 23:34:35,873 - INFO: Received exit signal SIGINT...
2023-05-02 23:34:35,874 - INFO: Cancelling 4 outstanding tasks
2023-05-02 23:34:35,875 - INFO: Closed FritzBox TR-069 connection
2023-05-02 23:34:35,876 - INFO: Closed FritzBox Lua connection
2023-05-02 23:34:35,876 - INFO: Closed InfluxDB session
2023-05-02 23:34:35,877 - INFO: Successfully shutdown fritzinfluxdb

`

Answer 1 · 2023-05-02T22:02:13.000Z

Hey,

I would recommend to run it with DEBUG logging and increase the timeout to 20 seconds and set the interval to 60 seconds. Maybe this improves the situation.

Answer 2 · 2023-05-04T07:03:58.000Z

Thx. It works now. Ricardo ***@***.***> schrieb am Mi., 3. Mai 2023, 00:02:

…

Hey, I would recommend to run it with DEBUG logging and increase the timeout to 20 seconds and set the interval to 60 seconds. Maybe this improves the situation. — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOJCDB72RSHS7NJ65EOLG2DXEF767ANCNFSM6AAAAAAXTTKQBA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 3 · 2023-05-05T21:20:22.000Z

Hi I ve got another problem. When I start it with systemctl I get everytime (code=exited, status=1) When I do the identical execstart on bash it works fine since the last hour. Do you have an idea why it don't work as a Service? Ricardo ***@***.***> schrieb am Mi., 3. Mai 2023, 00:02:

…

Hey, I would recommend to run it with DEBUG logging and increase the timeout to 20 seconds and set the interval to 60 seconds. Maybe this improves the situation. — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOJCDB72RSHS7NJ65EOLG2DXEF767ANCNFSM6AAAAAAXTTKQBA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 4 · 2023-05-05T21:51:30.000Z

Hey,

Do you have some more information? Usually you can use journalctl to get more details.

systemctl status ftitzinfluxdb

Answer 5 · 2023-05-08T18:06:22.000Z

Hi, Here is the result... ● fritzinfluxdb.service - Fritz to InfluxDB daemon Loaded: loaded (/etc/systemd/system/fritzinfluxdb.ser Active: activating (auto-restart) (Result: exit-code) Process: 3831 ExecStart=/opt/fritzinfluxdb/.venv/bin/p Main PID: 3831 (code=exited, status=1/FAILURE) I hope you have an idea to fix this. Ricardo ***@***.***> schrieb am Fr., 5. Mai 2023, 23:51:

…

Hey, Do you have some more information? Usually you can use journalctl to get more details. systemctl status ftitzinfluxdb — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOJCDB33ECRU3BVFMLDOC7TXEVY6ZANCNFSM6AAAAAAXTTKQBA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 6 · 2023-05-08T19:08:55.000Z

Hi,

Unfortunately I'm unable to help you based on the output of your post. There is an error code but no log message regarding the reason.

Did you check the log files?