sunhux
asked on
pkgadd fails with 'unable to find user noaccess'
I used root to install on dozens of Solaris 10 x86 without issue
but this server gave me this issue. Pkg is not corrupt as I
compared its size with another good working pkg:
# pkgadd -d ./Agent-Solaris_5.10_U7-9. 0.0-5000.x 86_64.pkg
The following packages are available:
1 ss-agent XXXXXXX Agent
(x86_64) 9.0.0-5000
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Processing package instance <ss-agent> from </var/tmp/Agent-Solaris_5. 10_U7-9.0.
0-5000.x86_64.pkg>
XXXXXXX (x86_64) 9.0.0-5000
Copyright (c) 2004-2012 xxxxx Inc.
All rights reserved.
## Executing checkinstall script.
unable to find user <noaccess>.
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <ss-agent> failed.
No changes were made to the system.
but this server gave me this issue. Pkg is not corrupt as I
compared its size with another good working pkg:
# pkgadd -d ./Agent-Solaris_5.10_U7-9.
The following packages are available:
1 ss-agent XXXXXXX Agent
(x86_64) 9.0.0-5000
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Processing package instance <ss-agent> from </var/tmp/Agent-Solaris_5.
0-5000.x86_64.pkg>
XXXXXXX (x86_64) 9.0.0-5000
Copyright (c) 2004-2012 xxxxx Inc.
All rights reserved.
## Executing checkinstall script.
unable to find user <noaccess>.
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <ss-agent> failed.
No changes were made to the system.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Or could it be checkinstall script was 'tampered' with?
Got to check it out in 2 days' time as I'm on medical leave
Got to check it out in 2 days' time as I'm on medical leave
Must be some hardening script
ASKER
environment: they don't have noaccess nor any user with uid 60002 in
/etc/passwd but installation went through for them (at least 300+ of them).
It's just this one VM that's odd