Page 1 of 1
None IP reachable for this host
Published: May 22, 2018 - 2:29 PM
by Floflobel
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,
Re: None IP reachable for this host
Published: May 22, 2018 - 3:58 PM
by dcardon
Hello Floflobel,
Floflobel wrote: ↑May 22, 2018 - 2:29 PM
I had to roll back my WAPT server following data corruption.
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)?
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?
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?
Sincerely,
Denis
Re: None IP reachable for this host
Published: May 23, 2018 - 11:59
by Floflobel
Hello dcardon,
Thank you for your quick response.
dcardon wrote: ↑May 22, 2018 - 3:58 PM
Hello Floflobel,
Floflobel wrote: ↑May 22, 2018 - 2:29 PM
I had to roll back my WAPT server following data corruption.
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)?
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.
dcardon wrote: ↑May 22, 2018 - 3:58 PM
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?
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?
Sincerely,
Denis
As previously stated, I am on version 1.5.23 and the WAPT server IP address has never changed.
That's exactly it, I can push the updates directly to the workstations if they are turned on.
Sincerely,