scheduler / cron problem: Bus error (core dumped)

[ehsander]

Hi all,

I've encountered the following problem (Version 5.2.0j (Build 5804)).

Some months ago, I set up a cronjob to enable the SugarCRM scheduler, which was working fine, until last evening, after adding a group mail inbox (monitored IMAP account), but I don't know for sure if it has caused this problem (connection test was ok)...

Whenever it checks the inbound email accounts, the cron mails me the error: "Bus error (core dumped)", after the job has timed out.

Using google, I only found references to OS / compiling errors and such, so it seems a bit of an "odd" error... The hosting provider claims that no changes have been made to the server configuration

Does anyone have any clue on this one?

Thanks!

Sander

[ehsander]

Still not solved this one, we did some Apache and SugarCRM log browsing, found no particularities. Anyone any clue?

[ehsander]

Server information can be found at phpinfo.antagonist.nl by the way .

[blackradius]

I can say that I have experienced the same error too.

[ehsander]

I can say that I have experienced the same error too.

Thanks for the response, interesting. Did you find any solution? Still having the problem?

Kind regards,

Sander

[ehsander]

The problem does not appear if all IMAP accounts are disabled by changing them to "inactive"...

[blackradius]

the job completes so I haven't been inclined to find what the real issue is as there are so many other issues to deal with.

If I find anything, I'll post back here.

[ehsander]

Thanks!

But... do you have any clue where to look?
I've checked out the Apache logs, sugarcrm.log, nothing particular... only this error returned by the cron. The job does not complete if any IMAP account (connection tested ok) is set to active.

Kind regards,

Sander

[blackradius]

it actually dumps the core, you could use a core file debugger to look at it.

[ehsander]

The error seems to be caused by one specific email we received on one account, which was unintentionally sent to 464 (!) email addresses using the CC-field (oh my god...), by one of our relations...

Ofcourse this is a somewhat odd scenario, but shouldn't Sugar have thrown at least an exception of some sort? It seems to me to be a bug...