It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,786
×562
×101
×9

question asked: Jul 13 '16, 9:03 a.m.
question was seen: 2,178 times
last updated: Jul 14 '16, 11:49 a.m.

Related questions

FAQ - How this Forum works

Jazz Build Engine 6.0.2 not running on Ubuntu

0
Liora Milbaum (513●2●82●117) | asked Jul 13 '16, 9:03 a.m.
edited Jul 13 '16, 1:22 p.m. by David Lafreniere (4.8k●7)
I have installed the Jazz Build Toolkit ubuntu package on Ubuntu 12.04.

The jbe service doesn't run. 

Any ideas why?

Liora
Comments
David Lafreniere commented Jul 13 '16, 1:21 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

You need to provide a little more detail with this question.


-How are you running the JBE service?
-What happens?
   -Is there any output or logs anywhere?
etc.

Liora Milbaum commented Jul 13 '16, 1:51 p.m.

The package is installed according to the manual

dpkg -i jbe_6.0.2-1_i386.deb

The service is created by the package installation.
Tried to run the file '/etc/init.d/jbe start' manually. Same result. jbe not running.

Ralph Schoon commented Jul 14 '16, 2:54 a.m. | edited Jul 14 '16, 2:55 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

There must be log files or errors or something. If you can't provide anything like this, there is no way to  help you. Run the JBE manually (not the service) and try to find some information that way.

Liora Milbaum commented Jul 14 '16, 4:28 a.m.

I do not know where this packages logs the errors. 

Can you point out the file name?

Ralph Schoon commented Jul 14 '16, 4:39 a.m. | edited Jul 14 '16, 4:42 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I don't have Ubuntu. Find the JBE executable file or the jbe.sh (from the service) and run the JBE from that folder. JBE shows execution, actions and likely fatal errors in the shell.

I would also assume that in the service like if starting it as executable, you will have to provide the repository URI, the username, the password and the engine ID otherwise JBE will exit.

Liora Milbaum commented Jul 14 '16, 11:26 a.m.

I have followed your suggestion.

List bellow my tries and outcomes:

First run:
ubuntu@ip-10-0-1-70:~$ /usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh
/usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh: 16: exec: /bin/java: not found
ubuntu@ip-10-0-1-70:~$ sudo ./jbe.sh

Liora Milbaum commented Jul 14 '16, 11:27 a.m.

 


Second run:

+ JAVA_HOME=/usr/lib/jbe/jdk

+ export JAVA_HOME

+ /usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh

/usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh: 16: exec: /usr/lib/jbe/jdk/bin/java: not found

+ exit 0

ubuntu@ip-10-0-1-70:~$ ls /usr/lib/jbe/jdk/bin/java

/usr/lib/jbe/jdk/bin/java

ubuntu@ip-10-0-1-70:~$ file !$

file /usr/lib/jbe/jdk/bin/java

/usr/lib/jbe/jdk/bin/java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped

Liora Milbaum commented Jul 14 '16, 11:27 a.m.

Third run:

ubuntu@ip-10-0-1-70:~$ sudo ./jbe.sh

+ JAVA_HOME=/opt/IBM/InstallationManager/eclipse/jre_7.0.9040.20160504_1613/jre

+ export JAVA_HOME

+ /usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh -repository https://ec2-52-31-121-246.eu-west-1.compute.amazonaws.com:9443/ccm -userId build -pass build -engineId jke.dev.engine

2016-07-14 15:25:48 [Jazz build engine] Running build loop...

2016-07-14 15:25:48 [Jazz build engine] Waiting for request...

Jul 14, 2016 3:25:50 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies

WARNING: Invalid cookie header: "Set-Cookie: WASReqURL=""; Expires=Thu, 01 Dec 1994 16:00:00 GMT; Path=/; Secure; HttpOnly". Invalid 'expires' attribute: Thu, 01 Dec 1994 16:00:0

Liora Milbaum commented Jul 14 '16, 11:38 a.m.

 Forth run (switching the -pass argument with -passwordFile)


ubuntu@ip-10-0-1-70:~$ sudo ./jbe.sh 

+ JAVA_HOME=/opt/IBM/InstallationManager/eclipse/jre_7.0.9040.20160504_1613/jre

+ export JAVA_HOME

+ /usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh -repository https://ec2-52-31-121-246.eu-west-1.compute.amazonaws.com:9443/ccm -engineId jke.dev.engine -userId build -passwordFile /home/jbe/passwordFile

Invalid or corrupt password file at "/home/jbe/passwordFile".

CRRTC3529W: The execution of Jazz Build Engine completed with a non-zero return code (RC=1).

+ exit 0

showing 5 of 9 show 4 more comments

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Liora Milbaum (513●2●82●117) | answered Jul 14 '16, 11:35 a.m.
  starting the jbe service in verbose mode

ubuntu@ip-10-0-1-70:~$ sudo sh -x /etc/init.d/jbe start

+ PATH=/sbin:/bin:/usr/sbin:/usr/bin

+ . /lib/lsb/init-functions

+ FANCYTTY=

+ [ -e /etc/lsb-base-logging.sh ]

+ . /etc/lsb-base-logging.sh

+ LOG_DAEMON_MSG=

+ DAEMON=/home/jbe/jbe-daemon.sh

+ PIDFILE=/var/run/jbe.pid

+ test -x /home/jbe/jbe-daemon.sh

+ test -e /home/jbe/jbe.config

+ cat /home/jbe/jbe.config

+ JBE_OPTS=-configuration /home/jbe/internalConfiguration -clean -consoleLog -repository https://ec2-52-31-121-246.eu-west-1.compute.amazonaws.com:9443/ccm -engineId jke.dev.engine -userId build -passwordFile /home/jbe/passwordFile

+ LOCKFILE=/var/lock/jbe

+ PIDFILE=/var/run/jbe.pid

+ log_daemon_msg Starting Jazz Build Engine jbe

+ [ -z Starting Jazz Build Engine ]

+ log_use_fancy_output

+ TPUT=/usr/bin/tput

+ EXPR=/usr/bin/expr

+ [ -t 1 ]

+ [ xxterm-256color != x ]

+ [ xxterm-256color != xdumb ]

+ [ -x /usr/bin/tput ]

+ [ -x /usr/bin/expr ]

+ /usr/bin/tput hpa 60

+ /usr/bin/tput setaf 1

+ [ -z ]

+ FANCYTTY=1

+ true

+ /usr/bin/tput xenl

+ /usr/bin/tput cols

+ COLS=80

+ [ 80 ]

+ [ 80 -gt 6 ]

+ /usr/bin/expr 80 - 7

+ COL=73

+ log_use_plymouth

+ [ n = y ]

+ plymouth --ping

+ printf  * Starting Jazz Build Engine jbe       

 * Starting Jazz Build Engine jbe       + /usr/bin/expr 80 - 1

+ /usr/bin/tput hpa 79

                                                                               + printf  

 + lock_jbe

+ [ -x /usr/bin/lockfile-create ]

+ lockfile-create /var/lock/jbe

+ LOCKTOUCHPID=5890

+ start-stop-daemon --start -d /home/jbe -c jbe -u jbe --quiet -b --startas /home/jbe/jbe-daemon.sh -- -configuration /home/jbe/internalConfiguration -clean -consoleLog -repository https://ec2-52-31-121-246.eu-west-1.compute.amazonaws.com:9443/ccm -engineId jke.dev.engine -userId build -passwordFile /home/jbe/passwordFile

+ status=0

+ unlock_jbe

+ [ -x /usr/bin/lockfile-create ]

+ kill 5890

+ lockfile-remove /var/lock/jbe

+ log_end_msg 0

+ [ -z 0 ]

+ [ 73 ]

+ [ -x /usr/bin/tput ]

+ log_use_plymouth

+ [ n = y ]

+ plymouth --ping

+ printf \r

+ /usr/bin/tput hpa 73

                                                                         + [ 0 -eq 0 ]

+ echo [ OK ]

[ OK ]

+ return 0

ubuntu@ip-10-0-1-70:~$ 

Comments
Liora Milbaum commented Jul 14 '16, 11:44 a.m.

 Switching the -passwordFile argument with -pass for the service resulted the same failure.

Liora Milbaum commented Jul 14 '16, 11:49 a.m.

 Replacing the content of /home/jbe/jbe-deamon.sh did the trick:


#!/bin/sh

JAVA_HOME=/opt/IBM/InstallationManager/eclipse/jre_7.0.9040.20160504_1613/jre

export JAVA_HOME

/usr/lib/jbe/buildsystem/buildengine/eclipse/jbe.sh "$@" >> /var/log/jbe.log &

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.