Am 27.07.2016 um 02:59 schrieb John Pearson:
> Hello Michael,
>
> After the problem first occurred I reviewed bug #767468 and purged both
> cgmanager and sytemd-shim, but the problem remained. And, of course,
> /proc shows systemd-machined (and only systemd-machined) still "thought"
> /nfs/home w
Am 13.09.2016 um 11:21 schrieb Vektor:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: important
>
> Dear Maintainer,
>
> systemd-journald is deleting log messages when it shouldn't, it is not
> respecting SystemMaxUse and SystemKeepFree as configured in
> /etc/systemd/journald.conf
>
Am 22.07.2016 um 00:28 schrieb Yuri D'Elia:
> On Fri, Jul 22 2016, Michael Biebl wrote:
>> So, this is the main reason I'm worried about enabling lz4 support.
>> Afair, it's not runtime configurable, so each new journal entry would be
>> lz4 compressed, which effectively means we will have to use
Your message dated Sat, 22 Oct 2016 02:20:37 +0200
with message-id <51463290-6bd3-4ef9-0066-55ad31389...@debian.org>
and subject line Re: Bug#767551: closed by Michael Biebl
(Re: Bug#767551: udev: udev_root support missing)
has caused the Debian Bug report #767551,
regarding udev: udev_root suppo
Your message dated Sat, 22 Oct 2016 02:16:49 +0200
with message-id <5221ecd5-6205-24b3-b58f-07bca8b78...@debian.org>
and subject line Re: Bug#837157: systemd: Use idiomatic variables in
debian/rules
has caused the Debian Bug report #837157,
regarding systemd: Use idiomatic variables in debian/rule
Am 01.02.2016 um 16:41 schrieb Josh Triplett:
> On Mon, Feb 01, 2016 at 04:24:21PM +0100, Ondřej Surý wrote:
>> Hi Michael,
>>
>> I never bothered to implement more than 'd', but I am happy to
>> contribute my sysvrc shell snippet I use as replacement for systems
>> without systemd-tmpfiles install
Control: reassign -1 zsh 5.2-5
Am 26.09.2016 um 23:11 schrieb Martin Steigerwald:
> Am Montag, 26. September 2016, 13:53:21 CEST schrieb Josh Triplett:
>> On Mon, Sep 26, 2016 at 10:27:40PM +0200, Martin Steigerwald wrote:
>>> Am Montag, 26. September 2016, 13:08:07 CEST schrieb Josh Triplett:
>>>
Processing control commands:
> reassign -1 zsh 5.2-5
Bug #836580 [systemd] systemd: systemctl status pipes through less with escape
sequences not applied
Bug reassigned from package 'systemd' to 'zsh'.
No longer marked as found in versions systemd/231-5.
Ignoring request to alter fixed versions o
Processing control commands:
> tags -1 - moreinfo
Bug #830775 [systemd] systemd: systemctl poweroff ask me twice for user and
password.
Removed tag(s) moreinfo.
> forwarded -1 https://github.com/systemd/systemd/issues/4124
Bug #830775 [systemd] systemd: systemctl poweroff ask me twice for user an
Control: tags -1 - moreinfo
Control: forwarded -1 https://github.com/systemd/systemd/issues/4124
Am 11.07.2016 um 14:33 schrieb Pavel Kosina:
> Its ssh, putty,
>
> dady@linuxbox:~$ systemctl poweroff
> AUTHENTICATING FOR org.freedesktop.login1.set-wall-message ===
> Authentication is require
Your message dated Sat, 22 Oct 2016 01:57:45 +0200
with message-id
and subject line Re: Bug#837218: lv: breaks systemctl display status
has caused the Debian Bug report #837218,
regarding lv: breaks systemctl display status
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> forcemerge 839607 -1
Bug #839607 [systemd] Robustify manager_dispatch_notify_fd()
Bug #839811 [systemd] systemd causes slow system with systemd-notify empty
string
Bug #839607 [systemd] Robustify manager_dispatch_notify_fd()
Marked as found in versions systemd/215-1
Control: forcemerge 839607 -1
Am 11.10.2016 um 23:43 schrieb Keller Fuchs:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: important
> File: systemd-logind
>
> Dear maintainers,
>
> On a shell server I co-administer (to1.hashbang.sh), systemd-logind got
> stuck in a restart loop, forcing
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #835464 [udev] udev: Modules no longer loaded
Added tag(s) unreproducible and moreinfo.
--
835464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo unreproducible
Am 26.08.2016 um 02:53 schrieb Jean-Philippe MENGUAL:
> Package: udev
> Version: 231-4
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
Processing control commands:
> reassign -1 initscripts
Bug #782142 [systemd] systemd: Tries to mount NFS shares twice (?)
Bug reassigned from package 'systemd' to 'initscripts'.
No longer marked as found in versions systemd/215-14.
Ignoring request to alter fixed versions of bug #782142 to the sam
Your message dated Sat, 22 Oct 2016 00:18:38 +0200
with message-id <28bb6fa4-e538-3108-79d4-ba6802838...@debian.org>
and subject line Re: systemd: users should not have to put a value greater than
desired in MaxRetentionSec to avoid loss of information
has caused the Debian Bug report #766074,
reg
Control: reassign -1 initscripts
On Wed, 8 Apr 2015 13:33:54 +0200 (CEST) Santiago Vila
wrote:
> Package: systemd
> Version: 215-14
>
> After a recent upgrade in a lab where I use NFS, I see messages like this:
>
> ifup[370]: mount.nfs: /home/nfs is busy or already mounted
That hook is shipped
I just want to follow up on this that I believe I have found the reason for
this bug and I have a solution which I am testing out.
In the output of `systemctl status systemd-journald` it says:
Active: failed (Result: start-limit)
and this is related to the systemd mechanism to stop cycles where
No. Journald doesn't start from boot, rsyslog does but isn't listening
to the socket.
and if I run
$ logger ciao
logger: socket /dev/log: Connessione rifiutata
Files open by rsyslog are these:
root@mongibello /proc/948/fd # ll
totale 0
lr-x-- 1 root root 64 ott 21 14:53 0 -> /dev/null
l-wx
Am 21.10.2016 um 15:31 schrieb Salvo Tomaselli:
> Hello,
>
> me neither. I don't know when it 1st happened. I just wanted to see
> something in the logs and there were no logs besides the ones
> generated by the kernel in /var/log/syslog
/var/log/syslog is not generated by the kernel, but your s
Processing commands for cont...@bugs.debian.org:
> severity 793116 important
Bug #793116 [systemd] systemd: journald randomly exits with USR1, leaving
/dev/log unusable
Severity set to 'important' from 'critical'
> tags 793116 + moreinfo
Bug #793116 [systemd] systemd: journald randomly exits with
Hello,
me neither. I don't know when it 1st happened. I just wanted to see
something in the logs and there were no logs besides the ones
generated by the kernel in /var/log/syslog
I don't know how you can reproduce the problem.
I did not change my journald.conf, which I attach.
2016-10-21 15:2
Control: severity -1 important unreproducible
Control: tags -1 moreinfo
Am 21.10.2016 um 15:02 schrieb Salvo Tomaselli:
> severity 793116 critical
> thanks
>
> I am experiencing the same problem, but upon reboot journald won't
> start, so I have no logging whatsoever.
>
> For this reason I'm ra
Processing control commands:
> severity -1 important unreproducible
Unknown command or malformed arguments to command.
> tags -1 moreinfo
Bug #793116 [systemd] systemd: journald randomly exits with USR1, leaving
/dev/log unusable
Added tag(s) moreinfo.
--
793116: http://bugs.debian.org/cgi-bin
severity 793116 critical
thanks
I am experiencing the same problem, but upon reboot journald won't
start, so I have no logging whatsoever.
For this reason I'm raising the severity of the problem, since I have
no way of knowing what the daemons on my machine are up to.
___
Processing commands for cont...@bugs.debian.org:
> severity 793116 critical
Bug #793116 [systemd] systemd: journald randomly exits with USR1, leaving
/dev/log unusable
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
793116
27 matches
Mail list logo
