[systemd-devel] Where are the places systemd logs?

[Reindl Harald]

Am 07.01.20 um 02:16 schrieb Jeffrey Walton:
> On Mon, Jan 6, 2020 at 7:49 PM Reindl Harald <h.reindl at thelounge.net> wrote:
>>
>>
>>
>> Am 07.01.20 um 01:43 schrieb Jeffrey Walton:
>>> On Mon, Jan 6, 2020 at 7:41 PM Reindl Harald <h.reindl at thelounge.net> wrote:
>>>>
>>>> Am 07.01.20 um 01:34 schrieb Jeffrey Walton:
>>>>> I am missing information about my services. I've got dead services without logs.
>>>>>
>>>>> Where are the places systemd logs?
>>>>
>>>> journalctl unless you configure rsylog or something else to fetch the
>>>> logs for classic textfiles
>>>
>>> No, journalctl is missing the entries.
>>
>> you really need to be morte specific what you are talking about at all -
>> i get the feeling you talk about logs which are completly unrelated to
>> syslog at all
>>
>>> Is there a way to configure systemd to log to /var/log/messages?
>>
>> no, and anything that's not visibile in journalctl simply don't exist
> 
> Thanks.
> 
> Something is broken here. I can manually start a service, but systemd
> can't/won't automatically start it at boot. But the kicker is, there
> are no logs anywhere until I manually start it.
> 
> The service was previously [trying to] starting at boot, but it failed
> to start because systemd seems to lie about when the network is
> available. So I added additional After= and Wants=, and now no service
> and no logs.
> 
> I really don't get this tool and why it hides so much information from people.

i don't hide anything

what about stop talking generic stuff and post your systemd-units and
learn about "systemctl status" which at least on not 10 years old
systems even outputs the logs of a specific service including stdout/stderr