Hi Jan,
Yes, this actually solves the problem. Thanks!
Regards,
Martijn
On Monday, July 4, 2016 at 11:33:49 AM UTC-4, Jan wrote:
>
> If the VERSION file is empty then the startup may indeed fail.
> My local 2.8 then fails with the error message
>
> 2016-07-04T15:30:46Z [8965] FATAL Database '_system' needs upgrade.
> Please start the server with the --upgrade option
>
> This is probably the same thing that you are seeing.
> It should help to put the following content into the two empty VERSION
> files:
>
> {"version":20809,"tasks":[]}
>
> and save them. Please note that "20809" means ArangoDB 2.8.9. If you're
> running a different version, then the number should different (e.g.
> ArangoDB 2.8.5 = 20805, ArangoDB 2.8.6 = 20806 etc.).
> I hope this helps.
> Best regards
> Jan
>
>
> Am Montag, 4. Juli 2016 15:31:08 UTC+2 schrieb Cloud Coders:
>>
>> Hi Frank,
>>
>> I'm back so i can put the time and effort into this issue a bit more
>> easily.
>>
>> In the database directories are VERSION files, but 2 of them are empty (0
>> bytes) and 1 has got some content. This one i sent to hackers (at)
>> arangodb.org
>>
>> But i'm suspecting the problems are to do with these empty VERSION files
>> and i think they are empty because they could not be written when the disk
>> was flooded.
>>
>> Regards,
>>
>> Martijn
>>
>
--
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.
