Hmm. You'll get quite a lot of output but you can try setting the "plugin.lazysearch2" log setting to DEBUG and "database.sql" to INFO and seeing what you get logged just prior to the point where you get that error about the "customsearch" column.
Could you try setting those logging options (and saving them so they survive a restart), then restart the server and capture the log leading up to the error? If the log is large (and it likely is!), could you email it to "stuart -at- hickinbottom dot com" to spare the list? Thanks, Stuart On 17/01/2010 8:31 PM, dip wrote: > hickinbottoms;507502 Wrote: > >> On an Ubuntu installation I think you can do that with the following: >> >> echo "desc tracks" | mysql -v --protocol TCP -u slimserver -P 9092 >> slimserver >> >> Substitute "albums", "contributors" and "genres" for "tracks" in the >> above command to look in each table. In each case it should dump the >> names of the columns in each table, and there should be a >> "customsearch" >> in each case. >> > I did that and in each output a "customsearch" is included. So that > seems not to be the problem. > > Anything else I can try? > > > _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
