Iām getting 2 main errors on my system, loads of cron errors and a few subpanel errors. Iād like to tackle the cron errors first, as there are so many of them.
Can you suggest which log files I should start looking at. Hereās the main system log, or part of it.
Thanks
Wed Jul 4 17:32:02 2018 [14653][1][FATAL] Job 2aa14dbe-0daa-6ae0-1afa-5b3cf6261779 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:33:01 2018 [14658][1][FATAL] Job 6f96fec3-8122-7f0c-f32a-5b3cf6aa8b3e (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:34:01 2018 [14663][1][FATAL] Job ce481094-6b4c-25d4-4fd0-5b3cf6a6a4ad (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:35:02 2018 [14668][1][FATAL] Job 25f0c007-af7b-2631-f1b6-5b3cf7c62926 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:36:01 2018 [14674][1][FATAL] Job 88947a0e-cd8d-36c7-fe41-5b3cf7831935 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:37:02 2018 [14679][1][FATAL] Job cd68aa35-08da-ee57-b5bb-5b3cf7eb6650 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:38:01 2018 [14684][1][FATAL] Job 37e3111b-5a87-3cca-f5c4-5b3cf7a0b569 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:39:01 2018 [14691][1][FATAL] Job 8c31235c-70e8-1c7d-0c34-5b3cf8adc7a8 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:40:02 2018 [14738][1][FATAL] Job ee109535-cba8-27dd-557b-5b3cf8e681d5 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:41:01 2018 [14762][1][FATAL] Job 3dcc6b90-d654-446d-f3e9-5b3cf8d2738b (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:42:02 2018 [14768][1][FATAL] Job 6bab0f65-7260-481b-d548-5b3cf88ff575 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:43:01 2018 [14773][1][FATAL] Job 3e18b441-7695-67eb-15f5-5b3cf9218883 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:44:01 2018 [14778][1][FATAL] Job a5ec1407-9e60-dcbc-a954-5b3cf912ae18 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:45:02 2018 [14783][1][FATAL] Job e97ce875-500a-c7b3-f439-5b3cf98064da (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:46:01 2018 [14789][1][FATAL] Job 5acec61c-2244-9d45-8aa2-5b3cf9e1a29c (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:47:01 2018 [14794][1][FATAL] Job a38bbe3a-e0a4-dca4-4a8d-5b3cfa906b40 (Run Report Generation Scheduled Tasks) failed in CRON run
Wed Jul 4 17:48:02 2018 [14799][1][FATAL] Job b87b0c0d-a353-2b78-b43c-5b3cfab76d00 (Run Report Generation Scheduled Tasks) failed in CRON run
If you look also at php_errors.log (or whatever your web server log is called) you can cross the information. For example, youmight have a PHP error for each of those CRON errors, saying why the job failed.
Are you using Scheduled Reports? If not, you can simply turn off that job. If you are, you can try deleting existing Reports to see if any one of them is causing the errors.
Iāve been trying to upload the error.log file, Iāve tried dragging the file to the add file, but canāt seem to get it going, so hereās the dropbox link to the file https://www.dropbox.com/s/29taq89y0ms1hh3/error.zip?dl=0
Thereās 14 log files in the /var/log/apache2 area.
About the log rotation scheme, thatās basic Apache configuration, has nothing to do with SuiteCRM. Google for how-toās, you will find many.
Examining your log, I think itās worth starting by fixing this frequent warning
Declaration of MyEmailsDashlet::process() should be compatible with DashletGeneric::process($lvsParams = Array, $id = NULL) in /var/www/html/suitecrm/modules/Emails/Dashlets/MyEmailsDashlet/MyEmailsDashlet.php on line 48, referer: http://193.37.226.213/suitecrm/index.php?action=ajaxui
Which version of SuiteCRM are you running? Can you make this line here
Iāve rebooted it nothing seems broken, but then it didnāt before. Hereās the link to the erorlog after the edit and reboot, and the altered php file
That fix is already in more recent versions of SuiteCRM (the link I gave you was to the code of 7.10.7), for some reason it is not included in your version (I guess it should be because itās LTS).
I donāt have time now to examine your full logs. If you still have the cron errors try looking into Scheduled Reports and test them from there to see if they work well.
You can go in Admin / Schedulers and check each job individually.
Thereās one for Reminders, and one for Scheduled Reports. See ālast ran successfullyā property. (also check if the timezone looks right on those times).
Maybe (just maybe) a FATAL error on one job is preventing the other jobs from running. You can try disabling the Scheduled reports job to see if the others run.
The email scheduler is run quite frequently, but the scheduled report says
Job Name: Run Report Generation Scheduled Tasks
Status: Active
Date & Time Start: 01/01/2015 12:00
Active From: Always
Date & Time End: Active To: Always
Last Successful Run: Never
Interval: As often as possible.
Execute If Missed: Job:
function::aorRunScheduledReports
Date Created:
03/21/2018 17:19 by Administrator
Date Modified:
07/06/2018 16:01 by Administrator
So it looks like this has probelms, what would you recommend?
It makes sense that it doesāt run correctly, because itās leaving FATALs in the logs.
As I wrote above, either disable the job if you donāt need it, or try to go in the Scheduled Reports module an delete individual Reports until you find out which one is causing the error.
I turned off āRun Report Generation Scheduled Tasksā and the relevant cron errors went away. Half way there.
I deleted the report and turned reporting back on, and the errors have reoccurred.
Even thought the report runs, and produced valid results, the reporting module is faulty in some way.
Are there any know problems with the reporting module in my version? Can I opy a known good copy of the rporting module over and see if the problems go?
I wonder if the fact the reminder pop ups donāt work is related. I assumed this was a browser issue, but in retrospect I wonder if theyāre related.
Getting the reminders to work sometimes has additional challenges (like timezones in CLI PHP). But you can start by checking if āRun email reminder Notificationsā is running successfully. I think the other reminders (on-screen) also depend on this (not sure though).
I find it weird that we canāt figure out your Reports problem better. We should be getting specific errors wither in suitecrm.log or php_errors.log when a specific report failsā¦ itās hard to troubleshoot from a distance, without informationā¦
Thanks for that, I have the email reminders working, itās the pop up ones that seem to be failing, but Iād rather leave that till the Cron issue is fixed.
Ok, I donāt normally analyze full logs people send me, but I did have a look at yours and this is my advice
clear old stuff from your logs, theyāre getting big and hard to manage in a text editor
in Admin / System settings, increase your log level to Debug. Now, after a minute, you should have the same Job failed Fatal error, but you also have a bunch of messages before giving you clues into what SuiteCRM was trying to do when it failed.
in error.log you have messages that might explain why reminders arenāt working - but as you said, letās leave that for later
Iāve had a look at the log, after cleaning it up. Bear in mind Iām not a programmer or developer. but I think the version of PHP may be incompatible, from
Wed Jul 11 20:39:02 2018 [1364][1][DEPRECATED] Formatting correction: SchedulersJobs->failure_count had formatting automatically corrected. This will be removed in the future, please upgrade your external code
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] Hook called: SchedulersJobs::before_save
[color=#ff0000]Wed Jul 11 20:39:02 2018 [1364][1][DEPRECATED] SugarBean.php: preprocess_fields_on_save() is deprecated[/color]
Wed Jul 11 20:39:02 2018 [1364][1][INFO] Query:UPDATE job_queue
SET assigned_user_id=ā1ā,name=āRun Report Generation Scheduled Tasksā,date_modified=ā2018-07-11 19:39:01ā,scheduler_id=ā8a8367f2-3503-68ac-4c3e-5ab2943d2a88ā,execute_time=ā2018-07-11 19:39:00ā,status=ādoneā,resolution=āfailureā,message=āUnexpected failure, please check PHP logs and suitecrm.log\nā,target=āfunction::aorRunScheduledReportsā,data=NULL,requeue=0,retry_count=NULL,failure_count=1,job_delay=0,client=āCRON00a00c65aa19870da6b1b6a14ee132df:1364ā,percent_complete=NULL
WHERE job_queue.id = ā7fb4a2d6-18b5-8912-a1bd-5b465ce6f1feā AND deleted=0
Wed Jul 11 20:39:02 2018 [1364][1][INFO] Query Execution Time:0.0084750652313232
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] SecuritySuite: Get SecuritySuite Enabled Modules: SELECT lhs_module, rhs_module FROM relationships WHERE deleted=0 AND (lhs_module = āSecurityGroupsā OR rhs_module=āSecurityGroupsā)
Wed Jul 11 20:39:02 2018 [1364][1][INFO] Query:SELECT lhs_module, rhs_module FROM relationships WHERE deleted=0 AND (lhs_module = āSecurityGroupsā OR rhs_module=āSecurityGroupsā)
Wed Jul 11 20:39:02 2018 [1364][1][INFO] Query Execution Time:0.00035405158996582
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] Hook called: SchedulersJobs::after_save
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] Creating new instance of hook class AOD_LogicHooks without parameters
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] Creating new instance of hook class AssignGroups without parameters
Wed Jul 11 20:39:02 2018 [1364][1][DEBUG] Creating new instance of hook class AOW_WorkFlow without parameters
Those ādeprecatedā messages are just warnings for the future. The SuiteCRM team will take care of those whenever theyāre approaching the moment to drop compatibility with the older versions.
Iāll try to look for more clues in your logs tomorrow.
hello Mr. pgr,
I seen that you helped many people plz help me too
actully whenever i running cron.php using task schedular itās showing error bad data passed in; return to homepage.