Hi list,
I hit a bug today in the "scope" unit support. Reproducible like this:
systemd-nspawn -bD /srv/subarch
systemctl stop machine-subarch.scope
systemctl start machine-subarch.scope
I wasn't sure whether "start" would do anything or not so I gave it a
shot, but it turned out to crash the ho
On Mon, Apr 22, 2013 at 11:31 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> Otherwise, we get SYSLOG_IDENTIFIER=python or something
> similar, which is completely useless.
I think we shouldn't be creating one-off arguments for every possible
field someone might want to add, but something more generic
012 at 12:43 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Mon, Oct 15, 2012 at 11:30:09PM +0300, Marti Raudsepp wrote:
>> 1. Event data
>> One clear use case that's fairly easy to support is supplying custom
>> message-specific data, such as MESSAGE_ID. Or details of the e
On Sun, Oct 14, 2012 at 2:22 PM, David Strauss wrote:
> This support has been on my task list for a while. Thanks for taking a
> first stab at it. A cursory look at the patch looks promising, and
> I'll probably commit it after some basic testing in the next few days.
I've been pondering how deve
On Mon, Oct 1, 2012 at 8:22 PM, Jan Engelhardt wrote:
>>and how they should do this after the change that there
>>is no flag? dispaly a RANDOM line?
>
> That is a possibility. Based upon that you are only interested
> in the device anyway, I conclude the mountpoint is irrelevant.
I didn't read th
Hi list,
The attached patch implements journal integration for the Python
logging framework. Tested on my Arch Linux machine, using Python 2.7
and 3.2, but should be compatible with all versions from 2.5 through
3.3
The logging framework has a mechanism for supplying additional
key-value pairs, b
Hi list,
Recently I upgraded to Gnome 3.6 on my Arch Linux desktop, but
gnome-session didn't work no matter what I tried. Ages of debugging
later, strace revealed this:
[pid 2063] open("/proc/1/cgroup", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[...]
[pid 2063] writev(2, [{"gno
On Wed, May 30, 2012 at 10:59 PM, Lennart Poettering
wrote:
> Many people have configured their classic syslog daemon to output logs
> on /dev/tty12. If you press C-s there (or accidentally hit Scroll Lock)
> you end up freezing syslog too and thus freezing the entire machine
> sooner or later. It
On Wed, May 30, 2012 at 10:52 PM, Marti Raudsepp wrote:
> The two broken files (mostly consisting of zeroes) attached.
Well, they are now... :)
Regards,
Marti
broken-journal.tar.gz
Description: GNU Zip compressed data
___
systemd-devel mailing l
Hi list,
As usual, attempting to debug one problem inevitably leads to another
bug. I found out that after filling my disk and SIGKILLing journald a
few times, it seems to corrupt the journal archive. Seems to be
reproducible every time.
journalctl reports: Failed to iterate through journal: Bad m
On Wed, May 30, 2012 at 4:45 PM, Lennart Poettering
wrote:
> OK, there indeed was a loop here, where we ended up processing messages
> we ourselves wrote to kmsg. I have fixed that now in git. Could you test
> please if this solves your problems?
Thanks. Yes, looks like this fixes my issue.
I fi
On Mon, May 28, 2012 at 8:33 PM, Marti Raudsepp wrote:
> Removing /var/log/journal/* didn't help -- journald created new files
> and got stuck again.
Well removing the whole /var/log/journal and restarting journald fixed
the problem. Re-creating and restarting reproduced int every t
Hi list,
Long story short, I believe there are two problems with journald:
1) journald gets stuck in an infinte loop, trying to send the message
"Dropping message, as we can't find a place to store the data" to
somewhere -- occurs in v44 and v183 (Arch Linux)
2) A journald problem can effectively
On Mon, Mar 26, 2012 at 21:07, Lennart Poettering
wrote:
> Marti, sorry for changing my mind on this: would be great if you could
> prep a patch for this for systemd itself.
D'oh, I already prepared a patch for kexec, although I haven't sent it out yet.
> Hmm, so since this would then belong in
Hi list,
I was recently pondering how systemd could use kexec "properly", in a
reasonably general way, to make reboots faster. I exchanged an email
with Poettering on the systemd list and he suggested me to ask here.
My current proposal:
1. Include a template 'kexec-load.service' with kexec-tools
On Thu, Mar 22, 2012 at 02:16, Mirco Tischler wrote:
> Unless you want to use kexec on panic. In that case the kexec kernel
> should be loaded at boot, doesn't it? But I don't know if this is
> actually in use or more a debugging tool for kernel devs.
Sure, the crashdump kernel is loaded with 'ke
Hi,
I've been trying to figure out how to use systemd's kexec functionality right.
When one runs "systemctl kexec", systemd simply shuts down and
executes 'kexec -e'. For this to work, a kexec-able kernel has to be
already loaded.
Now, when do I load this kernel? Loading at startup means that I'
2012/3/15 Martín Marqués :
> I the old system, I had the script make a redirection of the pg_ctl
> (postgresql script for starting, stopping, etc the server) output to a
> file, which would be the log file (default behaviour in Debian).
If you're talking about catching errors from pg_ctl itself th
On Wed, Mar 14, 2012 at 20:10, Lennart Poettering
wrote:
> I think I would prefer if do not repeat the the meta data in the output,
> and just output the actual message, line-by-line, prefixed with
> whitespace. So that we'd get this:
>
> Mar 07 12:23:57 host postgres[6326]: line1
>
urnal/sd-journal.c:651
#8 sd_journal_next (j=0xbc0010) at src/journal/sd-journal.c:686
#9 main (argc=5, argv=0x7fff1d5ce308) at src/journal/journalctl.c:263
From 9266fc6a58065a7c5dab67430fd78925e519dce9 Mon Sep 17 00:00:00 2001
From: Marti Raudsepp
Date: Fri, 9 Mar 2012 16:23:00 +0200
Subject: [PATCH] journa
Hi list,
Some applications, such as PostgreSQL have log messages consisting of
multiple lines. When reporting to syslog, these messages are
artificially split into multiple log lines. But it would be nice to
get rid of that legacy with journal -- to prevent lines from being
interleaved with other
On Tue, Nov 1, 2011 at 19:26, Lennart Poettering wrote:
> I didn't really give this much testing, so it would be good if you could
> check out if this works for you!
I built git version as of 263653e10353d8ad155f1faba01981816a2bb712 and
indeed this fixes the simple case.
> I have now commited a
> On Fri, 09.09.11 13:57, Marti Raudsepp (ma...@juffo.org) wrote:
>> Tom Gundersen on #systemd reduced the problem down to this: "telinit u
>> && reboot"
>> When I run the above, I get into the same state that /sbin/reboot
>> doesn't function.
On Fri, Sep 9, 2011 at 13:57, Marti Raudsepp wrote:
> I'm using systemd 35 on Arch Linux testing. Recently I had an upgrade
> for the glibc package and following that, I couldn't use sysvinit's
> /sbin/reboot -- the command would broadcast its message, wait for a
>
Dear list,
I'm using systemd 35 on Arch Linux testing. Recently I had an upgrade
for the glibc package and following that, I couldn't use sysvinit's
/sbin/reboot -- the command would broadcast its message, wait for a
few seconds and then quit. 'systemctl reboot' still works as supposed.
This is w
25 matches
Mail list logo
