Re: cron job and headers sent error [message #182769 is a reply to message #182768] |
Sun, 08 September 2013 15:35 |
Richard Yates
Messages: 86 Registered: September 2013
Karma:
|
Member |
|
|
On Sun, 08 Sep 2013 16:40:30 +0200, "J.O. Aho" <user(at)example(dot)net>
wrote:
> On 08/09/13 15:36, Richard Yates wrote:
>> I have a script that runs automatically every night that shortens some
>> tables. It has been working fine (Actually still is doing what it is
>> supposed to). However I started getting an email warning notice when
>> it runs. In says headers have already been sent in line two of the
>> database Connection script that is included. I cannot figure out how
>> anything is being sent. The connection script does not output
>> anything. Line 2 identifies whether the script is running on the local
>> or production server. Any ideas where the error is coming from? Here
>> are the warning message, the cron script and the included connection
>> script:
>>
>> -------- warning notice
>>
>> <b>Warning</b>: session_start() [<a
>> href='function.session-start'>function.session-start</a>]: Cannot send
>> session cookie - headers already sent in
>> <b>/home/twpalygj/public_html/Connections/gleanslo.php</b> on line
>> <b>2</b><br />
>
> This is a warning you usually get when you have white spaces or bom
> sequence in your files. Check all your files that are used, that they do
> not have anything before or after the PHP tages (<?php and ?>).
Thanks. I will check again for spaces. What is 'bom sequence'?
> As you are anyway running a cron job, why do you call it over tcp/ip?
I don't know what you mean by calling it over tcp/ip. It is set up via
cPanel and runs automatically on the domain host server.
> I would recommend you to rewrite the cron job to just connect to the
> database and do it's job,
Do you mean putting the connection script directly into the cron
script rather than using an includes()?
> do have error handling in the script which
> gives you proper explanations why something goes wrong if something does
> that.
The folder on the production server is outside of the 'public_html'
root folder so I cannot dorectly run it in my browser. I have to test
it inside another folder on my local server.
> A good thing is also log to syslog so you can see the job has been
> properly done and you can also forward that to splunk or similar.
The domain host has the cron job in a folder that I can upload to. The
error_log there has the same warning message that was sent. I do not
see any syslog. I do not know what splunk is.
|
|
|