| Anonymous | Login | 2024-04-25 07:35 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 | ||||
| 0000725 | ClearOS | app-zarafa - Zarafa Engine | public | 2012-08-27 20:58 | 2012-09-10 21:19 | ||||
| Reporter | bchambers | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 6.3.0 | ||||||||
| Target Version | 6.3.0 Updates | Fixed in Version | 6.3.0 Updates | ||||||
| Summary | 0000725: Zarafa Server daemon doesn't start - user login sees "Unable to connect to Zarafa server" | ||||||||
| Description | It is possible to get into a scenario where the zarafa server does not start....log file contains: Mon Aug 27 22:17:29 2012: Config error: Config file '/etc/zarafa/ldap.cfg' does not exist. Mon Aug 27 22:17:29 2012: Config error: option 'ldap_group_type_attribute_value' cannot be empty! Mon Aug 27 22:17:29 2012: Config error: option 'ldap_user_type_attribute_value' cannot be empty! Mon Aug 27 22:17:29 2012: Cannot instantiate user plugin: Not a valid configuration file. This would occur if someone installs Zarafa before selecting the directory manager (OpenLDAP or Windows AD). Because Zarafa Server is not a listed daemon (why?) on the Zarafa summary, an admin would be unaware that one of the Zarafa daemons is not running. After initializing OpenLDAP, running: [root@system zarafa]# /etc/rc.d/init.d/zarafa-server restart Stopping zarafa-server: [FAILED] Starting zarafa-server: [ OK ] Starts the service...and user can login. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0000553) user2 2012-08-28 03:48 |
Adding the standard "Select your directory" widget will resolve the issue. Will do. zarafa-server is called "Zarafa Storage Server" in the UI. There are references to both "Zarafa Server" and "Zarafa Storage Server" in various places, but the Zarafa manual uses "Zarafa Server". Dropping "Storage" seems like the better way forward. |
|
(0000554) bchambers (administrator) 2012-08-28 10:30 |
Hmmm...maybe the status of the running 'storage/server' daemon is broken, because the Zarafa webconfig dashboard showed all 'green' running icons...but dropping to shell and running: [root@system zarafa]# /etc/rc.d/init.d/zarafa-server restart Stopping zarafa-server: [FAILED] Starting zarafa-server: [ OK ] Showed that it was not started...will test more and confirm. |
|
(0000555) timb80 (developer) 2012-08-29 10:35 |
Confirmed here - services are shown as running if pid file exists, but service is dead. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-08-27 20:58 | bchambers | New Issue | |
| 2012-08-27 20:58 | bchambers | Status | new => assigned |
| 2012-08-27 20:58 | bchambers | Assigned To | => bchambers |
| 2012-08-27 21:11 | bchambers | Assigned To | bchambers => user2 |
| 2012-08-27 21:11 | bchambers | Severity | major => minor |
| 2012-08-28 03:48 | user2 | Note Added: 0000553 | |
| 2012-08-28 10:30 | bchambers | Note Added: 0000554 | |
| 2012-08-29 09:45 | user2 | Relationship added | related to 0000732 |
| 2012-08-29 10:35 | timb80 | Note Added: 0000555 | |
| 2012-08-29 11:27 | user2 | Status | assigned => resolved |
| 2012-08-29 11:27 | user2 | Fixed in Version | => 6.3.0 Updates |
| 2012-08-29 11:27 | user2 | Resolution | open => fixed |
| 2012-09-10 21:19 | user2 | Status | resolved => closed |
|
Issue History |