Massive error.err file problems

[jmedinger]

Since upgrading from v7 to v8.5.1 we have seen the error.err file which is written to the cgi-bin directory grow wildly out of control - to the point that it exceeded the disk quota for the site bring the site down...

The last count was a 315Mb file racked up after 2 weeks of the site being online

This is a sample of the file...

Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:48, Internal Errors = REFPAGE:http://www.sitename.com/acatalog/index.html
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:48, Internal Errors = ACTION:Finish
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:48, Internal Errors = ACTION:Finish
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:48, Internal Errors = ORDERNUMBER:CO36AQ50014986
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:48, Internal Errors = ORDERNUMBER:CO36AQ50014986
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = Hello
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = HOME:index.html
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = HOME:index.html
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = ACTION:Done
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = ACTION:Done
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = REFPAGE:http://www.sitename.com/acatalog/index.html
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = REFPAGE:http://www.sitename.com/acatalog/index.html
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = RANDOM:0.694905171710165
Program = ORDERSCR, Program version = 507   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:49, Internal Errors = RANDOM:0.694905171710165
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:50, Internal Errors = Hello
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:50, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:50, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:50, Internal Errors = SECTIONID:pagenames.html
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = Hello
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = PRODREF:170742-BB
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = PRODREF:170742-BB
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = Hello
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = NOLOGIN:1
Program = SearchSc, Program version = 115   , HTTP Server = Apache/2.0.52 (CentOS)        , Return code = 999                 , Date and Time = 2007/07/03 16:51, Internal Errors = SECTIONID:toys-for-boys.html

Obviously the site is generating tonnes of error messages - is there any way that these can be identified as tracked back to their source?

Thanks

Jos

[stonda]

Hi
This problem is treated here :
http://community.actinic.com/showthread.php?t=24882
And as Bill says :"the error messages are a nuisance rather than a show stopper, but it does need more investigation"
Regards

[jmedinger]

This really is a show stopper however...

We reset the error.err file at 17.30 tonight and now, 50 minutes later it's already at 150K

Over a couple of weeks, this results in the site quota being exceeded and the site being brought down as no CGI scripts can then run.

The errors shown in the sample above are also completely different to the ones that were discussed in the thread you mentioned (incidentally I did read all of that before posting this thread) so I guess reverting cart scripts to their original state simply isn't going to send these errors away.

Anyone know of a way I can 'reverse engineer' the messages so I can identify where they come from and how to stop them?

Thanks

Jos

[dave_finlayson]

The errors on the other post are benign HOWEVER if there are alot in your file like the ones above I think they DEFINATELY need investigating. Call Actinic!

[NormanRouxel]

Did you have any customised Perl scripts in your V7 installation?

These would have been overwritten in the V8 upgrade.

[jmedinger]

Norman

There were a couple of very minor modifications made to one or two .pl files however these were bug fixes supplied by Actinic and were addressed in the new versions of the scripts for v8.

Other than that, no - all was standard Actinic...

Regards

Jos

[NormanRouxel]

OK. Best call on Actinic - It looks like something very strange is wrong. Or something is attacking your site (those "Hello" enties are suspicious).

You could also change your network settings and upload the entire site to a temporary server under a different domain name and see if you still get errors there.

There's also a possibility that you're running out of server resources and that's causing the problem. Again, switching to another temp server may help indicate that.