I have a travis config with neo4j service enabled as described in the documentation:
services:
- neo4j
However neo4j service began failing to start when its starting command changed from
sudo service neo4j start
to
sudo systemctl start neo4j
and failed with the following message:
Failed to start neo4j.service: Unit neo4j.service not found.
Specifying dist: trusty
fixed the issue. But it should work on all environments, isn’t it?
For a better search of this topic, here’s the error i’ve been getting in the build logs:
neo4j.exceptions.ServiceUnavailable: Failed to establish connection to ('127.0.0.1', 7687) (reason 111)
I’m facing similar issues with Xenial, Bionic. But it works with Trusty.
I hope Travis fix it soon.
On Xenial:
# Services
Failed to start neo4j.service: Unit neo4j.service not found.
On Bionic:
# Services
Failed to start neo4j.service: Unit neo4j.service not found.
On Trusty:
Active database: graph.db
Directories in use:
home: /usr/local/neo4j-3.2.7
config: /usr/local/neo4j-3.2.7/conf
logs: /usr/local/neo4j-3.2.7/logs
plugins: /usr/local/neo4j-3.2.7/plugins
import: /usr/local/neo4j-3.2.7/import
data: /usr/local/neo4j-3.2.7/data
certificates: /usr/local/neo4j-3.2.7/certificates
run: /usr/local/neo4j-3.2.7/run
Starting Neo4j.
WARNING: Max 30000 open files allowed, minimum of 40000 recommended. See the Neo4j manual.
Started neo4j (pid 4021). It is available at http://localhost:7474/
There may be a short delay until the server is ready.
See /usr/local/neo4j-3.2.7/logs/neo4j.log for current status.
Please link to an affected build, and the last successful build if applicable. Otherwise, there’s insufficient information for diagnostics.
I can confirm this issue exists and hasn’t been resolved.
See https://travis-ci.org/JDRomano2/comptox_ai/builds/656455702#L162
(disregard the rough state of the rest of the build)
I can’t test on Trusty due to lack of a Python 3.7 archive.