Main
Index
Search
Posts
Who's
Online
Log
In

Home: Discontinued/Classic Products: Listings Manager (Realty Manager & Auto Manager):
DB Filelock error

 

 


Cathy
User

Feb 4, 2009, 5:54 PM

Post #1 of 3 (2318 views)
Shortcut
DB Filelock error Can't Post

I have a strange thing that just started happening to an install that has been working perfectly for years. Starting today, anytime the admin.cgi is accessed (you don't even have to log in - just access the log-in page) a filelock.dat file is created in the /data directory and, with that file creation, any search.cgi functions cease and return a a DB Filelock error. The admin.cgi works fine, but the search.cgi returns a DB Filelock error. The error remains even after exiting the admin.cgi program. The only way to restore the search.cgi function on the website is to manually remove the filelock.dat file that is created when the admin.cgi is accessed.

I have tried removing the # from the disable_filelocking = 1 in the config.ini, I have double checked all the file permissions, and we are running the most current version of the program.

This just started out of the blue today, no server changes (that I know of), nothing has changed with any of the files (with the except to the change to the config.ini file that was made after the problem started).

We have tested extensively and the problem is definitely related to accessing the admin.cgi. Any ideas on what might be causing this ?


Donna
Staff / Moderator


Feb 5, 2009, 2:53 PM

Post #2 of 3 (2291 views)
Shortcut
Re: [Cathy] DB Filelock error [In reply to] Can't Post

Hi Cathy,

Hmm, you've gone through all the usual checks with the permissions, as that's usually the culprit... in which case, we'd probably have to take a closer look. Can you fill in a support request?

http://www.interactivetools.com/forum/gforum.cgi?post=69121#69121

Donna

--
support@interactivetools.com


Cathy
User

Feb 5, 2009, 5:35 PM

Post #3 of 3 (2288 views)
Shortcut
Re: [Donna] DB Filelock error [In reply to] Can't Post

This morning while waiting for a reply, since I'm two hours ahead of you, I decided to just upload the /exec folder files . That took care of the problem! Only thing I can figure is that the admin.cgi, or one of the other /exec folder files, had gotten corrupted somehow and re-uploading resolved it.

The thing that had me was that just even accessing the admin.cgi url, even without logging in, was messing things up. Gremlins in the machine!

Thanks anyhow.