On Thu, 3 Mar 2016, Michael Dressel wrote: > Hi, > > I just created another error using the openafs repository. > I was on commit > b702ab5da216976ed01ad3b1c474ecd4cc522ff2 > and checked out cb0081604ef5369f34279c6eb77eb4d28406f2ac > > This created the error shown below.
Er, are those versions you were running, or are you just saying that you were in a git repo and HEAD was b702ab5da216976ed01ad3b1c474ecd4cc522ff2 and you ran 'git checkout cb0081604ef5369f34279c6eb77eb4d28406f2ac'? In any case, I don't think there's anywhere near enough information to diagnose any issues that might be present. For this sort of 'lost contact' situation, it can be helpful to have a network capture of the traffic in question. -Ben > reverse order: > > Mar 03 10:12:10 ... kernel: afs: file server ... in cell ... is back up (code > 0) (multi-homed address; other same-host interfaces may still be down) > Mar 03 10:11:54 ... kernel: afs: failed to store file (network problems) > Mar 03 10:11:54 ... kernel: afs: failed to store file (network problems) > Mar 03 10:11:54 ... kernel: afs: Lost contact with file server ... in cell > ... (code -32) (all multi-homed ip addresses down for the server) > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
