ClearFoundation

Okay, I'm having a bad week. I had a hard drive die in my old clearOS rig so I decided to upgrade to 6.2, it wasn't working right in a VM (never completed installation), and now it's giving me all sorts of heck. Every time I click in to groups, users, or account manager it flashes the dialog to pick between OpenLDAP and the Active Directory thing before going to a blank page. I've attached a screenshot.

I told it to use the openLDAP user manager so I could get my Flexshares set up and crack in to my backups and see if I have my hard drives backed up recently, I have tons of what look like warning icons, and no "Users" menu.

What did I mess up and how can I go about fixing it?

Edit: File didn't attach. Fixed that.

Hi, the warning icons represent new menu shortcuts that have just been installed. They will go with time...

Is 'app-users' installed?

Regarding the account manager issue...
Is openldap installed? 'rpm -q openldap'
Is the service running? 'service slapd restart'

RPM command returned that it was install, "yum install app-users" returned that it was the latest version and up to date. So I restarted it, failed to stop it, succeeded in restarting it.

I got excited and replied to this post at this point. Then went to check the web interface. The problem has not changed. My memory of Windows 95 says to uninstall/reinstall it. How would I go about doing this or what else should I do? I've been down for about a week and home users are starting to get on to me. . .

Now I went to the marketplace to see if I could uninstall the user manager via that. Big mistake. I got an error that another user was accessing it, refreshed, "Connection failed: couldn't connect to host".

I'm reformatting to the 32 bit version because this is portentious of very bad things in the future. However, should I switch to the active directory thing instead of OpenLDAP? Issues with OpenLDAP have required I reformat in the past.

Edit: Decided to try "yum remove app-users" first and go through that...are the repositories down or is it just me?

Edit 2: Okay...got it all back installed, repositories working, am back at the same place. Also noted that when I click "Directory Server" it says "Generating configuration" and has for the past 30 minutes. Am going to assume it's not generating the configuration, reboot, give it one more shot, then format with the 32 bit version.

With the problem my step-by-step was the following:
1. Install 64 bit edition of ClearOS
2. Install many apps when prompted to.
3. Meander around the menus and eventually click on users, select OpenLDAP

This resulted in the users, groups, user manager, and directory server being inaccessible.

I fixed this problem by doing the following.
1. Installing the 32 bit edition of ClearOS
2. Installing no applications when prompted to.
3. Going directly to the Users menu and selecting OpenLDAP.

I'll continue by installing related applications in small batches and will update this thread if I have further issues with user management!

Same problem here on 64-bit version. Any solutions?

Same happened to me.
I installed one 64bit server and it worked, did not write down the steps.

Then installed another 64bit 6.2 in gateway mode - went to market place and only added users and groups and directory serivce - added the base domain and get a spinning wheel in the Directory Status screen stating Generating configuration...

The reason i had to go with 64bit was due to trick hardware and the older 5.2 32 bit which could not see the onboard dual ethernet cards.

I even just for fun tried to get the Zarafa installed and that too is quirky - perhaps 6.3 will smooth it out?

PS: Tim re the app users groups etc

# yum list installed | grep users
app-users.noarch 1:1.1.1-1.v6 @clearos-updates
app-users-core.noarch 1:1.1.1-1.v6 @clearos-updates
l7-filter-userspace.x86_64 0.13-1.v6 @clearos

# yum list installed | grep group
app-groups.noarch 1:1.1.0-1.v6 @clearos
app-groups-core.noarch 1:1.1.0-1.v6 @clearos
mod_authz_unixgroup.x86_64 1.0.3-1.v6 @clearos

# yum list installed | grep ldap
app-ldap-core.noarch 1:1.1.0-1.v6 @clearos
app-openldap-core.noarch 1:1.1.1-1.v6 @clearos
app-openldap-directory.noarch 1:1.1.1-1.v6 @clearos-updates
app-openldap-directory-core.noarch 1:1.1.1-1.v6 @clearos-updates
apr-util-ldap.x86_64 1.3.9-3.el6_0.1 @anaconda-ClearOSCommunity-201204201335.x86_64/6.2
nss-pam-ldapd.x86_64 0.7.5-14.el6_2.1 @anaconda-ClearOSCommunity-201204201335.x86_64/6.2
openldap.x86_64 2.4.23-26.el6 @clearos-core
openldap-clients.x86_64 2.4.23-26.el6 @clearos-core
openldap-servers.x86_64 2.4.23-26.el6 @clearos-core
pam_ldap.x86_64 185-11.el6 @anaconda-ClearOSCommunity-201204201335.x86_64/6.2
webconfig-php-ldap.x86_64 5.3.3-3.v6.6 @anaconda-ClearOSCommunity-201204201335.x86_64/6.2

I think the problem I'm having is related. (ClearOS Pro, 64-bit, recent fresh first-time install, updated)

I don't recall if the initial configuration hung up, but I did have a problem trying to create groups and accounts. That was over a month ago, and gateway functions were ok, so I didn't pursue.

Now however I would like to run openvpn server. All related apps (certificates manager, groups, users) are inactive; message is "Before configuring user and group accounts" I have to set up Account Synchronization. I thought I had specified that during the boot install. Setting in the web ui fails (trying to set Standalone, other modes fail the same way) with the message

str2entry: invalid value for attributeType objectClass #0 (syntax 1.3.6.1.4.1.1466.115.121.1.38)

which seems to be related to openldap, which is installed and up to date per yum update openldap.

I'm tempted to do a fresh install, but I don't know how much time it will take to get the gateway working again.

Can I buy a clue? Just kidding, I already made the mistake of opening a ticket, the support group replied with an irrelevant suggestion and cited $250 per incident cost. Now I have no idea why I bought Pro

Hi Keith,

I saw your ticket today and was going to suggest you come to the forums where we can help sort out what appears to be an isolate bug...by that I mean, I can't reproduce it, so it is something specific to your configuration.

PM me or attach to your support ticket that you opened the file created in /tmp/ when you run:


We'll take a look and see if we can reproduce the error you're seeing...from your error message, something in your organization data is breaking LDAP (best guess at this point by a non-LDAP expert).

Oh..and as for:
I already made the mistake of opening a ticket, the support group replied with an irrelevant suggestion and cited $250 per incident cost. Now I have no idea why I bought Pro

Hmm...don't you think that's a bit disingenuous? The ClearCenter store clearly makes the distinction that the LITE provides support on a per-incident basis. I get your point about this potentially being a bug, and we're absolutely interested in solving it, but to have a solid business model we must put support resources first to customers who have paid for it. I get that no-one wants to pay $250 for an incident...especially if it's a bug. However, the LITE subscription's 'reason for being' is for those who wanted access to the Professional Edition's premium business apps, but specifically didn't want to lean on ClearCenter for support (eg. they have internal Linux gurus, hobbiest etc.).

Anyways, just wanted to set the record straight and make sure you had all the information. We're here to help on the forums, but there's just no way we can provide support at $80 price point. Feel free to send me an email if you want to talk refund...we're not a giant corporate bundle of evil....yet. Moohhaahaaahaa.

Ben

I've seen the LDAP objectClass error noted a few times on another post here... Pete noted he was monitoring the issue
www.clearfoundation.com/component/option...it,10/limitstart,10/