[RESOLVED] Version Upgrade

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
Yan
Messages: 4
Registration: January 24, 2024 - 3:23 PM

January 24, 2024 - 3:36 PM

Good morning, :)
I was working on version 1.8 of WAPT and I am currently installing the Enterprise version 2.4 and scaling it up.
I repackaged everything.
On some packages, I'm encountering errors that I didn't have before:

Code: Select all

SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 62-63: malformed \N character escape
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 62-63: malformed \N character escape (setup.py, line 17)
And

Code: Select all

AccessDenied: psutil.AccessDenied (pid=3172)
(In this last package, I kill a process, hence the psutil import)

It would seem that this is coming from the agent, right? Python version?
Thank you for your help :)
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 25, 2024 - 4:39 PM

Hello Yann,
Yan wrote: January 24, 2024 - 3:36 PM Good morning, :)
I was working on version 1.8 of WAPT and I am currently installing the Enterprise version 2.4 and scaling it up.
I repackaged everything.
On some packages, I'm encountering errors that I didn't have before:

Code: Select all

SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 62-63: malformed \N character escape
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 62-63: malformed \N character escape (setup.py, line 17)
WAPT version 1.8 came with Python 2.7, and version 2 comes with Python 3.8. Now, files must be UTF-8/Unicode compatible. You can verify that you have correctly configured this

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *
at the beginning of your file.

Perhaps you have a string with a \N but not an "r" in front of it to put it in raw mode and tell it not to interpret the backslash. Can you display line 17? (cf. https://www.geeksforgeeks.org/python-raw-strings/)
And

Code: Select all

AccessDenied: psutil.AccessDenied (pid=3172)
(In this last package, I kill a process, hence the psutil import)

It would seem that this is coming from the agent, right? Python version?
Thank you for your help :)
The accessdenied error comes from the OS; we would need more information about what you're trying to kill and how you retrieved the PID. The code in setup.py might also help answer this.

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Yan
Messages: 4
Registration: January 24, 2024 - 3:23 PM

February 9, 2024 - 10:48

Good morning :) ,
Thank you for your reply, I managed to solve it by doubling the "\\" in the file paths.
To stop the processes, I now use the command

Code: Select all

run(r'taskkill /f /im xxxxxx.exe')
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

February 9, 2024 - 10:55

Hi Yann,

thanks for the feedback. :-)

I'm marking the topic as RESOLVED.

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked