Re: [systemd-devel] systemd coredumps
Oh. I see I need to ask OpenSuse to fix or get a newer OpenSuse version. Thank you Markus "ZbigniewJędrzejewski-Szmek" wrote in message news:20150101181747.gl18...@in.waw.pl... On Thu, Jan 01, 2015 at 01:13:30PM -0500, Dave Reisner wrote: On Thu, Jan 01, 2015 at 07:05:04PM +0100, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote: > > Hi, > > > > How can I find out why systemd core dumps and requires system > > reboot :-( ? > > > > I just did > > > > # systemctl status sockd-1.5.0 > > Failed to issue method call: Did not receive a reply. Possible > > causes include: the remote application did not send a reply, the > > message bus security policy blocked the reply, the reply timeout > > expired, or the network connection was broken. > > # systemctl status sockd-1.5.0 > > Failed to get D-Bus connection: Failed to connect to socket > > /run/systemd/private: Connection refused > > > > 2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted > > connection on private bus. > > 2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC... > > 2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus > > request: org.freedesktop.DBus.Properties.GetAll() on > > /org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0 > > 2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion > > 'endswith(path, ".service")' failed at src/core/service.c:1077, > > function service_load_sysv_name(). Aborting. > The reason is given right here. A failed assertion, i.e. a programming > error. > > Please open a bug on bugs.freedesktop.org and attach the core if you can > and describe the steps to trigger this. Hrmm? The OP is using a build of systemd v195. It's unlikely this is reproducible at HEAD, or any recent release. The referenced function was removed in v214 (see commit 817e224bbce3ed) when sysv unit handling was moved off to a generator. Good point, I didn't look at the version. Indeed, the bug is long fixed. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd coredumps
OK I logged it as https://bugs.freedesktop.org/show_bug.cgi?id=87943 . I can't seem to get a core dump file. Markus "ZbigniewJędrzejewski-Szmek" wrote in message news:20150101180504.gj18...@in.waw.pl... On Thu, Jan 01, 2015 at 05:57:43PM -, Markus Moeller wrote: Hi, How can I find out why systemd core dumps and requires system reboot :-( ? I just did # systemctl status sockd-1.5.0 Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. # systemctl status sockd-1.5.0 Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused 2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted connection on private bus. 2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC... 2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0 2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion 'endswith(path, ".service")' failed at src/core/service.c:1077, function service_load_sysv_name(). Aborting. The reason is given right here. A failed assertion, i.e. a programming error. Please open a bug on bugs.freedesktop.org and attach the core if you can and describe the steps to trigger this. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd coredumps
Hi, How can I find out why systemd core dumps and requires system reboot :-( ? I just did # systemctl status sockd-1.5.0 Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. # systemctl status sockd-1.5.0 Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused 2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted connection on private bus. 2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC... 2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0 2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion 'endswith(path, ".service")' failed at src/core/service.c:1077, function service_load_sysv_name(). Aborting. 2015-01-01T17:52:01.686714+00:00 opensuse12 systemd[1]: Caught , dumped core as pid 2925. 2015-01-01T17:52:01.687538+00:00 opensuse12 systemd[1]: Freezing execution. I am running Opensuse 12.3 # rpm -q -f /sbin/init systemd-sysvinit-195-13.45.1.x86_64 # systemd --version systemd 195 suse +PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ Thank you Markus ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-sysv-generator question
Thank you Markus "Mantas Mikulėnas" wrote in message news:capwny8vgpomx8nfym+k84-w5sf8-5+yo2zuzuqx3__thoq2...@mail.gmail.com... On Wed, Dec 31, 2014 at 4:31 PM, Markus Moeller wrote: Hi, I am knew to systemd and wonder how to use it correctly. I have a simple /etc/init.d/squid startup script which works with systemd. I now copied it to /etc/init.d/mysquid and updated the content accordingly. Now /etc/init.d/mysquid start fails saying the services fail is missing. I check the starndard squid package installer and it also does not contain a services file. I only saw update-rc which I run, but no change. After long search of my filesystem I found /run/systemd/generator.late/squid.service with a comment: # Automatically generated by systemd-sysv-generator Reading about systemd-sysv-generator it says it is run early in the boot process so after a reboot I also got /run/systemd/generator.late/mysquid.service How can I run the service file creation manually instead of forcing a system reboot ? Use `systemctl daemon-reload`. -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-sysv-generator question
Hi, I am knew to systemd and wonder how to use it correctly. I have a simple /etc/init.d/squid startup script which works with systemd. I now copied it to /etc/init.d/mysquid and updated the content accordingly. Now /etc/init.d/mysquid start fails saying the services fail is missing. I check the starndard squid package installer and it also does not contain a services file. I only saw update-rc which I run, but no change. After long search of my filesystem I found /run/systemd/generator.late/squid.service with a comment: # Automatically generated by systemd-sysv-generator Reading about systemd-sysv-generator it says it is run early in the boot process so after a reboot I also got /run/systemd/generator.late/mysquid.service How can I run the service file creation manually instead of forcing a system reboot ? Thank you Markus Apologies if this is not the right mailing list for this question ( please let me know which one is) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
