You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Valery Vybornov (Jira)" <ji...@apache.org> on 2020/02/16 15:26:00 UTC
[jira] [Comment Edited] (BIGTOP-3307) systemd fails to properly
start Hadoop services
[ https://issues.apache.org/jira/browse/BIGTOP-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037857#comment-17037857 ]
Valery Vybornov edited comment on BIGTOP-3307 at 2/16/20 3:25 PM:
------------------------------------------------------------------
The following lines in systemd log indicate that the issue is likely caused by recent changes in systemd called 'stricter PIDfile handling`.
{noformat}
Feb 10 17:22:05 bigtop1.vagrant systemd[1]: New main PID 14387 does not belong to service, and PID file is not owned by root. Refusing.
Feb 10 17:22:05 bigtop1.vagrant systemd[1]: New main PID 14387 does not belong to service, and PID file is not owned by root. Refusing.
{noformat}
The following systemd commit is related:
[https://github.com/systemd/systemd/commit/db256aab13d8a89d583ecd2bacf0aca87c66effc]
Description of the new behavior:
{panel}The PID file does not need to be owned by a privileged user, but if it is owned by an unprivileged user additional safety restrictions are enforced: the file may not be a symlink to a file owned by a different user (neither directly nor indirectly), and the PID file must refer to a process already belonging to the service.{panel}
was (Author: vvybornov):
The following lines in systemd log indicate that the issue is likely caused by recent changes in systemd called 'stricter PIDfile handling`.
{noformat}
Feb 10 17:22:05 bigtop1.vagrant systemd[1]: New main PID 14387 does not belong to service, and PID file is not owned by root. Refusing.
Feb 10 17:22:05 bigtop1.vagrant systemd[1]: New main PID 14387 does not belong to service, and PID file is not owned by root. Refusing.
{noformat}
The following systemd commit is related:
[https://github.com/systemd/systemd/commit/db256aab13d8a89d583ecd2bacf0aca87c66effc]
Description of the new behavior:
{noformat}
The PID file does not need to be owned by a privileged user, but if it is owned by an unprivileged user additional safety restrictions are enforced: the file may not be a symlink to a file owned by a different user (neither directly nor indirectly), and the PID file must refer to a process already belonging to the service.{noformat}
> systemd fails to properly start Hadoop services
> -----------------------------------------------
>
> Key: BIGTOP-3307
> URL: https://issues.apache.org/jira/browse/BIGTOP-3307
> Project: Bigtop
> Issue Type: Bug
> Components: Init scripts, provisioner
> Affects Versions: 1.3.0, 1.4.0
> Environment: Windows 10
> Vagrant 2.2.7
> Reporter: Valery Vybornov
> Priority: Major
> Attachments: vagrant-log.txt, vm-log.txt
>
>
> Steps to reproduce:
> # Install Vagrant
> # Download and untar 1.4.0 tarball from the site
> # cd bigtop/provisioner/vargant
> # Follow the steps in README until first vagrant up (no changes to config files)
> Expected results:
> At least four services (namenode, resourcemanager, proxyserver, historyserver) in running state (according to systemd)
> Actual results:
> The four above mentioned services in failed state (according to systemd), and installation script failed.
> Yet OS processes up and running for all four services, according to ps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)