Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - arangodb

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: arangodb 3.1.6-1

Git Clone URL: https://aur-dev.archlinux.org/arangodb.git (read-only)
Package Base: arangodb
Description: A multi-model NoSQL database, combining key-value, document and graph data models.
Upstream URL: https://www.arangodb.com/
Keywords: database document graph key-value model multi nosql
Licenses: Apache
Conflicts: arangodb-git, arangodb-latest
Provides: arangodb=3.1.6
Submitter: bpdp
Maintainer: sleepycat
Last Packager: sleepycat
Votes: 9
Popularity: 0.121044
First Submitted: 2012-08-23 14:29
Last Updated: 2016-12-23 02:22

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

asaaki commented on 2015-02-21 19:53

Even with go provided via Arch the needed disk space for a build of ArangoDB from sources is around 3,2 GiB. So, no real improvement here.

asaaki commented on 2015-02-19 17:08

I'll change this build setup soon (using Go package instead of a bundled one).
Should reduce the amount of needed disk space a little bit.

evilgnome commented on 2015-02-19 16:58

My build failure was probably due to running out of space in the build dir. When the failure happened, the space the operation used was 3.7 gigs!

evilgnome commented on 2015-02-18 23:18

This fails to compile for me, x86_64.

...
CXXLD bin/arangoimp
collect2: error: ld returned 1 exit status
Makefile:3363: recipe for target 'bin/arangoimp' failed
make[1]: *** [bin/arangoimp] Error 1
make[1]: Leaving directory '/.../src/ArangoDB-2.4.3'
Makefile:2056: recipe for target 'all' failed
make: *** [all] Error 2

Also, why does it provide a bundled go, rather than depending on community's?

asaaki commented on 2014-11-17 22:54

Version 2.3.0 was released. Could you update the package, please?

ayr0 commented on 2014-06-27 18:30

2.1.2 has been released. Arangodb notifies there is an update everytime I launch it.

bpdp commented on 2013-12-03 20:02

hello,

Updated to 1.4.3, accomodating changes from @neng. thank you. @mgushee looks good now.

neng commented on 2013-12-03 18:21

v1.4.3 was out. I've created a git-based package: arangodb-git. In there, I made some changes that may be useful for this package too.

In arangodb.install, added this:

chown arangodb:arangodb /var/lib/arangodb-apps &> /dev/null

In arangodb.service, added this option to ExecStart:
--gid arangodb

mgushee commented on 2013-11-20 21:51

Also, I found a couple of other issues:

1) In the service file, it says

After=syslog.target network.target

Now, I don't understand systemd well enough to be certain this is an error, but I note that 'syslog.target' doesn't exist on my system, nor does the documentation ('systemd.special' manpage) list it among the built-in targets. On the other hand, there *is* a 'syslog.socket', so maybe that's what you meant?

Also--and here again, I'm too new both to ArangoDB and systemd to be sure--but if syslog.socket is indeed needed in the service file, that suggests you might need to add syslog-ng as a package dependency. Though I deleted the syslog reference from the service file, and it doesn't seem to hurt anything (yes, logging appears to work).

2) I think this is really an upstream issue, but I thought you should be aware of it: when I installed the package and attempted to start the arangodb service, I got the following error (from /var/log/arangodb/arangod.log):

ERROR unable to create base application directory '/usr/share/arangodb/js/apps/databases'

I eventually discovered that the fix for this is to edit /etc/arangodb/arangod.conf as follows:

[javascript]
....
app-path = /usr/share/arangodb/js/apps ==> /var/lib/arangodb/apps

I don't know if that's really right, but at least it is writable by the arangodb user.

The question is, though, why was that path set to /usr/share/.... in the first place? Well, I grepped through the source directory, and I found templates for the config files that contain the variable @PKGDATA_DIR@ --which is ultimately derived from the configure option --datarootdir, which I see you set to /usr/share. But I don't think it's your fault, since ./configure --help says (a) $PREFIX/share is the default, and (b) the specified directory is supposed to be read-only.

I'm going to post to the ArangoDB mailing list about this; anything you want to say?

PS: since ArangoDB 1.4.1 is out, I bumped the version number in PKGBUILD, and the package built without any obvious problems.

mgushee commented on 2013-11-20 18:58

Also, I found a couple of other issues:

1) In the service file, it says

After=syslog.target network.target

Now, I don't understand systemd well enough to be certain this is an error, but I note that 'syslog.target' doesn't exist on my system, nor does the documentation ('syslog.special' manpage) list it among the built-in targets. On the other hand, there *is* a 'syslog.socket', so maybe that's what you meant?

Also--and here again, I'm too new both to ArangoDB and systemd to be sure--but if syslog.socket is indeed needed in the service file, that suggests you might need to add syslog-ng as a package dependency. Though I deleted the syslog reference from the service file, and it doesn't seem to hurt anything (yes, logging appears to work).

2) I think this is really an upstream issue, but I thought you should be aware of it: when I installed the package and attempted to start the arangodb service, I got the following error (from /var/log/arangodb/arangod.log):

ERROR unable to create base application directory '/usr/share/arangodb/js/apps/databases'

I eventually discovered that the fix for this is to edit /etc/arangodb/arangod.conf as follows:

[javascript]
....
app-path = /usr/share/arangodb/js/apps ==> /var/lib/arangodb/apps

I don't know if that's really right, but at least it is writable by the arangodb user.

The question is, though, why was that path set to /usr/share/.... in the first place? Well, I grepped through the source directory, and I found templates for the config files that contain the variable @PKGDATA_DIR@ --which is ultimately derived from the configure option --datarootdir, which I see you set to /usr/share. But I don't think it's your fault, since ./configure --help says (a) $PREFIX/share is the default, and (b) the specified directory is supposed to be read-only.

I'm going to post to the ArangoDB mailing list about this; anything you want to say?

PS: since ArangoDB 1.4.1 is out, I bumped the version number in PKGBUILD, and the package built without any obvious problems.