Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fritzcollectd stops in Docker environment arbitrarily #50

Open
christofkac opened this issue Aug 7, 2020 · 0 comments
Open

Fritzcollectd stops in Docker environment arbitrarily #50

christofkac opened this issue Aug 7, 2020 · 0 comments

Comments

@christofkac
Copy link

I use Fritzcollectd based on the Docker container https://hub.docker.com/r/gizmoh/fritzcollectd.
I set it up successfully but run into the problem, that the logging into the InfluxDb stops suddenly and only continues when I restart the container.

Sometimes it stops after some minutes, sometimes after hours or days.

As I thought that the container might be wrong, I even created my own container based on Debian Buster (https://hub.docker.com/repository/docker/christofk/fritzcollectd) unfortunately with the same result.

The same Docker container collects also other values via collectd like cpu, disk - those work fine. Only the collection of the Fritzcollectd values stops. Therefore I raise this issue.

To check if the log provides anything reasonable, I also enabled the logging Verbose "True".

Two examples of logs, where you see the abortion:

  1. [2020-08-02 23:59:05] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'gauge', type_instance: 'dslstatus', values: '[1]'
    [2020-08-02 23:59:05] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'gauge', type_instance: 'constatus', values: '[1]'
    [2020-08-02 23:59:05] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'bytes', type_instance: 'totalbytesreceived', values: '[2011476325]'
    [2020-08-02 23:59:08] fritzcollectd: Calling action: WANIPConn:1 GetStatusInfo {}
    [2020-08-02 23:59:08] fritzcollectd: Calling action: WANCommonIFC:1 GetCommonLinkProperties {}
    [2020-08-02 23:59:08] fritzcollectd: Calling action: WANCommonIFC:1 GetAddonInfos {}
    [2020-08-02 23:59:08] fritzcollectd: Calling action: DeviceInfo:1 GetInfo {}

  2. [2020-08-03 10:28:58] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'gauge', type_instance: 'dslstatus', values: '[1]'
    [2020-08-03 10:28:58] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'gauge', type_instance: 'constatus', values: '[1]'
    [2020-08-03 10:28:58] fritzcollectd: Dispatching: host: 'FritzBox', plugin: 'fritzbox', plugin_instance: '1', type: 'bytes', type_instance: 'totalbytesreceived', values: '[3148009476]'
    [2020-08-03 10:29:06] fritzcollectd: Calling action: WANIPConn:1 GetStatusInfo {}
    [2020-08-03 10:29:06] fritzcollectd: Calling action: WANCommonIFC:1 GetCommonLinkProperties {}
    [2020-08-03 10:29:06] fritzcollectd: Calling action: WANCommonIFC:1 GetAddonInfos {}
    [2020-08-03 10:29:06] fritzcollectd: Calling action: DeviceInfo:1 GetInfo {}
    [2020-08-03 10:29:12] fritzcollectd: Calling action: LANEthernetInterfaceConfig:1 GetStatistics {}
    [2020-08-03 10:29:12] fritzcollectd: Calling action: WANCommonInterfaceConfig:1 GetCommonLinkProperties {}
    [2020-08-03 10:29:13] fritzcollectd: Calling action: X_AVM-DE_Homeauto:1 GetGenericDeviceInfos {'NewIndex': 0} `

It seems to stop at different points.

How shall I proceed?

Thanks
Christof

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant