Neo4j Standalone on Fedora 16

[Georg Summer]

Hi everyone,

I want to have neo4j standalone server running as a service on a Fedora 16 VM.
I can start the server without any problems from the cmdline (/bin/neo4j start)

The neo4j install obviously does not work because it uses update-rc.d
with is a Debian thing. So I replaced it with the Fedora equivalent:
chkconfig --add ${SERVICE_NAME}
The service gets installed and written into /etc/rc.d/init.d and
/etc/rc.d/rcX.d. (written into as in symbolic link to the neo4j
object)
using chkconfig I can see that the service is registered to be ON on
runlevel 3-5.
I can also start it from there (including through systemd: sudo
systemctl start neo4j-service.service)

When I reboot the machine though nothing happens. The server is not
started and there is nothing written into the
$NEO4J_HOME/data/log/*.log messages. Also nothing pops up in
/var/log/messages or /var/log/boot.log or dmesg.
After the reboot I can without any problems start the server again.

Am I missing something obvious here?

best regards,

Georg

[Julian Simpson]

Is it possible to see the console of the VM?  It's possible that errors in the init script will end up there of it fails to find a JVM, or become the 'neo4j' user at runtime.

We use that script for the Debian/Ubuntu packages, and it works fine ( obviously you need to replace the distro-specific stuff from it, which you've done).

We will be making changes to support RedHat-based distros in future.

J.

[Georg Summer]

I tried reproducing the error on a physical machine and got the following error:

Starting Neo4j Server...Error: Could not find or load main class 
org.neo4j.server.storemigration.PreStartupStoreUpgrader 

so I googled that and ended up here:

http://groups.google.com/group/neo4j/browse_thread/thread/bb5ec4fa58cc52a8

there it is mentioned that after moving the neo4j and friends to /opt helps.

Did that and it worked.

The previous location of the neo4j directory (just tar.gz extracted) was /media/Data/neo4j-community-1.6.1.

/media/Data was mounted to a disk image (own virtuell drive). The store is still at /medai/Data/graphdb/graph.db

Works like a charm now. Could it be that init.d scripts are restricted to certain directories?

Georg