| Summary: | mythbackend does not start via systemd | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Patrick Hibbs <codebase7> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | Keywords: | PATCH, Triaged |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mythtv | CVE: | |
| Status comment: | |||
| Attachments: |
Fixed mythbackend.service.in
Replacement spec for other bugs mentioned in report. |
||
Created attachment 4261 [details] Fixed mythbackend.service.in This is the fixed mythbackend.service.in file. As a sidenote I did notice some other bugs against mythtv as well: https://bugs.mageia.org/show_bug.cgi?id=2449 https://bugs.mageia.org/show_bug.cgi?id=9135 I fixed the spec file for these, but I don't know if anyone would want the fixed spec. I could attach it or make a diff if anyone does. for the second one you could add it yep Keywords:
(none) =>
PATCH, Triaged Created attachment 4264 [details] Replacement spec for other bugs mentioned in report. Ok, then. The attached spec file actually contains fixes for both bugs mentioned above: https://bugs.mageia.org/show_bug.cgi?id=2449 https://bugs.mageia.org/show_bug.cgi?id=9135 This spec is not needed for the orginal intent of this bug report, as it can be fixed only with the service.in file replacement. Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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 =>
RESOLVED |
Description of problem: When mythbackend is started via systemd it can fail (i.e abort) if the mysql / mariadb connection info is different from the defaults. This is due to the rpm spec file running sed over the mythbackend.service.in file and not changing a variable as a result of a typo in the .in file. (The mythbackend.service.in file has an enviroment variable defined in it as @syscondir@ when it should be @sysconfdir@. sed would normally expand this into /etc (as %{_sysconfdir} expands to /etc.) but due to the typo it does not.) This causes mythbackend to look at an invalid path for it's configuration directory and as a result falls back to default settings. Which if you have changed the username / password / or database (and you should) for mysql / mariadb the connection will fail. I'll attach a sample fixed version of mythbackend.service.in below. Version-Release number of selected component (if applicable): mythtv-0.26.0-20130328.1.mga3 How reproducible: Install mythbackend and friends as normal. Change the connection settings for the mysql user. Try to start mythbackend via systemd. Reproducible: Steps to Reproduce: