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.
Please sign in to leave a comment.