Big blocks of NULL in log file?

Configuration
1

Hello folks, I am starting to get things working well. I have been getting large blocks of ‘null’ in my home-assistant.log file. I can see those in Notebook++. Below the nulls is the text shown below. I have Amcrest cameras (3), owntracks, and lots of Sonoff/Tasmota/mqtt devices. It appears some thing(s) are not always responding. Hard to tell what is the problem.
Does anyone know whats happening or have suggestions on how to debug.
Any help would be greatly appreciated.

Blockquote

[ Big block of NULLs here]

2018-02-22 22:08:09 WARNING (SyncWorker_12) [homeassistant.components.switch.tplink] Could not read state for treadmill: Communication error
2018-02-23 10:01:43 WARNING (SyncWorker_7) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’,))’: /cgi-bin/snapshot.cgi?channel=0
2018-02-23 10:01:43 WARNING (SyncWorker_7) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’,))’: /cgi-bin/snapshot.cgi?channel=0
2018-02-23 10:01:43 WARNING (SyncWorker_7) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’,))’: /cgi-bin/snapshot.cgi?channel=0
2018-02-23 10:01:43 WARNING (SyncWorker_7) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’,))’: /cgi-bin/snapshot.cgi?channel=0
2018-02-23 10:01:55 WARNING (SyncWorker_16) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ProtocolError(‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’,))’: /cgi-bin/snapshot.cgi?channel=0

Blockquote

2

That’s usually a symptom of sd-card corruption, I would do a backup asap. Check that the psu has enough ampage for your pi and try not to power it down by pulling the plug.

3

Those are both good ideas. So far, I have done the following:
The supply is a 5vdc, 2.5amp, but I will check its operation on an oscilloscope (could be defective).
I changed to a new Sandisk 64Gb class 10 SD card to see if that was the problem, but no change.
I wish I had more info to find the ‘ProtocolError’

4

You can try setting up the logger component…see below - change error for debug to get more info for each component - don’t set them all as you will be overwhelmed by the amount of info :stuck_out_tongue: There are probably more than this but I only have the ones I need set-up, the ones you need may not be here :stuck_out_tongue:

logger:
  default: info
  logs:
    botocore: error
    dlipower: error
    homeassistant.components.alarm_control_panel: error
    homeassistant.components.alert: error
    homeassistant.components.api: error
    homeassistant.components.plexapi: error
    homeassistant.components.automation: error
    homeassistant.components.binary_sensor: error
    homeassistant.components.camera: error
    homeassistant.components.climate: error
    homeassistant.components.cover: error
    homeassistant.components.device_tracker: error
    homeassistant.components.http: error
    homeassistant.components.light: error
    homeassistant.components.media_player: error
    homeassistant.components.mqtt: error
    homeassistant.components.notify: error
    homeassistant.components.recorder: error
    homeassistant.components.remote: error
    homeassistant.components.sensor: error
    homeassistant.components.switch: error
    homeassistant.components.telegram_bot: error
    homeassistant.components.xiaomi: debug
    homeassistant.components.discovery: error
    homeassistant.helpers: error
    homeassistant.loader: error
    libopenzwave: error
#    openzwave: error
    plexapi: error
    pychromecast: error
    root: error
    telegram: error
    urllib3: error
1 Like
5

Big help to me, thank you. I did not have the logger implemented. Tomorrow I can hit the debugging hard with the new tool set. :sunglasses:

6

The trouble with having lot’s of null’s in the log file is - are there other groups of nulls in the HA code or database etc :stuck_out_tongue:

7

I suspect the database may be getting them. I had a 350 Mb database after only a month of op and fairly modest config.

8

Well that’s really small, mine is currently 185mb after only 2 days :stuck_out_tongue:

9

I printed out your “logger” code and added it to my configuration.yaml.
I really like the info it provides. That should make debugging much more productive.
The really interesting thing is that the nulls did not occur and no errors of any kind show.
I guess they may return and now I have a tool to handle that…thanks.

Or maybe my errors are like cockroaches and scuury away when the light comes on :wink: