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:
>
> 1. start ssh and connect to remote serrver : ssh -i <private-key>
> <server-name> -p <password>
> 2. 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
> 3. exit from the remote server and stop ssh
> 4. 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
> <http://wso2.com>
>
>
> _______________________________________________
> 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
