-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Depending on the part of the supportconfig that is running at each
percentage it could be. If the box is slow or the data being reported
take a long time to grab (Yast stuff can take a long time as the y2log can
become enormous, and hwinfo output can take a long time too, and there are
others of course) then eventually that part of the supportconfig can
timeout (I think there is a ten-minute timeout by default via NSA). You
can run supportconfig directly on your server and see why it takes a
while, or see how long it takes to really complete, and that may be good
for using NSA in the future.
Good luck.
joea wrote:
> OK, so it seems to have taken off again, and has completed. Guess this
> is normal behavior.
>
> joe a.
>
> joea;1840656 Wrote:
>> Just installed NSA. Connecting to OES1 box, scans to about 26%
>> complete, then starts to grow the "timeout" bar. Been watching for
>> about 10 minutes and it has grown to 28% complete, and timeouts to about
>> 23%.
>>
>> ??
>>
>> joe a.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJKhEReAAoJEF+XTK08PnB5b6cQAJ1GV89MZ2 1snjaCz/zjes27
xpU2xzMFBMRfZwdLb8RevxnOWCSeiqMbEhtQ+effaC1Ur4X8TY U9mDeROpZBczEs
IxdsB4tVsLvuSGJaVhOXM9MNeyz3YEhYzo4GX8xIy4wEQujlvr gH+cJUlHU7lBw0
sbTf65ktfrCCVHBNV87Him0ODaZBnNufB/RFS5a8Lr7bfw3QR+D7OBn/wCGUx3PX
gKOTT3xcX59c2FBJVopIlPB7Z0CS5EpLTcxeWhUmKWpesYCcaN Pi3QUiG9p2UHb8
Io7UXTv5uCWtzl0EIllpQunqmS9pJqMZoIqITyAfvHbtnv1hV1 t4cyI/Zk01ip8l
p4mSTf7DQpZI1omaHl/reY7lVxhh1Z+Q1xJehoMHR4MP9gPk6LS/CmzoLL+gF0bw
DaVzaa++XeID6woKiAUjFV9yuDeE8zDth7XYSEFdNKIOrZvUI6 Tki/PpkBYEdN3m
kyW1nlpk8omzkdpLOsE6aftoiwnmLZfuZF/B5a7E6ds0LmpVFaeSUKROv0COflYI
9CCrb0+TYPubEK9G2v5g5YSaa7P3A4rnvklwlhgUDQ9nQ350Cv UYI/y+a9uudifl
YurCEbXzCnwdCJz1hq+H6wTYynY3/DsTDsNXJ1W7j14WahuFE+7Vw2oXMUJPdPyn
v9NwHH12jwsIBCk8gx4j
=Kwh1
-----END PGP SIGNATURE-----
Re: Hangs at 26%
Threaded Mode
