Fuego wiki

Login or create account

Troubleshooting Guide in 'raw' format

This page describes problems encountered using Fuego, and their solutions.

''Note for Editors: please put each issue in it's own page section''

= Installation =
== Problem with default Jenkins port ==
Fuego has Jenkins default to using port 8090 on the host system.  However,
if you have something else already running on port 8090, you may wish to
change this.

You can change the Jenkins port during installation of Fuego,
using an argument to the script.  For example,
to install Fuego with Jenkins configured to use port 9999, use
the following command during installation:
  $ ./ fuego 9999

To change the Jenkins port for an already-built Fuego container,
start the container, and inside the container edit the file:
 * /etc/default/jenkins

Change the line that says: HTTP_PORT=8090

Change to port to whatever your like.

Also, check the line that defines JENKINS_ARGS.  Mine looked like this:
JENKINS_ARGS="--webroot=/var/cache/jenkins/war --httpPort=8090 --prefix=/fuego"

Change this line to read as follows:
JENKINS_ARGS="--webroot=/var/cache/jenkins/war --httpPort=$HTTP_PORT --prefix=/fuego"

Then restart Jenkins:
 * $ service jenkins restart

== Problem creating docker file ==
Make sure you are running on a 64-bit version of the Linux kernel on
your host machine.

== Problem starting Jenkins after initial container creation ==
Doug Crawford reported a problem starting Jenkins in the container
after his initial build.

$ sudo ./
Created JTA container 6a420f901af7847f2afa3100d3fb3852b71bc65f92aecd13a9aefe0823d42b77
$ sudo ./ Starting JTA container
[....] Starting Jenkins Continuous Integration Server: jenkinssu: System error  failed!
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[ ok ] Starting network benchmark server.

The error string is jenkinssu: System error

Takuo Kogushi provides the following response:

I had the same issue. I did some search in the net and found it is not a problem of fuego itself.
As far as I know there are two workarounds;
 * 1) Rebuild and install libpam with --disable-audit option (in the container) or
 * 2) Modify to add --pid="host" option to docker create command

Here is a patch provided by Koguchi-san:
diff --git a/fuego-host-scripts/ b/fuego-host-scripts/
index 2ea7961..24663d6 100755
--- a/fuego-host-scripts/
+++ b/fuego-host-scripts/
@@ -7,7 +7,7 @@ while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symli  done  DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )"

-CONTAINER_ID=`sudo docker create -it -v $DIR/../userdata:/userdata --net="host" fuego`
+CONTAINER_ID=`sudo docker create -it -v $DIR/../userdata:/userdata --pid="host" --net="host" fuego`
 echo "Created Fuego container $CONTAINER_ID"
 echo $CONTAINER_ID > $DIR/../

Actually I have not tried the first one and do not know if there is any side effects for the second.

This may be related to this docker bug:

== Problem with bad port on ssh connection == doesn't parse SSH_PORT from:
 * /home/jenkins/fuego/engine/scripts/overlays/base/base-board.fuegoclass
because it is missing double quotes.

The symptom is the following:
You see the following in the test log for some test you tried to run:
+++ sshpass -e ssh -o ServerAliveInterval=30 -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
ConnectTimeout=15 -p root@ true
Bad port 'root@'
+++ abort_job 'Cannot connect to via ssh'
+++ set +

The error string here is "Bad port 'root@'"

This occurs because the port is empty.  It should have been passed
to the ssh command after the '-p' command line option, but since it
is empty, it uses the account-name@address combination as the argument.

The reason it is empty is that a bug in the base-board.fuegoclass is
missing the double-quotes.

This is fixed in the fuegotest repository with the following commit:

= General =
== Timeout executing ssh commands ==
In some cases, the ssh command used by Fuego takes a very long
time to connect.  There is a timeout for the ssh commands,
specified as 15 seconds in the cogent repository and 30 seconds
in the fuegotest repository.

The timeout for ssh commands is specified in the file
 * /home/jenkins/fuego/engine/scripts/overlays/base/base-params.fuegoclass

You can change ConnectTimeout to something longer by editing the file.

FIXTHIS - make ConnectTimeout for ssh connections a board-level test variable

== ssh commands taking a long time ==
Sometimes, even if the command does not time, the SSH operations
on the target take a very long time for each operation.

The symptom is that when you are watching the console output for
a test, the test stops at the point of each SSH connection to the

One cause of long ssh connection times can be that the target
ssh server (sshd) is configured to do DNS lookups on each inbound

To turn this off, on the target, edit the file:
 * /etc/ssh/sshd_config
and add the line:

UseDNS no

This line can be added anywhere in the file, but I recommend adding
it right after the UsePrivilegeSeparation line (if that's there).

TBWiki engine 1.8.3 by Tim Bird