couchdb 1.5.1-1 Loaded but Inactive(Dead)

Ask questions about Arch Linux ARM. Please search before making a new topic.
Topic locked

couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby bbaronas » Fri May 02, 2014 5:28 pm

Hello,

Allow me to start by saying I am very new to Archlinux ARM. I have familiarity with Debian/Ubuntu on Odroid-XU, but I have found Archlinux ARM quite intriguing, and began looking into it for a project. However, I am very early on in my learning and have hit a snag.

I have installed (or have tried to install) couchdb using $this->bbcode_second_pass_code('', 'pacman -S couchdb') and letting it run. It installed couchdb 1.5.1-1 and the necessary erlang components and appears to have worked without incident.

However, whenever I try to test couchdb using $this->bbcode_second_pass_code('', 'curl -XGET http://127.0.0.1:5984/') I get the error:
$this->bbcode_second_pass_quote('', 'c')url: (7) Failed to connect to 127.0.0.1 port 5984: Connection refused


systemctl status couchdb reveals:
$this->bbcode_second_pass_quote('', '') couchdb.service - CouchDB Server
Loaded: loaded (/usr/lib/systemd/system/couchdb.service; enabled)
Active: inactive (dead) since Fri 2014-05-02 10:42:15 MDT; 38min ago
Process: 678 ExecStop=/usr/bin/couchdb -d (code=exited, status=0/SUCCESS)
Process: 628 ExecStart=/usr/bin/couchdb -b -o /dev/null -e /dev/null (code=exited, status=0/SUCCESS)
Main PID: 643 (code=exited, status=0/SUCCESS)


Which appears to me that the service is enabled, but it remains inactive. The logs do not appear to show any errors.

For reference I am running on an Odroid-XU+E using the mainline linux kernel (3.13.0-2)

I am not quite sure how to interpret the status of loaded but inactive and do not know how to make couchdb active.

Any help with this would be greatly appreciated.
bbaronas
 
Posts: 3
Joined: Fri May 02, 2014 5:06 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby WarheadsSE » Fri May 02, 2014 6:06 pm

enabled != started
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby bbaronas » Fri May 02, 2014 6:42 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'e')nabled != started


I understand. However, I have tried $this->bbcode_second_pass_code('', ' systemctl enable couchdb ') AND $this->bbcode_second_pass_code('', ' systemctl start couchdb ') (plus restart, stop/start, etc). The status is still the same:
$this->bbcode_second_pass_quote('', '') couchdb.service - CouchDB Server
Loaded: loaded (/usr/lib/systemd/system/couchdb.service; enabled)
Active: inactive (dead) since Fri 2014-05-02 12:26:20 MDT; 8s ago
Process: 768 ExecStop=/usr/bin/couchdb -d (code=exited, status=0/SUCCESS)
Process: 718 ExecStart=/usr/bin/couchdb -b -o /dev/null -e /dev/null (code=exited, status=0/SUCCESS)
Main PID: 733 (code=exited, status=0/SUCCESS)

May 02 12:26:19 alarm-xu couchdb[718]: Apache CouchDB has started, time to relax.
May 02 12:26:19 alarm-xu systemd[1]: Started CouchDB Server.


$this->bbcode_second_pass_code('', ' curl -XGET http://127.0.0.1:5984/ ')

$this->bbcode_second_pass_quote('', ' ')curl: (7) Failed to connect to 127.0.0.1 port 5984: Connection refused


I am trying to get to started. What am I missing? In my Debian build, I just had to verify user permissions, and rights to the folders. The service started and ran fine. Here, it gives me this information and does not start.
bbaronas
 
Posts: 3
Joined: Fri May 02, 2014 5:06 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby WarheadsSE » Fri May 02, 2014 7:26 pm

journalctl -u couchdb.service
netstat -atnp | grep 5984
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby bbaronas » Fri May 02, 2014 7:44 pm

Here are my results from $this->bbcode_second_pass_code('', 'journalctl -u couchdb.service'):

$this->bbcode_second_pass_quote('', '[')root@alarm-xu ~]# journalctl -u couchdb.service
-- Logs begin at Thu 2014-05-01 13:10:16 MDT, end at Fri 2014-05-02 12:53:17 MDT. --
May 01 14:41:10 alarm systemd[1]: Starting CouchDB Server...
May 01 14:41:11 alarm couchdb[419]: Apache CouchDB has started, time to relax.
May 01 14:41:11 alarm systemd[1]: Started CouchDB Server.
May 01 14:45:05 alarm systemd[1]: Starting CouchDB Server...
May 01 14:45:05 alarm couchdb[491]: Apache CouchDB has started, time to relax.
May 01 14:45:05 alarm systemd[1]: Started CouchDB Server.
-- Reboot --
May 01 14:46:15 alarm systemd[1]: Starting CouchDB Server...
May 01 14:46:15 alarm systemd[1]: Started CouchDB Server.
May 01 14:46:15 alarm couchdb[148]: Apache CouchDB has started, time to relax.
May 01 14:55:13 alarm-xu systemd[1]: Starting CouchDB Server...
May 01 14:55:13 alarm-xu couchdb[403]: Apache CouchDB has started, time to relax.
May 01 14:55:13 alarm-xu systemd[1]: Started CouchDB Server.
May 01 14:58:58 alarm-xu systemd[1]: Starting CouchDB Server...
May 01 14:58:58 alarm-xu couchdb[486]: Apache CouchDB has started, time to relax.
May 01 14:58:58 alarm-xu systemd[1]: Started CouchDB Server.
May 01 15:05:59 alarm-xu systemd[1]: Stopped CouchDB Server.
May 01 15:06:08 alarm-xu systemd[1]: Starting CouchDB Server...
May 01 15:06:08 alarm-xu couchdb[576]: Apache CouchDB has started, time to relax.
May 01 15:06:08 alarm-xu systemd[1]: Started CouchDB Server.
May 02 07:33:34 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 07:33:34 alarm-xu couchdb[29448]: Apache CouchDB has started, time to relax.
May 02 07:33:34 alarm-xu systemd[1]: Started CouchDB Server.
-- Reboot --
May 02 07:43:36 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 07:43:36 alarm-xu systemd[1]: Started CouchDB Server.
May 02 07:43:37 alarm-xu couchdb[146]: Apache CouchDB has started, time to relax.
-- Reboot --
May 02 07:56:41 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 07:56:41 alarm-xu systemd[1]: Started CouchDB Server.
May 02 07:56:42 alarm-xu couchdb[148]: Apache CouchDB has started, time to relax.
-- Reboot --
May 02 07:58:37 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 07:58:37 alarm-xu systemd[1]: Started CouchDB Server.
May 02 07:58:38 alarm-xu couchdb[147]: Apache CouchDB has started, time to relax.
May 02 08:07:19 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 08:07:19 alarm-xu couchdb[387]: Apache CouchDB has started, time to relax.
May 02 08:07:19 alarm-xu systemd[1]: Started CouchDB Server.
May 02 10:26:04 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 10:26:04 alarm-xu couchdb[531]: Apache CouchDB has started, time to relax.
May 02 10:26:04 alarm-xu systemd[1]: Started CouchDB Server.
May 02 10:42:02 alarm-xu systemd[1]: Stopped CouchDB Server.
May 02 10:42:13 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 10:42:13 alarm-xu couchdb[628]: Apache CouchDB has started, time to relax.
May 02 10:42:13 alarm-xu systemd[1]: Started CouchDB Server.
May 02 12:26:18 alarm-xu systemd[1]: Starting CouchDB Server...
May 02 12:26:19 alarm-xu couchdb[718]: Apache CouchDB has started, time to relax.
May 02 12:26:19 alarm-xu systemd[1]: Started CouchDB Server.


It just shows many starts and restarts

$this->bbcode_second_pass_code('', 'netstat -atnp | grep 5984') returned nothing. A regular netstat -atnp shows:
$this->bbcode_second_pass_quote('', '[')root@alarm-xu ~]# netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 179/nginx: master p
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 148/sshd
tcp 0 248 xxx.xxx.xxx.xxx:22 xxx.xxx.xxx.xxx:55835 ESTABLISHED 376/sshd: root@pts/
tcp6 0 0 :::22 :::* LISTEN 148/sshd
bbaronas
 
Posts: 3
Joined: Fri May 02, 2014 5:06 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby WarheadsSE » Fri May 02, 2014 9:08 pm

Is the couchdb process even running? Perhaps there is an issue with the config. Consider attempting to run it by hand, and see any debug output you can.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: couchdb 1.5.1-1 Loaded but Inactive(Dead)

Postby kmihelich » Fri May 02, 2014 9:33 pm

The current version of couchdb is broken against the current version of erlang (R17), and 1.5.1 isn't in our repositories because it won't build against R17. The related bug upstream was just closed yesterday:
https://issues.apache.org/jira/browse/COUCHDB-2200

If you want to use couchdb, then you need to downgrade your erlang to R16 until whatever next release of couchdb that has this new support for R17 has been picked up by Arch.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm
Top
Topic locked

Return to User Questions

Who is online

Users browsing this forum: Google [Bot] and 19 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group    © Arch Linux ARM