Hello,
I had to roll back my WAPT server due to data corruption.
The entire server is functional, and package deployment works correctly.
However, I can't access the machine via VNC, nor can I manage the computer remotely. Everything was working fine before the rollback. Is there anything I can do to resolve this issue?
Sincerely,
None IP reachable for this host
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Floflobel,
Sincerely,
Denis
Was it the WAPT that was corrupted, or the virtual machine itself? If it was the WAPT itself, could you provide more details? Was the rollback a rollback to the same version (1.3 to 1.3 or 1.5 to 1.5)?
Are you using version 1.3 or 1.5? If you're using 1.3, have you changed the IP address of your WAPT server? When you say the deployment is successful, do you mean you're able to push updates from the console?Floflobel wrote: ↑May 22, 2018 - 2:29 PM The entire server is functional, and package deployment is working correctly.
However, I cannot access the machine via VNC, nor can I manage the computer remotely. Everything was working fine before the rollback. Is there a procedure to follow to resolve this issue?
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello dcardon,
Thank you for your quick response.
I performed a rollback of the entire VM to the same major version to avoid as many problems as possible.
I don't know if I've made a minor update in the meantime.
My server is currently on version 1.5.23.
That's exactly it, I can push the updates directly to the workstations if they are turned on.
Sincerely,
Thank you for your quick response.
It was indeed the machine that had been corrupted for some time.
I performed a rollback of the entire VM to the same major version to avoid as many problems as possible.
I don't know if I've made a minor update in the meantime.
My server is currently on version 1.5.23.
As previously stated, I am on version 1.5.23 and the WAPT server IP address has never changed.dcardon wrote: ↑May 22, 2018 - 3:58 PMAre you using version 1.3 or 1.5? If you're using 1.3, have you changed the IP address of your WAPT server? When you say the deployment is successful, do you mean you're able to push updates from the console?Floflobel wrote: ↑May 22, 2018 - 2:29 PM The entire server is functional, and package deployment is working correctly.
However, I cannot access the machine via VNC, nor can I manage the computer remotely. Everything was working fine before the rollback. Is there a procedure to follow to resolve this issue?
Sincerely,
Denis
That's exactly it, I can push the updates directly to the workstations if they are turned on.
Sincerely,
