Very useful is database statement logging at first. Can you reproduce the problem at least once on a server where you have permissions to change database server configuration? Which database do you use? I explain the simplest form for Postgresql and MySql.
For Postgresql in the file /etc/postgresql/*/main/postgresql.conf uncomment the line #log_statement = 'none' and change it to log_statement = mod # This controls which SQL statements are logged. With value "mod" logs all ddl statements, plus data-modifying statements such as INSERT, UPDATE, DELETE... read http://www.postgresql.org/docs/current/static/runtime-config-logging.html for more details Restart Postgresql server. Log file is usually /var/log/postgresql/postgresql-*-main.log* If you use MySQL: -- file /etc/my.cnf -- [mysqld] # usual options # ... # binary log for satchmo log-bin=/var/lib/mysqlyour-mysql-binary-log-file-prefix binlog-do-db=name_of_your_satchmo_database # for more details http://dev.mysql.com/doc/refman/5.0/en/binary-log.html --- Restart MySQL server. Logged commands can be later converted from binary form to text form by this command: $ mysqlbinlog /var/lib/mysqlyour-mysql-binary-log-file-prefix.* >output.sql In both cases make a backup of original database at the same time. Also regularly save the http log to be not overwritten old logs by a log rotate. This is sufficient for later analyzing and for reconstructing any previous state of database. (I am also interested in this error. If you possibly can not analyze logs by yourself and very probably can not give out of your hands contained private data, it would be time consuming for both but still possible to analyze it interactively and some contract would by necessary.) -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
