[jira] [Commented] (BIGTOP-2742) broken zeppelin init script

["Evans Ye (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795142#comment-16795142 ] 

Evans Ye commented on BIGTOP-2742:
----------------------------------

Looks like no much progress reached. Push back to 1.5.0.

> broken zeppelin init script
> ---------------------------
>
>                 Key: BIGTOP-2742
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2742
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Init scripts
>    Affects Versions: 1.2.0
>            Reporter: Kevin W Monroe
>            Assignee: Roman Shaposhnik
>            Priority: Major
>             Fix For: 1.4.0
>
>
> Trying to apt install zeppelin on a machine with the bigtop-1.2 repo fails:
> {quote}
> $ sudo apt-get install zeppelin
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following additional packages will be installed:
>   spark-core spark-python
> The following NEW packages will be installed:
>   spark-core spark-python zeppelin
> 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> Need to get 886 MB of archives.
> After this operation, 1,030 MB of additional disk space will be used.
> Do you want to continue? [Y/n]
> WARNING: The following packages cannot be authenticated!
>   spark-core spark-python zeppelin
> Authentication warning overridden.
> Get:1 http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/ubuntu/16.04/x86_64 bigtop/contrib amd64 spark-core all 2.1.0-1 [169 MB]
> Get:2 http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/ubuntu/16.04/x86_64 bigtop/contrib amd64 spark-python all 2.1.0-1 [819 kB]
> Get:3 http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/ubuntu/16.04/x86_64 bigtop/contrib amd64 zeppelin all 0.7.0-1 [716 MB]
> Fetched 886 MB in 30s (28.7 MB/s)
> Selecting previously unselected package spark-core.
> (Reading database ... 96072 files and directories currently installed.)
> Preparing to unpack .../spark-core_2.1.0-1_all.deb ...
> Unpacking spark-core (2.1.0-1) ...
> Selecting previously unselected package spark-python.
> Preparing to unpack .../spark-python_2.1.0-1_all.deb ...
> Unpacking spark-python (2.1.0-1) ...
> Selecting previously unselected package zeppelin.
> Preparing to unpack .../zeppelin_0.7.0-1_all.deb ...
> Unpacking zeppelin (0.7.0-1) ...
> Processing triggers for systemd (229-4ubuntu16) ...
> Processing triggers for ureadahead (0.100.0-19) ...
> Setting up spark-core (2.1.0-1) ...
> update-alternatives: using /etc/spark/conf.dist to provide /etc/spark/conf (spark-conf) in auto mode
> Setting up spark-python (2.1.0-1) ...
> Setting up zeppelin (0.7.0-1) ...
> update-alternatives: using /etc/zeppelin/conf.dist to provide /etc/zeppelin/conf (zeppelin-conf) in auto mode
> Job for zeppelin.service failed because a configured resource limit was exceeded. See "systemctl status zeppelin.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript zeppelin, action "start" failed.
> ● zeppelin.service - LSB: Zeppelin
>    Loaded: loaded (/etc/init.d/zeppelin; bad; vendor preset: enabled)
>    Active: failed (Result: resources) since Fri 2017-04-14 16:25:18 UTC; 10ms ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 30639 ExecStart=/etc/init.d/zeppelin start (code=exited, status=0/SUCCESS)
> Apr 14 16:25:16 ip-172-31-30-107 systemd[1]: Starting LSB: Zeppelin...
> Apr 14 16:25:16 ip-172-31-30-107 su[30651]: Successful su for zeppelin by root
> Apr 14 16:25:16 ip-172-31-30-107 su[30651]: + ??? root:zeppelin
> Apr 14 16:25:16 ip-172-31-30-107 su[30651]: pam_unix(su:session): session opened for user zeppelin by (uid=0)
> Apr 14 16:25:18 ip-172-31-30-107 zeppelin[30639]:  * Started Zeppelin:
> Apr 14 16:25:18 ip-172-31-30-107 systemd[1]: zeppelin.service: PID file /var/run/zeppelin/zeppelin-zeppelin-$(hostname).pid not readable (yet?) after start: No su...r directory
> Apr 14 16:25:18 ip-172-31-30-107 systemd[1]: Failed to start LSB: Zeppelin.
> Apr 14 16:25:18 ip-172-31-30-107 systemd[1]: zeppelin.service: Unit entered failed state.
> Apr 14 16:25:18 ip-172-31-30-107 systemd[1]: zeppelin.service: Failed with result 'resources'.
> Hint: Some lines were ellipsized, use -l to show in full.
> dpkg: error processing package zeppelin (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (229-4ubuntu16) ...
> Processing triggers for ureadahead (0.100.0-19) ...
> Errors were encountered while processing:
>  zeppelin
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> {quote}
> Digging into the error reveals a problem with the init script's {{pidfile}}:
> {quote}
> $ journalctl -xe
> ...
> -- The start-up result is done.
> Apr 14 16:59:28 ip-172-31-30-107 su[31453]: pam_unix(su:session): session closed for user zeppelin
> Apr 14 16:59:28 ip-172-31-30-107 zeppelin[31443]:  * Started Zeppelin:
> Apr 14 16:59:28 ip-172-31-30-107 systemd[1]: zeppelin.service: PID file /var/run/zeppelin/zeppelin-zeppelin-$(hostname).pid not readable (yet?) after start: No such file or dir
> Apr 14 16:59:28 ip-172-31-30-107 systemd[1]: Failed to start LSB: Zeppelin.
> -- Subject: Unit zeppelin.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit zeppelin.service has failed.
> --
> -- The result is failed.
> {quote}
> The init script is looking for the literal string _$(hostname)_ in the pid filename.  This is annoying, but not a show-stopper.  The zeppelin process does indeed start up -- it's just that systemctl reports a failure because it's looking for a non-existent pidfile.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)