What can i do that Jira starts automaticly after Reboot on Ubuntu

[Ralf Thmas]

Hello,

i did this :

Run Jira as a systemd service on linux | Jira | Atlassian Documentation

But after Reboot Jira is not starting ! 

What can i do ?

Greets

Ralf

[Ralf Thmas]

Hello,

i installed this on an new Ubunt 20.04 Longtime Release

Greets

Ralf

[Nic Brough -Adaptavist-]

Ok, you must have installed something that still uses SystemV.

[Nic Brough -Adaptavist-]

Your Ubuntu install is partially dependent on the sysV method of startup, and hence needs matching entries for that to match the systemd ones (Are you on an older version of Ubuntu?  Asking because more recent ones don't do sysV or have automated the synchronisation)

To fix it, create a new sysv file for jira - /etc/systemd/system/jira , with content:

### BEGIN INIT INFO
# Provides:          jira
# Required-Start:    $all
# Required-Stop:
# Default-Start:     3 4 5
# Default-Stop:
# Short-Description: Jira systemd config 
### END INIT INFO

[Ralf Thmas]

i just call this file "jira" ?? Or is this with an special extension ?

Or what is sysv ?

[Nic Brough -Adaptavist-]

Yes, it's just jira, like I said.  

SysV is shorthand for SystemV, one of the startup frameworks that Linux systems use.

[Ralf Thmas]

yes end the File end with*.sysv ?

[Nic Brough -Adaptavist-]

No, that's not what I said.

[Ralf Thmas]

ok i create in that an file with no ending

[Ralf Thmas]

Hello,

i created that file jira.system but it is not working

Greets

Ralf

[Ralf Thmas]

in etc/init.d we have already an jira file i see. With that content

[Ralf Thmas]

i renamed /etc/systemd/system/jira.service to jira . It is also not working

[Nic Brough -Adaptavist-]

You need to stop jumping around between your two startup systems and second-guessing what all of these files might be.

etc/init.d is one way of handling services, systemd is another.  They work differently, but because you've got both active in your system, they need to be a little bit aligned.

Forget the init files for now.  Have you worked through the doc you originally posted?  What did you do differently to that?  Ignoring the reboot part, what does "systemctl start jira" do when you've set up your services the way the doc says to?

[Ralf Thmas]

Hello,

i make same file like in description. If i do systemctl start jira i get this

-- The unit UNIT has successfully entered the 'dead' state.
Oct 18 17:20:15 epr-sand-jira audit[972]: AVC apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" name="/proc/>Oct 18 17:20:15 epr-sand-jira kernel: audit: type=1400 audit(1634570415.279:206): apparmor="ALLOWED" operation="open" p>Oct 18 17:20:18 epr-sand-jira multipathd[590]: sda: add missing path
Oct 18 17:20:18 epr-sand-jira multipathd[590]: sda: failed to get udev uid: Invalid argument
Oct 18 17:20:18 epr-sand-jira multipathd[590]: sda: failed to get sysfs uid: Invalid argument
Oct 18 17:20:18 epr-sand-jira multipathd[590]: sda: failed to get sgio uid: No such file or directory
lines 2702-2749/2749 (END)
Oct 18 17:20:14 epr-sand-jira systemd-logind[1086]: New session 3 of user root.
-- Subject: A new session 3 has been created for user root
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat

Greets

Ralf