Description: ------------ Not sure what is going on. That's why I am reporting this bug. I just see this in my cron email. I wish I could provide more information to help but this is all I get. Fatal error: Call to undefined function: quote() in /home/www/facternet.com/freespace/includes/PEAR/Mail/Queue/Container/db.php on line 122 Test script: --------------- I don't know how to write a test script. Expected result: ---------------- I don't expect to see an error. Actual result: -------------- Fatal error: Call to undefined function: quote() in /home/www/facternet.com/freespace/includes/PEAR/Mail/Queue/Container/db.php on line 122

which version are you using? Can you try the latest CVS one? http://cvs.php.net/pear/Mail_Queue/

Thank you for the quick response. I have downloaded the CVS versions and am trying them. Hopefully my client won't receive any further errors in cron and I can get back to Christmas :-) Let me know if you need anything.

> Let me know if you need anything. yep, one thing: if you can confirm that the CVS version works fine, please close this bug report :-) Thanks for your help and happy Xmas!

The new file versions didn't fix the error.

what's the line of the error? Did you upgrade all the Mail_Queue files or just db.php? Have you checked for db connection problems just after the call to the constructor?

My client sent me notification that cron is now sending him a change history web page. What is going on? Here is the section of code used: include_once './mail_queue_config.php'; /* How many mails could we send each time the script is called */ $max_amount_mails = 50; /* we use the db_options and mail_options from the mail_queue_config */ $mail_queue =& new Mail_Queue($db_options, $mail_options); /* really sending the messages */ $mail_queue->sendMailsInQueue($max_amount_mails);

Ok I'm foolish. I have replaced the files with the CVS history logs instead of the sourcecode. I have since replaced the files with the sourcecode. Now to wait and see if the error surfaces.

any news? Can I close this bug report?

This bug still exists. I've tried checking out v1.1.4 from the CVS and that doesn't help.

can you add these lines at the beginning of the _preload() function? ============================================== if (!is_a($this->db, 'DB_common')) { return new Mail_Queue_Error(MAILQUEUE_ERROR_CANNOT_CONNECT, $this->pearErrorMode, E_USER_ERROR, __FILE__, __LINE__, 'db connection lost'; } ============================================== it looks like $this->db does no longer hold a valid db connection...

so, was it a "dropped connection" issue? Can I close this report or do you have something to add?

This problem seems to be still alive. I discovered that this has something to do with the error message “too many connections”. The MDB2 container or Mail_queue isn’t closing the DB connection properly. Every time I run the queue I see there is an additional MySQL process created, though sleeping but not appreciated. I think this error can be replicated by setting the max connections of the MySQL to < 5. Or do a SHOWPROCESS after a queue run. Info: PEAR mail_queue version 1.2.1 and MDB2 2.4.1 **** Cron error *** PHP Fatal error: Call to undefined function: quote() in /usr/share/pear/Mail/Queue/Container/db.php on line 122 **

I've added a check for a valid DB connection in _preload(). Please fetch the CVS version and retry. TIA.

I am the provebial 'noob' in regard to PEAR but i am getting a similar error in mdb2.php , line 109 error reads (slight edit): Fatal error: Call to undefined function: quote() in /home/content/x/x/x/pxxxxxe/html/pear/PEAR/Mail/Queue /Container/mdb2.php on line 109 it's a shared host, (my) 'local' version of PEAR installed yesterday with zero problems via go-pear.php (4th March 2008) versions: PEAR Base System 1.7.1 (stable) Mail_Queue 1.2.1 (stable) Can you confirm -in gentle noob terms- that this is definitely a connection issue? If so, how can i test to find out what the exact problem is? an error saying that the function is undefined is not all that helpful. It may be that i'm doing something dum, but apart from that it still seems that somewhere along the line this error is not being caught properly and that kinda is what's making me send this... naw... actually i'd just really like to know how to fix it :p Cheers pk