[Fuego] Regarding changing jenkins service port change (from 8080 -> 8082)
daniel.sangorrin at toshiba.co.jp
daniel.sangorrin at toshiba.co.jp
Thu Feb 21 00:31:11 UTC 2019
Hello Dhinakar,
Maybe your docker is using previous cached steps.
Could you comment out NO_CACHE from docker-build-image.sh and try again?
Thanks,
Daniel
> -----Original Message-----
> From: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>
> Sent: Wednesday, February 20, 2019 11:23 PM
> To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) <daniel.sangorrin at toshiba.co.jp>
> Cc: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>; fuego at lists.linuxfoundation.org;
> dhinakar.k at gmail.com
> Subject: RE: RE: RE: [Fuego] Regarding changing jenkins service port change (from 8080 -> 8082)
>
> Hi Daniel,
>
>
>
> Any idea why the below error is throw, I was trying to use port 8082 for fuego in another server. Just did the port
> changes manually (updated ftc, common.sh etc.) and executed install.sh.
>
> Not sure why it is getting refused.
>
>
>
> Step 46/57 : RUN service jenkins start && sleep 30 && sudo -u jenkins java -jar
> /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s http://localhost:8082/fuego install-plugin /tmp/flot.hpi &&
> sleep 10 && service jenkins stop
> ---> Running in 34f879a820f8
> Starting Jenkins Continuous Integration Server: jenkins.
> java.io.IOException: Failed to connect to http://localhost:8082/fuego/
> at hudson.cli.CLI.getCliTcpPort(CLI.java:267)
> at hudson.cli.CLI.<init>(CLI.java:128)
> at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72)
> at hudson.cli.CLI._main(CLI.java:473)
> at hudson.cli.CLI.main(CLI.java:384)
> Suppressed: java.net.ConnectException: Connection refused (Connection refused)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:580)
> at java.net.Socket.connect(Socket.java:529)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
> at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
> at sun.net.www.http.HttpClient.New(HttpClient.java:357)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1062)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:916)
> at
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1157)
> at hudson.cli.FullDuplexHttpStream.<init>(FullDuplexHttpStream.java:77)
> at hudson.cli.CLI.connectViaHttp(CLI.java:152)
> at hudson.cli.CLI.<init>(CLI.java:132)
> ... 3 more
> Caused by: java.net.ConnectException: Connection refused (Connection refused)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:580)
> at java.net.Socket.connect(Socket.java:529)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
> at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
> at sun.net.www.http.HttpClient.New(HttpClient.java:357)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1062)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:916)
> at hudson.cli.CLI.getCliTcpPort(CLI.java:265)
> ... 4 more
> 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:8082/fuego install-plugin /tmp/flot.hpi &&
> sleep 10 && service jenkins stop' returned a non-zero code: 255
>
>
>
>
> Regards,
>
> Dhinakar
>
>
>
>
>
> --------- Original Message ---------
>
> Sender : Dhinakar Kalyanasundaram <dhinakar.k at samsung.com> Staff Engineer/FDS SW /SSIR/Samsung
> Electronics
>
> Date : 2019-02-20 19:11 (GMT+5:30)
>
> Title : RE: RE: [Fuego] Regarding changing jenkins service port change (from 8080 -> 8082)
>
>
>
> Hi Daniel,
>
>
>
> Thanks for the response and the patch 'port: allow users to choose a different port for jenkins'.
>
> The usage is I need to clone fuego, and while executing ./install.sh I need to provide 'port' number (as shown
> below)
>
> # install.sh [--help] [--priv] [<image_name>] [<port>]
>
> This will remove the hard-coded port number (default: 8080) in files such as ftc, common.sh etc.
>
> So port needs to be fixed while creating the image (via install.sh), once the image is created port cannot be
> changed?
>
> Is it possible to use an image and create containers each with different port number?
>
> It will help me avoid the install step and create identical copies of container with only port number differing.
>
>
>
> Note: I will let you know about your patch in my next email, I am cloning and installing in another instance
>
>
>
> Regards,
>
> Dhinakar
>
>
>
>
>
> --------- Original Message ---------
>
> Sender : daniel.sangorrin at toshiba.co.jp <daniel.sangorrin at toshiba.co.jp>
>
> Date : 2019-02-20 12:33 (GMT+5:30)
>
> Title : RE: [Fuego] Regarding changing jenkins service port change (from 8080 -> 8082)
>
>
>
> Hello Dhinakar,
>
> > From: fuego-bounces at lists.linuxfoundation.org <fuego-bounces at lists.linuxfoundation.org> On Behalf Of
> > Dhinakar Kalyanasundaram
> > Sent: Tuesday, February 19, 2019 10:59 PM
> > Dear Fuego Users,
> >
> >
> >
> > I want to run multiple instances of fuego (in one powerful server) to cater to different projects (which need to
> be kept
> > separate for security).
> >
> > In this regard I thought I can assign a unique port for each instance, for e.g. 8080 -> Project1, 8081 ->
> Project2 etc.
> >
> > If there is any other better way to achieve the objective please let me know.
> >
> > I modified all occurrences of port 8080 to 8082 under fuego (Dockerfile, ftc, common.sh etc.) & fuego-core
> > directories in my existing installation.
> >
> > Recreated the container -> ./fuego-host-scripts/docker-create-usb-privileged-container.sh
> > containerbackup-15thfeb2019 container-19thfeb2019
> >
> > And Started it -> ./fuego-host-scripts/docker-start-container.sh container-19thfeb2019
> >
> > But it is still running on port 8080 only.
> >
> > The 'containerbackup-15thfeb2019' image that I used to create the new container was running on port 8080,
> could
> > it be because of it?
> >
> > I thought if I make changes in 'fuego', 'fuego-core' directories and recreate the container & start, it should
> listen on
> > port 8082.
> >
> > Should I create a new image after the modification and then create a container and start?
> >
> > Can someone help in this regard?
>
> I just sent a few patches to support the creation of Fuego images using separate TCP ports.
> They are on the "next" branch of my repository (https://bitbucket.org/nirrognas/) for now.
> Could you give them a try?
>
> Thanks,
> Daniel
>
>
> >
> > Thanks.
> >
> >
> >
> > Regards,
> >
> > Dhinakar
> >
> >
> >
> >
> >
> >
> >
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinakar.k&do=bWFpbElEPTIwMTkwMj
> E5
> >
> MTM1OTE1ZXBjbXM1cDg4N2Y5ZDQxNjA5N2U2NzIxODNkYWYwN2E5OGU3MzQ4NyZyZWNpcGllbnRBZGRyZ
> XNzP
> > WZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_>
>
>
>
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinakar.k&do=bWFpbElEPTIwMTkwMj
> IwMTQyMjUyZXBjbXM1cDg4OGQ2YmJhOWI0ZjZjODg2OWE1ZGNmMjdmNDY2MzdiNiZyZWNpcGllbnRBZGRyZ
> XNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5jby5qcA__>
More information about the Fuego
mailing list