From: dhinakar k <dhinakar.k@gmail.com>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] Fuego 1.1 version error during install
Date: Mon, 10 Apr 2017 17:31:27 +0530 [thread overview]
Message-ID: <CABehs3O_BKM7vYFAA1mZWZ1Q=qGHnmcC87Fnt4LnsuOhF50NDQ@mail.gmail.com> (raw)
In-Reply-To: <000401d2b19d$2e3b0f50$8ab12df0$@toshiba.co.jp>
[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]
Hi,
Thanks for your response.
It seems the problem is due to the Jenkins port & service issue. I was have
plain vanilla Jenkins running at 8080 port and wanted to setup Fuego at
8081. So temporarily stopped Jenkins service @8080. This caused the issue.
Now I have swapped the ports so that I can go with defaults to make things
easy for Fuego. So that issue is solved now.
Regards,
Dhinakar
On Apr 10, 2017 7:23 AM, "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
wrote:
> > -----Original Message-----
> > From: fuego-bounces@lists.linuxfoundation.org [mailto:
> fuego-bounces@lists.linuxfoundation.org] On Behalf Of dhinakar k
> > ---> Running in 9cc9272ed6a4
> > ---> 85db72cbfc81
> > Removing intermediate container 9cc9272ed6a4
> > Step 32 : RUN source /etc/default/jenkins && JAVA_ARGS="$JAVA_ARGS
> -Djenkins.install.runSetupWizard=false" && if [ -n
> > "$HTTP_PROXY" ]; then PROXYSERVER=$(echo $http_proxy | sed -E
> 's/^http://' | sed -E 's/\///g' | sed -E 's/(.*):(.*)/\1/') &&
> > PROXYPORT=$(echo $http_proxy | sed -E 's/^http://' | sed -E 's/\///g' |
> sed -E 's/(.*):(.*)/\2/') && JAVA_ARGS="$JAVA_ARGS -
> > Dhttp.proxyHost="${PROXYSERVER}" -Dhttp.proxyPort="${PROXYPORT}"
> -Dhttps.proxyHost="${PROXYSERVER}" -
> > Dhttps.proxyPort="${PROXYPORT}; fi && sed -i -e
> "s#^JAVA_ARGS.*#JAVA_ARGS\=\"${JAVA_ARGS}\"#g" /etc/default/jenkins;
> > ---> Running in 6721c884cf16
> > ---> 027eb9ad54a5
> > Removing intermediate container 6721c884cf16
> > Step 33 : RUN service jenkins start && sleep 30 && sudo -u
> jenkins java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s
> > http://localhost:8080/fuego install-plugin description-setter &&
> sudo -u jenkins java -jar /var/cache/jenkins/war/WEB-INF/jenkins-
> > cli.jar -s http://localhost:8080/fuego install-plugin pegdown-formatter
> > ---> Running in bfbc88626a6f
> > Starting Jenkins Continuous Integration Server: jenkins.
> > description-setter is neither a valid file, URL, nor a plugin artifact
> name in the update center
> > No update center data is retrieved yet from:
> http://updates.jenkins-ci.org/update-center.json
> > description-setter looks like a short plugin name. Did you mean ?null??
> >
> > ERROR: Error occurred, see previous output.
> > The command '/bin/sh -c service jenkins start && sleep 30 &&
> sudo -u jenkins java -jar /var/cache/jenkins/war/WEB-INF/jenkins-
> > cli.jar -s http://localhost:8080/fuego install-plugin
> description-setter && sudo -u jenkins java -jar
> /var/cache/jenkins/war/WEB-
> > INF/jenkins-cli.jar -s http://localhost:8080/fuego install-plugin
> pegdown-formatter' returned a non-zero code: 5
> > [sudo] password for dhinakar:
> >
> >
> >
> > Any clue what is the issue?
>
> It may be a problem with your environment/company network(?).
> You could install it without plugins first, and then install the plugins
> by hand from the Jenkins interface.
>
> Thanks,
> Daniel
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4452 bytes --]
next prev parent reply other threads:[~2017-04-10 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 5:08 [Fuego] Fuego 1.1 version error during install dhinakar k
2017-04-10 1:52 ` Daniel Sangorrin
2017-04-10 12:01 ` dhinakar k [this message]
2017-04-11 23:32 ` Daniel Sangorrin
2017-04-12 2:07 ` dhinakar k
2017-04-12 2:50 ` Bird, Timothy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABehs3O_BKM7vYFAA1mZWZ1Q=qGHnmcC87Fnt4LnsuOhF50NDQ@mail.gmail.com' \
--to=dhinakar.k@gmail.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=fuego@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.