SCIENTIFIC-LINUX-USERS Archives

February 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"W. Mark Smith" <[log in to unmask]>
Reply To:
W. Mark Smith
Date:
Mon, 12 Feb 2007 13:07:52 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (118 lines)
I built version openafs-1.4.2. I also noticed that my 'configure' line is
different from the SL src rpm:

My configure:
%configure --with-afs-sysname=%{sysname} \
        --enable-redhat-buildsys \
        --enable-transarc-paths \
        --with-krb5
make dest_nolibafs

From openafs-1.4.1-11.SL.spec (lines 482-494):
%if %{krb5support}
# Now build aklog/asetkey

(cd afs-krb5/src &&
	PATH=/usr/kerberos/bin:$PATH \
        ./configure --prefix=/usr --with-krb5=/usr/kerberos \
            --with-afs=`pwd`/../../${sysname}/dest/ && \
        make all PROGS="asetkey aklog ka-forwarder" && \
        touch afs2k5db && touch fakeka && \
        make install PROGS="asetkey aklog ka-forwarder" \
            DESTDIR=`pwd`/../../${sysname}/dest/ INSTALL_BIN=/bin \
            INSTALL_SBIN=/etc) || exit 1
%endif

It seems that I built things differently: I just use whatever aklog is
built by 'make dest_nolibafs', whereas the SL package builds it separately
as shown above. The SL package also uses a source file
(openafs-krb5-2.0.tar.gz) that I don't use.

I'm using my existing installation/configuration that was in place before
I switched over to the SL rpm, so I haven't tried asetkey either. It's
possible that I might have the same problem with that binary. Perhaps this
is related to my problem and I need to re-run asetkey? I'm hesitant to try
that at this point since I'm afraid of breaking something....

I had an offline comment that hinted that this may be a krb4 vs krb5
issue. My configuration is krb5 only (I don't use fakeka or any 5-to-4
translation).  Do you know of any reason that this shouldn't work with a
krb5-only installation?

Mark


> Which version of openafs is your aklog binary from, that works?
>
> Troy
>
> W. Mark Smith wrote:
>> Troy,
>>
>> Thanks for the tip. Unfortuantely, that didn't work for me. I have in
>> fact
>> restarted (and rebooted) both client and server. The strange thing is
>> that
>> /usr/bin/afs5log from the pam_krb5-2.1.8-1 grabs the ticket with no
>> problem immediately after aklog fails. Also, the aklog binary from my
>> own
>> build of openafs works with no problems.
>>
>> Mark
>>
>>> W. Mark Smith wrote:
>>>> Hello,
>>>>
>>>> I seem to be having trouble with the version of aklog that is included
>>>> in package openafs-krb5-1.4.1-0.11.SL (I'm using SL 4.4).
>>>>
>>>> $ kinit
>>>> Password for [user]@[REALM]:
>>>> $ aklog
>>>> aklog: Couldn't get [cell] AFS tickets:
>>>> aklog: unknown RPC error (-1765328228) while getting AFS ticket
>>>>
>>>> I did a google search for this error, but all instances that I found
>>>> had a different error code, and none of the suggestions worked for
>>>> me. I consistently get the error code shown above on all machines on
>>>> which I have tried.  I consistently get the same problem on both
>>>> i386 and x86_64 platforms.
>>>>
>>>> The AFS-related packages I have installed are as follows:
>>>>
>>>> $ rpm -qa | grep afs
>>>> openafs-server-1.4.1-0.11.SL
>>>> kernel-module-openafs-2.6.9-42.0.3.EL-1.4.1-0.11.SL
>>>> krbafs-devel-1.2.2-6
>>>> openafs-client-1.4.1-0.11.SL
>>>> kernel-module-openafs-2.6.9-42.0.8.EL-1.4.1-0.11.SL
>>>> openafs-kpasswd-1.4.1-0.11.SL
>>>> openafs-1.4.1-0.11.SL
>>>> openafs-compat-1.4.1-0.11.SL
>>>> krbafs-1.2.2-6
>>>> openafs-krb5-1.4.1-0.11.SL
>>>>
>>>>
>>>> Interestingly, I tried using the aklog binary from an rpm I had
>>>> built before my switch to SL, and it worked with no problems.
>>>>
>>>> Does anyone else have this problem or any ideas for a possible
>>>> solution other than re-compiling aklog?
>>>>
>>>> Thanks,
>>>> Mark
>>> Hi Mark,
>>> Have you restarted openafs since updating to the 1.4.1 version of
>>> openafs?
>>> And is AFS running?  (I know it's a silly question, but that's usually
>>> my problem when aklog doesn't work.)
>>>
>>> Troy
>
> --
> __________________________________________________
> Troy Dawson  [log in to unmask]  (630)840-6468
> Fermilab  ComputingDivision/LCSI/CSI DSS Group
> __________________________________________________
>

ATOM RSS1 RSS2