Page 1 of 1
[RESOLVED] No machine reachable after update 1.8
Published: January 28, 2020 - 2:57 PM
by mart03
Specify installed WAPT version (1.8.0)
* Specify server OS (Linux / Windows) and version (Debian Buster)
* Specify OS of the administration/package creation machine (Windows 10)
Hello,
I just finished upgrading to 1.8, however, my entire network is no longer visible. When I say visible, I mean that they detect all of my networks as disconnected (reachable) (except for about fifteen machines)...
I've reset the WebSockets and cleared my console cache, but still nothing.
Thank you for your help.
Re: No machine reachable after update 1.8
Published: January 28, 2020 - 5:16 PM
by sfonteneau
Hello
, could you give us more details?
Which version are you using?
Simon
Re: No machine reachable after update 1.8
Published: January 28, 2020 - 6:11 PM
by mart03
I'm coming from version 1.7.4.
Here is an image of my console attached.
- Annotation 2020-01-28 181214.png (106.54 KB) Viewed 7254 times
While all of my workstations are reachable via their IP address.
There are some positions that reappeared after a restart.
THANKS
Re: No machine reachable after update 1.8
Published: January 28, 2020 - 8:27 PM
by sfonteneau
Has the waptupgrade package been delivered?
On an agent you can launch:
Code: Select all
"C:\Program Files (x86)\wapt\runwaptservice.bat" -ldebug
To understand the problem
[RESOLVED] No machine reachable after update 1.8
Published: January 29, 2020 - 09:09
by mart03
Hello,
the package is showing as TO-UPDATE, but it doesn't indicate that the machine is reachable. This morning most PCs were reachable, so I think the daily reboot was enough for the console to "see" them again. There's nothing alarming in the debug logs, at least no errors at first glance.
I'm marking this as resolved.
Thanks
Re: [SOLVED] No machine reachable after update 1.8
Published: January 29, 2020 - 5:47 PM
by jeancharles
I have the same problem: two newly installed agents (version 1.8.0), and the status isn't showing up.
I've rebooted both the client and the server without success.
We'll see if sleeping on it helps!
Re: [SOLVED] No machine reachable after update 1.8
Published: January 30, 2020 - 10:34 AM
by jeancharles
I've updated Windows on both the server and the client, disabled the firewall, and reinstalled the WAPT agent, but nothing has worked.
In the performance monitor, I can see the connections to the WAPT server via TCP/443 and TCP/80, but they aren't showing up in the console.
I also can't see the self-service packages.
Where should I look? I can create a new thread if needed. Thank you for your help.
Re: [SOLVED] No machine reachable after update 1.8
Published: January 30, 2020 - 10:51 AM
by jeancharles
Result of wapt-get update-status:
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
waptserver is not available or error in inventory. Update of status not properly sent.
I can ping the wapt server, and testing with Edge shows access to the local wapt site is OK.
Re: [SOLVED] No machine reachable after update 1.8
Published: January 30, 2020 - 10:56 AM
by jeancharles
C:\Users\> wapt-get update
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
Update package list from
https://svwapt01/wapt,
https://srvwapt01/wapt-host
2020-01-30 10:51:30,392 CRITICAL Error merging Packages from
https://srvwapt01/wapt into db: HTTPError: 400 Client Error: Bad Request for url:
https://srvwapt01/wapt/Packages
Total packages: 0
Added packages:
Removed packages:
Discarded packages count: 0
Pending operations:
upgrade:
additional:
install:
remove:
Repositories URL:
https://srvwapt01/wapt
https://srvwapt01/wapt-host