Turnkeylinux Missing No such file or directory exist

possibility1234

New Member
Mar 26, 2025
8
0
1
Hello All--

I read in a post to execute pveam update to resolve this issue

unable to open file '/var/lib/pve-manager/apl-info/releases.turnkeylinux.org' - No such file or directory
400 Parameter verification failed.

Executing pveam update did not work for me. Checking the log at cat /var/log/pveam.log revealed these error logs. pasted below. Can someone help how to overcome this hurdle?

2025-03-13 03:24:21 starting update
2025-03-13 03:24:21 start download http://download.proxmox.com/images/aplinfo-pve-8.dat.as
2025-03-13 03:24:33 download failed: 500 Can't connect to download.proxmox.com:80 (Temporary failure in name resolution)
 
Hello,
the network configuration of your node seems to be incorrect.
Would you like to post the output of following command cat /etc/network/interfaces ?
And then describe additionally, how your node is connected to the internet.
 
Hello All--

I read in a post to execute pveam update to resolve this issue

unable to open file '/var/lib/pve-manager/apl-info/releases.turnkeylinux.org' - No such file or directory
400 Parameter verification failed.

Executing pveam update did not work for me. Checking the log at cat /var/log/pveam.log revealed these error logs. pasted below. Can someone help how to overcome this hurdle?

2025-03-13 03:24:21 starting update
2025-03-13 03:24:21 start download http://download.proxmox.com/images/aplinfo-pve-8.dat.as
2025-03-13 03:24:33 download failed: 500 Can't connect to download.proxmox.com:80 (Temporary failure in name resolution)
Hi Possibility! This sounds like a connectivity issue! Specifically, you are being told that your machine cannot connect to a DNS server to resolve the address download.proxmox.com . To fix this, as fba pointed out, you would have to look at the contents of your /etc/network/interfaces file. Could you give us some more information on your network setup, please?
 
Thank you. Resolved the present error by
1. ADDING 8.8.8.8 to Proxmox DNS to download file
2. Setup a Container with ID as 29998
3. Setup a Storage called nas-archive
4. Start the Container 29998
5. Ran apt-get update

I need to resolve two error:

1. 400 parameter verification failed
2. failed to create file: /etc/haproxy/haproxy.cfg: because of "Key is stored in legacy trusted.gpg keyring"/etc/apt/trusted.gpg

The entire error is pasted below

400 Parameter verification failed.
template: no such template
pveam download <storage> <template>
CT 29998 already exists on node 'pve'
CT 29998 already running
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
curl is already the newest version (7.88.1-10+deb12u12).
gnupg2 is already the newest version (2.2.40-1.1).
0 upgraded, 0 newly installed, 0 to remove and 52 not upgraded.
W: http://haproxy.debian.net/dists/buster-backports-2.3/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
100 5604 100 5604 0 0 1607 0 0:00:03 0:00:03 --:--:-- 1608
OK
deb http://haproxy.debian.net buster-backports-2.3 main
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '2.3.20-1~bpo10+1' (HAProxy 2.3:buster-backports-2.3 [amd64]) for 'haproxy'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
haproxy : Depends: libssl1.1 (>= 1.1.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
W: http://haproxy.debian.net/dists/buster-backports-2.3/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
failed to create file: /etc/haproxy/haproxy.cfg: No such file or directory
Failed to restart haproxy.service: Unit haproxy.service not found.
 
I can't really help you if you don't tell me what you did to lead to the errors you describe.
 
I have this set of script , executing sh scripts/setup-haproxy.sh brought up errow dowlnloading files. I noticed that release.turnkeylinux is a repositories of Proxmox with the link. the pve subfolder has all the files needed. I resolved this series of errors following this steps below

Resolved the present error with this steps:
Thank you. Resolved the present error by
1. ADDING 8.8.8.8 to Proxmox DNS to download file
2. Setup a Container with ID as 29998
3. Setup a Storage called nas-archive
4. Start the Container 29998
5. Ran apt-get update

However, I got this error message after I applied this changes above
1. 400 parameter verification failed
2. failed to create file: /etc/haproxy/haproxy.cfg: because of "Key is stored in legacy trusted.gpg keyring"/etc/apt/trusted.gpg

The entire error is pasted below

400 Parameter verification failed.
template: no such template
pveam download <storage> <template>
CT 29998 already exists on node 'pve'
CT 29998 already running
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
curl is already the newest version (7.88.1-10+deb12u12).
gnupg2 is already the newest version (2.2.40-1.1).
0 upgraded, 0 newly installed, 0 to remove and 52 not upgraded.
W: http://haproxy.debian.net/dists/buster-backports-2.3/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
deb http://haproxy.debian.net buster-backports-2.3 main
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '2.3.20-1~bpo10+1' (HAProxy 2.3:buster-backports-2.3 [amd64]) for 'haproxy'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
haproxy : Depends: libssl1.1 (>= 1.1.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
W: http://haproxy.debian.net/dists/buster-backports-2.3/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
failed to create file: /etc/haproxy/haproxy.cfg: No such file or directory
Failed to restart haproxy.service: Unit haproxy.service not found.
 
You're using some script, which is neither created nor supported by Proxmox. You should ask the maintainer of the script for help or get some help here: https://github.com/community-scripts/ProxmoxVE/discussions

To provide some hints anyway:
1. the containers the script wants to created already exist, most likely due to your earlier attempts
2. whatever template the script wants to use doesn't exist in your local storage
3. you need to do what is described here for the haproxy repo. https://gist.github.com/bmatthewshea/7d5b96763607738df9cadb17df48ec00
 
The link helped. Thank you

However, How do I identify badly placed key from apt-key? a cat command brought up the key in the right template?. I have attached samples from apt-key list
 

Attachments

I have this set of script , executing sh scripts/setup-haproxy.sh brought up errow dowlnloading files.

Those scripts are 5 years old and are using Debian 10/Buster, which is EOL since 2,5 years.

I would recommend to base your efforts on recent versions respectively guides...