Mailing List Archive: Bricolage: devel

soap xml story importing

Index | Next | Previous | View Threaded

rotoole at gmail

Oct 9, 2008, 7:37 AM

Post #1 of 4 (1493 views)
Permalink

soap xml story importing

Hi List,

I'm trying to import stories from a legacy cms into bricolage. The import is
working for most xml files, but many produce the error:
*
**Unable to execute SQL statement
Check the Apache error log for more detail.*

When I look at the apache log there is a ton of output to parse through,
most of it irrelevant. It's hard to find what I need, because the log
doesn't list the names of the xml files next to the error output and there
is a lot of output per error.

Is this the best way to debug these types of database errors? Is there a
more expedient way for bric to let me know what the specific issue is, like
in the SOAP error output as opposed to the log file.

Does anyone have any suggestion for the best way to attack this problem?

Best,
Ryan

greg at node79

Oct 9, 2008, 7:45 AM

Post #2 of 4 (1415 views)
Permalink

Re: soap xml story importing [In reply to]

Hi Ryan,

You could ask bric_soap for some extra debugging information. The --
verbose switch can be passed to bric_soap up to three times (each one
will add even more debugging goodness).

The third --verbose will give you a full XML dump of messages going
back and forth. More details on the error might be there and easier to
spot compared to the Apache error logs.

cheers,
-Greg

On 9-Oct-08, at 10:37 AM, Ryan O'Toole wrote:

> Is this the best way to debug these types of database errors? Is
> there a
> more expedient way for bric to let me know what the specific issue
> is, like
> in the SOAP error output as opposed to the log file.

rotoole at gmail

Oct 9, 2008, 12:07 PM

Post #3 of 4 (1413 views)
Permalink

Re: soap xml story importing [In reply to]

I've tried all three levels of verbosity but none yielded useful information
about the database error. That is still buried in the log.

Ryan

david at kineticode

Oct 9, 2008, 9:00 PM

Post #4 of 4 (1399 views)
Permalink

Re: soap xml story importing [In reply to]

On Oct 9, 2008, at 12:07, Ryan O'Toole wrote:

> I've tried all three levels of verbosity but none yielded useful
> information
> about the database error. That is still buried in the log.

I don't understand why your log is so verbose. What does your
bricolage.conf look like?

Best,

David

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads