[RESOLVED] clock icon stuck on reachable column

Empbilly · January 25, 2018 - 4:59 PM

Hello,

WAPT Server version: 1.5.1.16 (debian 9.3)
WAPT Setup version: 1.5.1.16 (windows 7)

I have some computers already on the server. After placing another 3 computers in the wapt server, they got the clock icon stuck on reachable column.

I went to one of the computers, I logged in with my domain account and still did not upgrade to the green icon.

What can it be?

http://i.imgur.com/6MSRvuM.png

January 25, 2018 - 5:17 PM

Th clock icon means that the host has not yet (or not being able) established a Websocket connection to the server.
Either the waptservice can not be started properly
Or there is a http proxy defined for the System Account (we currently have an issue with proxy settings and webscockets, normally, proxy should be disabled when nothing is defined in wapt-get.ini, but in fact, the setting in registry is taken in accoun...)

Check to restart the waptservice directly on the computer and check the log in "c:\program files (x86)\wapt\log\waptservice.log"

Hubert

Empbilly · January 26, 2018 - 11:35

I had built the waptsetup with the private key option enabled and tried to find it in c:\private but could not find it. I thought it was automatically sent, but I do not think so.

How is it done?

Another doubt with version 1.5 is that when installing or upgrading a package, a new package appears on almost all machines. The package name is the UUID of the Overview tab.

https://i.imgur.com/bLZBpVf.png

PS: The [img] tag is not working correctly.

Is that the way it is or is my installation in trouble?

Empbilly · January 29, 2018 - 3:24 PM

Regarding the post above, any idea what it might be?

agauvrit · January 30, 2018 - 09:49

empbilly wrote: ↑Jan 26, 2018 - 11:35 I had built the waptsetup with the private key option enabled and tried to find it in c:\private but could not find it. I thought it was automatically sent, but I do not think so.

How is it done?

Did you generate your private key and certificate?

The private key field is set in your waptconsole.exe pointing to your generated private key (*.pem), the related certificate (*.crt) is bundled in your WAPT Agent during agent building.

Doc: https://www.wapt.fr/en/doc/Installation ... index.html

empbilly wrote: ↑Jan 26, 2018 - 11:35 Another doubt with version 1.5 is that when installing or upgrading a package, a new package appears on almost all machines. The package name is the UUID of the Overview tab.

https://i.imgur.com/bLZBpVf.png

The package named after the computer UUID is the "Host Package" which describes computer configuration.
The host package was named using the host FQDN, now with WAPT 1.5 it's named after computer UUID.

Empbilly · January 30, 2018 - 1:06 PM

agauvrit wrote: ↑Jan 30, 2018 - 09:49
empbilly wrote: ↑Jan 26, 2018 - 11:35 I had built the waptsetup with the private key option enabled and tried to find it in c:\private but could not find it. I thought it was automatically sent, but I do not think so.

How is it done?
Did you generate your private key and certificate?

The private key field is set in your waptconsole.exe pointing to your generated private key (*.pem), the related certificate (*.crt) is bundled in your WAPT Agent during agent building.

Doc: https://www.wapt.fr/en/doc/Installation ... index.html

empbilly wrote: ↑Jan 26, 2018 - 11:35 Another doubt with version 1.5 is that when installing or upgrading a package, a new package appears on almost all machines. The package name is the UUID of the Overview tab.
https://i.imgur.com/bLZBpVf.png

The package named after the computer UUID is the "Host Package" which describes computer configuration.
The host package was named using the host FQDN, now with WAPT 1.5 it's named after computer UUID.

Thanks for the explanation agauvrit!!!