17

I found in my error log this (Note: i didn't removed the filename)

Of course I don't have any script with 1 bn lines.

PHP Version 5.3.3-7
Apache 2

The other weird thing is that I have a 

set_error_handler( 'myHandler' );

To write in the error log other inforamtion too, but with this error it seems PHP just ignores my error_handler. I don't have any code that can generate this errore before my call to set_error_handler

Edit

  • Debian at 64Bit
  • I didn't edit, in the error log there aren't any filename, in fact I don't know which script causes this.
  • I have APC installed
Improve this question
17
  • looks like a bug in PHP for the line number. If this isn't a production server, I'd attempt to downgrade PHP and see what line number you get. Then you'd be able to report it. Commented Nov 13, 2011 at 9:40
  • 3
    This question is best asked in the general user's PHP mailing list, and I suspect that you might have to raise a bug request. In all likelihood the line counter has had an arithmetic overflow of some sort. Commented Nov 13, 2011 at 9:42
  • 1
    Can you provide the script that produces this in its entirety? Do you have looped requires? Commented Nov 13, 2011 at 9:55
  • Did you edit the error log and removed the filename or was there no filename? Are you using a 32bit or 64bit system? Commented Nov 13, 2011 at 9:57
  • 6
    1768776801 is 0x696d6461 in hex, and the the four bytes of this number in little-endian order are the ASCII codes for a, d, m and i. I'll second @YzmirRamirez's suggestion that something funny is going on. Commented Nov 13, 2011 at 10:12

1 Answer 1

Reset to default
3

This is more a comment than an actual answer:

You need to find out which actual code is triggering the error. As long as you don't it's hard to say what specifically is going on.

To start debugging, ensure that you have configured error logging in your php.ini so it's independent to runtime configuration.

Then you can install xdebug and add backtraces to your log. The important part is here, that it is independent to set_error_handler.

This logging information should already give you more insight. If not, start with remote debugging and step through the code until the warning occurs.

Related Question:

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Probably your custom error handler is triggering the problem. Could explain why no file is given, but that's guessing only (which should be prevented in debugging). Post your error handler code anyway. But don't rely to your handler in this case, check with xdebug if you can find out more. Should give you results faster. Enable it only if a specific request header is set via .htaccess so you can reproduce on your own but the live site's normal users are not that affected by it. In any case, you introduce your (less tested than xdebug's code) to the live site?
Well I would at least suspect it, because normally PHP does not track files and line numbers when invoking it (as it's the error handler), but you should verify this behaviour. What happens if you remove your error handler and just log the errors? Does they still happen?
You can't reproduce, you don't even have access logs. You don't want to debug. Fly blind and fly high. Good luck! (Does not sound that you're worried enough)
yes123, why don't you say upfront that you're using APC? It re-orders all code, so it sounds at least plausible APC is related to what happens.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.