We have been working on a new database which has been working fine for couple weeks but we are receiving lock errors as of today. I did find any documentation on the website. Would appreciate any help on this.
000 Could not create locks for database /data/WWW/database via monitor: Unsuccessful response code 500 (Failed) in the function TXcreateLocksViaMonitor
000 Could not open locking mechanism for database /data/WWW/database in the function TXdblockOpenViaMethods
000 Couldn't connect to /data/WWW/database in the function SQLConnect
Texis -version
Texis Web Script (Vortex) Copyright (c) 1996-2016 Thunderstone - EPI, Inc.
Commercial Version 7.05.1454612339 20160204 (x86_64-unknown-linux2.6.9-64-64)
This may be due to a permissions error. Make sure that the database dir and its parent dir are writable by the same -- non-root -- user that owns /usr/local/morph3/bin/monitor and all your databases. Make sure that monitor is setuid to that user.
Ok. But that's SYSINDEX, just one table. What are the perms on the database dir itself -- and its parent dir, which can affect it at database creation? And all the other files in the database?
Is monitor.log writable by apache? That `Unsuccessful response code 500 (Failed)' message in vortex.log should have occurred with a more detailed message in monitor.log.
Edit /usr/local/morph3/conf/texis.ini, look for the [Scheduler] section, and set Verbose=0x10 (i.e. just below the commented-out `;Verbose = 0'). Then restart monitor (monitor -k; monitor) and re-try accessing the database. If the `Unsuccessful response code ...' errors continue, look at monitor.log again.
Also, has any software changed on the system between when it was working and not? I notice the file size of the monitor executable is different than as distributed. It should be 9511704 bytes.