[systemd-devel] Is this list still active? Where can I get basic help with systemd

Tue Dec 5 18:33:26 UTC 2017

Getting rid of the template syntax changed the behavior but now it appears
there's another problem I don't understand.
it tries to start the unit and it shows some encouraging signs but fails
because a timeout was exceeded.
Celery starts and shows healthy output but then sends a SIGCHLD and then
dies
I don't know if you know what celery is but its a task queue so it does
create child processes
I thought the Type=forking line in the service unit would let systemd about
that.
Or maybe its dying for some other reason?
It works fine when run without systemd
I don't think I can send you detailed output until we get this issue
resolved with the mailing list and why its not excepting emails with debug
output.
Short emails seem to post. Long ones don't. There's no indication of whats
going on
I'll try including the journalctl -xe output and see if that crashes the
email list:

Dec 05 13:20:30 stower celery[5675]: ---- **** -----
Dec 05 13:20:30 stower celery[5675]: --- * ***  * --
Linux-3.10.0-693.5.2.el7.x86_64-x86_64-with-centos-7.4.1708-Core 2017-12-05
13:19:02
Dec 05 13:20:30 stower celery[5675]: -- * - **** ---
Dec 05 13:20:30 stower celery[5675]: - ** ---------- [config]
Dec 05 13:20:30 stower celery[5675]: - ** ---------- .> app:
 tasks:0x1e15c90
Dec 05 13:20:30 stower celery[5675]: - ** ---------- .> transport:
 amqp://guest:**@localhost:5672//
Dec 05 13:20:30 stower celery[5675]: - ** ---------- .> results:     rpc://
Dec 05 13:20:30 stower celery[5675]: - *** --- * --- .> concurrency: 2
(prefork)
Dec 05 13:20:30 stower celery[5675]: -- ******* ---- .> task events: OFF
(enable -E to monitor tasks in this worker)
Dec 05 13:20:30 stower celery[5675]: --- ***** -----
Dec 05 13:20:30 stower celery[5675]: -------------- [queues]
Dec 05 13:20:30 stower celery[5675]: .> celery
 exchange=celery(direct) key=celery
Dec 05 13:20:30 stower celery[5675]: [tasks]
Dec 05 13:20:30 stower celery[5675]: . tasks.test.add
Dec 05 13:20:30 stower celery[5675]: . tasks.twt_api.tasks.twt_followers_ids
Dec 05 13:20:30 stower celery[5675]: . tasks.twt_api.tasks.twt_friends_ids
Dec 05 13:20:31 stower systemd[1]: Received SIGCHLD from PID 5675 (celery).
Dec 05 13:20:31 stower systemd[1]: Child 5675 (celery) died (code=exited,
status=0/SUCCESS)
Dec 05 13:20:31 stower systemd[1]: Child 5675 belongs to celery_bf.service
Dec 05 13:20:31 stower systemd[1]: celery_bf.service: control process
exited, code=exited status=0
Dec 05 13:20:31 stower polkitd[684]: Unregistered Authentication Agent for
unix-process:5659:1185247 (system bus name :1.53, object path
/org/freedesktop/Polic
Dec 05 13:20:31 stower systemd[1]: celery_bf.service got final SIGCHLD for
state final-sigterm
Dec 05 13:20:31 stower systemd[1]: celery_bf.service changed final-sigterm
-> failed
Dec 05 13:20:31 stower systemd[1]: Job celery_bf.service/start finished,
result=failed
Dec 05 13:20:31 stower systemd[1]: Failed to start Celery bf Service.
-- Subject: Unit celery_bf.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit celery_bf.service has failed.
-- 
-- The result is failed.
Dec 05 13:20:31 stower systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Mana
Dec 05 13:20:31 stower systemd[1]: Sent message type=method_call sender=n/a
destination=org.freedesktop.DBus object=/org/freedesktop/DBus
interface=org.freedes
Dec 05 13:20:31 stower systemd[1]: Unit celery_bf.service entered failed
state.
Dec 05 13:20:31 stower systemd[1]: celery_bf.service failed.
Dec 05 13:20:31 stower systemd[1]: celery_bf.service: cgroup is empty
Dec 05 13:20:31 stower systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/freedesktop/systemd1/unit/celery_5fbf_2eservice
interface=or
Dec 05 13:20:31 stower systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/freedesktop/systemd1/unit/celery_5fbf_2eservice
interface=or
Dec 05 13:20:31 stower systemd[1]: Got message type=method_call
sender=:1.54 destination=org.freedesktop.systemd1
object=/org/freedesktop/systemd1/unit/celery_
Dec 05 13:20:31 stower systemd[1]: Sent message type=method_call sender=n/a
destination=org.freedesktop.DBus object=/org/freedesktop/DBus
interface=org.freedes
Dec 05 13:20:31 stower systemd[1]: Sent message type=method_call sender=n/a
destination=org.freedesktop.DBus object=/org/freedesktop/DBus
interface=org.freedes
Dec 05 13:20:31 stower systemd[1]: Sent message type=method_call sender=n/a
destination=org.freedesktop.DBus object=/org/freedesktop/DBus
interface=org.freedes
Dec 05 13:20:31 stower systemd[1]: SELinux access check
scon=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcon=unconfined_u:object_r:systemd_unit_file
Dec 05 13:20:31 stower systemd[1]: Sent message type=method_return
sender=n/a destination=:1.54 object=n/a interface=n/a member=n/a
cookie=1317 reply_cookie=7
Dec 05 13:20:31 stower systemd[1]: Got cgroup empty notification for:
/system.slice/celery_bf.service
Dec 05 13:20:31 stower systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/freedesktop/systemd1/agent
interface=org.freedesktop.systemd
Dec 05 13:20:31 stower systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n/a object=/org/freedesktop/DBus
interface=org.freedesktop.

On Tue, Dec 5, 2017 at 1:04 PM, Doug Snyder <webcoach101 at gmail.com> wrote:

> I'm trying to get you the debug output as described in
> https://freedesktop.org/wiki/Software/systemd/Debugging/#index3h1
> I'm sending the emails but they aren't showing up in the email list at:
> https://lists.freedesktop.org/archives/systemd-devel/
> 2017-December/thread.html#39934
> with or without email attachments
>
> At this point two people have said I have an updated systemd which is
> strange because I thought I used the latest CentOS minimal install
> $ systemctl --version
> systemd 219
> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
> So maybe it makes sense for me to just update and see if that resolves
> this.
>
> I don't know how to do that though.
> I found these instruciton but they don't work anymore:
> https://www.certdepot.net/new-systemd-version/
>
>
>
> On Tue, Dec 5, 2017 at 9:36 AM, Lennart Poettering <lennart at poettering.net
> > wrote:
>
>> On Sa, 02.12.17 20:40, Doug Snyder (webcoach101 at gmail.com) wrote:
>>
>> > I'm trying to write a basic systemd service. The ExecStart command I'm
>> > using works. The systemd service doesn't. It throws a cryptic error and
>> I
>> > can't find any documentation on the web that makes any sense of it. I
>> > posted on this list and got no responses. Is this list active? If not is
>> > there somewhere I can get basic help for setting up a service. Systemd
>> is
>> > the default tool daemonizing on most Linux distros right? There must be
>> > some way to get help to get a basic example working.
>>
>> Please always indicate which systemd version you are using, which
>> distribution and which kernel.
>>
>> > Nov 20 13:58:33 stower systemd[1]: celery_bf.service failed to run
>> 'start'
>> > task: Operation not supported
>>
>> Hmm, this indicates that some kernel functionality required is not
>> available in the kernel. I am not sure which one that is, and logging
>> is a bit too brief for that.
>>
>> If you run "systemd-analyze set-log-level debug", and run this again,
>> what do you see then?
>>
>> Lennart
>>
>> --
>> Lennart Poettering, Red Hat
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20171205/b07a9bfe/attachment-0001.html>