I took at look at the directory that is failing chown:
ls -ld /afs/hep.wisc.edu/atlas/vdt/vdt-app-data/globus/persisted
drwxr-xr-x 2 nengxu 20435 2048 Oct 16 10:57
/afs/hep.wisc.edu/atlas/vdt/vdt-app-data/globus/persisted
Notice that the group ownership is numerical id 20435. I think it is the
group ownership that is related to the problem. If I try 'chown nengxu'
on that directory, the operation succeeds without any error (because the
directory is already owned by nengxu). If I try 'chown nengxu:' on that
directory, I get the same error reported in the VDT installation log. If
I just create a directory with my default group ownership and then try
the above chown operations, they both succeed.
The chown man page says this:
"If a colon or dot but no group name follows the user name, that user is
made the owner of the files and the group of the files is changed to
that userâs login group."
So on the machine where you are running the installation, I am guessing
that group 20435 does not match your login group.
--Dan
Annabelle Leung wrote:
> Hi Alain,
>
> I just tried installing it on a local disk and it works fine. The last
> error messages I have been getting with my attempt to install on afs is:
>
> vdt-untar: vdt_globus_ws_essentials-VDT1.8.1-x86_rhas_4.tar
> vdt-untar: logging files to
> /afs/hep.wisc.edu/atlas/vdt/vdt/etc/package_data/Globus-Base-WS-Essentials.filelist
> All of the packages in your GLOBUS_LOCATION are already set up.
> ### 2007-10-16 10:57:13 (import) loaded by vdt/setup/configure_globus_ws
> ### 2007-10-16 10:57:13 (import) @ARGV = [ ]
> ### 2007-10-16 10:57:13 (failsafe_system) mkdir -p
> /afs/hep.wisc.edu/atlas/vdt/globus/var/log
> ### 2007-10-16 10:57:13 (pick_user) Globus web services will run as:
> nengxu
> ### 2007-10-16 10:57:13 (failsafe_system) mkdir -p
> /afs/hep.wisc.edu/atlas/vdt/vdt-app-data/globus/persisted
> ### 2007-10-16 10:57:13 (failsafe_system) chown -R nengxu:
> /afs/hep.wisc.edu/atlas/vdt/vdt-app-data/globus/pers
> isted
> chown: changing ownership of
> `/afs/hep.wisc.edu/atlas/vdt/vdt-app-data/globus/persisted': Operation
> not permitt
> ed
>
> I am not installing it as root on /afs but as a user.
>
> Annabelle
>
>
> On Oct 16, 2007, at 4:30 PM, Alain Roy via RT wrote:
>
>>>> Command failed:
>>>> ./condor_configure --install --maybe-daemon-owner --make-
>>>> personal-condor --install-log ../post-install/README
>>>> Exited with value 9
>>>> Pacman install failed
>>>
>>> Am I doign something wrong?
>>
>> Can you please look in vdt-install.log and see if there is a good error
>> message? Near the bottom, when condor_configure was run, we probably got
>> a good error message that will help us figure out what the problem is.
>>
>> What OS are you installing on? You mentioned AFS: do you know the
>> installation works when you install on a local disk, or is it just a
>> hunch that it's an AFS problem?
>>
>> Thanks,
>> -alain
>>
>>
>> --
>> View ticket at
>> <http://vdt.cs.wisc.edu/rt/Ticket/Display.html?user=guest&pass=guest&id=3036
>> <http://vdt.cs.wisc.edu/rt/Ticket/Display.html?user=guest&pass=guest&id=3036>>
>> VDT Support, vdt-support@ivdgl.org <mailto:vdt-support@ivdgl.org>
>
> Annabelle Leung
> University of Wisconsin-Madison
> Bat.32 R-A03
> CERN
> CH-1211
> Geneva, Switzerland
> +41 22 767 7373
>
> Annabelle.Leung@cern.ch <mailto:Annabelle.Leung@cern.ch>
>
>
>