I installed neo4j 3.0.3. I took 2.3.0-M02 database, enabled upgrade by setting uncommenting
dbms.allow_format_migration=true
and started server, but it fails with
2016-06-15 17:50:18.439+0000 INFO Starting...
2016-06-15 17:50:18.874+0000 INFO Bolt enabled on localhost:7687.
2016-06-15 17:50:19.027+0000 INFO Starting upgrade of database
2016-06-15 17:50:19.046+0000 INFO Migrating Indexes (1/3):
2016-06-15 17:50:19.049+0000 INFO 10% completed
2016-06-15 17:50:19.049+0000 INFO 20% completed
2016-06-15 17:50:19.049+0000 INFO 30% completed
2016-06-15 17:50:19.050+0000 INFO 40% completed
2016-06-15 17:50:19.050+0000 INFO 50% completed
2016-06-15 17:50:19.050+0000 INFO 60% completed
2016-06-15 17:50:19.050+0000 INFO 70% completed
2016-06-15 17:50:19.050+0000 INFO 80% completed
2016-06-15 17:50:19.050+0000 INFO 90% completed
2016-06-15 17:50:19.050+0000 INFO 100% completed
2016-06-15 17:50:19.051+0000 INFO Migrating Legacy indexes (2/3):
2016-06-15 17:50:19.057+0000 INFO 10% completed
2016-06-15 17:50:19.058+0000 INFO 20% completed
2016-06-15 17:50:19.058+0000 INFO 30% completed
2016-06-15 17:50:19.058+0000 INFO 40% completed
2016-06-15 17:50:19.058+0000 INFO 50% completed
2016-06-15 17:50:19.058+0000 INFO 60% completed
2016-06-15 17:50:19.058+0000 INFO 70% completed
2016-06-15 17:50:19.058+0000 INFO 80% completed
2016-06-15 17:50:19.058+0000 INFO 90% completed
2016-06-15 17:50:19.059+0000 INFO 100% completed
2016-06-15 17:50:19.059+0000 INFO Migrating Store files (3/3):
2016-06-15 17:50:19.067+0000 INFO 10% completed
2016-06-15 17:50:19.067+0000 INFO 20% completed
2016-06-15 17:50:19.067+0000 INFO 30% completed
2016-06-15 17:50:19.068+0000 INFO 40% completed
2016-06-15 17:50:19.068+0000 INFO 50% completed
2016-06-15 17:50:19.068+0000 INFO 60% completed
2016-06-15 17:50:19.068+0000 INFO 70% completed
2016-06-15 17:50:19.068+0000 INFO 80% completed
2016-06-15 17:50:19.068+0000 INFO 90% completed
2016-06-15 17:50:19.068+0000 INFO 100% completed
2016-06-15 17:50:19.091+0000 INFO Successfully finished upgrade of database
2016-06-15 17:50:19.389+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#3693c13' was successfully initialized, but failed to start. Please see attached cause exception. Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#3693c13' was successfully initialized, but failed to start. Please see attached cause exception.
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#3693c13' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:68)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:217)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:87)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:66)
at org.neo4j.server.CommunityEntryPoint.main(CommunityEntryPoint.java:28)
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.server.database.LifecycleManagingDatabase#3693c13' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:189)
... 3 more
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.CommunityFacadeFactory, /home/pavel/devel/neo4j-community-3.0.3/data/databases/graph.db
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:144)
at org.neo4j.kernel.impl.factory.CommunityFacadeFactory.newFacade(CommunityFacadeFactory.java:40)
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:108)
at org.neo4j.server.CommunityNeoServer.lambda$static$31(CommunityNeoServer.java:55)
at org.neo4j.server.CommunityNeoServer$$Lambda$43/1644443712.newGraphDatabase(Unknown Source)
at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:89)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
... 5 more
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.storageengine.impl.recordstorage.RecordStorageEngine#6ec66b58' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.NeoStoreDataSource.start(NeoStoreDataSource.java:503)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.impl.transaction.state.DataSourceManager.start(DataSourceManager.java:99)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:140)
... 11 more
Caused by: org.neo4j.kernel.impl.store.InvalidRecordException: DynamicRecord[1869509480,used=false,(0),type=-1,data=byte[],start=true,next=-1] not in use
at org.neo4j.kernel.impl.store.record.RecordLoad.verify(RecordLoad.java:63)
at org.neo4j.kernel.impl.store.CommonAbstractStore.verifyAfterNotRead(CommonAbstractStore.java:1229)
at org.neo4j.kernel.impl.store.CommonAbstractStore.readIntoRecord(CommonAbstractStore.java:1051)
at org.neo4j.kernel.impl.store.CommonAbstractStore.access$000(CommonAbstractStore.java:60)
at org.neo4j.kernel.impl.store.CommonAbstractStore$1.next(CommonAbstractStore.java:1177)
at org.neo4j.kernel.impl.store.CommonAbstractStore$1.next(CommonAbstractStore.java:1142)
at org.neo4j.kernel.impl.store.RecordCursor.getAll(RecordCursor.java:106)
at org.neo4j.kernel.impl.store.CommonAbstractStore.getRecords(CommonAbstractStore.java:1124)
at org.neo4j.kernel.impl.store.TokenStore.ensureHeavy(TokenStore.java:141)
at org.neo4j.kernel.impl.store.TokenStore.getStringFor(TokenStore.java:146)
at org.neo4j.kernel.impl.store.TokenStore.getTokens(TokenStore.java:100)
at org.neo4j.kernel.impl.storageengine.impl.recordstorage.RecordStorageEngine.start(RecordStorageEngine.java:415)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
... 19 more
I tried to google this one up, but there not much to be found, except the code itself.
Upgrades from milestones are usually not supported.
Can you check that the old store was ok with the consistency checker?
http://www.markhneedham.com/blog/2014/01/22/neo4j-backup-store-copy-and-consistency-check/
You could also try to use my store-copy tool on your store to copy over all non-affected records: https://github.com/jexp/store-utils/tree/30
Related
My jenkins server is getting stopped while the jenkins pipeline is running.
I don't know why its happening
Can anyone help me on this
Thanks in advance.
Jenkins logs
2022-02-28 11:36:16.019+0000 [id=78] INFO o.j.p.workflow.job.WorkflowRun#finish: pipeline #82 completed: SUCCESS
2022-02-28 12:33:52.148+0000 [id=230] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 12:33:52.171+0000 [id=230] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 14 ms
2022-02-28 13:04:29.255+0000 [id=278] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started telemetry collection
2022-02-28 13:04:30.277+0000 [id=278] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished telemetry collection. 1,015 ms
2022-02-28 13:33:52.148+0000 [id=332] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 13:33:52.158+0000 [id=332] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-02-28 14:33:52.148+0000 [id=425] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 14:33:52.158+0000 [id=425] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-02-28 15:33:52.148+0000 [id=526] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 15:33:52.156+0000 [id=526] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 4 ms
2022-02-28 16:33:52.149+0000 [id=631] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 16:33:52.161+0000 [id=631] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 7 ms
2022-02-28 16:36:45.550+0000 [id=646] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Fingerprint cleanup
2022-02-28 16:36:45.660+0000 [id=646] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Fingerprint cleanup. 106 ms
2022-02-28 17:17:51.445+0000 [id=704] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Workspace clean-up
2022-02-28 17:17:51.570+0000 [id=704] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Workspace clean-up. 121 ms
2022-02-28 17:33:52.149+0000 [id=732] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 17:33:52.157+0000 [id=732] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 4 ms
2022-02-28 18:33:52.149+0000 [id=827] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 18:33:52.157+0000 [id=827] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-02-28 19:33:52.148+0000 [id=914] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 19:33:52.162+0000 [id=914] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-02-28 20:33:52.149+0000 [id=1013] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 20:33:52.156+0000 [id=1013] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 4 ms
2022-02-28 21:33:52.149+0000 [id=1102] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 21:33:52.180+0000 [id=1102] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 28 ms
2022-02-28 22:33:52.149+0000 [id=1188] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 22:33:52.161+0000 [id=1188] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 9 ms
2022-02-28 23:33:52.148+0000 [id=1289] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-02-28 23:33:52.156+0000 [id=1289] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-03-01 00:33:52.148+0000 [id=1376] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-03-01 00:33:52.157+0000 [id=1376] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 5 ms
2022-03-01 01:33:52.148+0000 [id=1469] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
2022-03-01 01:33:52.156+0000 [id=1469] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Periodic background build discarder. 6 ms
2022-03-01 02:33:52.148+0000 [id=1554] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started Periodic background build discarder
I've been trying to restart neo4j after adding new data on an EC2 instance. I stopped the neo4j instance, then I called systemctl start neo4j, but when I call cypher-shell it says Connection refused, and connection to the browser port doesn't work anymore.
In the beginning I assumed it was a heap space problem, since looking at the debug.log it said there was a memory issue. I adjusted the heap space and cache settings in neo4j.conf as recommended by neo4j-admin memrec, but still neo4j won't start.
Then I assumed it was because my APOC package was outdated. My neo4j version is 3.5.6, but APOC is 3.5.0.3. I download the latest 3.5.0.4 version, but still neo4j won't start.
At last I tried chmod 777 on every file in the data/database and plugin directories and the directories themselves, but still neo4j won't start.
What's strange is when I try neo4j console for all of these attempts, both cypher-shell and the neo4j browser port works just fine. However, obviously I would prefer to be able to launch neo4j with systemctl.
Right now the only hint of error I can find in debug.log is the following:
2019-06-19 21:19:55.508+0000 INFO [o.n.i.d.DiagnosticsManager] Storage summary:
2019-06-19 21:19:55.508+0000 INFO [o.n.i.d.DiagnosticsManager] Total size of store: 3.07 GB
2019-06-19 21:19:55.509+0000 INFO [o.n.i.d.DiagnosticsManager] Total size of mapped files: 3.07 GB
2019-06-19 21:19:55.509+0000 INFO [o.n.i.d.DiagnosticsManager] --- STARTED diagnostics for KernelDiagnostics:StoreFiles
END ---
2019-06-19 21:19:55.509+0000 INFO [o.n.k.a.DatabaseAvailabilityGuard] Fulfilling of requirement 'Database available' mak
es database available.
2019-06-19 21:19:55.509+0000 INFO [o.n.k.a.DatabaseAvailabilityGuard] Database is ready.
2019-06-19 21:19:55.568+0000 INFO [o.n.k.i.DatabaseHealth] Database health set to OK
2019-06-19 21:19:56.198+0000 WARN [o.n.k.i.p.Procedures] Failed to load `apoc.util.s3.S3URLConnection` from plugin jar `
/var/lib/neo4j/plugins/apoc-3.5.0.4-all.jar`: com/amazonaws/ClientConfiguration
2019-06-19 21:19:56.199+0000 WARN [o.n.k.i.p.Procedures] Failed to load `apoc.util.s3.S3Aws` from plugin jar `/var/lib/n
eo4j/plugins/apoc-3.5.0.4-all.jar`: com/amazonaws/auth/AWSCredentials
2019-06-19 21:19:56.200+0000 WARN [o.n.k.i.p.Procedures] Failed to load `apoc.util.s3.S3Aws$1` from plugin jar `/var/lib
/neo4j/plugins/apoc-3.5.0.4-all.jar`: com/amazonaws/services/s3/model/S3ObjectInputStream
2019-06-19 21:19:56.207+0000 WARN [o.n.k.i.p.Procedures] Failed to load `apoc.util.hdfs.HDFSUtils$1` from plugin jar `/v
ar/lib/neo4j/plugins/apoc-3.5.0.4-all.jar`: org/apache/hadoop/fs/FSDataInputStream
2019-06-19 21:19:56.208+0000 WARN [o.n.k.i.p.Procedures] Failed to load `apoc.util.hdfs.HDFSUtils` from plugin jar `/var
/lib/neo4j/plugins/apoc-3.5.0.4-all.jar`: org/apache/hadoop/fs/FSDataOutputStream
...
...
...
2019-06-19 21:20:00.678+0000 INFO [o.n.g.f.GraphDatabaseFacadeFactory] Shutting down database.
2019-06-19 21:20:00.679+0000 INFO [o.n.g.f.GraphDatabaseFacadeFactory] Shutdown started
2019-06-19 21:20:00.679+0000 INFO [o.n.k.a.DatabaseAvailabilityGuard] Database is unavailable.
2019-06-19 21:20:00.684+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Database shutdown" # txId: 1
checkpoint started...
2019-06-19 21:20:00.704+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by "Database shutdown" # txId: 1
checkpoint completed in 20ms
2019-06-19 21:20:00.705+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in vers
ion 0
2019-06-19 21:20:00.725+0000 INFO [o.n.i.d.DiagnosticsManager] --- STOPPING diagnostics START ---
2019-06-19 21:20:00.725+0000 INFO [o.n.i.d.DiagnosticsManager] --- STOPPING diagnostics END ---
2019-06-19 21:20:00.725+0000 INFO [o.n.g.f.GraphDatabaseFacadeFactory] Shutdown started
2019-06-19 21:20:05.875+0000 INFO [o.n.g.f.m.e.CommunityEditionModule] No locking implementation specified, defaulting
to 'community'
2019-06-19 21:20:06.080+0000 INFO [o.n.g.f.GraphDatabaseFacadeFactory] Creating database.
2019-06-19 21:20:06.154+0000 INFO [o.n.k.a.DatabaseAvailabilityGuard] Requirement `Database available` makes database unavailable.
2019-06-19 21:20:06.156+0000 INFO [o.n.k.a.DatabaseAvailabilityGuard] Database is unavailable.
2019-06-19 21:20:06.183+0000 INFO [o.n.i.d.DiagnosticsManager] --- INITIALIZED diagnostics START ---
I think the warning isn't an issue, since it's just a warning and not an error or exception. Also it seems that the database just shuts down automatically, and then restarts, creating an infinite loop. This loop does not happen when I call neo4j console (all the warnings still exist in the logs). All my ports are default.
Any clue why this is happening? I've never encountered this error when I previously launched neo4j on this instance.
If it works with neo4j console but not with systemctl, you should check the rights of the Neo4j folder.
I'm pretty sure you have a problem on it, and that the systemctl doesn't run Neo4j with the same user as you
I know this question has been asked here: GraphAware Neo4j UUID not working. Nobody has answered it and I cant comment to ask that guy because I dont have enough reputation. I have all both the server framework and the uuid jar files in plugins folder and this is my config:
com.graphaware.runtime.enabled=true
com.graphaware.module.UIDM.1=com.graphaware.module.uuid.UuidBootstrapper
com.graphaware.module.UIDM.uuidProperty=uuid
For some reason when I create a node. I'm not getting anything.
This is my log output:
2017-01-13 17:59:47.762+0000 INFO Neo4j Server shutdown initiated by request
2017-01-13 17:59:47.789+0000 INFO [c.g.s.f.b.GraphAwareServerBootstrapper] stopped
2017-01-13 17:59:47.789+0000 INFO Stopping...
2017-01-13 17:59:47.835+0000 INFO Shutting down GraphAware Runtime...
2017-01-13 17:59:47.836+0000 INFO Shutting down module UIDM
2017-01-13 17:59:47.836+0000 INFO Terminating task scheduler...
2017-01-13 17:59:47.836+0000 INFO Task scheduler terminated successfully.
2017-01-13 17:59:47.836+0000 INFO GraphAware Runtime shut down.
2017-01-13 17:59:47.846+0000 INFO Stopped.
2017-01-13 17:59:49.770+0000 INFO Starting...
2017-01-13 17:59:55.480+0000 INFO Bolt enabled on localhost:7687.
2017-01-13 18:00:03.164+0000 INFO [c.g.r.b.RuntimeKernelExtension] GraphAware Runtime enabled, bootstrapping...
2017-01-13 18:00:03.177+0000 INFO Running in a single-node architecture (Neo4j Community)
2017-01-13 18:00:03.186+0000 INFO [c.g.r.b.RuntimeKernelExtension] Bootstrapping module with order 1, ID UIDM, using com.graphaware.module.uuid.UuidBootstrapper
2017-01-13 18:00:03.275+0000 INFO uuidProperty set to uuid
2017-01-13 18:00:03.285+0000 INFO Registering module UIDM with GraphAware Runtime.
2017-01-13 18:00:03.286+0000 INFO [c.g.r.b.RuntimeKernelExtension] GraphAware Runtime bootstrapped, starting the Runtime...
2017-01-13 18:00:07.046+0000 INFO Starting GraphAware...
2017-01-13 18:00:07.047+0000 INFO Loading module metadata...
2017-01-13 18:00:07.047+0000 INFO Loading metadata for module UIDM
2017-01-13 18:00:07.098+0000 INFO Module UIDM seems to have been registered before, metadata loaded successfully.
2017-01-13 18:00:07.098+0000 INFO Module UIDM seems to have changed configuration since last run, will try to re-initialize...
2017-01-13 18:00:07.099+0000 INFO InitializeUntil set to 9223372036854775807 and it is 1484330407098. Will re-initialize.
2017-01-13 18:00:08.797+0000 INFO Started.
2017-01-13 18:00:09.044+0000 INFO [c.g.s.f.b.GraphAwareServerBootstrapper] started
2017-01-13 18:00:09.045+0000 INFO Mounted unmanaged extension [com.graphaware.server] at [/graphaware]
2017-01-13 18:00:14.228+0000 INFO Module metadata loaded.
2017-01-13 18:00:14.228+0000 INFO Starting transaction-driven modules...
2017-01-13 18:00:14.229+0000 INFO Transaction-driven modules started.
2017-01-13 18:00:14.230+0000 INFO There are no timer-driven runtime modules. Not scheduling any tasks.
2017-01-13 18:00:14.230+0000 INFO GraphAware started.
2017-01-13 18:00:14.230+0000 INFO [c.g.r.b.RuntimeKernelExtension] GraphAware Runtime automatically started.
2017-01-13 18:00:14.268+0000 INFO Mounting GraphAware Framework at /graphaware
2017-01-13 18:00:14.283+0000 INFO Will try to scan the following packages: {com.**.graphaware.**,org.**.graphaware.**,net.**.graphaware.**}
2017-01-13 18:00:15.944+0000 INFO Remote interface available at http://localhost:7474/
So I upgraded my Neo4j cluster instalation to 3.0.3 and it seems I can not load the database that comes with the instalation. This is the log file
<code>2016-06-28 14:11:20.879+0000 INFO Starting...
2016-06-28 14:11:21.620+0000 INFO Write transactions to database disabled
2016-06-28 14:11:22.483+0000 INFO Bolt enabled on localhost:7687.
2016-06-28 14:11:22.504+0000 INFO Initiating metrics...
2016-06-28 14:11:24.344+0000 INFO Attempting to join cluster of [192.168.1.91:5001, 192.168.1.92:5001, 192.168.1.93:5001]
2016-06-28 14:11:54.762+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingData$
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#1f7853af' wa$
at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:68)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:217)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:87)
at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:66)
at org.neo4j.server.enterprise.EnterpriseEntryPoint.main(EnterpriseEntryPoint.java:32)
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.server.database.LifecycleManagingDatabase#1f7853af' was succ$
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:189)
... 3 more
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.ha.factory.HighlyAvailableFacadeFactory, /opt/neo4j/neo4j-enterprise$
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:144)
at org.neo4j.kernel.ha.factory.HighlyAvailableFacadeFactory.newFacade(HighlyAvailableFacadeFactory.java:42)
at org.neo4j.kernel.ha.HighlyAvailableGraphDatabase.<init>(HighlyAvailableGraphDatabase.java:41)
at org.neo4j.server.enterprise.EnterpriseNeoServer.lambda$static$0(EnterpriseNeoServer.java:80)
at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:89)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
... 5 more
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.cluster.client.ClusterJoin#4b6942a0' was successfully initia$
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:140)
... 10 more
Caused by: java.util.concurrent.TimeoutException
at org.neo4j.cluster.statemachine.StateMachineProxyFactory$ResponseFuture.get(StateMachineProxyFactory.java:300)
</code>
Is there any fresh db I could try to load ? Thanks.
Is that on a single instance or cluster?
Best try it in standalone mode first.
How did you upgrade? Using the admin-tool with
neo4j-admin --mode database --from neo4j-2x-db --to neo4j-3x-db ?
see: https://neo4j.com/guides/upgrade/#neo4j-3-0
and: http://neo4j.com/docs/operations-manual/3.0/#upgrade-instructions-2x
I'm making an expensive call to my Heroku Rails server. After 13-15 seconds the console in my browser reports a Service Unavailable 503 error. However when I check my heroku logs, it reports:
Completed 200 OK in 45592ms (Views: 220.3ms | ActiveRecord: 33457.5ms)
Other times the heroku logs report a memory exceeded quota. Here is an example of that below.
2015-06-11T15:17:20.238285+00:00 app[web.1]: Completed 200 OK in 81881ms (Views: 201.6ms | ActiveRecord: 18021.2ms)
2015-06-11T15:17:33.482930+00:00 heroku[web.1]: Process running mem=841M(164.4%)
2015-06-11T15:17:33.482930+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2015-06-11T15:17:53.147570+00:00 heroku[web.1]: Process running mem=841M(164.4%)
2015-06-11T15:17:53.147679+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2015-06-11T15:17:59.751540+00:00 app[web.1]: E, [2015-06-11T15:17:59.695813 #3] ERROR -- : worker=2 PID:13 timeout (121s > 120s), killing
2015-06-11T15:17:59.916750+00:00 app[web.1]: E, [2015-06-11T15:17:59.906435 #3] ERROR -- : reaped #<Process::Status: pid 13 SIGKILL (signal 9)> worker=2
2015-06-11T15:18:02.487428+00:00 app[web.1]: I, [2015-06-11T15:18:02.427293 #16] INFO -- : worker=2 ready
Why is it reporting a Completed 200 when the console is reporting a 503?
there are 2 different things here:
your app
the heroku load balancer
In this case the load balancer see that the request is taking too long and sends you the 503. In the back the service processes the request and returns completes with a 200.
See:
https://devcenter.heroku.com/articles/limits
https://devcenter.heroku.com/articles/request-timeout
Heroku does not gives us much information for error-code = H10. Simple put, something is going wrong with your application code / configuration. To see what's going wrong, run heroku run rails console and you will be able to see error details which will be help you in resolving the error. No need to use logs. heroku run rails console is a big help
This happened with me when I used Node. I put a timeout for 30 seconds and I used to get HTTP:503. I then came to know that it's the timeout that caused the issue. I changed the timeout to <30 seconds and it is working fine. Maybe it's because of the loadbalancer that Heroku uses.
Thanks.