Software Distribution SD swacl very slow

[Tom Geudens]

Hi,
We use SD to install software on our retail- servers (A500 HP-UX 11.00). We've recently noticed that setting the SD-accesslist starts to take longer and longer. This is starting to cause trouble.
I searched the patch database for similar problems ... but did not find any. Does anyone have this problem / know how to solve it.
Example :
root/fs39131#swacl -l product -M user:root@sv00127:a SYS_MAINTENANCE_FVS @ fs39131:/SD/DEPOT

This "local" command is taking more than 1 hour to execute !

Thanks in advance,
Tom Geudens

[Mateja Bezjak · Accepted solution]

Hi Tom,

This swacl command should only take 1-2 seconds. What is the output of "id" command?
If you export SDU_DEBUG=3 and run swacl, where does it hang?
Have you experienced any other slow downs (when running swinstall)?

What is the content of /SD/DEPOT/catalog/SYS_MAINTENANCE_FVS/pfiles/_ACL and _OWNER?

Regards,
Mateja

[Tom Geudens]

Hi,
Here goes :
root/fs39131#id
uid=0(root) gid=3(sys) groups=0(root),1(other),2(bin),4(adm),5(daemon),6(mail),7
(lp),20(users),101(dba)

SEC_IdEqual: comparing 'root' to 'xpsd' using UTIL_HostsEqual
==> It definitely hangs here, I verified this on another system where I execute several swacl's after another. It hangs for > 40 seconds for every statement.

root/fs39131#more /SD/DEPOT/catalog/SYS_MAINTENANCE_FVS/pfiles/_ACL
# default_realm=fs33502.dolmen.be
num_entries=9
user:root@sv00138.dolmen.be:0133
user:xpsd@sv00138.dolmen.be:0133
user:root@sv00127.dolmen.be:0133
user:root@sv00061.dolmen.be:0133
group:dba@sv00138.dolmen.be:0123
group:fvs@sv00138.dolmen.be:0123
group:p69@sv00138.dolmen.be:0133
group:sys@sv00138.dolmen.be:0123
any_other:0101

root/fs39131#more /SD/DEPOT/catalog/SYS_MAINTENANCE_FVS/pfiles/_OWNER
# default_realm=sv00138.dolmen.be
num_entries=2
user:xpsd:00
group:xpsd:00

B.t.w. you're going to get a lot of points for the SDU_DEBUG hint ... but for the moment I want to keep the rabbit away until there's a real solution :-)

Thanks already,
Tom Geudens

[Mateja Bezjak]

Hi Tom,

The problem might be in your default_realm and realm entries.

/SD/DEPOT/catalog/SYS_MAINTENANCE_FVS/pfiles/_ACL has a default_realm fs33502.dolmen.be

_OWNER has it sw00138.dolmen.be
Change these to fs39131.dolmen.be

Also check other files on this depot:
/SD/DEPOT/catalog/dfiles/_ACL
/SD/DEPOT/catalog/dfiles/_OWNER
/SD/DEPOT/catalog/dfiles/_PROD_DFLT_ACL


What are the system default default_realm and realm in /var/adm/sw/security/ files

Regards,
Mateja

[Tom Geudens]

Hi,
Changed all the realm settings to fs39131.dolmen.be ... that doesn't seem to do the trick however.
Maybe this can narrow it down :
If I clear the settings and than execute the following commands everything works quickly :
swacl -l product -M user:root@sv00127:a SYS_MAINTENANCE_FVS @ fs39131:/SD/DEPOT
swacl -l product -M user:xpsd@sv00127:a SYS_MAINTENANCE_FVS @ fs39131:/SD/DEPOT

However, if I reverse the commands I get the troubles described above (on the second command ... the one with root) ...

Regards,
Tom Geudens

[Mateja Bezjak]

Hi,

Another thing that comes to my mind is the _OWNER file. Our files look like:

# default_realm=sys_name.domain
num_entries=2
user:root:00
group:sys:00

Regards,
Mateja

[Tom Geudens]

Hi,
Thanks a lot Mateja, for your prompt answers. They did not actually solve the problem, but it was someone from HP that put together our SD environment ... and since we have the necessary loggins (thanks to you :-) ... the problem is an HP problem now. In the mean time we're going to use the workaround of always executing the swacl for root first ...

Thanks again (I gave you full points for the debug trick :-).
Regards,
Tom Geudens