Page 1 of 1
No Group Members displayed with SAC
Posted: Wed Aug 01, 2007 1:00 pm
by netcomrade
This doesn't seem to work in version 11.0.4
After we migrated the server to new hardware, still doesn't work.
Where should we look for potential problems?
Thanks,
-Andrey
Posted: Fri Aug 03, 2007 12:05 am
by netcomrade
Thanks for all the help!
Still doesn't work :(
Posted: Mon Aug 06, 2007 6:01 am
by dannyt
Hi,
There is not much data to go on - can you share more info such as:
-is it single or multiple system
-any error in scalix-caa.log or scalix-res.log
-has the system host name been changed
-what does the group entry look like in omsearch output
-how was the group created using SAC or omaddpdln command
-does it work for a newly created group
Regards,
Danny
Posted: Mon Aug 06, 2007 10:45 pm
by netcomrade
How would I know which info to give, there is no sticky on the forum :)
-is it single or multiple system
single
-any error in scalix-caa.log or scalix-res.log
nothing significant
some 'hearbeat' msgs
-has the system host name been changed
no, but it has been moved. However, before it was moved it would occasionally not work either
-what does the group entry look like in omsearch output
[root@mt-adm logs]# omsearch -e S="dbAlert"
S=dbAlert/OU1=mt-adm/OU2=mycorp/CN=mycorp dbAlert/INTERNET-ADDR="mycorp dbAlert" <dbAlert@mycorp.com>/ENTRY-TYPE=4/DL-POLICY=0/DL-MEMBERS=[S=secdba/OU1=mt-adm/OU2=mycorp/CN=mycorp - DBA Secondary]=[S=pridba/OU1=mt-adm/OU2=mycorp/CN=mycorp - DBA Primary]
omshowpdln -l dbAlert
secdba /mt-adm,mycorp/CN=mycorp - DBA Secondary
pridba /mt-adm,mycorp/CN=mycorp - DBA Primary
-how was the group created using SAC or omaddpdln command
via sac
-does it work for a newly created group
Yes (via sac)
Posted: Tue Aug 07, 2007 3:14 am
by dannyt
Hi,
SAC uses PARENT-DL in the members entry (which is a multi value local unique id of group the member belongs to) to determine group membership. So for each member you have do a omsearch -e s=<member name> -m @all-attr@ and check that the PARENT-DL contains the local unique id of the group (omsearch -e LOCAL-UNIQUE-ID=<this value> should find the group).
Since newly created group works fine, it is possible that the move might have changed something. The workaround is to recreate the group again.
Regards,
Danny