AWStats web statistics page does not work as expected

Follow

Comments

8 comments

  • Avatar
    Luis Zubeldia

    step 2, wich file i have to put Enable=0 ?

     

    -rw-r--r-- 1 root root 1664 nov 29 19:12 CentOS-Base.repo
    -rw-r--r-- 1 root root 1309 nov 29 19:12 CentOS-CR.repo
    -rw-r--r-- 1 root root 649 nov 29 19:12 CentOS-Debuginfo.repo
    -rw-r--r-- 1 root root 314 nov 29 19:12 CentOS-fasttrack.repo
    -rw-r--r-- 1 root root 630 nov 29 19:12 CentOS-Media.repo
    -rw-r--r-- 1 root root 1331 nov 29 19:12 CentOS-Sources.repo
    -rw-r--r-- 1 root root 2893 nov 29 19:12 CentOS-Vault.repo
    -rw-r--r-- 1 root root 957 dic 27 18:37 epel.repo
    -rw-r--r-- 1 root root 1056 dic 27 18:37 epel-testing.repo
    -rw-r--r-- 1 root root 353 may 2 07:55 plesk-migrator.repo
    -rw-r--r-- 1 root root 614 may 2 03:32 plesk.repo
    -rw-r--r-- 1 root root 636 may 2 06:12 tortix-common.repo

    0
    Comment actions Permalink
  • Avatar
    Nikolay Zhmuk

    2Luis, to all of them, except the following ones:

    -rw-r--r-- 1 root root 1664 nov 29 19:12 CentOS-Base.repo
    -rw-r--r-- 1 root root 1331 nov 29 19:12 CentOS-Sources.repo
    -rw-r--r-- 1 root root 2893 nov 29 19:12 CentOS-Vault.repo
    -rw-r--r-- 1 root root 353 may 2 07:55 plesk-migrator.repo
    -rw-r--r-- 1 root root 614 may 2 03:32 plesk.repo
    -rw-r--r-- 1 root root 636 may 2 06:12 tortix-common.repo

    To verify that proper package is installed, find awstat package and retrieve the information about the vendor:

    # rpm -qa | grep awstat
    awstats-7.4-centos7.17031414.noarch
    # rpm -qi awstats-7.4-centos7.17031414.noarch | grep Vendor
    Vendor : Plesk

    0
    Comment actions Permalink
  • Avatar
    Petr Voinov

    when epel (or other third party repo) is enabled, you can simply put:

    exclude=awstats*

    line at /etc/yum.repos.d/epel.repo, [epel] section.

    After this:

    1. yum remove awstats

    2. run pleks autoinstaller and reinstall awstats there.

    This will allow normal yum updates afterwards.

     

    1
    Comment actions Permalink
  • Avatar
    Pavel Mikhaylov (Edited )

    Hello Petr,

    Thank you for your input.

    The article has been modified with consideration of your recommendations.

    0
    Comment actions Permalink
  • Avatar
    Eric Bardoul

    Bonjour, 

    Le point 3 n'est pas clair pour le néophyte que je suis.

    Quels sont les référentiels tiers ? Ceux qui ne commencent pas par plesk ni par CentOS ?

    Ou faut il ajouter exclude=awstats* exactement ? A la fin ? Dans une section précise ?

    J'ai fait l'ajout en début de tous les fichiers trouvés qui ne commencent pas par plesk et j'ai une erreur  à l'étape 4 :

    File contains no section headers.
    file: file:///etc/yum.repos.d/CentOS-Base.repo, line: 13
    'exclude=awstats*\n'

    Merci de votre aide.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Eric, 

    > What are the third-party repositories? Those who do not start with plesk or CentOS?

    Yes, you are correct. These are repositories not provided by Plesk or CentOS.

    > Or should we add exclude=awstats* exactly? At the end ? In a specific section?

    Usually, it is enough to end at the end of the repository file.

    An example may be found here

    0
    Comment actions Permalink
  • Avatar
    Bob B (Edited )

    This issue is likely to occur when installing many of the available Plesk extensions, because some extensions enable the epel.repo.  

    There should be a way to:

    * Inform administrators that this will happen
    * Require extensions that enable 3rd party repos to inform admins about this
    * Have Plesk check for 3rd party repos and notify the admin

    For example, I recently installed the Warden Anti-spam and Virus Protection extension, which enabled the epel.repo.  That has been installed for some time but I've only now accidentally noticed that Awstats was no longer working.  All this time it would have been broken for our customers.

    Webalizer had also been updated from the epel.repo likely due to the same issue.  I followed the same steps to uninstall and reinstall Webalizer, as well.

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    Hi Bob B,

    Thanks for your feedback.

    I've checked in my test environment, that indeed Epel repo can be enabled, but also that the version provided by Plesk (at least for the CentOS 7) is higher than the one contained in Epel repo, so it should be kept the version from Plesk repos instead.

    Anyway, I've created this uservoice: When installing extensions, after install, 3rd party repos should remain disabled

    Please feel free to vote and comment there, so Developer team will read that.

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request