Discussion in 'Installation/Configuration' started by Tastiger, May 5, 2021.
I noticed this warning during installation - is it anything to worry about?
It means there was a problem with your resolver. Is a resolver listening on 127.0.0.53?
If there is I didn't do it.
It was an empty formatted HDD with fresh install of Ubuntu 20.04 as per
and then ran the ISPConfig auto-installer
I wonder if accidentally added a package during the install of 20.04?
Does the resolver work now?
I am starting over and see if I get the same error this time around
No still getting
Once this has finished installing what is the best way to check the resolver?
My signature has link to DNS tutorial. It has info on testing name server.
Check all services are running on that host with:
or better run the Read before posting common issues script.
Seems as the server is listening on 127.0.0.53
So no idea why the warning popped up, as I said it was a clean install but this time using the auto install
I would be interested to know if anyone else has had the same warning using the auto install.
Same here on fresh clean 20.04 when i run with --no-dns --no-pma --no-mailman.
Also have ipv6 disabled.
Glad I am not the only one who has found this issue.
My initial reason for posting the error was that if it is a blank HDD and all one is using is the auto installer, then the issue must be in the installer itself. Maybe there is an issue only with certain hardware?
Tried again with focal Server, this time with ipv6 enabled and installer still shows the same error.
Will try a debian install later this day.
The "[WARN] Unexpected resolver response:" this thread is about is just a warning and not an error, so nothing that stops the installation.
While this is in fact an error, something is wrong with your base system, or you don't have enough harddisk space or RAM.
OK, i gave the VM 4GB of RAM, how much is actually needed for the install?
The VM should have 2Gb or morw, so your system is fine with 4GB.
2 TB blank HDD
16 GB Ram
"something is wrong with your base system, or you don't have enough harddisk space or RAM."
So I suspect something is wrong with your base system
@till's response to @inka quoted some specific log messages which you did not print, @Tastiger, I suspect the comment on ram/disk size pertained to @inka's system and not yours.
That's indeed the case
Not done testing yet but i believe that next to CPU, RAM & root space size allocation, my problem was with the lxc virtual machine image i used at first and that it had to much stuff allready installed in it.
Things have changed with ispconfig installing over the last decade and i need to catch up.
Separate names with a comma.