I also had this issue: In my case, the problem was that our server is
behind the universities firewall and I need to use the universities
nameserver for resolution.
You might try to ping IP adresses (e.g. 126.96.36.199 belongs to google).
If this works, than it should be related to nameservers; see 'man
resolvconf' on how to solve this issue.
According to my experience, restarting the 'qlustar-initial-config'
often does not work properly; be prepared that you might to reinstall a
clean system, than fix its dns-resolution and only after this start the
I hope, this helps you?
On 19.01.20 11:06, mohd.farid.ismail(a)yandex.com wrote:
I'm having trouble getting pass the 1 boot process, which is to run
/usr/sbin/qlustar-initial-config. After entering a name for the cluster, I always get the
HTTP access to the Qlustar repository is not possible
Please check your curent network settings (received from DHCP):
Kernel IP routing table
Once you have made the required modifications, restart /usr/sbin/qlustar-initial-config!
I can access the network (sshing to another machine), but cannot ping. It seems the DNS
cannot be resolved (ping www.google.com
results in the error "Temporary failure in
name resolution.") Any hint on what I did wrong?
Qlustar-General mailing list -- qlustar-general(a)qlustar.org
To unsubscribe send an email to qlustar-general-leave(a)qlustar.org