Upgraded to 4.0.4, using the web browser interface.
When running ":sysinfo" query, I get an almost empty response. This is different from what I would have gotten back on v3.5.0.
I get the same type of issue when running commands from this blog post: How to generate sysinfo output from Cypher - Knowledge Base (v3.5 would output the same type of data, v4.0.4 comes back empty).
Is this a feature change in 4.0.4, or something that was moved out of the Community Edition, or is it just me?
webtic
(Paul Jongsma)
May 13, 2020, 10:08pm
#2
This is a sysinfo on a almost empty 4.0.3
The fact what no numbers are displayed make me think something is not ok on your end..
Thanks for confirming it could work Paul. I took a step back, tried to run from the base docker image, with the instructions , and still get the same issue (tried 4.0.4 and latest tags). Could it be something off with the Docker image?
docker run
--name testneo4j
-p7474:7474 -p7687:7687
-d
-v $HOME/neo4j/data:/data
-v $HOME/neo4j/logs:/logs
-v $HOME/neo4j/import:/var/lib/neo4j/import
-v $HOME/neo4j/plugins:/plugins
--env NEO4J_AUTH=neo4j/test
neo4j:latest
krid_mail
(Krid Mail)
August 14, 2020, 12:08pm
#4
Same issue with Community Version 4.1.0 on macOS Catalina. Database populated with > 30 million nodes and 300 million relations but not a single entry when querying :sysinfo
Does anybody found a solution for this?
Any help to fix this greatly appreciated
Krid
So I guess that :sysinfo is no longer supported on Community Edition per github issue:
opened 03:23PM - 15 May 20 UTC
closed 01:35PM - 06 Oct 20 UTC
To help us understand your issue, please specify important details, primarily:
…
- **Steps to reproduce**. *Not including reproduction steps will mean your bug will take considerably longer to investigate and fix. Please don't skip this*.
Start image: docker run --name testneo4j -p7474:7474 -p7687:7687 -d --env NEO4J_AUTH=neo4j/test neo4j:4.0.3
Open web browser to localhost:7474, login
Run ":sysinfo" command.
- Expected behaviour
Store Size is populated with a value, as are Id Allocation, Page Cache and Transactions lists.
- Actual behaviour
Item names are listed, but each item has a "-" for the value.
- Neo4j image tag being used, eg `neo4j:latest`, `neo4j:enterprise-3.5` etc
latest
4.0.4
4.0.3
- The output of the `docker version` command
PS U:\> docker version
Client: Docker Engine - Community
Version: 19.03.4
API version: 1.40
Go version: go1.12.10
Git commit: 9013bf5
Built: Thu Oct 17 23:44:48 2019
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.4
API version: 1.40 (minimum version 1.12)
Go version: go1.12.10
Git commit: 9013bf5
Built: Thu Oct 17 23:50:38 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683
- Operating system: (for example Windows 95/Ubuntu 16.04)
Windows 10 (also reproduced on MacOS 10.13.6)
Additionally, include (as appropriate) log-files, stacktraces, and other debug output.
Docker log (nothing out of the ordinary):
PS U:\> docker logs testneo4j
Changed password for user 'neo4j'.
Directories in use:
home: /var/lib/neo4j
config: /var/lib/neo4j/conf
logs: /logs
plugins: /var/lib/neo4j/plugins
import: /var/lib/neo4j/import
data: /var/lib/neo4j/data
certificates: /var/lib/neo4j/certificates
run: /var/lib/neo4j/run
Starting Neo4j.
2020-05-15 15:02:44.754+0000 INFO ======== Neo4j 4.0.3 ========
2020-05-15 15:02:44.763+0000 INFO Starting...
2020-05-15 15:02:49.560+0000 INFO Bolt enabled on 0.0.0.0:7687.
2020-05-15 15:02:49.561+0000 INFO Started.
2020-05-15 15:02:51.039+0000 INFO Remote interface available at http://0.0.0.0:7474/
2020-05-15 15:06:58.516+0000 WARN The client is unauthorized due to authentication failure.
PS U:\>
Also have tried running the query outlined here, get a blank result back:
https://neo4j.com/developer/kb/how-to-generate-sysinfo-output-from-cypher/?_ga=2.204988816.1280379950.1589317173-161711014.1573589649
I got the same issue in enterprise version 4.3.0, have you resolved this issue yet?
In your neo4j.config file, please double check that the following configuration option for allowing metrics exists and is enabled.
metrics.enabled=true