CentOS 6.1 status update & automated QA

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,354
Hi people, Just to let you know that all 6.1 packages are now built and ready to produce a 6.1 installable tree (and ISOs). Most of you already know that, as they are (hopefully) using the CR repo, and so are running 6.1 packages (+6.1 updates !) on your 6.0 boxes. The first tree that needed to be generated yesterday isn't bootable and we are working on that. Once that tree will be installable, it will be pushed to two targets : * a rsync target accessible from QA people for their own manual tests (pull on request) * a QA node (pushed from the builders) That second push will automatically triggers (at least we hope so ... :-) ) some automated QA tests around each pushed tree, with results being sent to the qa list. Let's see how it goes and how much time QA will be necessary for 6.1. Let me just repeat it in one sentence : all packages are built but the tree/isos aren't usable yet. More to come later

Fabian
http://qaweb.dev.centos.org/qa/node/116
 
Johnny Hughes at http://lists.centos.org/pipermail/centos/2011-December/120431.html
...and I expect 6.1 to be released within a week (including all SRPMS).

This was posted Fri Dec 2. I have a feeling that we really are getting there this time, hopefully we have CentOS 6.1 next friday! :)

Do you think the upgrade should be without problems regarding DirectAdmin? Or maybe it is best to wait upgrading until DirectAdmin Support confirm that they have tested 6.1?

I am currently running 6.0 64bit, and can't wait upgrading ... It been taking a long time now.
 
If you have a test box you should test by yourself, i really wouldnt update a production server untille da staff confirm is stable and working.

Regards
 
More news! http://qaweb.dev.centos.org/qa/node/118

6.1 Release Wrapping Up - 6.2 work underway!

We are working on wrapping up the 6.1 release and preparing to pus mirrors. QA has signed off and now we're working on the last minute tasks to get 6.1 officially released.

In other news, a bunch of packages just hit upstream -- looks as though 6.2 is released even though it hasn't been announce yet. We're already working on pulling in those updates and this will be a good test to see if all of our build and testing automation can help us cut down the release turn around time. More news to follow on 6.2 as we get a little further along in the process.h it to
 
If you have a test box you should test by yourself, i really wouldnt update a production server untille da staff confirm is stable and working.

Unfortunately my only "test box" is running CentOS 5.7. Has anybody yet attempted a upgrade from CentOS 6.0 to CentOS 6.1? Please post here and let us know if it is compatible with DirectAdmin for CentOS 6 or not? Thanks!
 
Thank you very much, Andrea! Actual I don't have a test box, what I called a test box is a box that is only running one of my name servers, so I can test with it, because it does not have customers, but it is CentOS 5.x box. My production server that have my customers, is a CentOS 6.0 64 bit box running the newest DirectAdmin version.
 
yum install openssh-server wget gcc gcc-c++ flex bison make bind bind-libs bind-utils openssl openssl-devel perl quota libaio libcom_err-devel libcurl-dev patch

Ive installed those as pre-requisite.

Everything installed fine. Except for named

Dec 12 21:33:11 93-63-209-88 named[4691]: /etc/named.conf:42: open: /etc/rndc.key: file not found

This is the only strange part.


Code:
DirectAdmin Values
Compiled on	CentOS 6.0 64-Bit
Compile Date	Dec 5 2011, 00:15:20
Server Version	1.40.1
Current Available Version	1.401000
Last Updated	Mon Dec 5 08:16:03 2011
Code:
[root@93-63-209-88 custombuild]# cat /etc/redhat-release
CentOS release 6.1 (Final)

Regards
 
Hello,

This is the code that generates the rndc.key file. It's in the setup.sh:
Code:
        RNDCKEY=/etc/rndc.key
        if [ -e $RNDCKEY ]; then
                if [ `cat $RNDCKEY | grep -c secret` -eq 0 ]; then
                        SECRET=`/usr/sbin/rndc-confgen | grep secret | head -n 1`
                        STR="perl -pi -e 's#hmac-md5;#hmac-md5;\n\t$SECRET#' $RNDCKEY;"
                        eval $STR;
                fi
        fi
Throw that into a script and see what it does.

Although, if the key is missing, the clearly the [ -e rndc.key ] won't work.. as the file must exist for it to work.
Let me know if the key does not exist at all after bind is installed.

John
 
Well when problem appear file doesnt exist but named is installed.

How should i do step-by-step install? Or, how seetup install named? Yum, pre-compiled, source?

Regards
 
Also i think that update from 6.0 to 6.1 will cause no problem at all cause every service is already running and working.

Regards
 
Ok, found where and how setup install bind, manually installed it and rndc.key is not there.

Default named.conf (when install da precompiled) have:

Code:
bindkeys-file "/etc/named.iscdlv.key";

And that file exist.

After that install i didnt see anything else on setup.sh that download/create the key so the pre-compiled package doesnt install it.

Ive also noticed that running an yum update will notice those updates related:

Code:
 bind                                                  x86_64                           32:9.7.3-2.el6_1.P3.3                               updates                           3.9 M
 bind-libs                                             x86_64                           32:9.7.3-2.el6_1.P3.3                               updates                           839 k
 bind-utils                                            x86_64                           32:9.7.3-2.el6_1.P3.3                               updates                           177 k
 binutils                                              x86_64                           2.20.51.0.2-5.20.el6_1.1                            updates                           2.8 M
 ca-certificates                                       noarch                           2010.63-3.el6_1.5                                   updates                           531 k

but aswell rndc.key is not craeted (neither restarting bind)

Ill restore snapshot again and test it again... if the package doesnt create the rndc.key i dont get why second time worked...
 
Again, rndc.key isnt installed by bind at all.

Am i doing something wrong or rndc.key should not be installed with bind? If is not installed by bind which software should create it?

Regards
 
Step-by-step output:

Code:
[root@93-63-209-88 ~]# wget http://files11.directadmin.com/services/es_6.0_64/bind-9.7.0-5.P2.el6.x86_64.rpm
--2011-12-12 21:10:03--  http://files11.directadmin.com/services/es_6.0_64/bind-9.7.0-5.P2.el6.x86_64.rpm
Resolving files11.directadmin.com... 93.63.209.92
Connecting to files11.directadmin.com|93.63.209.92|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3623168 (3.5M) [text/plain]
Saving to: âbind-9.7.0-5.P2.el6.x86_64.rpmâ

100%[==========================================================================================================================================>] 3,623,168   4.78M/s   in 0.7s

2011-12-12 21:10:04 (4.78 MB/s) - âbind-9.7.0-5.P2.el6.x86_64.rpmâ

[root@93-63-209-88 ~]# wget http://files11.directadmin.com/services/es_6.0_64/bind-libs-9.7.0-5.P2.el6.x86_64.rpm
--2011-12-12 21:10:07--  http://files11.directadmin.com/services/es_6.0_64/bind-libs-9.7.0-5.P2.el6.x86_64.rpm
Resolving files11.directadmin.com... 93.63.209.92
Connecting to files11.directadmin.com|93.63.209.92|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 849528 (830K) [text/plain]
Saving to: âbind-libs-9.7.0-5.P2.el6.x86_64.rpmâ

100%[==========================================================================================================================================>] 849,528     4.38M/s   in 0.2s

2011-12-12 21:10:08 (4.38 MB/s) - âbind-libs-9.7.0-5.P2.el6.x86_64.rpmâ

[root@93-63-209-88 ~]# wget http://files11.directadmin.com/services/es_6.0_64/bind-utils-9.7.0-5.P2.el6.x86_64.rpm
--2011-12-12 21:10:12--  http://files11.directadmin.com/services/es_6.0_64/bind-utils-9.7.0-5.P2.el6.x86_64.rpm
Resolving files11.directadmin.com... 93.63.209.92
Connecting to files11.directadmin.com|93.63.209.92|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 178560 (174K) [text/plain]
Saving to: âbind-utils-9.7.0-5.P2.el6.x86_64.rpmâ

100%[==========================================================================================================================================>] 178,560     --.-K/s   in 0.1s

2011-12-12 21:10:12 (1.14 MB/s) - âbind-utils-9.7.0-5.P2.el6.x86_64.rpmâ

[root@93-63-209-88 ~]# rpm -Uvh --nodeps --force bind-*
Preparing...                ########################################### [100%]
   1:bind-libs              ########################################### [ 33%]
   2:bind                   ########################################### [ 67%]
   3:bind-utils             ########################################### [100%]

[root@93-63-209-88 ~]# /etc/init.d/named restart
Stopping named:                                            [  OK  ]
Starting named:                                            [  OK  ]
[root@93-63-209-88 ~]# ls -l /etc/rndc.key
ls: cannot access /etc/rndc.key: No such file or directory

Regards
 
Command line:

Code:
rndc-confgen -a -c /etc/rndc.key

will correctly create the file, so, maybe should be changed the script to something like this (not a programmer feel free to correct me).

change this:

Code:
        RNDCKEY=/etc/rndc.key
        if [ -e $RNDCKEY ]; then
                if [ `cat $RNDCKEY | grep -c secret` -eq 0 ]; then
                        SECRET=`/usr/sbin/rndc-confgen | grep secret | head -n 1`
                        STR="perl -pi -e 's#hmac-md5;#hmac-md5;\n\t$SECRET#' $RNDCKEY;"
                        eval $STR;
                fi
        fi

with this
Code:
        RNDCKEY=/etc/rndc.key

        if [ ! -e $RNDCKEY ]; then
                echo "Creating RNDC key"
                rndc-confgen -a -c /etc/rndc.key
        fi

        if [ -e $RNDCKEY ]; then
                if [ `cat $RNDCKEY | grep -c secret` -eq 0 ]; then
                        SECRET=`/usr/sbin/rndc-confgen | grep secret | head -n 1`
                        STR="perl -pi -e 's#hmac-md5;#hmac-md5;\n\t$SECRET#' $RNDCKEY;"
                        eval $STR;
                fi
        fi

Hope this help.
 
Back
Top