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.
[RESOLVED] No machine reachable after update 1.8
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, could you give us more details?
Which version are you using?
Simon
, could you give us more details?
Which version are you using?
Simon
I'm coming from version 1.7.4.
Here is an image of my console attached.
While all of my workstations are reachable via their IP address.
There are some positions that reappeared after a restart.
THANKS
Here is an image of my console attached.
- Annotation 2020-01-28 181214.png (106.54 KB) Viewed 7255 times
There are some positions that reappeared after a restart.
THANKS
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Has the waptupgrade package been delivered?
On an agent you can launch:
To understand the problem
On an agent you can launch:
Code: Select all
"C:\Program Files (x86)\wapt\runwaptservice.bat" -ldebugHello,
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
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
-
jeancharles
- Messages: 21
- Registration: June 11, 2019 - 10:02
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!
I've rebooted both the client and the server without success.
We'll see if sleeping on it helps!
-
jeancharles
- Messages: 21
- Registration: June 11, 2019 - 10:02
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.
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.
-
jeancharles
- Messages: 21
- Registration: June 11, 2019 - 10:02
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.
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.
-
jeancharles
- Messages: 21
- Registration: June 11, 2019 - 10:02
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
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
