Log file shows fatal errors triggered by scheduler after setting up marketing e-mail

[jsoct]

Hello,

I installed SugarCRM 5.2.0c and activated the cron scheduler
Then I planned marketing e-mails using "sendmail", same messages appear when using SMTP

Now every time the cron scheduler is triggered, these lines below appear in the sugarcrm.log file:
(the first line only appeared once)

- How should I interpret these messages: "--->>>> 1" and ">>>>" ?
- How can I get a more detailed error description?

Mon Mar 30 02:21:03 2009 [23595][1][FATAL] If you see a whole string of these, there is a chance someone is attacking
your system.
Mon Mar 30 02:22:02 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:02 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:02 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] --->>>> 1
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] >>>>
Mon Mar 30 02:22:03 2009 [23630][1][FATAL] --->>>> 1

OS Linus SUSE 10.3
Sugar 5.2.0c
apache 2.2.4
php 5.2.6
mysql 14.12

[along]

I am showing the same thing after upgrade to 5.2.0c from 5.1. Never seen this before. They coincide with the run of the sugar cron job every 5 minutes. I've narrowed the source down in my case to scheduled job function:ollMonitoredInboxes, as when I change the frequency to 10 minutes, the errors also change to every 10 minutes.

Sugarcrm 5.2.0c
Apache 2.2.3
PHP 5.1.6

[along]

Just for kicks, I installed a clean copy of 5.2.0c with clean database and I see the same fatal errors immediately.
I used php 5.2.9 and MySQL 5.1.

[along]

Here is the answer, from another thread...

http://www.sugarcrm.com/forums/showt...6gt%3B%26gt%3B

refers to a bug that is fixed in the next patch. It's a harmless bug.