Where is / why is there no log for normal user systemd services?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
19
down vote

favorite
2












I'm trying to learn basic systemd usage and I've run into a confusing issue with user service units.



When running ordinary services with systemctl start some.service I can find the full log for this service (including what it has printed to stdout / stderr, as I understand it) by running sudo journalctl --unit some.service.



Consider the example servicefile chatty.service:



[Service]
ExecStart=/usr/bin/echo "test from chatty.service"


When I place this service file in ~/.config/systemd/user/chatty.service and run it with systemctl --user start chatty.service I cannot find its output sent to stdout in journalctl, neither with plain journalctl nor with journalctl --user. I only get the following output in both:



Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Starting chatty.service...
Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Started chatty.service.


And journalctl --unit chatty.service does not return anything at all (with or without --user makes no difference).



While if I move the same service file to /etc/systemd/system and run it with sudo systemd start chatty.service I then get the following output when I run sudo journalctl --unit chatty.service:



Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Starting chatty.service...
Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Started chatty.service.
Jan 15 19:28:08 qbd-x230-suse.site echo[27098]: test from chatty.service


It seems like the user service unit isn't as well integrated somehow, is this expected, am I missing something or is it a bug?



I am running openSUSE 13.1 x86-64, with systemd 208 (default install).










share|improve this question





















  • Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
    – lilydjwg
    Jan 22 '14 at 17:11















up vote
19
down vote

favorite
2












I'm trying to learn basic systemd usage and I've run into a confusing issue with user service units.



When running ordinary services with systemctl start some.service I can find the full log for this service (including what it has printed to stdout / stderr, as I understand it) by running sudo journalctl --unit some.service.



Consider the example servicefile chatty.service:



[Service]
ExecStart=/usr/bin/echo "test from chatty.service"


When I place this service file in ~/.config/systemd/user/chatty.service and run it with systemctl --user start chatty.service I cannot find its output sent to stdout in journalctl, neither with plain journalctl nor with journalctl --user. I only get the following output in both:



Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Starting chatty.service...
Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Started chatty.service.


And journalctl --unit chatty.service does not return anything at all (with or without --user makes no difference).



While if I move the same service file to /etc/systemd/system and run it with sudo systemd start chatty.service I then get the following output when I run sudo journalctl --unit chatty.service:



Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Starting chatty.service...
Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Started chatty.service.
Jan 15 19:28:08 qbd-x230-suse.site echo[27098]: test from chatty.service


It seems like the user service unit isn't as well integrated somehow, is this expected, am I missing something or is it a bug?



I am running openSUSE 13.1 x86-64, with systemd 208 (default install).










share|improve this question





















  • Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
    – lilydjwg
    Jan 22 '14 at 17:11













up vote
19
down vote

favorite
2









up vote
19
down vote

favorite
2






2





I'm trying to learn basic systemd usage and I've run into a confusing issue with user service units.



When running ordinary services with systemctl start some.service I can find the full log for this service (including what it has printed to stdout / stderr, as I understand it) by running sudo journalctl --unit some.service.



Consider the example servicefile chatty.service:



[Service]
ExecStart=/usr/bin/echo "test from chatty.service"


When I place this service file in ~/.config/systemd/user/chatty.service and run it with systemctl --user start chatty.service I cannot find its output sent to stdout in journalctl, neither with plain journalctl nor with journalctl --user. I only get the following output in both:



Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Starting chatty.service...
Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Started chatty.service.


And journalctl --unit chatty.service does not return anything at all (with or without --user makes no difference).



While if I move the same service file to /etc/systemd/system and run it with sudo systemd start chatty.service I then get the following output when I run sudo journalctl --unit chatty.service:



Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Starting chatty.service...
Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Started chatty.service.
Jan 15 19:28:08 qbd-x230-suse.site echo[27098]: test from chatty.service


It seems like the user service unit isn't as well integrated somehow, is this expected, am I missing something or is it a bug?



I am running openSUSE 13.1 x86-64, with systemd 208 (default install).










share|improve this question













I'm trying to learn basic systemd usage and I've run into a confusing issue with user service units.



When running ordinary services with systemctl start some.service I can find the full log for this service (including what it has printed to stdout / stderr, as I understand it) by running sudo journalctl --unit some.service.



Consider the example servicefile chatty.service:



[Service]
ExecStart=/usr/bin/echo "test from chatty.service"


When I place this service file in ~/.config/systemd/user/chatty.service and run it with systemctl --user start chatty.service I cannot find its output sent to stdout in journalctl, neither with plain journalctl nor with journalctl --user. I only get the following output in both:



Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Starting chatty.service...
Jan 15 19:16:52 qbd-x230-suse.site systemd[1168]: Started chatty.service.


And journalctl --unit chatty.service does not return anything at all (with or without --user makes no difference).



While if I move the same service file to /etc/systemd/system and run it with sudo systemd start chatty.service I then get the following output when I run sudo journalctl --unit chatty.service:



Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Starting chatty.service...
Jan 15 19:28:08 qbd-x230-suse.site systemd[1]: Started chatty.service.
Jan 15 19:28:08 qbd-x230-suse.site echo[27098]: test from chatty.service


It seems like the user service unit isn't as well integrated somehow, is this expected, am I missing something or is it a bug?



I am running openSUSE 13.1 x86-64, with systemd 208 (default install).







systemd






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 15 '14 at 18:35









Quantumboredom

5571512




5571512











  • Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
    – lilydjwg
    Jan 22 '14 at 17:11

















  • Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
    – lilydjwg
    Jan 22 '14 at 17:11
















Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
– lilydjwg
Jan 22 '14 at 17:11





Same systemd 208 here on Arch Linux. You can use journalctl --user --user-unit chatty to get those start/stop messages from systemd, but not what the echo process outputs, at least in my case. You can get the echoed message with journalctl --user or use some other filter.
– lilydjwg
Jan 22 '14 at 17:11











3 Answers
3






active

oldest

votes

















up vote
17
down vote













Use --user-unit option, and in your case...



journalctl --user-unit chatty





share|improve this answer






















  • Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
    – Quantumboredom
    Mar 28 '14 at 18:34










  • Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
    – elynnaie
    Mar 29 '14 at 13:15










  • That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
    – Quantumboredom
    Mar 30 '14 at 12:31










  • Arch Linux 3.13.7-1. systemd version 212.
    – elynnaie
    Mar 31 '14 at 6:52






  • 2




    I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
    – CMCDragonkai
    Jul 22 '14 at 6:22

















up vote
2
down vote













Until systemd v230, you had to use the less intuitive --user-unit flag to view the logs for your user's unit:



journalctl --user-unit chatty


Since systemd v230, you can now combine the --user and --unit flags as you'd expect:



journalctl --user --unit chatty


The --user --unit syntax is supported since Ubuntu 17.10.






share|improve this answer




















  • I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
    – LeGEC
    Oct 25 at 14:12

















up vote
0
down vote













Necroposting, but I faced and resolved the same issue today. Most probably journalctl --user-unit chatty didn't work you because you run it from root. However, per man journalctl, --user-unit filters log entries not only by _SYSTEMD_USER_UNIT=, but also by _UID=, and there is no chatty service with root's uid, so no entries are found.



It's likely that you also have tried to run journalctl --user-unit chatty from your usual user, but got No journal files were found. This happens because (and All users are granted access to their private per-user journals from man journalctl can be confusing here) in 2018 on my Debian 9 journalctl still is not persistent by default (Storage=auto in /etc/systemd/journald.conf, and /var/log/journal/ doesn't exist), and in non-persistent mode journald doesn't support splitting logs, so all logs end up in single place in /run/log/journal despite the fact that splitting is turned on by default -- see SplitMode in man journald.conf. Enabling persistency fixes this.



TL;DR: enable persistency by putting Storage=persistent to /etc/systemd/journald.conf and reloading journald with sudo systemctl restart systemd-journald.



Alternatively, search with sudo journalctl _SYSTEMD_USER_UNIT=chatty.service



Some more details are at
https://lists.freedesktop.org/archives/systemd-devel/2016-October/037554.html






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f109490%2fwhere-is-why-is-there-no-log-for-normal-user-systemd-services%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    17
    down vote













    Use --user-unit option, and in your case...



    journalctl --user-unit chatty





    share|improve this answer






















    • Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
      – Quantumboredom
      Mar 28 '14 at 18:34










    • Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
      – elynnaie
      Mar 29 '14 at 13:15










    • That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
      – Quantumboredom
      Mar 30 '14 at 12:31










    • Arch Linux 3.13.7-1. systemd version 212.
      – elynnaie
      Mar 31 '14 at 6:52






    • 2




      I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
      – CMCDragonkai
      Jul 22 '14 at 6:22














    up vote
    17
    down vote













    Use --user-unit option, and in your case...



    journalctl --user-unit chatty





    share|improve this answer






















    • Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
      – Quantumboredom
      Mar 28 '14 at 18:34










    • Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
      – elynnaie
      Mar 29 '14 at 13:15










    • That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
      – Quantumboredom
      Mar 30 '14 at 12:31










    • Arch Linux 3.13.7-1. systemd version 212.
      – elynnaie
      Mar 31 '14 at 6:52






    • 2




      I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
      – CMCDragonkai
      Jul 22 '14 at 6:22












    up vote
    17
    down vote










    up vote
    17
    down vote









    Use --user-unit option, and in your case...



    journalctl --user-unit chatty





    share|improve this answer














    Use --user-unit option, and in your case...



    journalctl --user-unit chatty






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 2 '17 at 18:55









    Tshepang

    25.6k71182262




    25.6k71182262










    answered Mar 27 '14 at 8:15









    elynnaie

    29628




    29628











    • Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
      – Quantumboredom
      Mar 28 '14 at 18:34










    • Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
      – elynnaie
      Mar 29 '14 at 13:15










    • That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
      – Quantumboredom
      Mar 30 '14 at 12:31










    • Arch Linux 3.13.7-1. systemd version 212.
      – elynnaie
      Mar 31 '14 at 6:52






    • 2




      I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
      – CMCDragonkai
      Jul 22 '14 at 6:22
















    • Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
      – Quantumboredom
      Mar 28 '14 at 18:34










    • Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
      – elynnaie
      Mar 29 '14 at 13:15










    • That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
      – Quantumboredom
      Mar 30 '14 at 12:31










    • Arch Linux 3.13.7-1. systemd version 212.
      – elynnaie
      Mar 31 '14 at 6:52






    • 2




      I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
      – CMCDragonkai
      Jul 22 '14 at 6:22















    Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
    – Quantumboredom
    Mar 28 '14 at 18:34




    Are you getting the "test from chatty.service" stdout message in the log output as well, or just the "Starting chatty.service..." and "Started chatty.service." messages?
    – Quantumboredom
    Mar 28 '14 at 18:34












    Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
    – elynnaie
    Mar 29 '14 at 13:15




    Yes, I was able to get the output from the process as well (i.e. the "test from chatty.service" message).
    – elynnaie
    Mar 29 '14 at 13:15












    That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
    – Quantumboredom
    Mar 30 '14 at 12:31




    That is what I was expecting as well, but I don't see it here. May I ask what operating system (with version) you are running?
    – Quantumboredom
    Mar 30 '14 at 12:31












    Arch Linux 3.13.7-1. systemd version 212.
    – elynnaie
    Mar 31 '14 at 6:52




    Arch Linux 3.13.7-1. systemd version 212.
    – elynnaie
    Mar 31 '14 at 6:52




    2




    2




    I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
    – CMCDragonkai
    Jul 22 '14 at 6:22




    I see the output in the main journalctl now. But when I try running journalctl --user I get No journal files were found. And the journalctl --user-unit chatty didn't work for me.
    – CMCDragonkai
    Jul 22 '14 at 6:22












    up vote
    2
    down vote













    Until systemd v230, you had to use the less intuitive --user-unit flag to view the logs for your user's unit:



    journalctl --user-unit chatty


    Since systemd v230, you can now combine the --user and --unit flags as you'd expect:



    journalctl --user --unit chatty


    The --user --unit syntax is supported since Ubuntu 17.10.






    share|improve this answer




















    • I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
      – LeGEC
      Oct 25 at 14:12














    up vote
    2
    down vote













    Until systemd v230, you had to use the less intuitive --user-unit flag to view the logs for your user's unit:



    journalctl --user-unit chatty


    Since systemd v230, you can now combine the --user and --unit flags as you'd expect:



    journalctl --user --unit chatty


    The --user --unit syntax is supported since Ubuntu 17.10.






    share|improve this answer




















    • I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
      – LeGEC
      Oct 25 at 14:12












    up vote
    2
    down vote










    up vote
    2
    down vote









    Until systemd v230, you had to use the less intuitive --user-unit flag to view the logs for your user's unit:



    journalctl --user-unit chatty


    Since systemd v230, you can now combine the --user and --unit flags as you'd expect:



    journalctl --user --unit chatty


    The --user --unit syntax is supported since Ubuntu 17.10.






    share|improve this answer












    Until systemd v230, you had to use the less intuitive --user-unit flag to view the logs for your user's unit:



    journalctl --user-unit chatty


    Since systemd v230, you can now combine the --user and --unit flags as you'd expect:



    journalctl --user --unit chatty


    The --user --unit syntax is supported since Ubuntu 17.10.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 30 at 14:37









    Mark Stosberg

    3,8271125




    3,8271125











    • I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
      – LeGEC
      Oct 25 at 14:12
















    • I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
      – LeGEC
      Oct 25 at 14:12















    I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
    – LeGEC
    Oct 25 at 14:12




    I'm not sur the "--user --unit" feature works on v230 ... running v232 here, and this feature doesn't work
    – LeGEC
    Oct 25 at 14:12










    up vote
    0
    down vote













    Necroposting, but I faced and resolved the same issue today. Most probably journalctl --user-unit chatty didn't work you because you run it from root. However, per man journalctl, --user-unit filters log entries not only by _SYSTEMD_USER_UNIT=, but also by _UID=, and there is no chatty service with root's uid, so no entries are found.



    It's likely that you also have tried to run journalctl --user-unit chatty from your usual user, but got No journal files were found. This happens because (and All users are granted access to their private per-user journals from man journalctl can be confusing here) in 2018 on my Debian 9 journalctl still is not persistent by default (Storage=auto in /etc/systemd/journald.conf, and /var/log/journal/ doesn't exist), and in non-persistent mode journald doesn't support splitting logs, so all logs end up in single place in /run/log/journal despite the fact that splitting is turned on by default -- see SplitMode in man journald.conf. Enabling persistency fixes this.



    TL;DR: enable persistency by putting Storage=persistent to /etc/systemd/journald.conf and reloading journald with sudo systemctl restart systemd-journald.



    Alternatively, search with sudo journalctl _SYSTEMD_USER_UNIT=chatty.service



    Some more details are at
    https://lists.freedesktop.org/archives/systemd-devel/2016-October/037554.html






    share|improve this answer


























      up vote
      0
      down vote













      Necroposting, but I faced and resolved the same issue today. Most probably journalctl --user-unit chatty didn't work you because you run it from root. However, per man journalctl, --user-unit filters log entries not only by _SYSTEMD_USER_UNIT=, but also by _UID=, and there is no chatty service with root's uid, so no entries are found.



      It's likely that you also have tried to run journalctl --user-unit chatty from your usual user, but got No journal files were found. This happens because (and All users are granted access to their private per-user journals from man journalctl can be confusing here) in 2018 on my Debian 9 journalctl still is not persistent by default (Storage=auto in /etc/systemd/journald.conf, and /var/log/journal/ doesn't exist), and in non-persistent mode journald doesn't support splitting logs, so all logs end up in single place in /run/log/journal despite the fact that splitting is turned on by default -- see SplitMode in man journald.conf. Enabling persistency fixes this.



      TL;DR: enable persistency by putting Storage=persistent to /etc/systemd/journald.conf and reloading journald with sudo systemctl restart systemd-journald.



      Alternatively, search with sudo journalctl _SYSTEMD_USER_UNIT=chatty.service



      Some more details are at
      https://lists.freedesktop.org/archives/systemd-devel/2016-October/037554.html






      share|improve this answer
























        up vote
        0
        down vote










        up vote
        0
        down vote









        Necroposting, but I faced and resolved the same issue today. Most probably journalctl --user-unit chatty didn't work you because you run it from root. However, per man journalctl, --user-unit filters log entries not only by _SYSTEMD_USER_UNIT=, but also by _UID=, and there is no chatty service with root's uid, so no entries are found.



        It's likely that you also have tried to run journalctl --user-unit chatty from your usual user, but got No journal files were found. This happens because (and All users are granted access to their private per-user journals from man journalctl can be confusing here) in 2018 on my Debian 9 journalctl still is not persistent by default (Storage=auto in /etc/systemd/journald.conf, and /var/log/journal/ doesn't exist), and in non-persistent mode journald doesn't support splitting logs, so all logs end up in single place in /run/log/journal despite the fact that splitting is turned on by default -- see SplitMode in man journald.conf. Enabling persistency fixes this.



        TL;DR: enable persistency by putting Storage=persistent to /etc/systemd/journald.conf and reloading journald with sudo systemctl restart systemd-journald.



        Alternatively, search with sudo journalctl _SYSTEMD_USER_UNIT=chatty.service



        Some more details are at
        https://lists.freedesktop.org/archives/systemd-devel/2016-October/037554.html






        share|improve this answer














        Necroposting, but I faced and resolved the same issue today. Most probably journalctl --user-unit chatty didn't work you because you run it from root. However, per man journalctl, --user-unit filters log entries not only by _SYSTEMD_USER_UNIT=, but also by _UID=, and there is no chatty service with root's uid, so no entries are found.



        It's likely that you also have tried to run journalctl --user-unit chatty from your usual user, but got No journal files were found. This happens because (and All users are granted access to their private per-user journals from man journalctl can be confusing here) in 2018 on my Debian 9 journalctl still is not persistent by default (Storage=auto in /etc/systemd/journald.conf, and /var/log/journal/ doesn't exist), and in non-persistent mode journald doesn't support splitting logs, so all logs end up in single place in /run/log/journal despite the fact that splitting is turned on by default -- see SplitMode in man journald.conf. Enabling persistency fixes this.



        TL;DR: enable persistency by putting Storage=persistent to /etc/systemd/journald.conf and reloading journald with sudo systemctl restart systemd-journald.



        Alternatively, search with sudo journalctl _SYSTEMD_USER_UNIT=chatty.service



        Some more details are at
        https://lists.freedesktop.org/archives/systemd-devel/2016-October/037554.html







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 7 at 17:12









        Rui F Ribeiro

        38.6k1479128




        38.6k1479128










        answered Dec 7 at 11:43









        ars

        1183




        1183



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f109490%2fwhere-is-why-is-there-no-log-for-normal-user-systemd-services%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?