Service not present

Under certain circumstances it might happen that the main storage service is not present. In most cases this is due to the fact the the required JPA unit service could not be started up.

Also see issue #76.

There may be several causes for this and this page tried to help you sort it out.

Invalid database settings

So if the database settings configured are not working, then the JPA unit service gets configured but cannot be started up. Since main storage service does have a dependency on the JPA unit service, this service cannot be started either.

Check if the database settings are working and correct them if necessary.

Troubles after upgrade

So after some upgrades it seems that the OSGi Configuration Admin service is not able to apply the configuration to the JPA unit. Again this will cause the main storage service to fail as well.

The reason for this is still unknown and under investigation. However there is an easy for that.

It is required to start the server instance manually with the parameter -clean:

/etc/init.d/package-drone-server stop  # or whatever startup service you use
/usr/lib/package-drone-server/instance/server -clean
/etc/init.d/package-drone-server start  # or whatever startup service you use