No worries. I'm glad it works. Am Freitag, 1. Juli 2016 09:27:43 UTC+2 schrieb Thomas Weiss: > > Hi Jan, > > I've gone through the setup script again and may have found the issue. I > was chmod'ing the /dbdata with go+w (which makes it look like 777) before > the installation of ArangoDB (and creation of the arangodb user), which may > be the reason why the access to that directory wasn't permitted. Working > fine now, my apologies and thanks! > > Thomas > > On Friday, July 1, 2016 at 3:10:19 PM UTC+8, Jan wrote: >> >> Hi Thomas, >> >> it works for me, so I am wondering whether I have carried out different >> steps. >> Here are mine: >> >> # stop running arangodb3 service >> steemann@flittard:~/Downloads$ sudo /etc/init.d/arangodb3 stop >> [ ok ] Stopping arangodb3 (via systemctl): arangodb3.service. >> >> # modify config to point to /dbdata >> steemann@flittard:~/Downloads$ sudo vim /etc/arangodb3/arangod.conf >> >> # create directory and give 777 permissions >> steemann@flittard:~/Downloads$ sudo mkdir /dbdata >> steemann@flittard:~/Downloads$ sudo chmod -R 777 /dbdata >> >> # restart arangodb3 >> steemann@flittard:~/Downloads$ sudo /etc/init.d/arangodb3 start >> [ ok ] Starting arangodb3 (via systemctl): arangodb3.service. >> >> # check if process is there >> steemann@flittard:~/Downloads$ ps fax | grep arangod >> 7856 pts/6 S+ 0:00 | \_ grep --color=auto arangod >> 7587 ? Ss 0:00 /usr/sbin/arangod --uid arangodb --gid >> arangodb --pid-file /var/run/arangodb/arangod.pid --temp.path >> /var/tmp/arangod --log.foreground-tty false --supervisor >> 7588 ? Sl 0:04 \_ /usr/sbin/arangod --uid arangodb --gid >> arangodb --pid-file /var/run/arangodb/arangod.pid --temp.path >> /var/tmp/arangod --log.foreground-tty false --supervisor >> >> # view directory >> steemann@flittard:~/Downloads$ ls -al /dbdata/ >> total 32 >> drwxrwxrwx 5 root root 4096 Jul 1 09:04 . >> drwxr-xr-x 25 root root 4096 Jul 1 09:04 .. >> drwxrwxrwx 3 arangodb arangodb 4096 Jul 1 09:04 databases >> drwxr-xr-x 2 arangodb arangodb 4096 Jul 1 09:04 journals >> -rw------- 1 arangodb arangodb 4 Jul 1 09:04 LOCK >> drwxr-xr-x 2 arangodb arangodb 4096 Jul 1 09:04 rocksdb >> -rw-rw---- 1 arangodb arangodb 68 Jul 1 09:04 SERVER >> -rw-rw---- 1 arangodb arangodb 50 Jul 1 09:04 SHUTDOWN >> >> I ran the above using ArangoDB-3.0.0 on an Ubuntu 16.04 LTS. >> >> Best regards >> Jan >> >> Am Freitag, 1. Juli 2016 08:58:11 UTC+2 schrieb Thomas Weiss: >>> >>> Hi Kaveh, >>> >>> Thanks for your reply. I've gone full steam and made that /dbdata 777, >>> but I still get that error. >>> >>> Thomas >>> >>> On Friday, July 1, 2016 at 2:44:19 PM UTC+8, Kaveh Vahedipour wrote: >>>> >>>> Hi Thomas, >>>> >>>> what are the user rights on "/dbdata"? v3.0 is somewhat more >>>> restrictive in that regards. The startup timing and how we retreat to >>>> arangodb user rights have changed since. >>>> >>>> Kind regards, >>>> Kaveh >>>> >>>> On Friday, July 1, 2016 at 8:01:53 AM UTC+2, Thomas Weiss wrote: >>>>> >>>>> Hi there, >>>>> >>>>> I'm trying to run 3.0 on an Ubuntu VM and it worked well until I tried >>>>> to locate the databases in a different location. >>>>> >>>>> I modified arangod.conf like: >>>>> [database] >>>>> directory = /dbdata >>>>> (which worked fine with 2.8 btw) >>>>> but now I get an error when I *sudo /etc/init.d/arangodb3 start*, and >>>>> looking at the logs it looks like a permission denied error. >>>>> >>>>> Interestingly, when I just *sudo arangod* it works fine. >>>>> >>>>> Any hint would be appreciated, thanks! >>>>> Thomas >>>>> >>>>
-- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
