* huangql [2014-12-24 17:46:19 +0800]: > I failed to restart afs service after I changed OPTIONS value in > /etc/sysconfig/afs file.
What was the old value, and what did you change it to? > At this time, I need to reboot the machine to make the new configuration > validate. Are you saying that afsd crashes on service restart but not when it is started for the first time after a reboot (with the same options)? > Openafs version: 1.6.5 A bit old. You may want to check the change logs of later versions for potentially relevant bug fixes. > Os version: Scientific Linux release 6.5 (Carbon) 2.6.32-431.el6.x86_64 > > I got the error message as following: > > [root@bws0609 ~]# /etc/init.d/afs restart > Stopping AFS client..... > Sending all processes using /afs the TERM signal ... [ OK ] > Sending all processes using /afs the KILL signal ... [ OK ] > Starting AFS client..... > /etc/init.d/afs: line 230: 26271 Segmentation fault /usr/vice/etc/afsd > ${AFSD_OPTIONS} Has a core file been left behind? If so, could you extract a backtrace from it? > Dec 24 17:30:29 bws0609 kernel: Starting AFS cache scan... > Dec 24 17:30:29 bws0609 kernel: afsd[26271]: segfault at 18 ip > 0000003736679753 sp 00007fff5f346fa0 error 4 in > libc-2.12.so[3736600000+18a000] To me this looks like an attempt to dereference a null pointer to a struct (with the component of interest being at offset 0x18). A backtrace might help one figure out where that unexpected null pointer came from. _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info