Forums

Resolved
0 votes
I'm stuck. I wanted to install and configure FlexShares, but I got this error initially on the shares screen so I tried going to accounts>Users and encountered the same thing. I am also getting this error in accounts>Groups. I'm really sure as to why this is happening.

Here is a list of the installed modules:
Description Version Released Installed
Advanced firewall module 5.1-20 12/22/09 04/28/10
Backup and restore module 5.1-20 12/22/09 04/15/10
Bandwidth manager module 5.1-20 12/22/09 04/15/10
Caching nameserver module 5.1-20 12/22/09 04/15/10
Firewall - DMZ and 1-to-1 NAT module 5.1-20 12/22/09 04/28/10
Firewall - gateway module 5.1-20 12/22/09 04/15/10
Flexshare module 5.1-20 12/22/09 04/28/10
Mailer module 5.1-20 12/22/09 04/15/10
Multi-WAN module 5.1-20 12/22/09 04/15/10
Network tools module 5.1-20 12/22/09 04/15/10
Protocol filter module 5.1-20 12/22/09 04/15/10
RAID tools module 5.1-20 12/22/09 04/15/10
Remote backup service module 5.1-21 Manually upgraded 04/15/10
SSL certificates module 5.1-20 12/22/09 04/15/10
System statistics module 5.1-20 12/22/09 04/15/10
Web proxy access control module 5.1-20 12/22/09 04/28/10
Web proxy server module 5.1-20 12/22/09 04/28/10
Windows - file and network module 5.1-20 12/22/09 04/28/10

Additional info:
Kernel Version 2.6.18-164.11.1.v5 (SMP)

A little background info: this system is the same one that I had to install the Sangoma WANPipe drivers on that I mentioned in this thread: here

Some how something rendered my Graphical Console inoperative (X will no longer start). I can still configure the system by either using the web console or logging on to one of the consoles then doing an export DISPLAY (pointing it at another system that I have here) then running xconsole. However, both config methods still suffer this problem.
Tuesday, May 18 2010, 12:16 AM
Share this post:
Responses (1)
  • Accepted Answer

    Friday, July 13 2012, 07:26 PM - #Permalink
    Resolved
    0 votes
    This is old but unanswered. I just found it , so here we go:

    There are multiple reasons why this can happen but look for this one. In 5.2, if the password in /etc/kolab/kolab.conf does not match the one in /etc/openldap/slapd.conf then you can get this issue.

    grep SHA /etc/kolab/kolab.conf && grep SHA /etc/openldap/slapd.conf


    If they password hashes are NOT the same, replace the slapd value with the one from kolab.conf and restart ldap.
    The reply is currently minimized Show
Your Reply