HW Error?

[Scott D. Allen]

We're running 10.20 on a K360 with Visibility installed. Last night, we were getting some error messages when users tried to login like this:

hwiftp: empty list
Assertion failed: !(fgets(hardwareAddr, (STRLEN-1), fstream) == NULL), file snlui.c, line 1249
visib.profile.ist[106]: 10419 Abort
chmod: can't access /home/username/v63yoln/setme_vis10406.sh
visib.profile.ist[106]: /home/username/v63yoln/setme_vis10406.sh: not found.

People without this visibility profile were able to login and the system was working fine. Has anyone seen this type of error before? If so, what is it relating to? If not, would you say it is hardware or application related (from the hardwareAddr error)?

TIA.

--Scott

[Rick Garland]

It appears to be SW related to the Visability.

Are there any special setups required, for instance the set priv?

[Scott D. Allen]

I don't know. There doesn't appear to be anything in the profile like that. I see where the error messages from chmod and "file not found" are coming from, but that doesn't explain the hwiftp and hardwareAddr fget failure messages. It might just be a transient and I'll probably have to call Visibility on it. Thanks.
--Scott

[Alex Glennie]

As to the other errors: Assertion failed:!
(fgets(hardwareAddr,(STRLEN-1) .... I don't think these are h/w either !

A couple of things to check ?

Check the permissions of lanscan ....

- apply: # chmod 4555 /usr/sbin/lanscan
# ll /usr/sbin/lanscan -r-sr-xr-x 1 root bin if necessary

also try increasing : nfiles, maxfiles, maxfiles_lim parameters

[Scott D. Allen]

My lanscan is -r-xr-sr-x (2555?) not 4555. I don't think that's the problem though because we rebooted the system and now everything's fine. Weird. I'm going to see if visibility has any notes on this error.

--Scott

[Scott D. Allen]

My lanscan is -r-xr-sr-x (2555?) not 4555. I don't think that's the problem though because we rebooted the system and now everything's fine. Weird. I'm going to see if visibility has any notes on this error.

--Scott

[Cheryl Griffin]

Scott,

I searched the internet using www.google.com for "empty list" "assertion failed" and it came up with a 19 hits. You might find something related there.

[Alan Riggs · Accepted solution]

I have run across the hwiftp: empty list error before. In my case it resulted from a running kernel not agreeing with /stand/vmunix. I had made a kernel change but had had to delay the reboot. Apparently this caused some internal buffer overun or other inconsistency which caused lanscan, netstat, glance, etc. to fail. Rebooting (whiched synced /stand/vmunix with the running kernel) corrected the problem.