Hello everyone,
I'm still testing WAPT 1.5.1.21.
I've created/modified about 70 packages to suit my setup.
My idea is to use WAPT at the end of a system image deployment to install the software according to the final target of the workstation... so to keep the system and applications separate.
During my tests on a VM (Win7x64) and a physical Win7x64 machine, I'm asking WAPT to install a package with 30 dependencies...
But WAPTDeploy crashes mid-installation... for example: 21 packages to install... I shut down the workstation... the installations start... and poof, after 10 minutes, the workstation shuts down.
I've tried several timers: sometimes 1 minute 35 seconds, 13 minutes, 15 minutes 20 seconds... very random...
I tried deleting the local GPOs (gpt.ini) but no luck: WAPTExit stopped at 1 minute 35 seconds...
What should I do?
[Resolved] WAPTExit shuts down {randomly}
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
waptexit will shut down if the waptservice stops responding (there is a timeout).
Depending on the load of the installations and the type of machine, this must explain the variability in the occurrence of the phenomenon.
I think the timeout is 2s on wapt 1.5.1.21 which is quite short.
You can try setting a much higher value (20s for example) in the wapt-get.ini file on the machines:
c:\wapt\wapt-get.ini (or c:\program files(x86)\wapt\wapt-get.ini)
Depending on the load of the installations and the type of machine, this must explain the variability in the occurrence of the phenomenon.
I think the timeout is 2s on wapt 1.5.1.21 which is quite short.
You can try setting a much higher value (20s for example) in the wapt-get.ini file on the machines:
c:\wapt\wapt-get.ini (or c:\program files(x86)\wapt\wapt-get.ini)
Code: Select all
[global]
...
waptservice_timeout=20
Tranquil IT
Thank you for your quick response.
In my wapt-get.ini file, I have this:
So there's no value for waptservice_timeout... I'll add that value and let you know if there's any improvement.
In my wapt-get.ini file, I have this:
Code: Select all
[global]
repo_url=https://wapt.xxxxxxxxxxx/wapt
send_usage_report=1
use_hostpackages=1
wapt_server=https://wapt.xxxxxxxxxxx
use_kerberos=0
check_certificates_validity=1
verify_cert=0
dnsdomain=
max_gpo_script_wait=180
pre_shutdown_timeout=180
hiberboot_enabled=0
[wapt-templates]
repo_url=https://store.wapt.fr/wapt
verify_cert=1
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
I tested with waptservice_timeout=20 ... there's been some improvement, but the installations stopped halfway through...
I'll try with a value of "40"...
If I use a very large value like 150, could that have any (negative) side effects?
Thanks.
I'll try with a value of "40"...
If I use a very large value like 150, could that have any (negative) side effects?
Thanks.
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
Setting a value that is too high can cause a shutdown timeout issue if, for some reason, Windows terminates the waptservice before waptexit starts.
in this specific case. https://wapt.tranquil.it/wapt/nightly/w ... -7ee22ace/ )
in this specific case. https://wapt.tranquil.it/wapt/nightly/w ... -7ee22ace/ )
Tranquil IT
I need to migrate from 1.5.21 to 1.7, but are you sure about the link provided?
Shouldn't it be https://wapt.tranquil.it/wapt/nightly/w ... 5-7d975db1 ?
Shouldn't it be https://wapt.tranquil.it/wapt/nightly/w ... 5-7d975db1 ?
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
Hello,
since the update to version 1.7.3.5, everything seems to be working correctly.
I did leave the "waptservice_timeout" at 40.
WAPTExit seems stable and completes installations/updates successfully.
Thank you for your help.
since the update to version 1.7.3.5, everything seems to be working correctly.
I did leave the "waptservice_timeout" at 40.
WAPTExit seems stable and completes installations/updates successfully.
Thank you for your help.
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
