Hi Chris, I have tested the scenario according to your information and still couldn't reproduce the issue. I could run wso2server as a background process over ssh with command;
vagrant ssh -c './wso2carbon-4.2.0/bin/wso2server.sh start' I can access management console if I ssh vagrant guest session save response with wget. (eg: wget --no-check-certificate https://10.0.2.15:9443/carbon/) It only terminate the server if I call vagrant reload command which reboot the VM. I have updated the jira ticket with the steps I have followed. Thanks, Nipuni On Sat, Jul 19, 2014 at 4:16 PM, chris snow <[email protected]> wrote: > Hi Nipuni, I've updated the JIRA ticket with some more information... > > On Sat, Jul 19, 2014 at 10:28 AM, Nipuni Perera <[email protected]> wrote: > > Hi, > > > > I have tried -c option and followed the jira first and got following > > results. According to[1] -c option defines the cipher type. > > > > When running wso2server without -E option I got the following error, > > > > Error: JAVA_HOME is not defined correctly. > > CARBON cannot execute java > > > > When executing the ssh -c "./wso2server.sh start" command, I got the > > following error. > > > > Unknown cipher type './wso2server.sh start' > > > > @shameera > > I have updated the jira. > > > > @Isuru, > > According to my understanding, the jira is about executing wso2server > over > > ssh as a background process. I am not sure about the commands in the > jira. I > > tried to reproduce the issue and I have updated the jira with my > findings. > > Following the steps I have mentioned in the first email I could execute > > wso2server.sh over ssh as a nohup process. > > [1] http://unixhelp.ed.ac.uk/CGI/man-cgi?ssh+1 > > > > Thanks, > > Nipuni > > > > > > On Sat, Jul 19, 2014 at 2:32 PM, Isuru Perera <[email protected]> wrote: > >> > >> stratos.sh is just a renamed version of wso2server.sh and it is used in > >> Apache Stratos. > >> > >> Nipuni, it seems you have not followed what is mentioned in the JIRA. > >> Please double check. > >> > >> Thanks! > >> > >> > >> On Fri, Jul 18, 2014 at 11:28 PM, Shameera Rathnayaka < > [email protected]> > >> wrote: > >>> > >>> According to the JIRA, you should use -c not -E , did you test with > that > >>> option as well? , BTW wso2servers.sh is working fine with nohup not > sure > >>> about stratos.sh . you can update JIRA with your finding. > >>> > >>> @Isura , For that you need to start the server as background process , > if > >>> not server process terminate with user logging out. > >>> > >>> Thanks, > >>> Shameera. > >>> > >>> > >>> On Sat, Jul 19, 2014 at 11:33 AM, Isura Karunaratne <[email protected]> > >>> wrote: > >>>> > >>>> Hi Nipuni, > >>>> > >>>> AFAIK sever process will not terminate once you terminate the ssh > >>>> process . You have to kill the server process manually. User "ps > -ef|grep > >>>> carbon" to identity the process id and kill it using "kill -9 id" > command. > >>>> > >>>> Thanks > >>>> Isura > >>>> > >>>> > >>>> On Sat, Jul 19, 2014 at 10:10 AM, Nipuni Perera <[email protected]> > wrote: > >>>>> > >>>>> Hi, > >>>>> > >>>>> I am working on jira issue[1]. I have tested this with a remote BAM > >>>>> server and couldn't reproduce the issue. If wso2server.sh has been > executed > >>>>> over ssh as a nohup process, server does not stop after ssh process > >>>>> terminates. > >>>>> > >>>>> I have followed the steps below: > >>>>> > >>>>> start ssh and connect to remote serrver : ssh -i <private-key> > >>>>> <server-name> -p <password> > >>>>> start wso2server as a background process : sudo -E ./wso2server.sh > >>>>> start (this gives an error "ps: write error: Bad file descriptor" > but server > >>>>> starts successfully > >>>>> exit from the remote server and stop ssh > >>>>> I can access server after ssh is stopped. > >>>>> > >>>>> I have tested it starting wso2server as a nohup process : nohup sudo > -E > >>>>> ./wso2server.sh (This also works after ssh terminates) > >>>>> > >>>>> [1] https://wso2.org/jira/browse/CARBON-14813 > >>>>> > >>>>> Thanks, > >>>>> Nipuni > >>>>> -- > >>>>> Nipuni Perera > >>>>> Software Engineer; WSO2 Inc.; http://wso2.com > >>>>> Email: [email protected] > >>>>> Git hub profile: https://github.com/nipuni > >>>>> Mobile: +94 (71) 5626680 > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Dev mailing list > >>>>> [email protected] > >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Isura Dilhara Karunaratne > >>>> Software Engineer > >>>> > >>>> Mob +94 772 254 810 > >>>> > >>>> > >>>> _______________________________________________ > >>>> Dev mailing list > >>>> [email protected] > >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev > >>>> > >>> > >>> > >>> > >>> -- > >>> Software Engineer - WSO2 Inc. > >>> email: shameera AT wso2.com , shameera AT apache.org > >>> phone: +9471 922 1454 > >>> > >>> Linked in : http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 > >>> Twitter : https://twitter.com/Shameera_R > >>> > >>> _______________________________________________ > >>> Dev mailing list > >>> [email protected] > >>> http://wso2.org/cgi-bin/mailman/listinfo/dev > >>> > >> > >> > >> > >> -- > >> Isuru Perera > >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > >> Lean . Enterprise . Middleware > >> > >> about.me/chrishantha > >> > >> _______________________________________________ > >> Dev mailing list > >> [email protected] > >> http://wso2.org/cgi-bin/mailman/listinfo/dev > >> > > > > > > > > -- > > Nipuni Perera > > Software Engineer; WSO2 Inc.; http://wso2.com > > Email: [email protected] > > Git hub profile: https://github.com/nipuni > > Mobile: +94 (71) 5626680 > > > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > -- Nipuni Perera Software Engineer; WSO2 Inc.; http://wso2.com Email: [email protected] Git hub profile: https://github.com/nipuni Mobile: +94 (71) 5626680 <http://wso2.com>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
