Top of my head...... Looks like your unit file isn't telling us why , can you add more debug to it? Maybe use "set -x" or something into the unit file to see how far it's getting ....
Sent from my iPhone > On Apr 11, 2016, at 9:45 PM, Harshita Agrawal <[email protected]> wrote: > > Hi Jay, > > This is the output for journalctl -xe for flink services: > > > > [vagrant@bigtop1 ~]$ sudo journalctl -xe | grep flink > > Apr 12 01:20:31 bigtop1.vagrant yum[5384]: Installed: flink-1.0.0-1.noarch > -- Subject: Unit flink-master.service has begun start-up > -- Unit flink-master.service has begun starting up. > Apr 12 01:21:24 bigtop1.vagrant flink-master[5549]: Starting Flink master > (flink-master):[ OK ] > Apr 12 01:21:27 bigtop1.vagrant systemd[1]: flink-master.service: control > process exited, code=exited status=3 > -- Subject: Unit flink-master.service has failed > -- Unit flink-master.service has failed. > Apr 12 01:21:27 bigtop1.vagrant systemd[1]: Unit flink-master.service > entered failed state. > Apr 12 01:21:27 bigtop1.vagrant systemd[1]: flink-master.service failed. > -- Subject: Unit flink-worker.service has begun start-up > -- Unit flink-worker.service has begun starting up. > Apr 12 01:21:27 bigtop1.vagrant flink-worker[5722]: Starting Flink worker > (flink-worker):[ OK ] > Apr 12 01:21:30 bigtop1.vagrant systemd[1]: flink-worker.service: control > process exited, code=exited status=3 > -- Subject: Unit flink-worker.service has failed > -- Unit flink-worker.service has failed. > Apr 12 01:21:30 bigtop1.vagrant systemd[1]: Unit flink-worker.service > entered failed state. > Apr 12 01:21:30 bigtop1.vagrant systemd[1]: flink-worker.service failed. > > > On Mon, Apr 11, 2016 at 9:27 PM, Jay Vyas <[email protected]> > wrote: > >> What's the journalctl -xe output? >> >>>> On Apr 11, 2016, at 7:17 PM, Harshita Agrawal <[email protected]> >>> wrote: >>> >>> Hi, >>> >>> We are trying to deploy Flink in master worker configuration through >>> puppet. Running into the following error during the startup of the >>> master/worker services during deployment. >>> >>> >>> Error: Could not start Service[flink-master]: Execution of >> '/bin/systemctl >>> start flink-master' returned 1: Job for flink-master.service failed >> because >>> the control process exited with error code. See "systemctl status >>> flink-master.service" and "journalctl -xe" for details. >>> ==> bigtop1: Error: >>> /Stage[main]/Flink::Master/Service[flink-master]/ensure: change from >>> stopped to running failed: Could not start Service[flink-master]: >> Execution >>> of '/bin/systemctl start flink-master' returned 1: Job for >>> flink-master.service failed because the control process exited with error >>> code. See "systemctl status flink-master.service" and "journalctl -xe" >> for >>> details. >>> ==> bigtop1: Debug: Executing '/bin/systemctl start flink-worker' >>> ==> bigtop1: Debug: Executing '/bin/rpm -q hadoop --nosignature >> --nodigest >>> --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' >>> ==> bigtop1: Error: Could not start Service[flink-worker]: Execution of >>> '/bin/systemctl start flink-worker' returned 1: Job for >>> flink-worker.service failed because the control process exited with error >>> code. See "systemctl status flink-worker.service" and "journalctl -xe" >> for >>> details. >>> ==> bigtop1: Error: >>> /Stage[main]/Flink::Worker/Service[flink-worker]/ensure: change from >>> stopped to running failed: Could not start Service[flink-worker]: >> Execution >>> of '/bin/systemctl start flink-worker' returned 1: Job for >>> flink-worker.service failed because the control process exited with error >>> code. See "systemctl status flink-worker.service" and "journalctl -xe" >> for >>> details. >>> >>> >>> Any inputs on how to resolve this? >>> >>> Regards >>> Harshita > > > > -- > Regards, > Harshita Agrawal
