Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OrientDB failing to start on Ubuntu 16.04 with systemd #6511

Closed
1 of 5 tasks
austinsmorris opened this issue Aug 3, 2016 · 7 comments
Closed
1 of 5 tasks

OrientDB failing to start on Ubuntu 16.04 with systemd #6511

austinsmorris opened this issue Aug 3, 2016 · 7 comments
Assignees
Milestone

Comments

@austinsmorris
Copy link

OrientDB Version, operating system, or hardware.

  • I last tried this with 2.2.5 on Ubuntu 16.04 on an AWS EC2 t2.medium instance.

Operating System

  • Linux
  • MacOSX
  • Windows
  • Other Unix
  • Other, name?

Expected behavior and actual behavior

When starting orientdb, it should keep running.

Ubuntu 16.04 is the first LTS since Ubuntu switched from upstart to systemd. I followed the documentation to setup systemd, but it doesn't work well. When I start, orientdb startup up, but according to the logs, systemd or something immediately issues the stop command, so the service stops.

Steps to reproduce the problem

Follow the current orientdb documentation for running on ubuntu with systemd.

Additional details are available on my stack overflow question:
http://stackoverflow.com/questions/38644653/systemd-stops-orientdb-immediately-after-it-starts-on-ubuntu-16-04

I also asked on the mailing list:
https://groups.google.com/forum/#!topic/orient-database/OF1brvaY3uc

Let me know if you need any more information. I'm happy to help!

Thanks!

@tglman tglman self-assigned this Aug 4, 2016
@tglman
Copy link
Member

tglman commented Aug 4, 2016

hi @austinsmorris,

I think that the orientdb.sh script was thought for SystemV use and SystemD behave in a different way, i'll check what's going on and i'll try to understand why it block

@jack-y
Copy link

jack-y commented Aug 14, 2016

Hi,
I got the same issue with OpenSUSE Leap 42.1 and OrientDB 2.2.7.

@robfrank robfrank self-assigned this Aug 16, 2016
@robfrank
Copy link
Contributor

I'm investigating the problem.

robfrank added a commit that referenced this issue Aug 18, 2016
- new orientdb.service for systemd
- new script orientdb-sysd.sh to be used by systemd

refs #6511
@robfrank
Copy link
Contributor

Hi, I just pushed on develop branch an orientdb.service file and a new orientdb-sysd.sh script to be used by the service definition. I will update the doc. In the meanwhile you can take this files

@jack-y
Copy link

jack-y commented Aug 18, 2016

Thanks Roberto, these new files work for me (OpenSuse Leap 42.1 + OrientDB 2.2.7).

@robfrank
Copy link
Contributor

cool, we are still experimenting, maybe we will change something. It is my first time with systemd.

@robfrank robfrank modified the milestones: 2.2.x (next hotfix), 2.2.8 Aug 19, 2016
@ssenapat
Copy link

ssenapat commented Sep 5, 2018

I have installed the latest version of orientdb 3.06 on Centos 7 and facing the same issue with service.
Could you please help me out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants