Hi Xander, Do you have files on these cluster on the disk ? If so you can just relink them.
On Mon, Aug 25, 2014 at 12:47 PM, Luca Garulli <[email protected]> wrote: > Hi Xander, > Did you kill OrientDB process? The safest way to shutdown the server is > calling bin/shutdown.sh (or .bat on windows). > > After the auto repair, can you enter on it? You can try also to open the > database with Server's "root" user. > > Lvc@ > > ᐧ > > > On 25 August 2014 09:53, Xander Uiterlinden <[email protected]> > wrote: > >> Are there any recovery methods once the database is unaccessible ? >> >> >> On Thursday, August 21, 2014 5:38:05 PM UTC+2, Xander Uiterlinden wrote: >>> >>> 1.7.3 >>> >>> On Thursday, August 21, 2014 5:18:59 PM UTC+2, Lvc@ wrote: >>>> >>>> Hi Xander, >>>> What version? >>>> >>>> Lvc@ >>>> >>>> ᐧ >>>> >>>> >>>> On 21 August 2014 16:58, Xander Uiterlinden <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> We've been OrientDB with the Tinkerpop stack for quite some time now >>>>> and never experienced any issues. We're running a single node. Today our >>>>> database suddenly became inaccessible. >>>>> When connecting using the console it gives the following output: >>>>> >>>>> orientdb {remote:localhost/}> connect remote:localhost/mydb root root >>>>> >>>>> Disconnecting from remote server [remote:localhost/]... >>>>> OK >>>>> Connecting to database [remote:localhost/mydb] with user 'root'... >>>>> Error: com.orientechnologies.orient.core.index.OIndexException: >>>>> Cluster with id 4 does not exist. >>>>> >>>>> The logs give the following repeating message when attempting to log >>>>> on to this database: >>>>> >>>>> 2014-08-21 14:40:24:161 WARN Repairing security structures... >>>>> [OSecurityShared] >>>>> 2014-08-21 14:40:24:319 WARN Repair completed [OSecurityShared] >>>>> 2014-08-21 14:41:05:790 WARN Repairing security structures... >>>>> [OSecurityShared] >>>>> 2014-08-21 14:41:05:968 WARN Repair completed [OSecurityShared] >>>>> >>>>> I don't really know what is going on. Did anyone experience similar >>>>> behavior ? >>>>> Are there ways to recover from this ? >>>>> Other databases on the same node can be accessed just fine. >>>>> >>>>> Thanks, >>>>> >>>>> Xander >>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "OrientDB" 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. >>>>> >>>> >>>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" 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. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" 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. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
