Can you also tell what page was being requested and from what IP? As it is now, if someone (or perhaps a search engine's web crawler!) were to visit 'header.html' directly, they would receive such an error.
Can you reproduce this error log oddity, e.g. load this page a few times and see that your own IP is causing these errors?
Finally, have you turned display_errors On and set error_reporting to E_ALL to see if the errors are displayed?