[OpenAFS] Openafs-1.6.5 client crash when update the OPTIONS in afs config file

[HUANG Qiulan]

Dear all,

Many thanks.


> -----=D4=AD=CA=BC=D3=CA=BC=FE-----
> =B7=A2=BC=FE=C8=CB: "Stephan Wiesand" <stephan.wiesand@desy.de>
> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA12=D4=C228=C8=D5 =D0=C7=C6=DA=C8=D5
> =CA=D5=BC=FE=C8=CB: openafs-info <openafs-info@openafs.org>
> =B3=AD=CB=CD: huangql <huangql@ihep.ac.cn>
> =D6=F7=CC=E2: Re: [OpenAFS] Openafs-1.6.5 client crash when update the OP=
TIONS in afs config file
>=20
>=20
> On Dec 27, 2014, at 13:43 , Sergio Gelato wrote:
>=20
> > * huangql [2014-12-24 17:46:19 +0800]:
> >> I failed to restart afs service after I changed OPTIONS value in /etc/=
sysconfig/afs file.
> >=20
> > What was the old value, and what did you change it to?
>=20
> I second this question, as well as the others.
>=20
> >> At this time, I need to reboot the machine to make the new configurati=
on validate.
> >=20
> > 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)?
> >=20
> >> Openafs version: 1.6.5
> >=20
> > A bit old. You may want to check the change logs of later versions for
> > potentially relevant bug fixes.
>=20
> Looks like the ordinary SL6.{x|x<=3D5} packages. They're not supposed to =
crash under normal circumstances. Updating to 6.6 should bring the OpenAFS =
client to version 1.6.10, and there are indeed many fixes in there that sho=
uld make the client fail with an error message rather than a panic or a seg=
fault. But the culprit is most likely bad input from /etc/sysconfig/afs in =
either case. So, again: what't that file's content?
>=20
> >> Os version: Scientific Linux release 6.5 (Carbon)  2.6.32-431.el6.x86_=
64=20
> >>=20
> >> I got the error message as following:
> >>=20
> >> [root@bws0609 ~]# /etc/init.d/afs restart
> >> Stopping AFS client.....=20
> >> Sending all processes using /afs the TERM signal ...       [  OK  ]
> >> Sending all processes using /afs the KILL signal ...       [  OK  ]
> >> Starting AFS client.....=20
> >> /etc/init.d/afs: line 230: 26271 Segmentation fault      /usr/vice/etc=
/afsd ${AFSD_OPTIONS}
>=20
> You shouldn't run the init script directly. Use "service afs restart" ins=
tead.

I don't know what the difference between them?

>=20
> > Has a core file been left behind? If so, could you extract a backtrace =
from it?
> >=20
> >> Dec 24 17:30:29 bws0609 kernel: Starting AFS cache scan...
> >> Dec 24 17:30:29 bws0609 kernel: afsd[26271]: segfault at 18 ip 0000003=
736679753 sp 00007fff5f346fa0 error 4 in libc-2.12.so[3736600000+18a000]
> >=20
> > To me this looks like an attempt to dereference a null pointer to a str=
uct
> > (with the component of interest being at offset 0x18). A backtrace migh=
t
> > help one figure out where that unexpected null pointer came from.

I didn't get a core file. Do you know is there a switch for getting core fi=
le?

>=20
> --=20
> Stephan Wiesand
> DESY -DV-
> Platanenenallee 6
> 15738 Zeuthen, Germany
>=20