[systemd-devel] Failed to open system journal: Invalid argument
Hello Folks, I have enabled more debug logs & realized following 2 logs are continuously being dump. *Is it some known bug for systemd-journald for following version? I am using Angstrom distribution of debian OS?* root@arria10:~# uname -a Linux arria10 4.9.78-ltsi #1 SMP Thu Dec 13 12:01:27 PST 2018 armv7l GNU/Linux root@arria10:~# systemctl --version systemd 239 +PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid LOG: -- root@arria10:~# *[ 2002.668599] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B* *[ 2002.679080] systemd-journald[743]: Failed to open system journal: Invalid argument* [ 2002.686750] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2002.697135] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2002.705876] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2002.716317] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2002.723999] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2002.734703] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2002.742845] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.663137] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.673722] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2062.681505] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.691980] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2062.700808] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.711412] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2062.719171] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.729639] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2062.737827] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2062.748330] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2112.662005] systemd-journald[743]: Sent WATCHDOG=1 notification. [ 2112.669418] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2112.679851] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2112.687503] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2112.697859] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2112.706642] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2112.717098] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2112.724776] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2112.735142] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2112.743220] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.664190] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.674654] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2122.682278] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.692638] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2122.701584] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.712049] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2122.719695] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.730205] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2122.738354] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2122.748794] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2128.913734] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2128.924461] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2128.932107] systemd-journald[743]: Journal effective settings seal=yes compress=yes compress_threshold_bytes=512B [ 2128.942493] systemd-journald[743]: Failed to open system journal: Invalid argument [ 2128.951361] systemd-journald[743]: Journal effective
Re: [systemd-devel] interacting with logind to detect user idle time
Perfect, thank you very much! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] interacting with logind to detect user idle time
On Do, 16.05.19 17:12, Germano Massullo (germano.massu...@gmail.com) wrote: > To do practise I am using NetworkManager example [1] > All macros passed as arguments to functions > g_dbus_proxy_call_sync > g_dbus_proxy_new_for_bus_sync > are implemented at [2]. > Is there an equivalent of [2] for logind? I made a quick search into > systemd repository [3] but I am getting too many results with the > search words I am using. I just need to figure out what parameters I > have to pass to the previous functions in order to retrieve > IdleSinceHint property If you are looking for some help regarding gdbus, it's probably best to inquire on some gdbus/glib mailing list. With the "busctl" tool you can read the propery with a command like the following: busctl get-property org.freedesktop.login1 /org/freedesktop/login1/session/_31 org.freedesktop.login1.Session IdleSinceHint I am sure the gdbus folks will be able to give you the right hints how to do the same with native gdbus API calls quickly if you ask them for the equivalent of the above line. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 6/6] pstore: The new documentation for the pstore configuration file
Is there a pstore related man page you could add to the reference section? Le jeu. 16 mai 2019 à 17:03, systemd github import bot a écrit : > Patchset imported to github. > To create a pull request, one of the main developers has to initiate one > via: > < > https://github.com/systemd/systemd/compare/master...systemd-mailing-devs:1558016915-24397-7-git-send-email-eric.devolder%40oracle.com > > > > -- > Generated by https://github.com/haraldh/mail2git > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Weston not launching Via Service file.
On Fri, 17 May 2019 04:36:52 + Rajshekhar Sanda wrote: > Hello, > > > We are working on Genivi14, in which we are trying to launch weston > via service file. It is not working if iam giving Type=notify in > service file. > Hi, could you attach the stderr and stdout output of Weston as well, please? You should be able to find that in your system journal I guess. That should help diagnose if it is a problem with Weston or with the systemd unit file. Thanks, pq pgpmRXRbjS0SD.pgp Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
