Ahh..Fixed by adding in the explicit ip of my Orientdb server to the binary and http listeners in orientdb-server-config.xml
Tia On Thursday, January 16, 2014 10:52:40 AM UTC-8, tia wrote: > > Running Orientdb 1.6.2 and getting an error everytime for shutdown.sh > (same for prev. 1.5 version): > > > > > *Sending shutdown command to remote OrientDB Server instance...Jan 16, > 2014 10:48:37 AM com.orientechnologies.common.log.OLogManager logINFO: > Loading configuration from: > /Users/tnguyen/Apps/orientdb-community-1.6.2/config/orientdb-server-config.xml...java.io.IOException: > > Cannot connect to host 0.0.0.0:2424 <http://0.0.0.0:2424>* > > Am I missing cme configuration step prior to starting up the server (via > server.sh) ? > > Tia > > > On Monday, May 27, 2013 6:06:36 AM UTC-7, Lvc@ wrote: >> >> Hi Jonathan, >> corruptions happen when the server process is killer or in case of crash >> of JVM/OS. The new "plocal" storage acts in different way by avoiding such >> sensibility to hard shutdowns. In the upcoming 1.4 plocal is bundled but >> don't support transaction rollbacks right now (we need few weeks for that). >> >> My suggestion is to avoiding stopping OrientDB by killing the process bu >> rather use the shutdown.sh script. And do regular backups, but this >> suggestion is common to all DBMS. OrientDB has the AutomaticBackup plugin >> you can enable in orientdb-server-config.xml file. >> >> >> Lvc@ >> >> >> >> >> On 24 May 2013 21:59, Jonathan Wysocki <[email protected]> wrote: >> >>> I don't want to be negative >>> >>> >>> But im having a really hard time with orientdb >>> >>> closing ./orientdb stop >>> and then starting it makes it say tables havent properly closed. >>> >>> Tried removing a index and now i have >>> because when i tried to save (Insert) a record with the used index it >>> became Null. >>> >>> It really makes me wonder how stable orientdb is. >>> Maybe im a crappy user but the database is really making me frustrated. >>> >>> im using orientdb 1.3. >>> >>> i also tried export import the database. >>> >>> >>> >>> orientdb> drop index User.email; >>> >>> Removing index... >>> >>> Error: com.orientechnologies.orient.core.exception.ODatabaseException: >>> Error on deleting record #1:1 >>> Error: java.lang.IllegalStateException: Corrupted holes: found offset >>> 9628 instead of 8793 while creating a new hole on position 9581, size 33. >>> The closest hole 1 points to position 8793, size 1698312513 >>> >>> >>> orientdb> select from user; >>> >>> Error: com.orientechnologies.orient.core.exception.ODatabaseException: >>> Error on retrieving record #26:0 (cluster: user) >>> Error: com.orientechnologies.orient.core.exception.OStorageException: >>> Error on reading record from file 'default.0.oda', position 8793, size >>> 1.58Gb: the record size is bigger then the file itself (11.74Kb). Probably >>> the record is dirty due to a previous crash. It is strongly suggested to >>> restore the database or export and reimport this one. >>> orientdb >>> >>> >>> What shall i do if i go production and my server shutdown. >>> Do i lose everything? >>> >>> >>> -- >>> >>> --- >>> 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/groups/opt_out. >>> >>> >>> >> >> -- --- 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/groups/opt_out.
