Ejabberd systemctl startup works unreliably. 2 behaviours noticed: 1. systemctl [action] ejabberd.service doesn't work 2. systemctl doesn't see ejabberd.service afterinstallation To reproduce #1: 1. Install ejabberd 2. Break config file 3. issue systemctl start ejabberd.service Expected result: ejabberd doesn't start. Actual result: systemctl status ejabberd.service reports running --OR-- 1. Install ejabberd 2. Modify config file 3. Start ejabberd Expected result:ejabberd starts as ejabberd user. Actual result: ejabberd sometimes starts as root user, most often doesn't start To reproduce #2: 1. Install ejabberd 2. Uninstall ejabberd 3. Install ejabberd 4. issue systemctl start ejabberd.service Expected result: ejabberd starts. Actual result: systemctl complains about a missing file.
Assignee: bugsquad => mityaSource RPM: (none) => ejabberd
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD