Bad Lock Chains

lmaccallum · Post by **lmaccallum** » Wed Apr 26, 2006 11:33 am

Hello,

I am running Webinator Professional 5.1 on Solaris 10 x86

I modified the dowalk script to update the hosts on the output. This is allow the crawl to use an internal IP address and update the addresses to an external IP address.

I added 5 update statements: 1 to the html table, 2 to the refs table, and 2 to the error table.

The updates work but I get the following messages after I crawl the site:

Updating the URLs with the correct IP address for database /opt/webinator/texis/mepsredesignfull/db1

100 /opt/webinator/texis/scripts/webinator/dowalk(dispatch) 5183: Bad psl lock chain in the function unchain

100 /opt/webinator/texis/scripts/webinator/dowalk(dispatch) 5183: Bad nsl lock chain in the function unchain

100 /opt/webinator/texis/scripts/webinator/dowalk(dispatch) 5183: Bad ptl lock chain (-1, 1449) in the function unchain

100 /opt/webinator/texis/scripts/webinator/dowalk(dispatch) 5183: Bad ntl lock chain in the function unchain

Done updating the URLs with the correct IP address

What do these error messages mean? I don't see any documentation on error messages.

Post by **John** » Wed Apr 26, 2006 3:12 pm

It sounds as if there was an error in the locks, that was corrected when the walk started up. Was that a new
walk that was started, or did the SYSLOCKS file maybe get copied from somewhere?

It looks as if everything ended up OK though.

lmaccallum · Post by **lmaccallum** » Wed Apr 26, 2006 3:44 pm

Since I was modifying the dowalk script, I had run a "New" walk on an existing database several times in a row.

So what you are saying is that there is nothing to be concerned about - the messages are just a warning?

Can I delete the SYSLOCKS file before a new walk? I assume I cannot delete the file before a refresh walk.

Post by **John** » Wed Apr 26, 2006 4:49 pm

You should not generally delete the SYSLOCKS file, as there may be a database monitor process still using the file. Generally it will get cleaned up if there is an issue, and it does print the warning messages. You should make sure that it does not get modified by other processes, e.g. copying the files, backup/restores or file sharing across computers.