Cannot create groups in new installation

[thecowster]

I have installed the evaluation copy of Scalix 11.2.0 on Fedora 7. (Actually I tried FC6 first, but then found it to be unsopported. Fedora 7 works, but the release notes suggest I should have used FC5. Hmmm..)

Everything works fine - I have been able to create users via the admin interface.

BUT when I try to create a group I get an error when I click "Finish":

Code: Select all

Could not set new members for the group

To exit the "Create New Group" window I then try to click "Finish" again but this time get the error:

Code: Select all

Could not create a group with a name that already exists

So in the end I just click "Cancel".

Then if I select a different tab, such as "Users", and then reselect the "Groups" tab, I then get the error message:

Code: Select all

Could not retrieve the list of users who can modify the list of members for this group

I'm guessing that something pretty fundamental is going wrong here - like the postgres database is down, or else the ldap server isn't running. Where are groups defined? In ldap?

I expect I need to take a look at the ldap logs - but couldn't find any. Can you give me a hint as to how the appropriate ldap log files are named?

Thanks for any tips!
[/b]

[thecowster]

Hmm.. maybe I'm doing things backwards.

Having installed Scalix I'm now being referred to documentation which tells me what system requirements the software has, prior to install. And I'm missing something (tk.i386)

Perhaps I have to re-run the installer now I have installed the tk package. If that doesn't fix it, maybe I'll have to start from scratch again with a new Fedora 7 install (but I hope not!)

[chris]

LDAP in Scalix is actually an interface to x.400 directories stored internally.

The groups are in those directories.

Can you confirm that no other LDAP is running on port 389, and that Scalix LDAP is started and running? The omstat command should show that.

Thanks,

Chris

[thecowster]

LDAP is installed and the daemon is running:

Code: Select all

[root@mailtest ~]# omstat -a
..
LDAP Daemon                   Started        12:41:17
..


I looked for other processes running on port 389 using "netstat -ap" but could not see any listening on that port:

Code: Select all

[root@mailtest ~]# netstat -ap | grep 389
unix  3      [ ]         STREAM     CONNECTED     12389  3334/gnome-screensa


I also tried to telnet into the machine on port 389, which appears to accept connections.

[thecowster]

The only service that is not running is "Item Structure Server". I wonder if this is relevant?

Code: Select all

[root@mailtest ~]# omstat -a
PC Monitor                    Started        NON-STOP       0
Directory Relay Server        Started        12:41:17
Notification Server           Started        12:41:17       0
Shared memory daemon          Started        NON-STOP
Notification Monitor          Started        NON-STOP
Session Monitor               Started        NON-STOP
Indexer                       Started        NON-STOP
Stats Daemon                  Started        NON-STOP
Container Access Monitor      Started        NON-STOP
Item Structure Server         Stopped
Database Monitor              Started        12:41:17
Licence Monitor Daemon        Started        NON-STOP
LDAP Daemon                   Started        12:41:17
Queue Manager                 Started        NON-STOP
Item Delete Daemon            Started        NON-STOP
IMAP Server Daemon            Started        12:41:17
SMTP Relay                    Started        12:41:17
Mime Browser Controller       Started        12:41:17
Event Server                  Started        12:41:17


Cheers

[chris]

ok, you can use lsof -i :389 to check for sure.

Did you use the graphical installer or text mode?

Do you see anything in omshowlog that might point to the problem?

Cheers,

Chris

[chris]

The only service that is not running is "Item Structure Server". I wonder if this is relevant?

That's no problem. Item Structure Server is only needed for single mailbox backup and restore, and the system will start and stop it as needed. It's stopped most of the time.

[thecowster]

lsof i :389 yields:

Code: Select all

COMMAND  PID USER   FD   TYPE DEVICE SIZE NODE NAME
omslapd 2345 root   14u  IPv4   7899       TCP *:ldap (LISTEN)
omslapd 2345 root   15u  IPv4  17729       TCP mailtest.is-uk.com:ldap->mailtest.is-uk.com:39777 (ESTABLISHED)
java    5142 root   52u  IPv4  17728       TCP mailtest.is-uk.com:39777->mailtest.is-uk.com:ldap (ESTABLISHED)


The only errors I see in the logs are those that correspond to me trying to re-create a group which I already tried to create. The system appears to already have a record that the group was created, and thereby throws an error in the GUI saying that it can't create a group with a name that already exists. (Though there are no groups listed in the GUI so far)

The error details in this case are:

Code: Select all

ERROR                          Administration(omaddpdl      ) 10.15.07 13:44:39
[OM 18015] PDL being added is a duplicate, or a directory
entry is present which has the same name.

Current errno value: 2
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        <- dr_ACISetDefaultContext
        -> pdl_RemoveIa
        <- pdl_RemoveIa
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        -> cdl_IsOu1Hosting
        <- cdl_IsOu1Hosting
        -> dr_ACICheckReadPerm
        <- dr_ACICheckReadPerm
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        <- /build/11.2.0/src/bin/pdl/pdl_add.c:919[3,18015]
        <- /build/11.2.0/src/bin/pdl/pdl_add.c:965[3,18015]


Cheers

[thecowster]

It was getting clear that this issue might not be trivial to resolve. As it only takes minutes to re-install, I have just gone ahead and re-installed.

Now I can create groups without errors

[JacobLeaver]

I'm having exactly the same issue described above, running 11.1.0. Some additional information: although the web interface doesn't show the groups created, omshowpdl -l all does. I am also able to use omaddpdln to add members. Any additional troubleshooting steps or help would be appreciated, I'd rather not do a reinstall if I don't have to.

[chengcsw]

I have the same problem since 11.0.

The workaround is to use the command since it's a Linux system and we used to use commands.

There are less than 10% of admin features you can do it in SAC.