---------- Forwarded message ---------- From: Ted Creedon <[email protected]> Date: Thu, May 7, 2009 at 2:57 PM Subject: Re: [OpenAFS] /afs area is hanging To: Mark Henry <[email protected]>
Use select cut and paste typical portions of dmesg and /var/log/messages I fixed my problem by recreating all the principals using "kadmin.local -e des-cbc-crc:normal" which forces all the keys to be single des. Typical for 3 servers all of which hung after "ls /afs" I niced affsd to get enough keyboard control to see that klogd and syslog-ng are using all the cycles filling /var/log/messages with rx carps. I think that a massive error caused by mis-keying should not hang windows and linux clients... A key check diagnostic would certainly help. 1.5.59 win and 1.4.10 linux on 3 suse 10.2 and 11.1 server boxes, one is dual homed Seems to work fine now. On Thu, May 7, 2009 at 1:51 PM, Mark Henry <[email protected]> wrote: > > I ran the 'echo t' command recommended below once afs hung again. It > definitely put some output in dmesg. The only D states that were listed > were bash sessions (I think). It looks like they were sessions that I > opened after the user told me that afs was hung again. I tried to attach > the dmesg output and cmdebug output but the email was rejected because the > log files were way too big. Any ideas of what to try next? Or is there > anything in particular that I should look at in the cmdebug or dmesg output. > Thanks, > > Mark Henry > > > > *Felix Frank <[email protected]>* > > 05/04/2009 11:46 PM > To > Mark Henry <[email protected]> cc > [email protected] Subject > Re: [OpenAFS] /afs area is hanging > > > > > On Mon, 4 May 2009, Mark Henry wrote: > > > I tried the -fakestat-all option and it did not work. > > Weird. > > > I have searched /var/log/messages. I have checked the config files. > User > > authentication works fine (even when the system is hanging). If I run > the > > command 'ls -l /afs' that window is hung (or any other command that > > references afs). If an afs user logs in when the system is in a bad > state > > the session immediately hangs because it can't cd to the afs home dir. I > > don't know what to do other than reboot. Can someone tell me what else > to > > try to find out why this system is hanging? Thanks, > > You can find out just which call gets stuck by issuing an > 'echo t >>/proc/sysrq-trigger'. Call traces for all processes can then be > found in dmesg. The broken processes are probably in a D state. > > This will probably not identify the root cause, but may give a clue about > what's going on. > > HTH > - Felix > > > > _____________________________________________________________________________ > "This message and any attachments are solely for the intended recipient and > may contain confidential or privileged information. If you are not the > intended recipient, any disclosure, copying, use, or distribution of the > information included in this message and any attachments is prohibited. If > you have received this communication in error, please notify us by reply > e-mail and immediately and permanently delete this message and any > attachments. Thank you." > _____________________________________________________________________________ >
