| Anonymous | Login | 2024-04-25 00:51 MDT |
| 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 | ||||
| 0001220 | ClearOS | app-zarafa - Zarafa Engine | public | 2013-07-09 12:20 | 2013-07-24 09:43 | ||||
| Reporter | bchambers | ||||||||
| Assigned To | bchambers | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 6.4.0 | ||||||||
| Target Version | 6.4.0 Updates | Fixed in Version | 6.4.0 Updates | ||||||
| Summary | 0001220: Webaccess inaccessible if Apache web server is stopped | ||||||||
| Description | No way to tell on the Zarafa configuration page whether the Apache web server that powers ZCP WebAccess and/or WebApp is running. Clicking on the WebAccess link results in failure if Apache is stopped. Add HTTPD daemon to the list of services so admins can: a) visibly see that not all is 'green light' b) ability to start Apache (may not have app-web-server installed) | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-07-09 12:20 | bchambers | New Issue | |
| 2013-07-09 12:20 | bchambers | Status | new => assigned |
| 2013-07-09 12:20 | bchambers | Assigned To | => bchambers |
| 2013-07-11 07:32 | user2 | Status | assigned => resolved |
| 2013-07-11 07:32 | user2 | Fixed in Version | => 6.4.0 Updates |
| 2013-07-11 07:32 | user2 | Resolution | open => fixed |
| 2013-07-24 09:43 | user2 | Status | resolved => closed |
|
Issue History |