In the last few days I have been having a lot of issues with directadmin.
I have a lot of servers running it and now we seem to be having issues with latest installs.
1 httpd is having issues when it runs a tally every night, it is taking 2-3 mins for it to restart and run properly. I have even noticed when I do a fresh install after i get to the end of the install and try to access directadmin it takes a few mins for it to connect.
I get error page that it can't be found and then after a min or so I can click it and it will load properly. My customers are complaining that every night when tally runs httpd is down for anywhere from 1 -3 mins then comes back up.
I have even changed the /etc/init.d/httpd to
restart)
kill -USR1 `cat $PIDFILE`
;;
this seems to even make it worse.
2 this bind issue has me lost. I have read the threads here about it and can't decide what to do
if I add bind* to the yum exclude line yum will update fine however is this the best practice or what? I know there have been some bind issues and would like to have the latest version.
I use centos 5 minimal install and have not added bind except when directadmin installs it.
what is wrong with bind_chroot ? i have excluded it from the yum line and allowed it to update and everything seems fine with it installed. These are servers running 1 domain, is having bind_chroot a problem with servers running more than 1 domain.
can someone explain why we don't want it? I read here from support that we don't want it but why?
please shed some light on these 2 issues .
What is the best fix for this yum and bind issue?
I have a lot of servers running it and now we seem to be having issues with latest installs.
1 httpd is having issues when it runs a tally every night, it is taking 2-3 mins for it to restart and run properly. I have even noticed when I do a fresh install after i get to the end of the install and try to access directadmin it takes a few mins for it to connect.
I get error page that it can't be found and then after a min or so I can click it and it will load properly. My customers are complaining that every night when tally runs httpd is down for anywhere from 1 -3 mins then comes back up.
I have even changed the /etc/init.d/httpd to
restart)
kill -USR1 `cat $PIDFILE`
;;
this seems to even make it worse.
2 this bind issue has me lost. I have read the threads here about it and can't decide what to do
if I add bind* to the yum exclude line yum will update fine however is this the best practice or what? I know there have been some bind issues and would like to have the latest version.
I use centos 5 minimal install and have not added bind except when directadmin installs it.
what is wrong with bind_chroot ? i have excluded it from the yum line and allowed it to update and everything seems fine with it installed. These are servers running 1 domain, is having bind_chroot a problem with servers running more than 1 domain.
can someone explain why we don't want it? I read here from support that we don't want it but why?
please shed some light on these 2 issues .
What is the best fix for this yum and bind issue?
Last edited:
