Re: distributed-db-config error

32 views
Skip to first unread message
Message has been deleted

user.w...@gmail.com

unread,
May 25, 2016, 9:30:55 AM5/25/16
to OrientDB
Hello,

do you mean warning messages inside log?
I can't see any error messages in the file that you provided.

Il giorno mercoledì 25 maggio 2016 14:30:58 UTC+2, Rahul Narendra ha scritto:
HI

IN distributed-db-config setting facing below kind of error
plz help  me



Message has been deleted
Message has been deleted

user.w...@gmail.com

unread,
May 26, 2016, 3:00:24 AM5/26/16
to OrientDB
It's totally normal log, there aren't any critical errors, only info and warning informational messages.

Il giorno giovedì 26 maggio 2016 08:02:47 UTC+2, Rahul Narendra ha scritto:
HI LOOKINTO THIS ONE
---------- [OHazelcastPlugin]
2016-05-25 17:58:03:517 INFO  [user] Saving distributed configuration file for database 'GratefulDeadConcerts' to: C:\Users\608792888\Downloads\Orient\orientdb-community-2.2.0-SNAPSHOT_1\databases\GratefulDeadConcerts\distributed-config.json [OHazelcastPlugin]
2016-05-25 17:58:03:533 INFO  [user] found no previous messages in queue orientdb.node.user.GratefulDeadConcerts.request [OHazelcastDistributedMessageService]
2016-05-25 17:58:03:730 INFO  [172.31.66.202]:2481 [orientdb_test] [3.5.3] processors=4, physical.memory.total=3.2G, physical.memory.free=829.0M, swap.space.total=6.3G, swap.space.free=2.2G, heap.memory.used=58.1M, heap.memory.free=26.1M, heap.memory.total=84.3M, heap.memory.max=455.3M, heap.memory.used/total=69.02%, heap.memory.used/max=12.77%, minor.gc.count=8, minor.gc.time=38ms, major.gc.count=1, major.gc.time=24ms, load.process=18.00%, load.system=100.00%, load.systemAverage=n/a, thread.count=41, thread.peakCount=41, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operation.size=0, executor.q.priorityOperation.size=0, executor.q.response.size=0, operations.remote.size=1, operations.running.size=0, operations.pending.invocations.count=1, operations.pending.invocations.percentage=0.00%, proxy.count=5, clientEndpoint.count=0, connection.active.count=1, client.connection.count=0, connection.count=0 [HealthMonitor]
2016-05-25 17:58:04:007 INFO  [user] Publishing online status for database user.GratefulDeadConcerts... [OHazelcastDistributedDatabase]
2016-05-25 17:58:04:010 WARNI [user] updated node status to 'ONLINE' [OHazelcastPlugin]
2016-05-25 17:58:04:010 INFO  [user] received new status user.GratefulDeadConcerts=ONLINE [OHazelcastPlugin]
2016-05-25 17:58:04:014 WARNI Authenticated clients can execute any kind of code into the server by using the following allowed languages: [sql] [OServerSideScriptInterpreter]
2016-05-25 17:58:04:125 INFO  OrientDB Server is active v2.2.0-SNAPSHOT (build dev...@r${buildNumber}; 2015-12-16 10:39:09+0000). [OServer]
2016-05-25 17:58:13:424 INFO  [172.31.66.202]:2481 [orientdb_test] [3.5.3] Connection [Address[172.31.67.126]:2480] lost. Reason: java.io.EOFException[Could not read protocol type!] [TcpIpConnection]



Reply all
Reply to author
Forward
0 new messages