I enabled logging for mysqld.Then I wiped out my previous installation of interchange and started fresh with a new install and catalog. It exhibited the same behavior previously described. Then I went into mysqld.log to see what was happening. It shows all the successful connections and table creation from the install and the subsequent successful query of the database when I accessed the catalog while still logged into SSH. However, the error state that came up after I logged out of SSH and tried again to access the catalog was not recorded in mysqld.log.
This precedes the successful query:
060112 16:08:30 97 Connect suppressed on my_db
97 Query SET AUTOCOMMIT=1
The logfile ends with the following (immediately after the successful
query):
060112 16:08:51 98 Connect suppressed on98 Quit 060112 16:08:52 99 Connect suppressed on mysql
99 Query SET AUTOCOMMIT=1
99 Quit
Any attempt to access the catalog after logging the db_user out of SSH
is not recorded in mysqld.log.
Jeff Fearn wrote:
On 1/12/06, Simon Swegles <suppressed> wrote:I am fairly certain that this is the problem causing the error state: "serv /cgi-bin/serv/index.html Runtime error: table tree connect failed -- DBI connect('*****','*****',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /home/*****/interchange/lib/Vend/Table/DBI.pm line 581"Is there a message in your mysqld log? -- Jeff Fearn "Postmodernism: Once more without feeling." -- Geoffrey Nunberg _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
_______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.