Hi Cyrus,

it seems you ran

qlustar-initial-config -l

for some reason. The '-l' option is only for internal use and not documented anywhere.
Without that the additional hosts entry will not be there.

The qlumand-apt-trigger: timeout is normal, has no negative conseqeunces and comes whenever qlumand is not running, like before finishing the qlustar-initial-config stage.

Best,

Roland

On 7/10/24 16:21, c.gaviri--- via Qlustar General wrote:
Hi,

I tried the manual network config and unfortunately, there are issues with that method including the original one. It adds an entry into /etc/hosts as follows;

***********************
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

192.168.55.113 ql-repo repo.qlustar.com
***********************

When I run;

apt update ....
0% [Connecting to repo.qlustar.com (192.168.55.113)]

Also in that file should be the hostname and its IP. 

After I remove that entry and try again;

apt update        

qlumand-apt-trigger: timeout      *************************************

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

The qlumand-apt-trigger: timeout appears from running apt update. It appears again when I run the qlustar-initial-config. However I can now run qluman-cli --gencert and successfully generate a cert. So it's working as far as I can tell so far, it just depends what else may be affected by the timeout.

Thanks for your help.

Regards,

Cyrus
__