Better error messages for rpm installation

Follow

Bradley Watkins

• November 02, 2011 23:43

Because the deployment scripts use both HTTP and FTP to download the RPMs, the RPMs pulled via FTP were 0 bytes.  My default wgetrc doesn't have FTP proxying configured.  But the lack of error reporting for installation of these RPMs means that you get an error message later stating that a check for a particular file (in my case, mysqld) fails without any particular information as to why that might be.  Trapping the error that an 'rpm -Uvh <rpm filename>' gives would have been quite helpful in tracking down the issue.  The fix for my issue, of course, was configuring an ftp_proxy= line in my wgetrc.  But getting to that point took some digging that would not have been necessary with better and earlier error detection and reporting.

0

• 

  Johan

  • November 04, 2011 13:52

  Hi,

  Thanks for the feedback. We are adding a better install log where the error messages should be logged in plain text.

  Will let you know here that is completed. But did the rest of installation work out for you?

  We have also put up cmon 1.1.11  now and it fixes a bunch of recovery bugs in Galera, and also a problem with the cmon agents (they could get stuck when getting host statistics and report themselves as dead). How to upgrade is described in Tips and Tricks,

  Johan

  0

  Comment actions Permalink
• 

  Bradley Watkins

  • November 07, 2011 18:15

  Great, I'll check out the Tips and do an upgrade.  Once I had the correct RPMs the installation went very smoothly.  I'm still very early in evaluating Galera, so I'm no equipped to report any issues that are harder to detect, but so far so good.

  0

  Comment actions Permalink
• 

  Johan

  • November 11, 2011 10:15

  Hi,

  we have now added better error messages if mandatory commands fails (those executed with 'remote_cmd').

  You will now see e.g,:

  10.30.30.31: Executing 'rpm -Uvh /tmp/MySQL-client-5.5.16-1.rhel5.x86_64.rpm' [failed]
  package MySQL-client-5.5.16-1.rhel5.x86_64 is already installed

  (thus the error message of the failed command is printed out).

  This has been added to all configurators.

  Let me know if this helps.

  Thank you

  Johan

  0

  Comment actions Permalink
• 

  Bradley Watkins

  • November 11, 2011 13:09

  While I haven't done an install yet with the improved scripts, that is exactly what I was hoping to see.  I'll try to replicate my exact scenario on some new VMs just to double-check, but this looks good.  Thanks!

  0

  Comment actions Permalink

Please sign in to leave a comment.