Parsing "vos dump" output

command==> ./vos create myhost.com vicepxx root.afs -cell mycell.com vos : partition vicepxx does not exist on the server

"The box said I needed to install Windows 98 or better… so I installed Linux"

Hello all,

I'm in the process of setting up an afs cell and have successfully set up 
a server on Redhat 9.0 and a client on Windows XP. However, I'm running 
into problems with getting the client functional on my Windows 2000 
computer. It installs fine and everything seems to be set up so that it 
would work, but the service won't start. There is supposedly no error 
returned. I've tried starting it manually in Services and with the client 
manager. It just silently fails. I know that there have been some issues 
with my Client for Microsoft networks on that machine, but it appears to 
be installed and working. Is there any way to get more details on what's 
failing? Any ideas on how to make sure the Client for Microsoft Networks 
is working correctly? Thanks for any help.

-James

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Hi all,

Back in December '03 Rodney Dyer at UNC-C reported a problem the OpenAFS
Windows client.  I wanted to followup and confirm this rather annoying
problem.  For those that might have forgotten, the problem is that the afs
cache operates normally while the cache is filling however once the cache
is full, additional file operations leave open windows file handles.

I'm trying to install OpenAFS 1.2.10 from the Release webpage on 
www.openafs.org. The file's contents follow:

9:28:20 AM: Create log file
9:28:20 AM: Created log file
9:28:20 AM: osi_InitDebug code 1719

I tried restarting it again and the same error was produced.

-James

I still get the same error, 1719. If I start from the client control 
panel I get an error 0x0000042A. (Which seems to be a generic service 
won't start.) I googled for this error and saw a brief mention 2 years ago 
in March on this list. It seemed to say there that there was some 
contention over event logging service 1000 or something to that effect. I 
tried stopping all the services I could it didn't change the problem.

-James

On Sun, 14 Mar 2004, Jeffrey Altman wrote:

Please install the the 1.3.52 build instead of 1.2.10

James Burns wrote:

I'm trying to install OpenAFS 1.2.10 from the Release webpage on 
www.openafs.org. The file's contents follow:

9:28:20 AM: Create log file
9:28:20 AM: Created log file
9:28:20 AM: osi_InitDebug code 1719

I tried restarting it again and the same error was produced.

-James

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Perhaps someone could verify the correctness of the .exe file on the server?

Whenever I restart my Windows 2000 PC (currently automatically login
into Administrator account - as I am still in the process of
installing/configuring it), It gives me the following error:

AFS LOGON ERROR
"Integrated Login Failed: <some garbled text>"

(the garbled text looks like an encypted password?)

I click OK and then the "AFS Client Wizard" is displayed and reads:
"The  AFS Client service has not yet started".

I then click "Next" and the client seems to have been started,
prompting me for AFS cell, user name and password. The AFS cell edit
box already contains the correct value. The user name edit, on the
other hand, contains 'Administrator' - which is of course incorrect. I
type in my AFS username and password, click 'Next, and everything works
fine (I get the message: "The AFS Client is ready for use".

Now... while it is very nice that I can make my AFS client on Windows
2000 work, it is very inconvenient to always have to type the username
and password whenever I logon. So, my question is:

How do make the AFS client service start up automatically and
automatically logon using the username & password that work so
perfectly when I enter them manually?

I am using AFS Version 1.2.10

Thanks,
Pam 

__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

I'm testing the windows 1.3.6000 build--hoping it will solve several
outstanding problems I've seen with OpenAFS 1.2.11 on windows.

Can someone please confirm for me that obtaining tokens when logging into
Windows works on this build?

I have checked "Obtain AFS tokens when logging into Windows", and made sure
that "Fail Logins Silently" is "No", but I do not get tokens when
logging in.  Neither is there any error message to indicate that the client
is even attempting to contact a server, nor any record in the server logs.

I've confirmed that toggling the "Obtain AFS tokens..." checkbox does
indeed toggle
HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\LogonOptions.

I'm attempting standard AFS authentication, against krb5/fakeka.  I can
obtain tokens manually on the client without problems and that shows up in
the server logs as expected.

Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

I'm =
testing the windows 1.3.6000 build--hoping it will solve several
outstanding problems I've seen with OpenAFS 1.2.11 on windows.

Can someone please confirm for me that obtaining tokens when logging =
into
Windows works on this build?

I have checked "Obtain AFS tokens when logging into Windows", and made =
sure
that "Fail Logins Silently" is "No", but I do not get tokens when
logging in.  Neither is there any error message to indicate that the =
client
is even attempting to contact a server, nor any record in the server =
logs.

I've confirmed that toggling the "Obtain AFS tokens..." checkbox does
indeed toggle
HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\=
LogonOptions.

I'm attempting standard AFS authentication, against krb5/fakeka.  I can
obtain tokens manually on the client without problems and that shows up =
in
the server logs as expected.

Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://=
lists.openafs.org/mailman/listinfo/openafs-info

FWIW, I've seen that very slow behavior too, but figured it was something
I'm doing wrong... (the new versions, .5299 and .6000, also seem to
consistently crash, with the question about sending a crash report to MS,
every time I stop the service.)  I see this on WinXPsp1 with only MS
patches and OpenAFS installed.

The Win2000 I did worked.  The WinXP I can get tokens and see the share, but I 
have yet to see the cell in Explorer.  Clicking the drive letter causes a 
30-40 sec time delay and then I see no files or dirs.  I'll keep looking for 
something I messed up.

Best Regards,

Joshua Johnson

Jeffrey, thanks for your fast reply. It definitely explains why the
Integraged Login fails since 'Administrator' is not a valid user name
in my AFS cell. :)

The problem is that based on your advice, I created an account (Power
Users group) in my Windows 2000 workstation with the same exact
username used to obtain tokens for AFS, but I get the same exact error
when I login:

AFS LOGON ERROR
"Integrated Login Failed: <some garbled text>"

I click OK and then the "AFS Client Wizard" is displayed and reads:
"The AFS Client service has not yet started".

I click 'Next', but instead of starting the client and prompting me for
username and password (for successful login as happens when I login as
Administrator), I receive the following error:

"The AFS Client service could not be started"

Why can't the AFS Client service be started? Everything seems to be
installed properly since it starts successfully when logged in as
Administrator. Must a user have administrative priveleges in order to
start the AFS Client?

If not, what do I need to configure to make this work? I know about the
AFS Client Configuration in Control Panel, but I couldn't find there
anything directly related to my problem and I am afraid to start
experimenting with the various options there beyond repair...

Your help is very much appreciated!

Thanks,
Pam

--- Jeffrey Altman <jaltman@columbia.edu> wrote:

The username used to login to windows must match the username used to
obtain
tokens for AFS.  Otherwise, the AFS Integrated Logon cannot work.

Jeffrey Altman

Pamela Goetz wrote:

Whenever I restart my Windows 2000 PC (currently automatically login
into Administrator account - as I am still in the process of
installing/configuring it), It gives me the following error:

AFS LOGON ERROR
"Integrated Login Failed: <some garbled text>"

(the garbled text looks like an encypted password?)

I click OK and then the "AFS Client Wizard" is displayed and reads:
"The  AFS Client service has not yet started".

I then click "Next" and the client seems to have been started,
prompting me for AFS cell, user name and password. The AFS cell edit
box already contains the correct value. The user name edit, on the
other hand, contains 'Administrator' - which is of course incorrect.

I

type in my AFS username and password, click 'Next, and everything

works

fine (I get the message: "The AFS Client is ready for use".

Now... while it is very nice that I can make my AFS client on

Windows

2000 work, it is very inconvenient to always have to type the

username

and password whenever I logon. So, my question is:

How do make the AFS client service start up automatically and
automatically logon using the username & password that work so
perfectly when I enter them manually?

I am using AFS Version 1.2.10

Thanks,
Pam 

__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

FWIW, =
I've seen that very slow behavior too, but figured it was something
I'm doing wrong... (the new versions, .5299 and .6000, also seem to
consistently crash, with the question about sending a crash report to =
MS,
every time I stop the service.)  I see this on WinXPsp1 with only MS
patches and OpenAFS installed.

On Fri, Mar 19, 2004 at 09:51:58AM -0500, Jeffrey Altman wrote:

You can't start the service from a non-administrator account
with the 1.2.xx builds.  This was fixed in the 1.3.50 and higher builds.

well. I think you can but NOT from the gui. Using command line

net start "IBM AFS Client"

works for me.. since we do it all the time when afs becomes to
finicky.  But we're still at 1.2.8 and 1.2.10 versions. 

Do the following.  Install the 1.3.60 build that was announced
yesterday and append the service "TransarcAFSDaemon" to the
list specified in the registry value:

   Key:  HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
   Value:  ProviderOrder

This is really good news.  Sorry to be slow on the uptake but where is
the 1.3.60 build for windows found?  I didn't see it in the download
section on the web page last I checked..

I am running Windows 2003 Server, Enterprise Edition with KfW 2.5 and
using the loopback adapter.  OpenAFS was working fine for the most part
with 1.3.52 with only the crashes that I reported through rt, but those
appeared to have been caused by mis-matched versions of some of the
files.

Here is info from the event log:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date:  19-Mar-04
Time:  3:43:10p
User:  N/A
Computer: KBS-CDC
Description:
Faulting application afsd_service.exe, version 1.3.6000.0, faulting
module unknown, version 0.0.0.0, fault address 0x00000000.

C:\PROGRA~1\AFS\Client\Program;C:\PROGRA~1\AFS\Server\usr\afs\bin;C:\PROGRA~1\AFS\Common

which uses the same DLL names as the 1.3.60 version but is 
incompatible is way that will produce a crash.

It appears as though the afspthread.dll in the installer does not match
the version number of everything else:
 1.3.5299.0 shp     10,752 03-18-2004 afspthread.dll

Could that be a problem?

I have also noticed that typing in "tokens" at a cmd prompt seems to
take longer that it did under the 1.3.52 client.

  The behavior I was expiriencing was just like someone else already
posted.  I am running XP sp1.  I haven't tried the latest daily build,
but someone said that was showing the same behavior.  I will attempt to
try that version at some point and let you know if it works for me.

Tim

with windows 2k and better, you can list startup dependancies in the
service control manager for a particular service.

Where can I specify startup depencancies for openafs?  I only use
openafs clients.  All afs services live on unix boxes.

I would really like to be able to list something like the windows
'explorer' as a startup dependancy for the afs client to make certain
its the LAST service to start...

I tried installing the latest version to see if any of the changes 
affected the problems I was previously posting about here. Instead upon 
reboot I was greeted by a Visual C++ runtime buffer overflow and 
subsequent crash of winlogin.exe. This of course leads to a reboot of the 
machine. I did not have integrated login enabled, but do have a UareU 
fingerprint alternate login device. This problem did not exist in 1.3.59 
(which simply didn't start as noted previously). When I restarted in safe 
mode, after logging in there was a dialogue about how the AFS Client 
didn't start. Uninstalling OpenAFS fixed the crash during normal login. 
Something seems to be pretty broken.

-James

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

James Burns wrote:

I tried installing the latest version to see if any of the changes
affected the problems I was previously posting about here. Instead upon
reboot I was greeted by a Visual C++ runtime buffer overflow and
subsequent crash of winlogin.exe. This of course leads to a reboot of the
machine. I did not have integrated login enabled, but do have a UareU
fingerprint alternate login device. 

It may be UareU as they replace the GINA with their own! I had one of these
installed last week wit version 3.0.0, but uninstalled it to let someone else
try it. I will have to see if he has the problem as he installed 1.3.60.
(Sundays version)

But while I have the UareU installed I did not have any problems with AFS,
but I was not using integrated AFS login either.

This problem did not exist in 1.3.59
(which simply didn't start as noted previously). When I restarted in safe
mode, after logging in there was a dialogue about how the AFS Client
didn't start. Uninstalling OpenAFS fixed the crash during normal login.
Something seems to be pretty broken.

-James

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

I just tried 1.3.62. It no longer crashes, but makes login take about 5 
minutes. I haven't tried disabling the dll in the registry yet. When it 
did finally start up, it says that the server service started, but when 
trying to configure it I get "Failed to determine the current 
configuration of this machine. Error: Unknown code d 43 
(1067)(0x0000042B)" The client seems to be stuck in the starting state. 
The afsd_init.log shows:

11:52:11 PM: Create log file
11:52:11 PM: Created log file
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\JDK1.2\BIN;C:\GRAVIS\CORESO~1;C:\PROGRA~1\MCAFEE\MCAFEE~1\MCAFEE~1;F:\cygwin\bin;C:\Program Files\Common Files\Roxio Shared\DLLShared;"C:\Program Files\Symantec\Norton Ghost 2003\";C:\Program Files\Executive Software\Diskeeper\;C:\Program Files\OpenAFS\Client\Program;C:\Program Files\OpenAFS\Common
3/24/2004 11:52:12 PM: osi_InitDebug code 1719
3/24/2004 11:52:12 PM: --- begin dump ---
a - dumping scache - cm_currentSCaches=0, cm_maxSCaches=0
a - dumping cm_hashTable - cm_hashTableSize=0
a - Done dumping scache.
3/24/2004 11:52:12 PM: --- end   dump ---
3/24/2004 11:52:12 PM: UnhandledException : code : 0x80000003, address: 0x77fa144b

--# FV EIP----- RetAddr- FramePtr StackPtr Symbol
  0 .V 77fa144b 00401536 007aff78 00000000 DbgBreakPoint
  1 .V 00401536 7c2e02f7 007affa4 00000000 
  2 .V 7c2e02f7 00000000 007affec 00000000 StartServiceCtrlDispatcherW +1739 bytes
EXCEPTION_BREAKPOINT - continue execution ...

Which seems to be the same error as I was having before.

-James

      ----- cut here ---------
      REGEDIT4

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
      "ncacn_np"="rpcrt4.dll"
      "ncacn_ip_tcp"="rpcrt4.dll"
      "ncadg_ip_udp"="rpcrt4.dll"
      "ncacn_nb_tcp"="rpcrt4.dll"
      "ncacn_http"="rpcrt4.dll"
      ----- cut here --------- 
That worked perfectly. Thank you so much! Any idea about the server error? 
I'm figuring that it's some old file or registry entry, but I removed all 
the related ones I could find before installing 1.3.61.

-James

On Wed, 24 Mar 2004, Jeffrey Altman wrote:

In particular, you should have this in the registry:

      ----- cut here ---------
      REGEDIT4

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\*RPC*\ClientProtocols]
      "ncacn_np"="rpcrt4.dll"
      "ncacn_ip_tcp"="rpcrt4.dll"
      "ncadg_ip_udp"="rpcrt4.dll"
      "ncacn_nb_tcp"="rpcrt4.dll"
      "ncacn_http"="rpcrt4.dll"
      ----- cut here --------- 

Jeffrey Altman wrote:

Can you specify what keys, values and data are specified in the 
registry by

       HKLM\SOFTWARE\Microsoft\Rpc

and its children? 

Jeffrey Altman wrote:

RPC appears to be disabled on your machine.
AFS requires the use of RPC.  There is no way that AFS could run on it.

Error code 1719 is "There are no protocol sequences".  This is a windows
error indicating that RpcServerUseAllProtseqs() has failed. 

The reason that afslogon.dll is taking a while to succeed is that it is
attempting to start the AFS Client Service which won't start.

What policy has been applied to your machine that prevents the loading
of RPC Protocols implementations for TCP/IP, NETBIOS, etc.

Jeffrey Altman

I'm seeing a strange behavior with the installer. I'm using my own 
CellServDB. When I select it and click next I get the options for stuff to 
turn on and off in the config, but the cell name selection is greyed out. 
This usually causes a delay when starting up because openafs.org isn't in 
my CellServDB. I believe that all the 1.3.x have this problem.

-James

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

It's grayed out, both the label and the field. For the reinstall (I just 
reran the installer) it showed my cell name, but for the original install 
it show an uneditable openafs.org. (My cell name was uneditable in the 
reinstall also to be clear)

-James

The exact same things occurs when one attempts to install the windows
AFS server using the new installer.  I install everything and then have
to change the cell of my machine from openafs.org.  I used the included
CellServDB.  If I re-run the installer and don't select the AFS Server I
can then input a cell name.

<<CDC
Christopher D. Clausen
ACM@UIUC SysAdmin

On Thursday, March 25, 2004 6:22p <james@burns.net> wrote:

It's grayed out, both the label and the field. For the reinstall (I
just reran the installer) it showed my cell name, but for the
original install it show an uneditable openafs.org. (My cell name was
uneditable in the reinstall also to be clear)

-James

On Thu, 25 Mar 2004, Jeffrey Altman wrote:

Are you sure the "cell name" field is grey'd out?  Or is the "cell
name" simply selected?

James Burns wrote:

I'm seeing a strange behavior with the installer. I'm using my own
CellServDB. When I select it and click next I get the options for
stuff to turn on and off in the config, but the cell name selection
is greyed out. This usually causes a delay when starting up because
openafs.org isn't in my CellServDB. I believe that all the 1.3.x
have this problem.

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Yes, from my hard drive. However, even though the only entry in the file 
is for my cell, it still says the greyed out openafs.org. I don't think 
that it should do that.

-James

On Thu, 25 Mar 2004, Jeffrey Altman wrote:

That is not what the installer script says no what I experience when I 
use it.
You are selecting the "specify a cellservdb file" option?

James Burns wrote:

It's grayed out, both the label and the field. For the reinstall (I just 
reran the installer) it showed my cell name, but for the original install 
it show an uneditable openafs.org. (My cell name was uneditable in the 
reinstall also to be clear)

-James

I was also installing the server, so that is why it was greyed out 
apparently. I am still, however, unable to configure the server because of 
the error that I mentioned before, "Failed to determine current 
configuration of this machine. Error: Unknown code d 43 
(1067)(0x0000042B)"

-James

There is an important issue here. Will future versions of OpenAFS be dependent
on KfW?  

I'd be willing to contribute some time to get the Windows server working 
if someone could point me in the right direction. Also if there's a 
document on the "by hand" way, I'd be grateful for the too. I set up my 
linux server that way and would be happy to do windows by hand as well.

-James