First thing we can do is to cross validate this with our CI: https://ci.bigtop.apache.org/view/Test/job/Bigtop-trunk-smoke-tests-1.4.0/
>From your log it seems that failure happens at deployment stage, while our CI are good on Debian 9 with ARM and X86. I checked that both arm and x86 images are using following systemd version: root@04812187f0f2:~# systemd --version systemd 232 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN The version diff is probably the reason as what you investigated. I don't have any idea yet. Maybe other folks at Bigtop can chime in? Guodong Xu <[email protected]> 於 2019年6月24日 週一 下午4:18寫道： > Hi, all > > I found a crucial failure related to 'systemd' when installing Bigtop 1.4 > onto Debian 9. (Problem may exist on other versions of bigtop releases as > well, but I didn't test). > > The issue is when running '# systemctl status flink-taskmanager', it > always fail with such message: > Jun 24 07:28:59 j12-d05-09 systemd[1]: flink-taskmanager.service: New main > PID 26238 does not belong to service, and PID file is not owned by root. > Refusing. > > A further investigation leads me to this similar bug report in VNC: a bug > report from VNC users: https://bugzilla.redhat.com/show_bug.cgi?id=1583159 > > And to this change commit in systemd: commit link: > > https://github.com/systemd/systemd/commit/db256aab13d8a89d583ecd2bacf0aca87c66effc > > "core: be stricter when handling PID files and MAINPID sd_notify() > messages" > > Did anybody see this issue before? Should I log a bug for it? Solutions > maybe? Thanks a lot. > > PS, my 'systemd' version is: > # systemd --version > systemd 241 (241) > +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP > +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN > -PCRE2 default-hierarchy=hybrid > > Best regards > Guodong Xu >
