Better error messages for rpm installation
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.
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,
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.
Please sign in to leave a comment.