You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Leona Yoda (Jira)" <ji...@apache.org> on 2022/05/10 01:11:00 UTC

[jira] [Assigned] (BIGTOP-3681) Deploying Flink fails on aarch64

     [ https://issues.apache.org/jira/browse/BIGTOP-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leona Yoda reassigned BIGTOP-3681:
----------------------------------

    Assignee: Leona Yoda

> Deploying Flink fails on aarch64
> --------------------------------
>
>                 Key: BIGTOP-3681
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3681
>             Project: Bigtop
>          Issue Type: Bug
>          Components: deployment, flink
>            Reporter: Kengo Seki
>            Assignee: Leona Yoda
>            Priority: Major
>
> https://ci.bigtop.apache.org/view/Test/job/Bigtop-3.1.0-smoke-tests/COMPONENTS=hdfs.flink@flink,OS=centos-7-aarch64-deploy/26/console
> https://ci.bigtop.apache.org/view/Test/job/Bigtop-3.1.0-smoke-tests/COMPONENTS=hdfs.flink@flink,OS=debian-10-arm64-deploy/26/console
> {code}
> Error: Could not start Service[flink-jobmanager]: Execution of '/usr/bin/systemctl start flink-jobmanager' returned 1: Job for flink-jobmanager.service failed because the control process exited with error code. See "systemctl status flink-jobmanager.service" and "journalctl -xe" for details.
> Wrapped exception:
> Execution of '/usr/bin/systemctl start flink-jobmanager' returned 1: Job for flink-jobmanager.service failed because the control process exited with error code. See "systemctl status flink-jobmanager.service" and "journalctl -xe" for details.
> Error: /Stage[main]/Flink::Jobmanager/Service[flink-jobmanager]/ensure: change from stopped to running failed: Could not start Service[flink-jobmanager]: Execution of '/usr/bin/systemctl start flink-jobmanager' returned 1: Job for flink-jobmanager.service failed because the control process exited with error code. See "systemctl status flink-jobmanager.service" and "journalctl -xe" for details.
> {code}
> Probably BIGTOP-3571 was an incomplete solution.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)