When my openafs server processes did their weekly restarts this Sunday, they have not been able to start up again. I have tried rebooting.
Both PtLog and VLLog are filled with the following entries: Ubik: Synchronize database with server 0.0.0.0 failed (error = 10029) recovery running in state 17 Everything was working fine before the restart. I haven't made any configuration changes in several years, and no major software changes that I think would cause this. I am not sure why the ptserver and vlserver are trying to synchronize with 0.0.0.0, and search results for these messages as well as error 10029 haven't yielded any useful information. I have a very simple setup, with one server afsserver1.local at 192.168.0.2, and I'm running stock Debian 1.6.5-1 amd64 openafs servers. % rxdebug 192.168.0.2 7003 -version AFS version: OpenAFS 1.6.5-1-debian built 2013-07-24 % bos listhosts afsserver1.local Cell name is mshome.net Host 1 is afsdb1.local % vos listaddrs vos: could not list the server addresses u: no quorum elected Once or twice I have gotten vos listvldb to work, but mostly it gives me similar errors: % vos listvldb VLDB entries for all servers Could not access the VLDB for attributes u: no quorum elected I should note that I previously had two other servers which I have taken offline several years ago after I migrated all of the volumes off of them, but I never removed their addresses from the VLDB. It's never been a problem before, but I don't know if that's what's causing the problem now. I am totally puzzled at how to fix this problem. Any help to fix the problem as well as figure out what caused it would be greatly appreciated. Thanks _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
