couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: Upgrade to 1.0 on Ubuntu 10.4
Date Mon, 16 Aug 2010 19:30:29 GMT
Add +x to the hashbang, and run it again.

On 16 Aug 2010, at 20:26, Cory Zue wrote:

> Thanks, though this isn't exactly my issue.  Nothing is on port 5984
> (looking via netstat) when I run it through the init.d script, but it
> happily runs and takes 5984 when I just run the binary.  Again, think it has
> to be something with how the builtin script calls/configures the binary.
> 
> On Mon, Aug 16, 2010 at 7:13 PM, km <srikrishnamohan@gmail.com> wrote:
> 
>> ubuntu by default uses 0.10.x for its desktop operations on 5984, probably
>> its occupied. So
>> try changing the listening port to something else like 5985
>> and restart
>> KM
>> On Mon, Aug 16, 2010 at 9:41 PM, Cory Zue <czue@dimagi.com> wrote:
>> 
>>> Hey,
>>> 
>>> I had an Ubuntu machine running a couch 0.11 build from source.  I just
>>> tried upgrading to 1.0 using the super-convenient installer from
>> couch.io(
>>> http://www.couch.io/get#ubuntu).  I didn't touch any of the defaults
>>> during
>>> installation.
>>> 
>>> Couch seems perfectly happy when i start it
>>> from  /opt/couchdb-1.0.0/bin/couchdb (runs fine, all tests pass), but
>> when
>>> I
>>> start it using /opt/couchdb-1.0.0/etc/init.d/couchdb start it doesn't
>> work.
>>> Couch appears to be running and spawns several processes, but I can't
>> hit
>>> it on port 5984, and netstat doesn't show 5984 being occupied.
>>> 
>>> Any thoughts as to what might be going on here?  My initial thought was
>> one
>>> of the old environment variables from a previous install causing
>> something
>>> to go haywire in the init.d, but I haven't explored that much yet.
>>> 
>>> thanks,
>>> Cory
>>> 
>> 


Mime
View raw message