Error_log file just grow up

[Mark.B]

I would suggest at this point, if one of the users affected would please write up a bug report -
vB4 Bug
http://tracker.vbulletin.com/secure/...20&issuetype=1

Just fill in "Summary" and "Description", don't worry about any other fields.

Once done, if you want to post the bug report number / URL back here, I'll see what we can do to have someone investigate.

[slipkot]

Having the same issue. Also opened a ticket with #1360130 and created a jira issue

http://tracker.vbulletin.com/browse/VBIV-16079

[kemraj]

Thank you mark this is much more assuring, really hope this gets rectified soon. Someone did so already http://tracker.vbulletin.com/browse/VBIV-16079

[kh99]

nvm.

[bosss]

I did it (wrote bug report) and please some temporary fix ...file just growing up and cause database errors.
You should test before put vb 4.2.3 beta 4 in download section ...

regards

bosss

[Mark.B]

Thanks, I can't say what the cause is but the developers will now be able to look at it and advise what's going on.

"Watch" the bug to get any updates to it by email.

[kemraj]

Excellent wow now my Mobile app is not working, and i'm sure it has to do with this update getting "Unexpected server response"

[bosss]

SKIP_DS_ERRORS 

works not in my case ...file is 3.5 GB in one hour ...

but this

define('SKIP_ERRORS', true); 

slow process ...mean growing up file ...

[Mark.B]

None of the "SKIP_ERRORS" options has any effect in 4.2.3. They were for 4.2.2. But all they do is prevent notices and warnings being output to the screen - they do NOT stop them being logged in the server logs. that requires a change to php.ini on the server.

[bosss]

What you suggest - have this line in config.php or not ? Problem is that i must remove error_log file every few hours. otherwise site is not accessable ... get database error everybody who access site - please some fix or solution?

regards

bosss

[Mark.B]

What you suggest - have this line in config.php or not ? Problem is that i must remove error_log file every few hours. otherwise site is not accessable ... get database error everybody who access site - please some fix or solution?

regards

bosss

Doesn't matter whether you have the line in config.php or not - it has no effect in 4.2.3.

If it turns out to be a bug, there will be no fix until the developers provide one, which could be several weeks, or more.

If you're certain that this issue started with the upgrade to 4.2.3 then, as far as I am aware, there were no database changes from Beta 3 to Beta 4.
You could try backing up the database as a precaution, and then uploading the Beta 3 files again, to see if the issue stops.

[bosss]

I had not this problem before upgrade to beta 4 - as you can see some more users report same issue - file what rapidly growing up ... and i can not download beta 3 files ... mean to downgrade to beta 3 ...(in members area is only beta 4)

regards and thanks for help

bosss

[kh99]

What you suggest - have this line in config.php or not ? Problem is that i must remove error_log file every few hours. otherwise site is not accessable ... get database error everybody who access site - please some fix or solution?

You should be able to turn off php logging by setting log_errors=Off in your php.ini file.

[bosss]

Will try this solution... thanks for help

regards

bosss

[kemraj]

Doesn't matter whether you have the line in config.php or not - it has no effect in 4.2.3.

If it turns out to be a bug, there will be no fix until the developers provide one, which could be several weeks, or more.

If you're certain that this issue started with the upgrade to 4.2.3 then, as far as I am aware, there were no database changes from Beta 3 to Beta 4.
You could try backing up the database as a precaution, and then uploading the Beta 3 files again, to see if the issue stops.

Hey mark tell me if something just for clarification, when updating to the latest version (4.2.3 beta 4) i did an www.testsite.com/install/upgrade.php .So even if i did that their were no database changes right?, so i can safely downgrade to the previous version because its only template changes