Error upgrading XI from 2.5 to 2.7

[JakeHatMacys]

This is a new one for me:

Code: Select all

Making all in plugins-scripts
make[1]: Entering directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2/plugins-scripts'
/bin/echo "#! #PERL# -w" | /bin/gawk -f ./subst > check_mysql_health
/bin/echo "# nagios: -epn" >> check_mysql_health
/bin/echo >> check_mysql_health
/bin/echo "my %ERRORS=( OK => 0, WARNING => 1, CRITICAL => 2, UNKNOWN => 3 );" >> check_mysql_health
/bin/echo "my %ERRORCODES=( 0 => 'OK', 1 => 'WARNING', 2 => 'CRITICAL', 3 => 'UNKNOWN' );" >> check_mysql_health
for m in Nagios/DBD/MySQL/Server/Instance/Innodb.pm Nagios/DBD/MySQL/Server/Instance/Myisam.pm Nagios/DBD/MySQL/Server/Instance/Replication.pm Nagios/DBD/MySQL/Server/Instance.pm Nagios/DBD/MySQL/Server.pm Nagios/DBD/MySQL/Cluster.pm Nagios/Extraopts.pm; do \
                /bin/sed -e 's/^1;//g' < $m | /bin/gawk -f ./subst | /bin/grep -v "my %ERROR" >> check_mysql_health; \
        done
if [ -d "/usr/local/nagios/libexec" ]; then \
                for m in /usr/local/nagios/libexec/CheckMySQLHealthExt*.pm; do \
                        if [ -f $m ]; then \
                                /bin/echo found $m; \
                                /bin/sed -e 's/^1;//g' < $m | /bin/gawk -f ./subst | /bin/grep -v "my %ERROR" >> check_mysql_health; \
                        fi \
                done \
        fi
/bin/cat check_mysql_health.pl | /bin/grep -v "^use Nagios" | /bin/grep -v "^my %ERROR" | /bin/gawk -f ./subst >> check_mysql_health
chmod +x check_mysql_health
make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2/plugins-scripts'
Making all in t
make[1]: Entering directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2/t'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2/t'
make[1]: Entering directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/extraplugins/check_mysql_health-2.1.8.2'
Updating NRDP..
no crontab for nagios
Saving old crontab to /tmp/root.crontab.orig...
Removing XI cron jobs...
"-":4: bad minute
errors in crontab file, can't install.

[jdalrymple]

Weird...

what is the output of the following?

Code: Select all

[root@localhost ~]# crontab -l -u root

[JakeHatMacys]

Weird...

what is the output of the following?

Code: Select all

[root@localhost ~]# crontab -l -u root

[root@esu2v238 ~]# crontab -l -u root
5 0 * * * /usr/local/bin/nmon -x -f -t -s 900 -c 96 -m /archive/nmon_data 2>/dev/null
50 0 * * * /home/scripts/sys_info/prog/move_nmon_data.ksh 2>&1
50 2 * * 2 Shutting down ntpd: [ OK ]
Starting ntpd: [ OK ]

[lmiltchev]

Let's double check the root crontab. Run the following command and show us the ouput:

Code: Select all

cat /var/spool/cron/root

You can also open it for editing by running (logged in as root):

Code: Select all

crontab -e

and see if there is anything weird with the third line, line endings, formatting, etc.

[JakeHatMacys]

Let's double check the root crontab. Run the following command and show us the ouput:

Code: Select all

cat /var/spool/cron/root

You can also open it for editing by running (logged in as root):

Code: Select all

crontab -e

and see if there is anything weird with the third line, line endings, formatting, etc.

Code: Select all

[root@esu2v238 nagiosxi]# cat /var/spool/cron/root
5 0 * * * /usr/local/bin/nmon -x -f -t -s 900 -c 96  -m /archive/nmon_data 2>/dev/null
50 0 * * * /home/scripts/sys_info/prog/move_nmon_data.ksh 2>&1
50 2 * * 2 Shutting down ntpd:                             [  OK  ]
Starting ntpd:                                             [  OK  ]

[jdalrymple]

At this point I'd remove (move) that crontab, it's icky. I'd like to see if it's a new thing or if that mess has been there.
Can you hook us up with your upgrade.log? Maybe PM it in case it has some weird stuff in it.

Code: Select all

[root@localhost ~]# crontab -u root -l > ~/root.cronbak
[root@localhost ~]# crontab -u root -r

Then rerun the upgrade

[JakeHatMacys]

At this point I'd remove (move) that crontab, it's icky. I'd like to see if it's a new thing or if that mess has been there.
Can you hook us up with your upgrade.log? Maybe PM it in case it has some weird stuff in it.

Code: Select all

[root@localhost ~]# crontab -u root -l > ~/root.cronbak
[root@localhost ~]# crontab -u root -r

Then rerun the upgrade

PM'd the upgrade log and the upgrade completed without issue after I rand the crontab commands you had me run.

So thanks! no clue why that would've been messed up to begin with

[lmiltchev]

So thanks! no clue why that would've been messed up to begin with

I am glad your issue has been resolved! Is is safe to lock this topic?