Tranquil IT Forum

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

Hello,
you will find the information in /var/log/daemon.log.

This information should indeed be displayed on the console.

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

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.

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