/exe requires this capability. Thus if this capability is missing
@@ -53,5 +48,4 @@
# If there are many split up journal files we need a lot of fds to access them
# all in parallel.
-LimitNOFILE={{HIGH_RLIMIT_NOFILE}}
-
+LimitNOFILE=524288
```
Note that when I run `mender daemon` manually I get the following message three times:
```auto
WARN[0063] Returning artifact name from /etc/mender/artifact_info file. This is a fallback, in case the information can not be retrieved from the database, and is only expected when an update has never been installed before.
WARN[0064] Returning artifact name from /etc/mender/artifact_info file. This is a fallback, in case the information can not be retrieved from the database, and is only expected when an update has never been installed before.
WARN[0068] Returning artifact name from /etc/mender/artifact_info file. This is a fallback, in case the information can not be retrieved from the database, and is only expected when an update has never been installed before.
```
---
### Author:  [@pamolloy](https://hub.mender.io/u/pamolloy)
#### Post date: [November 22, 2022, 11:06am UTC](https://hub.mender.io/t/journal-log-messages-duplicated/5417/5 "2022-11-22T11:06:12Z")
Is there a way to prevent the warning about `artifact_info` from getting printed? Or maybe the default config is causing that polling that too often? I feel like I’m missing some persistent storage for Mender because even after several updates I still see this warning.
---
### Author:  [@snusifer](https://hub.mender.io/u/snusifer)
#### Post date: [November 23, 2022, 11:24am UTC](https://hub.mender.io/t/journal-log-messages-duplicated/5417/6 "2022-11-23T11:24:09Z")
Hello @pamolloy ,
Thanks for bringing this up.
Regarding the duplicate log messages in the journal, in your configuration journald symlinks `/dev/log` to `/run/systemd/journal/dev-log`, which is a socket that journald listens to. Additionally, mender-client is configured by default to forward log entries to the standard syslogger ( `syslogd`, `syslog-ng` or `rsyslog`). Most sysloggers listen to `/dev/log`. Presumably, this is why duplicate log messages happen as two identical streams are fed into journald; one from `/run/systemd/journal/dev-log` and one from `stdout`.
To fix the problem, try the following:
- In `/lib/systemd/system/mender-client.service`, change
`ExecStart=/usr/bin/mender daemon`
to
`ExecStart=/usr/bin/mender --no-syslog daemon`.
- (optionally) if you want log messages to be forwarded to `/var/log/syslog`, make sure the standard syslogger listens to `/run/systemd/journal/syslog` and set `ForwardToSyslog=yes` in your `/etc/systemd/journald.conf`.
Hope this helps 🙂
---
### Author:  [@snusifer](https://hub.mender.io/u/snusifer)
#### Post date: [November 23, 2022, 12:50pm UTC](https://hub.mender.io/t/journal-log-messages-duplicated/5417/7 "2022-11-23T12:50:52Z")
@pamolloy
With regards to the `artifact_info` point that you brought up, I just need to clarify some things. So to understand this correctly, did you run the `mender-client` in the shell alongside a `mender-client` already running and managed by `systemd`, while doing updates?
The one spawned in the shell, does it run with root privileges?
What version of mender are you running?
---
### Author:  [@pamolloy](https://hub.mender.io/u/pamolloy)
#### Post date: [November 23, 2022, 1:02pm UTC](https://hub.mender.io/t/journal-log-messages-duplicated/5417/8 "2022-11-23T13:02:37Z")
Thanks for the detailed reply! `--no-syslog` is exactly what I needed.
---
### Author:  [@pamolloy](https://hub.mender.io/u/pamolloy)
#### Post date: [November 23, 2022, 1:04pm UTC](https://hub.mender.io/t/journal-log-messages-duplicated/5417/9 "2022-11-23T13:04:30Z")
I believe this was the result of not persisting Mender data between updates. I now pass a directory that is persisted to Mender with `--data`.