Well, after rebooting again, things suddenly seem to be working. No idea
why...
I still have some problems with making RO copies of root.cell and root.afs,
though. Running "vos release" gives me:
<<
[EMAIL PROTECTED]:~$ vos release -id root.cell
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
The volume 536870918 could not be released to the following 1 sites:
picacho.ridgetop-group.local /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed
[EMAIL PROTECTED]:~$ vos release -id root.afs
Failed to start a transaction on the RO volume.
VOLSER: volume is busy
The volume 536870915 could not be released to the following 1 sites:
picacho.ridgetop-group.local /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed
>>
And in /var/log/openafs/VolserLog, there's this:
<<
...
Thu Oct 4 02:59:21 2007 1 Volser: Clone: Recloning volume 536870918 to
volume 536870919
Thu Oct 4 02:59:26 2007 1 transcreate: can't create transaction
Thu Oct 4 02:59:32 2007 1 Volser: Clone: Recloning volume 536870915 to
volume 536870916
Thu Oct 4 02:59:37 2007 1 transcreate: can't create transaction
>>
Before I get myself into trouble again with wild guessing, does anyone know
how I'm SUPPOSED to fix this?
Thanks!
Karl
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Karl M. Davis
Sent: Thursday, October 04, 2007 1:08 AM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: RE: [OpenAFS] AFS Fileserver Won't Start
Found the sysid file, removed it, and rebooted. Still have the same
problems, though.
Where might other entries be and how should I go about clearing them up?
Thanks,
Karl
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, October 04, 2007 12:42 AM
To: Karl M. Davis
Cc: [email protected]
Subject: RE: [OpenAFS] AFS Fileserver Won't Start
>
> The /etc/hosts file is correct, but I did add the second line to it
> somewhere before things went to pot:
> <<
> 127.0.0.1 localhost
> 192.168.2.6 picacho.ridgetop-group.local picacho
> 127.0.1.1 picacho.ridgetop-group.local picacho
I think you have to eliminate everything that resolves
127.something to picacho and the other way around. If you
have managed to get 127.something into your volume database,
all strange things may happen at once.
Volumes located on 127.0.0.1 are perfectly fine accessible
from 127.0.0.1 but of course from nowhere else.
You may need to start over by deleting your sysid file.
Harald.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
