ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000725ClearOSapp-zarafa - Zarafa Enginepublic2012-08-27 20:582012-09-10 21:19
Reporterbchambers 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.3.0 
Target Version6.3.0 UpdatesFixed in Version6.3.0 Updates 
Summary0000725: Zarafa Server daemon doesn't start - user login sees "Unable to connect to Zarafa server"
DescriptionIt 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.


Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0000732closed dsokoloski Daemon class and widget should provide "dead but pid file exists" status 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-08-27 20:58bchambersNew Issue
2012-08-27 20:58bchambersStatusnew => assigned
2012-08-27 20:58bchambersAssigned To => bchambers
2012-08-27 21:11bchambersAssigned Tobchambers => user2
2012-08-27 21:11bchambersSeveritymajor => minor
2012-08-28 03:48user2Note Added: 0000553
2012-08-28 10:30bchambersNote Added: 0000554
2012-08-29 09:45user2Relationship addedrelated to 0000732
2012-08-29 10:35timb80Note Added: 0000555
2012-08-29 11:27user2Statusassigned => resolved
2012-08-29 11:27user2Fixed in Version => 6.3.0 Updates
2012-08-29 11:27user2Resolutionopen => fixed
2012-09-10 21:19user2Statusresolved => closed

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   
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   
2012-08-29 10:35   
Confirmed here - services are shown as running if pid file exists, but service is dead.