The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Upgrade to 11.36.0.2 to 11.36.0.4 fails on Munin RPM

Discussion in 'General Discussion' started by wdwms, Jan 31, 2013.

  1. wdwms

    wdwms Member

    Joined:
    Jan 31, 2005
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    3 days in a row now we've been seeing this:

    PHP:
    20130131.222935]   Downloading http://httpupdate.cpanel.net/RPM/11.36/centos/5/i386/rpm.md5
    [20130131.222935]   cpanel-perl-514-Cache-Cache-1.06-1.cp1136.i386.rpm already downloaded
    [20130131.222935]   cpanel-perl-514-munin-1.4.7-3.cp1136.i386.rpm already downloaded
    [20130131.222935]   All files Staged
    [20130131.222935]   Testing if the newly downloaded RPMS can be installed without conflict
    [20130131.222935]   Testing RPM transaction
    [20130131.222935]    file /etc/init.d/munin-node from install of cpanel-perl-514-munin-1.4.7-3.cp1136.i386 conflicts with file from package munin-node-1.4.7-3.el5.noarch
    [20130131.222935]  file /etc/munin/munin-node.conf from install of cpanel-perl-514-munin-1.4.7-3.cp1136.i386 conflicts with file from package munin-node-1.4.7-3.el5.noarch
    [20130131.222935Exit Code2
    [20130131.222935] ***** FATALTest install failed:  file /etc/init.d/munin-node from install of cpanel-perl-514-munin-1.4.7-3.cp1136.i386 conflicts with file from package munin-node-1.4.7-3.el5.noarch
    [20130131.222935]  file /etc/munin/munin-node.conf from install of cpanel-perl-514-munin-1.4.7-3.cp1136.i386 conflicts with file from package munin-node-1.4.7-3.el5.noarch
    [20130131.222935]   The Administrator will be notified to review this output when this script completes
    [20130131.222935E Error testing if the RPMs will installDied at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 12517.
    [20130131.222935E Detected events which require user notification during updatenowWill send iContact the log
    [20130131.222935]   Removing staged files and directories for binaries/linux-i386cpanel
    [20130131.222935]   Removing staged files and directories for x3
    [20130131.222935]   Removing staged files and directories for x3mail
    => Log closed Thu Jan 31 22:29:35 2013
    [20130131.222935E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1359689314.logfailedexited with code 1 (signal 0)
    => 
    Log closed Thu Jan 31 22:29:36 2013
    How should we get by this error? things have been fine for 3 years w/out an issue.. this came out of the blue...
     
  2. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Thank you for reporting this. I have filed the issue with development. In the meantime you should be able to work around this by uninstalling the CentOS/RHEL munin RPM.
     
  3. wdwms

    wdwms Member

    Joined:
    Jan 31, 2005
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Whats the best way to do this?
     
  4. bmiguel84

    bmiguel84 Registered

    Joined:
    Feb 1, 2013
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Yeah... same error here.
    Just received an email from my server:

    "Problems were detected with cPanel-provided files which are RPM controlled.
    If you did not make these changes intentionally, you can correct them by running:

    > /usr/local/cpanel/check_cpanel_rpms --fix

    The following RPMs are found to be altered from their original install state:
    cpanel-perl-514-munin,1.4.7,3.cp1136,/etc/init.d/munin-node
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-check
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munindoc
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node-configure
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-run
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/whostmgr/docroot/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/lib/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/lib/munin/plugin-state
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/log/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/opt/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/run/munin"

    But, that script does not exist. It better to uninstall Munin until this bug is fixed?

    - - - Updated - - -

    Yeah... same error here.
    Just received an email from my server:

    "Problems were detected with cPanel-provided files which are RPM controlled.
    If you did not make these changes intentionally, you can correct them by running:

    > /usr/local/cpanel/check_cpanel_rpms --fix

    The following RPMs are found to be altered from their original install state:
    cpanel-perl-514-munin,1.4.7,3.cp1136,/etc/init.d/munin-node
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-check
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munindoc
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node-configure
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-run
    cpanel-perl-514-munin,1.4.7,3.cp1136,/usr/local/cpanel/whostmgr/docroot/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/lib/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/lib/munin/plugin-state
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/log/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/opt/munin
    cpanel-perl-514-munin,1.4.7,3.cp1136,/var/run/munin"

    But, that script does not exist. It better to uninstall Munin until this bug is fixed?
     
  5. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    You should be able to remove the operating system provided munin RPM via the following:

    yum erase munin-node
     
  6. mcongosto

    mcongosto Member

    Joined:
    Aug 1, 2011
    Messages:
    22
    Likes Received:
    0
    Trophy Points:
    1
    After latest update (build 4) munin stoped working. munin-node is running but nothing is showing in the graphs.

    Log shows things like this:


    Code:
    2013/02/02-08:52:11 [7213]      Logfile '/var/log/exim_mainlog' is not readable
    2013/02/02-08:52:11 [7213] Service 'exim_mailstats' exited with status 9/0.
    root@server [/var/log/munin]# tail munin-node.log
    2013/02/02-08:52:11 [7213]      Use of uninitialized value $dg in concatenation (.) or string at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/Munin/Node/Service.pm line 161.
    2013/02/02-08:52:11 [7213]      Use of uninitialized value $dg in numeric eq (==) at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/Munin/Node/Service.pm line 168.
    2013/02/02-08:52:11 [7213]      Use of uninitialized value $dg in numeric eq (==) at /usr/local/cpanel/3rdparty/perl/514/lib64/perl5/cpanel_lib/Munin/Node/Service.pm line 174.
    any idea?

    thanks!
     
  7. mcongosto

    mcongosto Member

    Joined:
    Aug 1, 2011
    Messages:
    22
    Likes Received:
    0
    Trophy Points:
    1
    My upgrade didn't fail but munin did not get updated:

    Version: 1.4.7-2.7

    And it is not working.

    What should i do? I'd love to keep historic data.

    thanks
     
  8. sHORTYWZ

    sHORTYWZ Well-Known Member

    Joined:
    Dec 14, 2003
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    6
    Same issue. Centos 5.7, Cpanel 11.36.0 Build 4.
     
  9. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Please open a support ticket at https://tickets.cpanel.net This way we can help you through these issues, identify the root cause, and get it resolved.
     
  10. kennethgray

    kennethgray Registered

    Joined:
    Sep 27, 2009
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I had the same problem with munin not working properly after the 11.36 upgrade. In addition, I was getting hundreds of email notifications about munin failing to open certain files and, therefore, not running (getting 300-500 emails per day can be a great motivator to fix things).

    My problem was that the new Cpanel RPM Munin install has different permissions from the old Cpanel Munin install and was causing issues. There was no distro or duplicate Munin install, ever. Here is what worked for me, though this may not be your solution and as always make a backup as it involves risk of data loss.

    1. The problem seems to be a permission error with the files munin-node uses to store data and generate graphs. If you have munin installed by Cpanel, those files will be located in:
    Code:
    /usr/local/cpanel/whostmgr/docroot/munin/DomainName.com/ServerName.DomainName.com
    2. SSH to your box, change to the directory at the DomainName level and check the file/directory permissions:
    Code:
    cd /usr/local/cpanel/whostmgr/docroot/munin/DomainName.com
    ls -al
    3. If the file permissions are numbers, you will see a listing like this (your numbers will be different):
    Code:
    -rw-r--r-- 1 31010 31012 13K Jan 31 14:20 index.html
    You want to change that to work for Munin, so run this command as root to change all permissions to Munin (make sure you are in the DomainName.com level directory!!):
    Code:
    chown -R munin:munin *
    Now if you run the ls command, you will get this:
    Code:
    -rw-r--r-- 1 munin munin 13K Feb  5 14:20 index.html
    4. Go in to WHM. We will need to reinstall Munin via the plugin menu. This did not result in any data loss for me, but be warned, it could result in data loss for you, so as I said earlier, make a backup. Also, this worked on my problem, which was a permission issue from earlier Cpanel/Munin versions. It may not work if your issue is that you have Munin from your distro RPM or something else!!

    In WHM, look for Home >> CPanel >> Manage Plugins. On the Munin tab, click "Uninstall Munin". This uninstalls the Munin plugin. Once uninstalled, go back to Home >> CPanel >> Manage Plugins, click the checkbox "Install Munin" and then click "Save" at the bottom of the Plugin page. This will install and update Munin.

    In my install, this is what worked. Munin updates and all data over the 5 day gap when Munin was not working was recovered. I would suggest testing/backing up before doing this anywhere else as it may not be a fix for all and changing permissions, uninstalling, etc, ... can always lead to data loss and things not working.

    Hope this sheds some light on the mystery. :)
     
  11. sHORTYWZ

    sHORTYWZ Well-Known Member

    Joined:
    Dec 14, 2003
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    6
    Ticket submitted and closed out with a fix.

    As the post above me goes into detail, it appears the Munin user was deleted somehow during the latest update. Reinstalling recreates this user and fixes everything.

    The question still remains as to why the user was deleted...
     
  12. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    The problem stemmed from a a flaw in the upgrade logic in our Munin RPM. When an upgrade is performed an additional event is triggered at the end of installing the new Munin RPM. In the flawed version this event would remove the munin user (the event in question is intended to cleanup things that may be left behind by the prior RPM and are no longer needed). We fixed the logic so the user is only uninstalled when Munin is uninstalled, not when it is upgraded.
     
  13. sHORTYWZ

    sHORTYWZ Well-Known Member

    Joined:
    Dec 14, 2003
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    6
    Kenneth, just an FYI - the update to Build 6 today broke Munin again... I have reopened my ticket so that it can be looked at.
     
  14. wdwms

    wdwms Member

    Joined:
    Jan 31, 2005
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Correct, munin is kaput here..

    root@tucker [/etc/munin/plugins]# /usr/local/cpanel/3rdparty/perl/514/sbin/munin-run load
    Use of uninitialized value $dg in concatenation (.) or string at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Munin/Node/Service.pm line 161.
    Use of uninitialized value $dg in concatenation (.) or string at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Munin/Node/Service.pm line 161.
    Use of uninitialized value $dg in numeric eq (==) at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Munin/Node/Service.pm line 168.
    Use of uninitialized value $dg in numeric eq (==) at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Munin/Node/Service.pm line 174.
     
  15. wdwms

    wdwms Member

    Joined:
    Jan 31, 2005
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Got this w/the upgrade this am:

    Problems were detected with cPanel-provided files which are RPM controlled.
    If you did not make these changes intentionally, you can correct them by running:

    > /usr/local/cpanel/scripts/check_cpanel_rpms --fix

    The following RPMs are found to be altered from their original install state:
    munin-common,1.4.7,3.el5,/var/run/munin
    munin,1.4.7,3.el5,/var/lib/munin
    munin,1.4.7,3.el5,/var/lib/munin/plugin-state
    munin,1.4.7,3.el5,/var/log/munin
    cpanel-perl-514-munin,1.4.7,4.cp1136,/etc/init.d/munin-node
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-check
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/bin/munindoc
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-node-configure
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/3rdparty/perl/514/sbin/munin-run
    cpanel-perl-514-munin,1.4.7,4.cp1136,/usr/local/cpanel/whostmgr/docroot/munin
    cpanel-perl-514-munin,1.4.7,4.cp1136,/var/lib/munin
    cpanel-perl-514-munin,1.4.7,4.cp1136,/var/lib/munin/plugin-state
    cpanel-perl-514-munin,1.4.7,4.cp1136,/var/log/munin
    cpanel-perl-514-munin,1.4.7,4.cp1136,/var/opt/munin
    cpanel-perl-514-munin,1.4.7,4.cp1136,/var/run/munin
     
  16. kennethgray

    kennethgray Registered

    Joined:
    Sep 27, 2009
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I got this same error when cPanel upgraded to 11.36.0.6 last night. It appears that the update upgrades the munin rpm and deletes the munin user from the system entirely. In other words, when you run the command
    Code:
    cd /usr/local/cpanel/whostmgr/docroot/munin; ls -al
    You get files with ownership set to numbers, not munin:munin as they should be. Attempting to change the files to munin ownership fails as there is no munin user. It also stopped the munin-node process, which was both good and bad. Good in that there weren't thousands of queued undelivered alert messages, bad in that munin couldn't track any data so there was data loss from when the update occured to when munin was fixed.

    I managed to fix this in WHM. My fix preserved all historical data, the only loss was a gap of data between the cPanel update and fixing munin, though as always if you try this, keep a backup as there are no guarantees this will work for you without data loss! The fix is to go in to WHM >> cPanel >> Manage Plugins. From there select uninstall Munin, once it completes, go back select the checkbox for install munin and keep updated, save and let munin install again. Under 11.36.0.6 it should install properly with the correct permissions. You can use the command above in SSH to see if it did (the files should be owned by munin:munin).

    The "fix" for the "fix" is all fine now, no big deal, but I am worried that munin will get broken after every cPanel update, so I think there is more debugging needed on the cPanel side to make sure that this is truly fixed.
     
  17. atoomic

    atoomic Registered

    Joined:
    Feb 8, 2013
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    that problem is known and fixed with the cpanel-perl-514-munin-1.4.7-4.cp1136 rpm
    the problems comes from the uninstall hook in any versions <= 1.4.7-3, which is run at the end of the upgrade

    running that command fix the problem when you upgrade from 1.4.7-3 or any previous version
     
Loading...

Share This Page