Server: Debian Stretch, Wapt 1.6.2.7 newly installed.
Hello,
I'm getting an error when I try to install Wapt packages from the 1.6.2.7 console, regardless of the Windows version on the machine hosting the console (Windows 7, 10, or Server 2008 R2) and the client machine (unless it's the machine on which the console is running). Screenshot attached.
However, everything works normally if I don't try to force the installation from the console. The pending packages install correctly when the machine shuts down.
Furthermore, if I request the installation from the client via the WaptTray, it works normally.
Where can I find more information about the cause of the error? Any ideas?
Thanks in advance,
Christophe
[RESOLVED] Error launching package installation
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
-
Christophe ROBERT
- Messages: 3
- Registration: Oct 05, 2018 - 11:50
- Attachments
-
- Screenshot 2018-10-05 at 11:29:29.jpg (11.6 KB) Viewed 4594 times
Hello,
you will find the information in /var/log/daemon.log.
This information should indeed be displayed on the console.
you will find the information in /var/log/daemon.log.
This information should indeed be displayed on the console.
Tranquil IT
-
Christophe ROBERT
- Messages: 3
- Registration: Oct 05, 2018 - 11:50
Hello,
Thank you htouvet for your reply.
But I can't find anything in daemon.log that could give me a clue.
No log line is generated when I trigger the error in the console.
I'm stumped...
Christophe
Thank you htouvet for your reply.
But I can't find anything in daemon.log that could give me a clue.
No log line is generated when I trigger the error in the console.
I'm stumped...
Christophe
You can start the server in a more verbose mode (loglevel info at a minimum)
on the server:
then you perform your action on the console.
You should see the cause of the error.
on the server:
Code: Select all
systemctl stop waptserver
/opt/wapt/runwaptserver.sh -linfo
You should see the cause of the error.
Tranquil IT
-
Christophe ROBERT
- Messages: 3
- Registration: Oct 05, 2018 - 11:50
Hello,
Bingo!
Thanks to this good advice, I was able to obtain these traces:
2018-10-16 17:14:39,193 INFO 0dfeebb199ab4d5c9117e2ab4431dff6: Received packet MESSAGE data 31[{"msg": "Error on client: SSLVerifyException(u'Data too old or in the future age: 596s...',)", "error_code": "sslverifyexception", "request_time": 0.046000003814697266, "success": false, "uuid": "AB1BA894-E753-11DD-8073-46623DD31DE2"}]
2018-10-16 17:14:39,194 INFO received ack from 0dfeebb199ab4d5c9117e2ab4431dff6 [/]
... which indicate a clock problem on the console PC: the clock was 10 minutes behind.
Once the clock was corrected, there were no more error messages, and everything worked.
However, are these traces recorded in a log file? It doesn't seem to be in daemon.log.
In any case, thank you so much!
Christophe
Bingo!
Thanks to this good advice, I was able to obtain these traces:
2018-10-16 17:14:39,193 INFO 0dfeebb199ab4d5c9117e2ab4431dff6: Received packet MESSAGE data 31[{"msg": "Error on client: SSLVerifyException(u'Data too old or in the future age: 596s...',)", "error_code": "sslverifyexception", "request_time": 0.046000003814697266, "success": false, "uuid": "AB1BA894-E753-11DD-8073-46623DD31DE2"}]
2018-10-16 17:14:39,194 INFO received ack from 0dfeebb199ab4d5c9117e2ab4431dff6 [/]
... which indicate a clock problem on the console PC: the clock was 10 minutes behind.
Once the clock was corrected, there were no more error messages, and everything worked.
However, are these traces recorded in a log file? It doesn't seem to be in daemon.log.
In any case, thank you so much!
Christophe
