[systemd-devel] general systemd behavior question

Jesse Cobra jessecobra at gmail.com
Tue Nov 24 08:49:58 PST 2015


> Sure; just look as "man systemd" how to enable debug output.

How embarrassing for me ;)

Thank you, exactly what I needed to continue.

I narrowed it down to a service, of which I do not need. Problem solved.

Thanks again and apologies for not just checking the man page!



On Mon, Nov 23, 2015 at 8:29 PM, Andrei Borzenkov <arvidjaar at gmail.com>
wrote:

> 24.11.2015 06:37, Jesse Cobra пишет:
>
>> It is not happening at this moment but last week I saw these messages in
>> dmesg:
>>
>> [  755.629529] systemd[1]: Cannot add dependency job for unit
>> dmesg.service, ignoring: Unit dmesg.service is masked.
>>
>> [ 5177.325999] systemd[1]: Cannot add dependency job for unit
>> dmesg.service, ignoring: Unit dmesg.service is masked.
>>
>>
>> [ 5199.328069] systemd[1]: Cannot add dependency job for unit
>> dmesg.service, ignoring: Unit dmesg.service is masked.
>>
>>
>> [ 5205.738687] systemd[1]: systemd-journald.service watchdog timeout
>> (limit
>> 1min)!
>>
>>
>> And they coincided with ALSA underruns in my application.
>>
>> But again, I am just asking in general, does systemd have its own log?
>> Debug logging that I can enable?
>>
>>
> Sure; jut look as "man systemd" how to enable debug output. It should go
> into journal by default but can also be redirected to dmesg/console
> (although it requires reboot).
>
> Just asking a general question since I do not know where to start.
>>
>> -Jesse
>>
>> On Mon, Nov 23, 2015 at 6:02 PM, Reindl Harald <h.reindl at thelounge.net>
>> wrote:
>>
>>
>>>
>>> Am 24.11.2015 um 01:49 schrieb Jesse Cobra:
>>>
>>> I wish I had more info.
>>>>
>>>>
>>> jesus christ you talk about "I often seesystemd events logged in dmesg"
>>> without posting them
>>>
>>> Does systemd itself have a log file?
>>>
>>>>
>>>> Not the service I am creating but systemd itself.
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 5
>>>> Date: Sat, 21 Nov 2015 11:58:51 +0100
>>>> From: Reindl Harald <h.reindl at thelounge.net <mailto:
>>>> h.reindl at thelounge.net>>
>>>> To: systemd-devel at lists.freedesktop.org
>>>> <mailto:systemd-devel at lists.freedesktop.org>
>>>> Subject: Re: [systemd-devel] generalsystemdbehaviorquestion
>>>> Message-ID: <56504E6B.90806 at thelounge.net
>>>> <mailto:56504E6B.90806 at thelounge.net>>
>>>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>>>
>>>> Am 21.11.2015 um 09:00 schrieb Jesse Cobra:
>>>>
>>>> I often seesystemd events logged in dmesg at this same time also at
>>>>> 1500 seconds or intervals of 1500 seconds. It could be totally
>>>>> unrelated.
>>>>>
>>>>> Anyways, doesSystemD itself have a log or a config file or some timeout
>>>>> setting around this?
>>>>>
>>>>>
>>>> a good start for questions would be include what you are talking about
>>>> since nobody has a look at your screen and the messages....
>>>>
>>>>
>>>
>>> _______________________________________________
>>> systemd-devel mailing list
>>> systemd-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20151124/9d301ab5/attachment.html>


More information about the systemd-devel mailing list