@Rumbelstilzchen,
As I said before,I'm not a profi in php, but.... if I see it with my dumby eyes :
1. I have not a remote php editor, I should have a remote hexa-editor to change only one byte ;
2. not earlier, but now I 've got a look at the content of that file,
cache_visitors.php is storing data in an array.
It was not ready when it stopped working, so it ends with a comma.
last used item was a search on "veranda verosol", found at 14 44 53 in the file pattern_referer.dta, wich seems to be a normal csv file, delimited with a pipe.
because both lines, 53 and 54 holds no scilly characters,
Zitat:Brunotti |10717
holds only a hex 20 is a normal space character, wouldn't harm a string as far as I can see.
so far, not good
If I should remove that particular space character in a "text-database-file" it would be only and shortly waiting untill the next "explosion", because we did nothing with the source of the problem.
Looking at these dta's, all the same pipe delimited's, :
logdb.dta,
logdb-counter.dta
are all ending on a hex 0A followed by a null byte.
pattern_referer.dta ends with a null byte, without a hex 0A.
A.
Could it therefore be possible, the source script is looking behind the EOF, ends unproperly without displaying an error because of passing 30 seconds php script working time ? ( before asking : I cannot change that time) or passing beause of surpressing errors ?
B.
Wich script is handling this , so I can look at it ?
C.
wich script is handling the ( omitted) 0A ....null byte sequence
Perhaps then we will find the source of the .. remember, I had this error also in the former versions.
But if I'm the only one with this kind of huge files, it's the wrong trail and is Web-statistik only usable with smaller websites or it needs a longer php working time than 30 seconds.