Constant 'ERROR -- docker plugin' entries in glances.log #2024
-
|
Glances v3.2.4.2 with PsUtil v5.9.0, Linux Mint 20.3 After reboot, autostart 'glances -w' From glances.log: Then I can access web interface to see the data and every 2-3 seconds the page updates as expected, but also this docker plugin ERROR is written in glances' log: 2022-04-02 16:44:01,216 -- ERROR -- docker plugin - Cannot get Docker version (('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))) This message repeats and repeats every few seconds until I close the browser tab. It doesn't matter if I access the url locally ('http://0.0.0.0:61208/') or remotely ('http://192.168.0.xxx:61208/'). The messages start logging when I open the interface and stop when I close it. Opening in terminal results in the same behavior. This also occurs when I use curl, i.e. 'curl http://0.0.0.0:61208/api/3/uptime' returns "1:55:37" and the same docker plugin ERROR message is logged, whether local or remote. The data seems to be reporting fine it's just constantly writing ERROR messages when I have the interface open, and since I was using curl to grab some api data on a regular basis, that would also generate repeated log entries. I don't have any docker files installed as far as I know. Q1: Is this something to worry about? It is slightly annoying but is it a problem, now or in the future, that needs correcting? If so, how please? Q2: Slightly OT, but notice that accessing the api via curl to get uptime returns a plain-text entry, not a json key/value as indicated in the documentation, and as returned by glances --issue, and as other plugins do. Again, not a real problem, or is it? Q3: Bonus Question! I see that glances shows my public IP address. How does this happen? I only know how to get that info from third party sites via curl/wget/etc, not programmatically from within my system. Educate me please on how glances does this. Will it update immediately if/when my ISP changes my public IP? Long text, minor issues about a great useful program. Didn't get any help when I RTFM and a search didn't find any similar issues/complaints so the problem is likely on my end. If these need to be asked elsewhere, let me know. Thanks for any help, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Solved. Simply sudo edit the /etc/glances/glances.conf (NOT the config file in the home directory) Don't know why those are set to disable=False as the default, or why that would throw constant errors, but there it is. Maybe I am the only user not running glances in docker with wifi. Still no idea why the api returns plain text not json. Nor do I comprehend how glances is determining my public IP. But the night is young ... fitz |
Beta Was this translation helpful? Give feedback.
Solved.
Simply sudo edit the /etc/glances/glances.conf (NOT the config file in the home directory)
In the [docker] block change first line to disable=True
Also did the same in the [wifi] block since I don't use that on these systems.
Obviously have to do this on all my machines, but it seems to be working better now.
Fewer warnings on start and no ERROR messages in the log when accessing either by web interface or api.
Don't know why those are set to disable=False as the default, or why that would throw constant errors, but there it is. Maybe I am the only user not running glances in docker with wifi.
Still no idea why the api returns plain text not json. Nor do I comprehend how glances i…