Awstats problems with S69

[dodedum]

OK I went to S69 to get rid of the problems with maill acocunts not working and now customers are complaining that awstats has stopped working gettting this error on 5 servers now.

Error: SiteDomain parameter not found in your config/domain file. You must add it for using this version.

Setup ('/home/domain/tmp/awstats/awstats.domain.com.conf' file, web server or permissions) may be wrong.
See AWStats documentation in 'docs' directory for informations on how to setup awstats.

So Nick is there a scripts/fixawstats or something?

Am I missing the meaning of the word STABLE????

Maybe we need another release version called SAFE find one that works and never upgrade it.

[ukhost]

Hi,

We had this problem with an EDGE build and now again with this STABLE build, we put in a ticket for the issue when it was on the EDGE build, but when they checked it, it had fixed its self half way through the day!!

Back again with the STABLE (69) release, off goes that support ticket again!!

Kind Regards,

Neil

[bdraco]

Please read your whm news:

Updated to awstats 5.1 (may cause errors for 24 hours after update).


Basiclly you just have to wait till awstats runs again so it creates a 5.1 friendly awstats conf

[bert]

Nick,

How can we &force& it to create the 5.1 friendly awstats conf ? We have servers that completely stopped logging awstats for a few days now.

[bdraco]

[quote:180b525925][i:180b525925]Originally posted by bert[/i:180b525925]

Nick,

How can we &force& it to create the 5.1 friendly awstats conf ? We have servers that completely stopped logging awstats for a few days now.[/quote:180b525925]

/scripts/runlogsnow should do it.

[Keegan]

With seperate installations of AWstats within customer accounts they are now getting permission errors.

I've run that bdraco but still having permission errors.

Multiple log pulls from one script in one domain no longer worked so we just used one account to pull their logs.

Guessing its a user issue, we cannot disable suexec