Tranquil IT Forum

dcardon wrote: ↑Jan 16, 2018 - 6:32 PM I think I see where the problem is. For now, you can run the following commands:

`rm -f /var/www/wapt/
waptsetup-tis.exe` `apt-get install --reinstall tis-waptsetup`

I'll fix it tomorrow. I thought this bug was already fixed... sorry.

Denis

I followed the instructions correctly, but there's no change for me; the setup and agent are still at 1.5.13. I don't understand... I'll wait for the next version!

Matthiman wrote: ↑Jan 17, 2018 - 3:27 PM I followed the instructions correctly but there's no change for me, still on 1.5.13 for the setup and the agent, I don't understand... I'll wait for the next version!

I restarted it this morning, it's working!
THANKS

Even when waptconsole.exe and the wapt installation folder are excluded, it automatically ejects the executable.

Hi,
I've had a strange issue since version 1.5.1.15. Some agents have correctly installed the wapt-upgrade 1.5.1.15 package, but in the wapt console, the wapt version column still shows 1.5.1.8...

And another odd thing is that some clients, while upgrading to 1.5.1.15, have corrupted themselves by removing Python libraries, making it impossible to restart the wapt service...

Have you ever seen this kind of behavior?
Thanks in advance,

Nobody? It happened to me again this morning.

guigeek wrote: ↑Jan 23, 2018 - 5:14 PM Hi,
I've had a strange issue since version 1.5.1.15. Some agents have correctly installed the wapt-upgrade 1.5.1.15 package, but in the wapt console, the wapt version column still shows 1.5.1.8...

And another strange thing: some clients, when upgrading to 1.5.1.15, corrupted themselves by removing Python libraries, making it impossible to restart the wapt service...

Have you ever seen this kind of behavior?
Thanks in advance,

Hello,

what is the correct order of operations when upgrading from version 1.3 to 1.5 using remote repositories?
We have set up a test WAPT infrastructure with a main central server and 12 remote repositories, currently at version 1.3.13.
Should we first update the tis-waptrepo package on all remote repositories and then update the main server?
Should we disable SyncThing replication beforehand? Or something else?

Thomas

Hello

, the documentation describes installing tis-waptrepo to install Apache.

In your case, you don't need to do anything on the remote repositories.

HOWEVER, BEWARE!

The migration from 1.3 to 1.5 requires all WAPT packages to be re-signed. This will generate traffic on all your remote repositories, so be mindful of your bandwidth!


Also, be aware that if you enable HTTPS certificate verification in version 1.5, you will need to replace the HTTPS certificates of the remote repositories.

sfonteneau wrote: ↑Feb 9, 2018 - 11:31 AM Hello,

The documentation says to install tis-waptrepo to install Apache.

In your case, you don't need to do anything on the remote repositories.

HOWEVER, BEWARE!

The migration from 1.3 to 1.5 requires that all WAPT packages be re-signed. This will generate traffic on all your remote repositories, so be careful with your bandwidth!


Also, be aware that if you enable HTTPS certificate verification in version 1.5, you will need to replace the HTTPS certificates of the remote repositories.

Good morning,

Thank you for your response.
Yes, I had noted that all packages needed to be resigned, and that this would therefore result in a complete replication
So there's no need to update the tis-waptrepo on the repo, ok, however they will remain at version 1.3.13, no problem?
Okay for the HTTPS certificate, I'll look into it more closely. Is there any documentation or tutorial for it?

THANKS

Hello, I would like to know if version 1.5 is still in beta or not?
Because I see that the download links on the website and in the documentation (even for version 1.5) download the installation file for version 1.3.

Thank you.

I don't want to spoil anything, but it's 21 days

until the next release. The links are being updated.

- Alexandre