You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2020/02/21 08:06:00 UTC
[jira] [Resolved] (BIGTOP-3307) systemd fails to properly start
Hadoop services
[ https://issues.apache.org/jira/browse/BIGTOP-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Masatake Iwasaki resolved BIGTOP-3307.
--------------------------------------
Resolution: Duplicate
I'm closing this as duplicate since BIGTOP-3302 was merged. Please reopen if we need additional fix.
> 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 up to and including 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)