Cron Daemon Problem

[ptdesigner]

Hello everybody.

After I update my system for 3.6 from 3.5.1 now, wen I receive a cron mail I receive another mail containing the following information:

 

Assunto (Subject): Cron <ptdesign@mercury> php -q /home/ptdesign/public_html/clients/admin/cron.php

Data: Sun, 10 Feb 2008 18:00:02 +0000

 

 

<br />

<b>Warning</b>: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cookie - headers already sent in <b>/home/ptdesign/public_html/clients/admin/../dbconnect.php</b> on line <b>0</b><br />

<br />

<b>Warning</b>: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cache limiter - headers already sent (output started at /home/ptdesign/public_html/clients/admin/../dbconnect.php:0) in <b>/home/ptdesign/public_html/clients/admin/../dbconnect.php</b> on line <b>0</b><br />

 

 

 

Any help will be helpfully.

Thanks

 

My mistake, this is in a wrong section.

[redroot]

I am receiving the exact same error after my upgrade from 3.5.1 to 3.6.0

 

<br />

<b>Warning</b>: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cookie - headers already sent in <b>/home/redroot/public_html/support/admin/../dbconnect.php</b> on line <b>0</b><br />

<br />

<b>Warning</b>: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cache limiter - headers already sent (output started at /home/redroot/public_html/support/admin/../dbconnect.php:0) in <b>/home/redroot/public_html/support/admin/../dbconnect.php</b> on line <b>0</b><br />

[Matt]

This is just a warning about there being output before the session started which PHP doesn't like. This is quite common when invoking a PHP file directly using php. It will not stop the cron functioning or running.

 

You should either change to using wget or get for your cron or set your control panel to send the cron output to "nobody". WHMCS will email you the cron report when it completes - you don't need the screen output emailing to you by your cp.

 

Matt

[redroot]

Switching it to a GET fixed the problem, thanks for the help Matt!

[Revolution]

I don't understand. Up until this last upgrade, my cron / piping has been perfect. Everrything is configured properly. Then I do the 3.6 upgrade and now I get the same error as listed above as well. Why would I need to change anything. Not sure why I need to. Why would the upgrade now produce the error. It was fine until now.

[TDub]

My cron stopped working after upgrading to 3.6 as well. I was using wget and it looks like the import path changed back to a default.

 

EDIT: Forgot, I use a scheduled windows task to handle this using WGET and somehow removed the wget folder. Restored it and it's fine again, so no issue.