Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGkcVSgKdxa0S5-+xejJxvB=SgT9HNBxJ=gcCsf1vv3EeEbppw@mail.gmail.com>
References: 
 <CAGkcVSgzOKh6KRpwwdzads5aad8cbQNCcpJsxbkoDEy-e43O-w@mail.gmail.com>
	<50C887E0.10201@yagni.com>
	<CABvT1DFrgVSYW17Uw0pQJT3oeMzEN+VXprsbW_zG0breH9so+g@mail.gmail.com>
	<CAGkcVSgKdxa0S5-+xejJxvB=SgT9HNBxJ=gcCsf1vv3EeEbppw@mail.gmail.com>
Date: Wed, 12 Dec 2012 15:00:08 +0000
Message-ID: 
 <CABvT1DELsdtzNdeRn+_1ct8wDpaPDSk-wU1hJBxv6X03xycotA@mail.gmail.com>
Subject: Re: Running couchdb remotely (from an interactive shell)
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

If you're reporting a bug in our init.d script (namely, that it fails
to daemonize couchdb correctly), then please open a JIRA ticket.

You do not need to restart couchdb just to change configuration,
though. Just use PUT's to :5984/_config/section/key -d 'value', and
couchdb will change internally and write out the new file.

I have some experience in managing remote couchdb nodes.

B.

On 12 December 2012 14:51, Nestor Urquiza <nestor.urquiza@gmail.com> wrote:
> Hi Robert,
>
> For maintenance purposes you might want to remotely restart couchdb.
> For example you remotely install couchdb and after that you remotely
> harden it (changing configuration files) which demands a restart.
>
> We prefer to maintain the servers remotely rather than login into them
> and manually execute commands. We script the commands for absolutely
> everything, from building the whole server to patching it to changing
> configuration etc.
>
> With the same recipe we guarantee not relying on memory or going
> manually through steps. The steps are in scripts.
>
> BTW we use Plain Old Bash (POB) recipes with the help of Remoto-IT, a
> simple and open source script based on expect and to remotely run
> scripts in a server.
>
> The init.d script as I said will die as it is attached to the console
> session if you are running it from ssh. The nohup command can be used
> like screen can be used as well (like mentioned in this thread).
>
> I believe in these days where automation is key, couchdb should
> support be run from a remote ssh interactive session. That is what my
> change (using nohup) allows. I am wondering if it makes sense to
> include the change even if it demands a configure or *.ini option.
>
> Right now we are just storing the modified script on svn and patching
> the original from POB recipes, it works but I just want to make sure
> this is not such a need that makes it reasonable to have it as a
> feature request for future releases of couchdb.
>
> Thanks!
> - Nestor
>
> On Wed, Dec 12, 2012 at 8:59 AM, Robert Newson <rnewson@apache.org> wrote:
>> CouchDB includes a script to launch it as a daemon, a standard init.d
>> script. I'm confused why you'd ssh to a machine, run couchdb in the
>> foreground, and log off.
>>
>>
>> On 12 December 2012 13:34, Wayne Conrad <wconrad@yagni.com> wrote:
>>> On 12/11/2012 11:53 AM, Nestor Urquiza wrote:
>>>> As other users have asked in the past to this list couchdb will not
>>>> run from a remote interactive shell but rather it will be killed when
>>>> the ssh session terminates. The command nohup can help with that. Here
>>>> is what I did (which works OK):
>>>
>>> Terminal multiplexors like screen and tmux are very good for "I want to
>>> start a non-daemon, disconnect, and come back later to see what happened."
>>>
>>> Here's how it works with screen:
>>>
>>> log on
>>> $ screen
>>> $ (enter log running command)
>>> type control-a d to detach the screen session
>>> log off
>>>
>>> later...
>>>
>>> log into the remote system
>>> $ screen -r
>>>
>>> and you'll be back in your long running program's term, including any output
>>> the program printed while you were gone.
>>>
>>> Best Regards,
>>> Wayne Conrad