The service 'named' is down on clean Ubuntu 22.04 LTS install

[ArashiInteractive]

Hi all,

As the subject states, I've just setup a new VPS running Ubuntu 22.04LTS and DirectAdmin 1.650, had errors during setup and now DA continually reminds me that 'named' is down and gives errors when I try to create new users/domains on the server.

How did I get here?
- Purchase VPS with Ubuntu 22.04LTS (4 vcore, 8gig RAM, 160gig SSD - should it matter)
- Try to install install script from: https://docs.directadmin.com/getting-started/installation/installguide.html
- This gave an error (forgot to write that one down, but I got around it by doing wget https://download.directadmin.com/setup.sh, then bash setup.sh 'supersecretlicensekeyhere'
- First time installing DA myself (previously it came pre-installed for me), was surprised that a few minutes later I got a message saying I could log in now.
- Logged in using the onscreen details to find a notice message waiting for me stating: The service 'named' on <name> is currently down
- Logging in with SSH and running systemctl status named returns Unit named.service could not be found
- Quick Google to find that this apparently sometimes happens and not much else
- Come to forums to hope someone has a better answer than that

So, as I said, it's a new install/server, no customers on here yet, thus now is the time to fully break it. Should DA have installed named if it's needed? If I were to manually install with sudo apt install named, would that magically fix all the things? Would I be better off re-installing the VPS fresh and seeing if it works the second time around? If this is the recommendation, would it be advisable to check that named is there and running before installing DA? Without starting a holy war, is this more of an Ubuntu issue? My other server is Ubuntu 20.04 LTS, it came pre-installed but not aware of any such issues over there.

When I added a new user, this is the output:

Could not write domain's db file in /etc/bind
Could not add the domain's zone: Error writing /etc/bind/example.com.db.temp.169766.ePUaxxc99L : Cannot write to /etc/bind/example.com.db.temp.169766.ePUaxxc99L: Error opening /etc/bind/example.com.db.temp.169766.ePUaxxc99LXqfwcw for writing: No such file or directory
Error reading /etc/bind/example.com.db.temp.169766.ePUaxxc99L. Check the error.log for information.
Can't get file lock on /etc/bind/named.conf
Error writing /etc/bind/example.com.db.temp.169766.ePUaxxc99L : Cannot write to /etc/bind/example.com.db.temp.169766.ePUaxxc99L: Error opening /etc/bind/example.com.db.temp.169766.ePUaxxc99LXqfwcw for writing: No such file or directory
Error reading /etc/bind/example.com.db.temp.169766.ePUaxxc99L. Check the error.log for information.
Can't get file lock on /etc/bind/named.conf

Which makes sense since named doesn't exist in my little world, apparently.

Any thoughts or advise to share?
Thanks in advance.

 

[Richard G]

- First time installing DA myself (previously it came pre-installed for me), was surprised that a few minutes later I got a message saying I could log in now.
- Logged in using the onscreen details to find a notice message waiting for me stating: The service 'named' on <name> is currently down
- Logging in with SSH and running systemctl status named returns Unit named.service could not be found

This is very important with the new installation system.

The main issue here is --you have to wait-- because DA is installed quickly and you can login, but everthing else is nowadays installed in the background.
So before you can see services running and trying to restart you should wait until everything is installed.
Depending on speed and cpu this takes an average of 30 minutes to an hour mostly.

Which makes sense since named doesn't exist in my little world, apparently.

Just wait until installation is finished. If you can't get it right, since you installed newly, then remove everything, to a new Ubuntu 22.04 LTS installation.
Then run DA as suggested in the docs, be sure to run sudo -s first so you really are root when running the command.

Then sit back and wait and remember when DA is installed, the rest is not yet, so keep sitting back and wait.
Piece after piece in DA you will see services coming up, including named.

 

[ArashiInteractive]

Since it's been more than a day, safe to assume that part didn't work I'd think. I did notice when I previously logged in a number of services - dovecot, exim, etc were all sitting in CustomBuild waiting to be installed.

So, round 2.

Did a re-install of the VPS, back to bare Ubuntu 22.04 LTS. When I logged in via SSH and ran
sudo -s bash <(curl -fsSL https://download.directadmin.com/setup.sh) 'mylicensekey'

It gave the following error:
bash: /dev/fd/63: No such file or directory
curl: (23) Failure writing output to destination

A prompt did not appear, so I let it sit there for ~30min. After no further output, I did Ctrl+C then back to
wget https://download.directadmin.com/setup.sh
sudo -s bash setup.sh 'mylicensekey'

After a short while, I got my new username/password for DA, with a path where I could watch the log output if I wanted.

I let this sit here for another 30min, tried to log in to see two messages - one saying CustomBuild installation had failed, the other once again telling me 'named' is currently down. The CustomBuild failed message pointed to a log, with the final line being

*** There was an error while trying to configure Apache 2. Check the /usr/local/directadmin/custombuild/configure/ap2/configure.apache file

Is this more sit and wait without touching, or has DA failed to install a second time?

 

[Richard G]

It gave the following error:
bash: /dev/fd/63: No such file or directory

I think it's already starting to go wrong here, this should not happen.
Probably the apache error later on is also an issue related to this somehow.

I think it's best to send in a ticket for this situation as this is ceratinly not a sit and wait anymore, seems DA really failed to install a second time, so something must be wrong, as I can't see anything wrong on your part.

@fln @DirectAdmin Support why is this going wrong?
@Zhenyapan any idea?