Coul you open a GitHub issue? That would make it easier to work on that.
Am Freitag, 16. Dezember 2016 17:58:28 UTC+1 schrieb Jake Lee:
>
> Hi.
> I used ArangoDB 3.0.8 very well for a month. I wanted to upgrade to
> newest ArangoDB, So I installed 3.1.5 as ArangoDB homepage's instruction.
> It installed well. But won't run.
> My environment is Ubuntu 14.04, 64bit.
> Whenever I run it, hereafter is result.
> # service arangodb3 restart
> * Stopping arango database server arangod
> [ OK ]
> * Waiting for shutdown
> [ OK ]
> * Starting arango database server arangod
>
> {startup} starting up in daemon mode
> changed working directory for child process to '/var/tmp'
> unable to start arangod. please check the logfiles for errors
>
> [fail]
>
>
> arangodb.log shows
> 2016-12-16T16:55:31Z [12428] INFO ArangoDB 3.1.5 [linux] 64bit, using
> VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1f 6 Jan 2014
> 2016-12-16T16:55:31Z [12428] INFO file-descriptors (nofiles) hard limit is
> 131072, soft limit is 131072
> 2016-12-16T16:55:31Z [12428] INFO JavaScript using startup
> '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
> 2016-12-16T16:55:33Z [12464] INFO ArangoDB 3.1.5 [linux] 64bit, using
> VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1f 6 Jan 2014
> 2016-12-16T16:55:33Z [12464] INFO using SSL options:
> SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
> 2016-12-16T16:55:33Z [12464] INFO Authentication is turned on
> 2016-12-16T16:55:33Z [12464] INFO Authentication system only
> 2016-12-16T16:55:33Z [12464] INFO Authentication for unix sockets is
> turned on
> 2016-12-16T16:55:33Z [12464] INFO file-descriptors (nofiles) hard limit is
> 131072, soft limit is 131072
> 2016-12-16T16:55:33Z [12464] INFO JavaScript using startup
> '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
> 2016-12-16T16:55:33Z [12464] INFO In database '_system': Database is
> up-to-date (30105/standalone/existing)
> 2016-12-16T16:55:33Z [12464] INFO In database 'naopushdb': Database is
> up-to-date (30105/standalone/existing)
>
> arangodb3.log.supervisor shows...
> 2016-12-16T16:44:05Z [11705] ERROR {startup} child 11706 died a horrible
> death, signal 11
> 2016-12-16T16:44:05Z [11705] ERROR {startup} child only survived for 0
> seconds, this will not work - please fix the error first
>
> I stucked with this. I failed to downgrade ArangoDB also. Stupidly I did
> not dumped out database. :(
> Any help very appreciate to me. Please.
>
>
--
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.
