I don't know if Path Filter has anything to do with this, but I'm desperate. The site is going live tomorrow.
Suddenly I get:

 * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 37 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 37 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 10' at line 1 query: LIMIT 0, 10 in /home/public_html/includes/database.mysql.inc on line 172.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 100' at line 1 query: LIMIT 0, 100 in /home/public_html/includes/database.mysql.inc on line 172.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 37 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 100' at line 1 query: LIMIT 0, 100 in /home/public_html/includes/database.mysql.inc on line 172.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 100' at line 1 query: LIMIT 0, 100 in /home/public_html/includes/database.mysql.inc on line 172.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 37 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 37 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 100' at line 1 query: LIMIT 0, 100 in /home/public_html/includes/database.mysql.inc on line 172.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 58 in /home/public_html/includes/database.mysql.inc on line 438.
    * user warning: Query was empty query: in /home/public_html/includes/database.mysql.inc on line 172.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 100' at line 1 query: LIMIT 0, 100 in /home/public_html/includes/database.mysql.inc on line 172.

Comments

RobRoy’s picture

RobRoy commented
Status: Active » Postponed (maintainer needs more info)

Don't think so. Path Filter doesn't really do any database interaction and includes/database.mysql.inc is calling those errors. You can try a var_dump(debug_backtrace()); after some of those preg calls to see what is calling that, but I don't think it's Path Filter.

Boletus’s picture

Boletus commented

Would you please care to elaborate on that? How do I do a var_dump(debug_backtrace());
I am mostly a administrator of Drupal. This is a complete nightmare...

RobRoy’s picture

RobRoy commented
Category: bug » support
Status: Postponed (maintainer needs more info) » Active

Put a var_dump(debug_backtrace()); after the preg_replace on line 438 in database.mysql.inc. Then you'll see a bug dump that will trace back from that preg
call to whatever code called it (so look for a module in that list).

Also you can just disable your contrib modules one at a time and see when it clears up.

#drupal-support on IRC is a good place to get real time help with that stuff also.

Boletus’s picture

Boletus commented

It seems the error showed up in the log when the Sitemap module was called by google.

Can you dechiper some information from this log entry?

Type	php
Date	Wednesday, March 7, 2007 - 22:51
User	Anonym
Location	http://www.sitename.se/gsitemap
Referrer	
Message	You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISTINCT(n.nid)), n.type, n.status, n.promote, s.comment_count, n.changed, g.pre' at line 1 query: SELECT DISTINCT( DISTINCT(n.nid)), n.type, n.status, n.promote, s.comment_count, n.changed, g.previously_changed, s.last_comment_timestamp, g.previous_comment, g.priority_override FROM node n LEFT JOIN node_comment_statistics s ON n.nid=s.nid LEFT JOIN gsitemap g ON n.nid=g.nid LEFT JOIN url_alias u ON src=CONCAT('node/', n.nid) INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'term_access'))) AND ( n.status > 0 AND (g.priority_override >= 0 OR g.priority_override IS NULL) AND n.type NOT IN ('')) in /home/public_html/includes/database.mysql.inc on line 172.
Severity	error
Hostname	66.249.65.8

There is no line 438 as far as I can see? It ends at line 425.

RobRoy’s picture

RobRoy commented
Status: Active » Closed (won't fix)

Hmmm...not sure, but you should try one of the support channels. It could have to deal with any access modules you have installed. Good luck!

Boletus’s picture

Boletus commented
Status: Closed (won't fix) » Closed (fixed)

There is a bug in the PCRE library that comes to life with PHP 5.2.1. The solution was to downgrade PCRE from 7.0 to an older version.

This seems to have taken care of my problem. Touch wood...