I am using Debian 9 as my OS.
root@mail:~# systemctl enable jira.service
jira.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable jira
insserv: warning: script 'K01jira' missing LSB tags and overrides
insserv: warning: script 'jira' missing LSB tags and overrides
update-rc.d: error: jira Default-Start contains no runlevels, aborting.
Would you please help me to fix this problem?
Hey Alexander, welcome to the Community!
You've likely got SysV startup scripts for Jira on your box. As Debian 9 runs systemd, it generally doesn't like the SysV/init.d startup scripts. Another Community user has written systemd startup scripts that should work for your case. Have a peek at that thread which contains the script as well as setup directions.
Thank you for a very fast response. I accept your welcome to this wonderful community. But i don’t understand one small thing in your answer. As i have said in my question command systemctl enable jira.service fails to perform correctly but at the same time those two commands do work correctly:
1. service jira start
2. service jira stop
Here comes this small thing which i don’t understand in your answer:
If i decide to take the SysV script from the link you have kindly provided me with then i have to delete some regular non SysV script that is now serving start and stop commands for jira? Would you please be so kind as to explain to me this little point in more details? Thanks.
Sorry it was a little confusing! I can see where this got difficult to follow.
The Jira installer put a SysV startup script on your system. What Jira is starting with now is currently an init.d/SysV script. A few years ago before systemd became a thing, you would start and stop these scripts like this:
sudo /etc/init.d/jira start
You'd also use the chkconfig command to control which services were brought up when the system restarted.
Now that you're using systemd with the systemctl command, this is all different! systemd does try to start/stop the old init.d/SysV scripts and generally is successful. That's why you're able to stop and start your Jira install currently. But systemd isn't so good at enabling them to launch on system startup. That's the error you're seeing right now. Your relatively new Debian 9 install which uses systemd, isn't able to convert the older Jira init.d startup script into something that launches at system start.
So that's what replacing the old init.d script you have right now with the newer systemd compatible script I linked to will do. It will make sure that systemd on your Debian 9 box is able to launch the service at startup, even though it can more or less launch the service with the current start/stop commands.
The Jira installer was bundled with the init.d script because not all Linux installs are using systemd, but for the most part the systemd boxes can start/stop init.d scripts. In the future if systemd becomes the defacto standard, the startup script that comes with Jira might be replaced. But for now, it just takes a little extra work for people with systemd enabled boxes to make sure the scripts are compatible with systemd.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events