i recently wanted to install the UBB.Classic 6.6 on My Webspace. I've done all the points on your installtion instructions. (All files are CHMODed correctly, uploaded in ASCII / BINARY correctly). Then I used the cp.cgi to compleate the installation, but then, after I filled out all the PAth boxes I got the following error for serveral times. (I reinstalled all files 2-3 times)
Code
Software error:
Can't EXlock '/home/9/lssharkn/ubb/cache-M7DVRNEZ/lock/global.cgi'. The exact error returned by the operating system is: Operation not supported
I don't know why. I rechecked all the File Permissions, etc. All Chace ans Forum etc. Dirs and files are created successfully.. may be you can halp me.
Hi there... It sounds to me like you don't have the flock (file locking) Perl module installed. You'll want to inquire with your host about having this particular module as it's necessary for the UBB.classic to run.... Let us know how it goes!
I have Perl 5.005_02. I am getting a similar error, but I'm pretty sure I do have the filelocking module because my UBB.classic 6.5.0 was working in its current location until a week or so ago. We did just move our fs, it's now an NFS mount and I think this has something to do with it. System is a Solaris 8 Sun sparc. Here's the error I'm getting:
Software error:
Can't EXlock '/path/to/ubb/cache-6K3B2NPK/lock/global.cgi'. The operating system has run out of file locks to give me. Please ask the administrator to contact the web hosting provider. The exact error returned by the operating system is: No record locks available
UBB.classic is not designed nor intended to function properly on an NFS mount: Many NFS implementations have buggy, broken, or completely non-functional file locking schemes.
UBB.classic should be run only on a non-virtual, non-network filesystem. This is not a direct limitation of UBB.classic, but a policy we've had to enact after finding such problems with normal file locking on NFS shares. There are simply too many problems for it to work right.
The exact error, in this case, "No record locks available," indicates that the file locking process has run out of available locks to hand out, as is noted in the verbose error message. A quick googling confirms this.
Saw the other threads on this as well and wrote my webhost to ask them to install more locks.
Just curious, is that a hard thing for them to do?
Asking because I know nothing about server side politics and I want to be prepared for their response (if they ever get back to me <img src="https://www.ubbcentral.com/boards/images/graemlins/blush.gif" alt="" /> )
Actually, I have no idea whatsoever how to adjust how many locks are available to the system. I would imagine it would vary based on the operating system and how locking is performed.