-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Minor - P4
-
None
-
Affects Version/s: 4.0.6
-
Component/s: Logging
-
Labels:None
-
ALL
-
-
Dev Tools 2019-04-08, Dev Tools 2019-04-22, Dev Tools 2019-06-17
When I try to start mongod on a centos server using `systemctl start mongod`, mongod generates different format of logs for journalctl.
e.g.Sometimes I got _SYSTEMD_UNIT in logs sometimes I didn't.
use `journalctl -o verbose` to see following logs
Thu 2019-03-14 08:56:25.564626 CST [s=f346de34a07a4ae4864c0b0d59247e13;i=380;b=8d1b546e8233453eb811aad9c83b
PRIORITY=6
_SYSTEMD_SLICE=system.slice
_BOOT_ID=8d1b546e8233453eb811aad9c83b60d0
_MACHINE_ID=5e6521e7a19a4ceaa05ce7b123bdf8b2
_HOSTNAME=localhost.localdomain
SYSLOG_FACILITY=3
_TRANSPORT=stdout
_SELINUX_CONTEXT=system_u:system_r:init_t:s0
_CAP_EFFECTIVE=0
_STREAM_ID=4b9a978cc3dc46a0b498c309478cc055
SYSLOG_IDENTIFIER=mongod
MESSAGE=Error reading config file: Permission denied
_PID=941
_UID=998
_GID=995
_COMM=mongod
_SYSTEMD_CGROUP=/system.slice/mongod.service
_SYSTEMD_UNIT=mongod.service
or
Thu 2019-03-14 09:52:28.999450 CST [s=f346de34a07a4ae4864c0b0d59247e13;i=3c2;b=8d1b546e8233453eb811aad9c83b
PRIORITY=6
_BOOT_ID=8d1b546e8233453eb811aad9c83b60d0
_MACHINE_ID=5e6521e7a19a4ceaa05ce7b123bdf8b2
_HOSTNAME=localhost.localdomain
SYSLOG_FACILITY=3
_SYSTEMD_CGROUP=/
_TRANSPORT=stdout
_SELINUX_CONTEXT=system_u:system_r:init_t:s0
_CAP_EFFECTIVE=0
SYSLOG_IDENTIFIER=mongod
MESSAGE=Error reading config file: Permission denied
_UID=998
_GID=995
_COMM=mongod
_STREAM_ID=b21afa0dd80f44dca15370450b1be552
_PID=1644
and only those with `_SYSTEMD_UNIT=mongod.service` can be seen by `journalctl -u mongod` or 'systemctl status mongod'