VisionFS failed to contact lock manager

[wfooshee]

Had a problem with VisionFS 3.0 on 5.0.5, started months ago, actually. Vision shares would be unavailable for 10 minutes or so every 5 hours or so. Found in the log (/usr/vision/vfsdata/logs/error.log) where VisionFS crashed with a Segment Violation. Searching for that brought memory errors, out of memory, etc. It was consistently periodic, every 4.5 to 5 hours, and would recover after about 10 minutes. (During that 10 minutes we cannot process credit card transactions at point-of-sale. Inconvenient.)

My solution was to add a cron job to simply restart VisionFS every hour, which is happening successfully.
New error on that: at one restart the log shows

2006/03/07 14:01:00.440 (pid 8382)
SCO VisionFS(3.0) ERROR:
locking/comms/failure
Failed to contact lock manager.
The server cannot run without the lock manager.
Check the vfslockd process is not being stopped.

Repeats every minute for 10 minutes, then there's a 15-minute period of nothing, then a successful start message for VisionFS.

I found this exact message with a solution for Unixware tuning, but could not correlate it to anything in OpenServer. They simply doubled existing values for MAXUP and SFNOLIM somewhere is system tuning. I have no Unixware experience, so I don't know what that means.

 

[motoslide]

There's a newer version of VisionFS. I'm not sure of the licensing implications. Different versions were included with certain releases of OpenServer.
The latest version I've seen is 3.10.911. It might be more reliable, but no guarantees.

You can update the MAXUP kernel parameter by running scoadmin --> Hardware/Kernel --> Tune paramters.
I'm not aware of a correlating parameter in OpenServer for the SFNOLIM value.

 

[wfooshee]

Don't know where to get it. All the links in SCO's Knowledgebase for 3.1 download are dead links to Tarantella. I found patches for 3.0 on SCO's ftp site and applied those, but I don't know where to get 3.1. SCO's knowledgebase clearly states that there are no licensing issues, 3.1 is (was) available for 5.0.5, came with 5.0.6, and will license according to the base OS license and user count. Can't find it, though.

Still happening that it does this lock manager problem on the occasional start.

Brain snap just received while typing. . . . I wonder if it hasn't successfully stopped at the point I'm trying to restart. My script uses a stop command with --kill, then a start command, I may increase my sleep time in between and see what happens. Had 5 seconds, gonna try 10.

 

[motoslide]

You can also check for any remaining connections after you tell VisionFS to stop:

$ netstat -an|grep 139|grep -v LISTEN
tcp        0      0  192.168.197.14.139     192.168.197.148.1066   ESTABLISHED
tcp        0      0  192.168.197.14.139     192.168.197.105.3547   ESTABLISHED

Based on SCO Tech Artical 110146, it looks to me that they DO allow you to upgrade to 3.1 if you are running 5.0.4, 5.0.5, or 5.0.6. I can FTP that version to you if you have a site available.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[khafner]

I have gone from visionfs to samba it is easier and I no longer have to worry about licenses. If it matters the licenses for the vision2K are keep on the server and with samba you don't have to worry you can use one copy on many machines with no problem.

 

[wfooshee]

Have abandoned VisionFS in favor of Samba, seems to be running well.