Anonymous | Login | 2024-11-21 01:52 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0006211 | ClearCenter | app-zarafa - Zarafa | public | 2015-11-13 10:12 | 2017-04-11 12:35 | ||||
Reporter | bchambers | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | major | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 7.1.0 | ||||||||
Target Version | 7.3.0 Updates | Fixed in Version | 7.3.0 Updates | ||||||
Summary | 0006211: Zarafa does not start on boot | ||||||||
Description | The upstream Zarafa RPMs still use the old SysV startup scripts. The boot ordering is not guaranteed and that's problematic. If the Zarafa server starts up before the MariaDB/MySQL database, the startup will fail. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |||||||
|
Notes | |
(0002291) bchambers (administrator) 2015-11-23 10:28 |
Contacted Zarafa's devel team...they are working on systemd support and will provides package updates when available. |
Issue History | |||
Date Modified | Username | Field | Change |
2015-11-13 10:12 | bchambers | New Issue | |
2015-11-22 20:45 | user2 | Target Version | 7.1.0 Updates => 7.2.0 Updates |
2015-11-23 10:28 | bchambers | Note Added: 0002291 | |
2015-12-29 09:46 | user2 | Status | new => confirmed |
2015-12-29 09:48 | user2 | Description Updated | View Revisions |
2015-12-29 09:52 | user2 | Relationship added | related to 0006771 |
2017-01-16 17:46 | user2 | Target Version | 7.2.0 Updates => 7.3.0 Updates |
2017-04-11 12:35 | user2 | Status | confirmed => resolved |
2017-04-11 12:35 | user2 | Fixed in Version | => 7.3.0 Updates |
2017-04-11 12:35 | user2 | Resolution | open => fixed |
2017-04-11 12:35 | user2 | Assigned To | => user2 |
2017-04-11 12:35 | user2 | Status | resolved => closed |