# Beaglebone Black, mender-client Unparsable output: incorrect line 'ext4' **URL:** \ **Category:** General Discussions\ **Tags:** beaglebone\ **Created:** [December 6, 2019, 9:04pm UTC](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334 "2019-12-06T21:04:53Z")\ **Posts on this page:** 4\ **Page:** 2
**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\ **Post date:** [January 28, 2020, 11:46am UTC](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334/21 "2020-01-28T11:46:44Z")
@colinbes I’ve finally caught up! U are right. This is not what I would be expecting either. Just gonna dig in the code a little bit. Will be back ---
**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\ **Post date:** [January 28, 2020, 12:08pm UTC](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334/22 "2020-01-28T12:08:59Z")
Alright, had a look. And I have not been able to reproduce. Here is the workflow I have gone through: ```auto root@qemux86-64:~# mender --version 2.1.2 runtime: go1.12.9 ``` From the CLI, std-level (info): ```auto root@qemux86-64:~# mender -install http://10.0.2.2:8000/test.mender INFO[0000] Loaded configuration file: /var/lib/mender/mender.conf module=config INFO[0000] Loaded configuration file: /etc/mender/mender.conf module=config INFO[0001] Mender running on partition: /dev/hda2 module=main INFO[0002] Performing remote update from: [http://10.0.2.2:8000/test.mender]. module=standalone ERRO[0002] Can not fetch update image: Get http://10.0.2.2:8000/test.mender: dial tcp 10.0.2.2:8000: connect: connection refused module=client_update ERRO[0002] Error while installing Artifact from command line: update fetch request failed: Get http://10.0.2.2:8000/test.mender: dial tcp 10.0.2.2:8000: connect: connection refused module=main ``` From the CLI with log-level warning: ```auto ERRO[0002] Can not fetch update image: Get http://10.0.2.2:8000/test.mender: dial tcp 10.0.2.2:8000: connect: connection refused module=client_update ERRO[0002] Error while installing Artifact from command line: update fetch request failed: Get http://10.0.2.2:8000/test.mender: dial tcp 10.0.2.2:8000: connect: connection refused module=main ``` Then changing the service unit file in systemd to: ```auto root@qemux86-64:~# sudo cat /etc/systemd/system/multi-user.target.wants/mender.service [Unit] Description=Mender OTA update service After=systemd-resolved.service [Service] Type=idle User=root Group=root ExecStart=/usr/bin/mender -daemon -log-level warning Restart=on-abort [Install] WantedBy=multi-user.target ``` And running: ```auto systemctl stop mender systemctl daemon-reload systemctl start mender ``` Then ```auto journalctl -u mender -a ``` Gives: ```auto Jan 28 12:07:53 qemux86-64 systemd[1]: Started Mender OTA update service. Jan 28 12:08:08 qemux86-64 mender[2088]: time="2020-01-28T12:08:08Z" level=err or msg="Failure occurred while executing authorization request: &url.Error{Op: \"Post\", URL:\"https://docker.mender.io/api/devices/v1/authentication/auth_re quests\", Err:(*net.OpError)(0xc0004b6550)}" module=client_auth Jan 28 12:08:08 qemux86-64 mender[2088]: time="2020-01-28T12:08:08Z" level=err or msg="authorization request error: dial tcp: lookup docker.mender.io on 10.0 .2.3:53: read udp 10.0.2.15:59244->10.0.2.3:53: i/o timeout" module=client_aut h Jan 28 12:08:08 qemux86-64 mender[2088]: time="2020-01-28T12:08:08Z" level=err or msg="authorize failed: transient error: authorization request failed: gener ic error occurred while executing authorization request: Post https://docker.m ender.io/api/devices/v1/authentication/auth_requests: dial tcp: lookup docker. mender.io on 10.0.2.3:53: read udp 10.0.2.15:59244->10.0.2.3:53: i/o timeout" module=state ``` ---
**Author:** ![colinbes](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/colinbes/32/448_2.png) [@colinbes](https://hub.mender.io/u/colinbes)\ **Post date:** [January 28, 2020, 3:35pm UTC](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334/23 "2020-01-28T15:35:31Z")
If I run **mender -install** then the console (terminal) displays info level logs as expected. If I run **mender -log-level warning** then the console (terminal) displays warning level logs as expected but info level at /var/log/messages and /var/log/syslog. Adding -log-level warning to systemd file makes no difference in /var/log/messages and /var/log/syslog files - they always contain info and above. I haven’t tried setting to debug to see if this effects log levels. On my beaglebone I don’t have journalctl, there is a systemctl-journal (or some similar name) but it doesn’t support -u option. ---
**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\ **Post date:** [January 31, 2020, 2:28pm UTC](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334/24 "2020-01-31T14:28:18Z")
Hey, @colinbes. You are right! It does spam the syslog it looks like. Ticket: [https://tracker.mender.io/browse/MEN-3135](https://tracker.mender.io/browse/MEN-3135) In the meantime, will something like: ```auto awk '!/info/' /var/log/syslog ``` Do it for you? [Previous page](https://hub.mender.io/t/beaglebone-black-mender-client-unparsable-output-incorrect-line-ext4/1334.md?page=1)