Hello,
when I open the wapt console (version 1.5.24) and navigate to the private repository, it's empty and displays the following error message:
An unhandled exception has occurred
. Exceptions.ValueError: invalid literal for int() with base 10: '1399a27'
Debian server,
Windows 7 client.
Can you help me, please?
Regards
[RESOLVED] Empty private repository and error message
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
Hello,
is this a "fresh" installation or an update of WAPT from a previous version?
Alexandre
is this a "fresh" installation or an update of WAPT from a previous version?
Alexandre
I suspect one of your packages has a non-canonical version... the console isn't tolerant.
Package versions must follow the format "1.2.3.4-5".
Check your repository directory on the WAPT server (c:\wapt\waptserver\repository\wapt on Windows) to see if a file is named with a version number of 1399a27.
If so, set that package aside and rescan for packages manually (wapt-scanpackages c:\wapt\waptserver\repository\wapt or wapt-get update-packages c:\wapt\waptserver\repository\wapt on Windows).
Package versions must follow the format "1.2.3.4-5".
Check your repository directory on the WAPT server (c:\wapt\waptserver\repository\wapt on Windows) to see if a file is named with a version number of 1399a27.
If so, set that package aside and rescan for packages manually (wapt-scanpackages c:\wapt\waptserver\repository\wapt or wapt-get update-packages c:\wapt\waptserver\repository\wapt on Windows).
Tranquil IT
Thank you for this information, but the server is running Debian, could you please provide me with the commands?htouvet wrote: ↑Jul 12, 2018 - 9:32 AM I think one of your packages has a non-canonical version... the console isn't tolerant.
Package versions must follow the format "1.2.3.4-5".
Check in your repository directory on the WAPT server (c:\wapt\waptserver\repository\wapt on Windows) if a file is named with a version number of 1399a27.
If so, set that package aside and restart the package scan manually (wapt-scanpackages c:\wapt\waptserver\repository\wapt or wapt-get update-packages c:\wapt\waptserver\repository\wapt on Windows).
on the server:
Code: Select all
ls /var/www/wapt/*1399a27*
mv /var/www/wapt/*1399a27* /root/
wapt-scanpackages /var/www/wapt
Tranquil IT
Problem solved!
I found the package in question, removed it, and ran the following commands:
/opt/wapt/wapt-scanpackages.py /var/www/wapt/
/opt/wapt/wapt-scanpackages.py /var/www/wapt-host/
/opt/wapt/wapt-scanpackages.py /var/www/wapt-group/
Thanks again for your help!
I found the package in question, removed it, and ran the following commands:
/opt/wapt/wapt-scanpackages.py /var/www/wapt/
/opt/wapt/wapt-scanpackages.py /var/www/wapt-host/
/opt/wapt/wapt-scanpackages.py /var/www/wapt-group/
Thanks again for your help!
