Ok, so what you are displaying there is the log messages created by systemd at start up, they are always in systemctl and the very latest have always been displayed with systemctl status.
What you do not see in your output is the logging created by the softwares themselves, a very different thing, that is going to /var/log for the services you displayed. This is not duplicate logging it is different logging in different places.
This discussion came up years ago about mosquitto and the mqtt_input services and it was decided to keep the 2 seperate as they are different things. Take emonhub for example, that produces a vast amount of helpful messages, therefore if this is going to journalctl rather than /var/log, the systemctl log messages are buried, you will need to use some filtering and regexes perhaps top find the systemd logs within the pages and pages of emonhub log messages. That’s if it’s still there, systemd will by default only keep upto 26mb of total logs, so vital boot up info will be quickly lost if every service is logging verbosely to that 26mb limit, yes it can be changed, but there is no need when the logs are kept separate as you demonstrate with your output, just the start and stops of the service(s) are displayed and retained as the faster moving log info is going to /var/log.
The start and stops are not displayed in my output above purely because the system has been up so long the logs have been rotated out (I only enabled persisting journalctl recently on this test server)
[email protected]:~$ systemctl status redis â redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor pre set: enabled) Active: active (running) since Tue 2019-02-26 09:25:09 GMT; 2 week s 4 days ago Docs: http://redis.io/documentation, man:redis-server(1) Main PID: 971 (redis-server) Tasks: 3 (limit: 4915) CGroup: /system.slice/redis-server.service ââ971 /usr/bin/redis-server 127.0.0.1:6379 Warning: Journal has been rotated since unit was started. Log output is incomple te or unavailable. [email protected]:~$ sudo journalctl -u redis-server -- No entries -- [email protected]:~$ sudo ls -la /var/log/redis total 6180 drwxr-x--- 2 redis redis 4096 Mar 10 06:25 . drwxr-xr-x 11 root root 4096 Mar 16 06:25 .. -rw-rw---- 1 redis redis 2899641 Mar 16 15:06 redis-server.log -rw-rw---- 1 redis redis 351060 Jan 14 06:24 redis-server.log.10.gz -rw-rw---- 1 redis redis 263921 Jan 6 06:24 redis-server.log.11.gz -rw-rw---- 1 redis redis 351542 Dec 31 06:24 redis-server.log.12.gz -rw-rw---- 1 redis redis 262797 Mar 10 06:24 redis-server.log.1.gz -rw-rw---- 1 redis redis 350019 Mar 4 06:24 redis-server.log.2.gz -rw-rw---- 1 redis redis 265519 Feb 24 06:24 redis-server.log.3.gz -rw-rw---- 1 redis redis 354475 Feb 18 06:24 redis-server.log.4.gz -rw-rw---- 1 redis redis 64552 Feb 10 06:24 redis-server.log.5.gz -rw-rw---- 1 redis redis 200074 Feb 8 19:29 redis-server.log.6.gz -rw-rw---- 1 redis redis 351475 Feb 4 06:24 redis-server.log.7.gz -rw-rw---- 1 redis redis 307853 Jan 27 06:24 redis-server.log.8.gz -rw-rw---- 1 redis redis 264428 Jan 20 06:24 redis-server.log.9.gz [email protected]:~$
see the last line of the status
Warning: Journal has been rotated since unit was started. Log output is incomple te or unavailable.