Simon Swegles wrote:
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=1The 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 mysql99 Query SET AUTOCOMMIT=199 Quit Any attempt to access the catalog after logging the db_user out of SSH is not recorded in mysqld.log.
That is odd. You did set the correct SQL user in the catalog configuration ? BTW: And yes, top posting is annoying. Bye Racke _______________________________________________ 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.