I installed arangodb 3.1.9 in my fedora box at home (8-Core,16 GB Ram+8 GB swap). There I had the exact same problem so I knew it wasn't about limited resources. After restoring ~20 databases there I had a problem restarting the service. Again!
But I noticed an error "Start-pre operation timed out. Terminating" so I began searching what the hell it means. My google skills didn't fail me and I came accross this http://unix.stackexchange.com/questions/227017/how-to-change-systemd-service-timeout-value#answer-276785. It seems that arangoodb 3 service file has a timeout value of 120 seconds and it was constantly failing because of that. I increased the timeout limit in the service file and it worked as expected in Fedora 25 and all databases where up and running. Tomorrow I will try it in Centos 7. I am 95% sure it's the same problem. But seriously guys come on! Is that detail somewhere in the documentation? Did I miss it ? The time limit is very small when you are working with many databases, collections, graphs and aql functions. I had this problem with even 10 databases! 10!!! I spent almost two and a half weeks tweaking a migration script to mass move 65 databases from arango 2.8 to 3.1 and this minor detail took me 3-4 workdays to find out. A clearer error message or an error code would be nice with a mention in the documentation. -- 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.
