You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Cory Zue <cz...@dimagi.com> on 2010/08/16 18:11:51 UTC
Upgrade to 1.0 on Ubuntu 10.4
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
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Cory Zue <cz...@dimagi.com>.
On Mon, Aug 16, 2010 at 10:15 PM, Noah Slater <ns...@apache.org> wrote:
> The first line of the file starts with a "#!" which is known as a
> "hasbang."
>
> If you append "+x" to the end of that line, you should see some pretty
> comprehensive debugging.
>
>
Where should this debugging be? I tried sticking it on the init.d script
but it still just spits out:
* Starting database server couchdb
without actually running couchdb (or at least all of it).
> On 16 Aug 2010, at 20:34, Cory Zue wrote:
>
> > On Mon, Aug 16, 2010 at 9:30 PM, Noah Slater <ns...@apache.org> wrote:
> >
> >> Add +x to the hashbang, and run it again.
> >
> >
> > Sorry, not sure what you mean by the hashbang? Both /bin/couchdb and
> > etc/init.d/couchdb are executable for everyone.
>
>
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Noah Slater <ns...@apache.org>.
The first line of the file starts with a "#!" which is known as a "hasbang."
If you append "+x" to the end of that line, you should see some pretty comprehensive debugging.
On 16 Aug 2010, at 20:34, Cory Zue wrote:
> On Mon, Aug 16, 2010 at 9:30 PM, Noah Slater <ns...@apache.org> wrote:
>
>> Add +x to the hashbang, and run it again.
>
>
> Sorry, not sure what you mean by the hashbang? Both /bin/couchdb and
> etc/init.d/couchdb are executable for everyone.
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Cory Zue <cz...@dimagi.com>.
On Mon, Aug 16, 2010 at 9:30 PM, Noah Slater <ns...@apache.org> wrote:
> Add +x to the hashbang, and run it again.
Sorry, not sure what you mean by the hashbang? Both /bin/couchdb and
etc/init.d/couchdb are executable for everyone.
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Noah Slater <ns...@apache.org>.
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 <sr...@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 <cz...@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
>>>
>>
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Cory Zue <cz...@dimagi.com>.
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 <sr...@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 <cz...@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
> >
>
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by km <sr...@gmail.com>.
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 <cz...@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
>
Re: Upgrade to 1.0 on Ubuntu 10.4
Posted by Cory Zue <cz...@dimagi.com>.
On Mon, Aug 16, 2010 at 6:11 PM, Cory Zue <cz...@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
>
Big thanks to tisba who helped me through this on IRC. The issue ended up
being a simple file permissions one. It seems the couch.io installer
doesn't give permissions to the couchdb user to /opt/couchdb-1.0.0/.
Running couch as root was working fine but the init.d script runs it as
couchdb user. Since they didn't even have permission to access the log
file, I was unable to see the log and thus unable to see why everything was
failing.
The solution ended up being to run the following command to give ownership
over that directory:
chown -R couchdb:couchdb
/opt/couchdb-1.0.0/{etc,var/lib,var/run,var/log}/couchdb
I don't know if this is a problem with new installs or only when upgrading
from a previous version, but it seems like it would be good to have this
documented somewhere to solve future headaches.
thanks to all that helped.
Cory