Couldn't find any package by glob error while installing Linux hearers

K

kumarullal

Renowned Member
Jun 17, 2009
184
0
81
LA, USA
I am trying to install Synology activebackup for business client on proxmox.
This is the error I am getting.


E: Unable to locate package linux-headers-5.15.102-1-pve E: Couldn't find any package by glob 'linux-headers-5.15.102-1-pve'
Don't know what happened?
How do I resolve this?
 
Proxmox VE has its own kernel and therefore its own header packages. Use apt install pve-headers-5.15.102-1-pve (if I did not make a typo) to install those kernel header. Install pve-headers of (pve-headers-5.15) to get the headers automatically with the new kernel update.
 
Ok, seems like it is synology problem while installing the agent.
The Linux headers are installed.
The installer complains of not installed.
* found linux-headers-5.15.102-1-pve not installed, install automatically * installing linux-headers-5.15.102-1-pve Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-headers-5.15.102-1-pve E: Couldn't find any package by glob 'linux-headers-5.15.102-1-pve' * install linux-headers-5.15.102-1-pve failed, please try again later, or run 'apt install linux-headers-5.15.102-1-pve manunally or download and install packag
What is globe?
 
Run apt update first. It might be possible that kernel 5.15.102 is retracted and you might want to run apt dist-upgrade first to install the latest kernel.
If installing the specific version does not work (because it does not exits because you or I made a typing mistake), try apt install pve-headers to install the latest kernel headers (like I said before).
 
I did apt upate, upgrade distibution upgrade.
The correct linux headers are installed. I think it is synology issue.
I will keep it open till I get a solution from synology, and try to post it here.
Thanks
 
Hello guys,

I've been thru this issue since proxox 7.3 here's how to solve it

wget https://mirror.cs.uchicago.edu/prox...e-headers-5.15.102-1-pve_5.15.102-1_amd64.deb

dpkg -i pve-headers-5.15.102-1-pve_5.15.102-1_amd64.deb

then it will work as magic and you will never see that error anymore
E: Unable to locate package linux-headers-5.15.102-1-pve
E: Couldn't find any package by glob 'linux-headers-5.15.102-1-pve'

so the main idea to download and install the headers file manually


i hope it will help you ,,, good luck

Together we discover the future :)
 
This is a fairly old post but just ran into the same issue today...

I managed to find a "nicer" solution to the linux headers problem but still ultimately could not get the backup agent working because the synosnap package is too old to run on modern proxmox I think.

Anyways for those who care, I used this thread as guide: https://community.synology.com/enu/forum/1/post/152443
I put the files in /home and ran: ./install.run --target ./tmp
This failed but now I had the individual setup stuff in /home/tmp/ directory.
I went to that new directory and opened ./install.sh with nano, goto the very end of the file and then a little up:
Change the word Linux to pve and save, now it wont look for Linux-headers but pve-headers and the install will proceed normally
1721063216282.png

However, even after all this synosnap does not install because it wants a old 5.15 kernel or something like that and gives dkms errors.
When i force install it with: dpkg --ignore-depends=dkms -i synosnap.deb
it installs with a some depreciated stuff warnings and then ultimately does not work and I just uninstalled everything :(

Hopefully at least this kinda helps someone in the future.
 
Last edited:
  • Like
Reactions: TeleTheo
Cecil said:
This is a fairly old post but just ran into the same issue today...

I managed to find a "nicer" solution to the linux headers problem but still ultimately could not get the backup agent working because the synosnap package is too old to run on modern proxmox I think.

Anyways for those who care, I used this thread as guide: https://community.synology.com/enu/forum/1/post/152443
I put the files in /home and ran: ./install.run --target ./tmp
This failed but now I had the individual setup stuff in /home/tmp/ directory.
I went to that new directory and opened ./install.sh with nano, goto the very end of the file and then a little up:
Change the word Linux to pve and save, now it wont look for Linux-headers but pve-headers and the install will proceed normally
View attachment 71374

However, even after all this synosnap does not install because it wants a old 5.15 kernel or something like that and gives dkms errors.
When i force install it with: dpkg --ignore-depends=dkms -i synosnap.deb
it installs with a some depreciated stuff warnings and then ultimately does not work and I just uninstalled everything :(

Hopefully at least this kinda helps someone in the future.
Click to expand...

Thank you very much! Thanks to the latest ABB-Update - where they added kernel 6 - it finally works for the latest version of proxmox.

Bash: 
wget http://download.proxmox.com/debian/pve/dists/bookworm/pve-no-subscription/binary-amd64/proxmox-headers-6.8.12-1-pve_6.8.12-1_amd64.deb
dpkg -i proxmox-headers-6.8.12-1-pve_6.8.12-1_amd64.deb
wget https://global.synologydownload.com/download/Utility/ActiveBackupBusinessAgent/2.7.0-3221/Linux/x86_64/Synology%20Active%20Backup%20for%20Business%20Agent-2.7.0-3221-x64-deb.zip
unzip Synology\ Active\ Backup\ for\ Business\ Agent-2.7.0-3221-x64-deb.zip
./install.run --target ./tmp
nano ./tmp/install.sh
cd ./tmp

Then in line 326 of 359 change
packages=(linux-headers-$(uname -r) dkms make)
to
packages=(pve-headers-$(uname -r) dkms make)
then run
./install.sh
and continue as usual.
Of my ext4 1TB system disk it recognizes the /dev/mapper/pve-root as /.

I did not try to do a restore, but the ABB portal shows the individual files of Disk 0 - Volume 1 (EFI) and LVM - pve-root (OS) in it's tree.
 
Last edited:
And they still have limited support for filesystems. I often thought of giving up ABB... I am excited to see how "well" this backup-image will work, in case my system disk crashes and I have to restore.
 
Veeam recently contacted me about adding lots more support specifically for proxmox if you are looking for a paid alternative.
Probably fueled a little by the fun recent events at vmware that shone a bright light on proxmox as an alternative :D
 
EDIT: Nevermind! Don't do this, it looks like it works but the backup fails upon reboot of the node. Switching linux- to pve- does survive reboots, so ignore my message.

---

Thanks a lot for the help with this.

Just one quick update, I found that instead of updating the package name, it was possible to update apt to apt-get in the script. Somehow apt-get is configured to understand that linux-headers... maps to pve-headers...

Don't ask me why, or how, it just seems to work. This looked like a slightly more resilient solution than modifying the mapping manually. Although, I'm not sure it is.

I just felt like sharing my discovery, maybe it's helpful to some.
 
Last edited:
Have just tested with v2.7.1 (updated in Feb 2025) and it works with modifications as in link above too. To download the package, use following:

Bash: 
wget https://global.synologydownload.com/download/Utility/ActiveBackupBusinessAgent/2.7.1-3235/Linux/x86_64/Synology%20Active%20Backup%20for%20Business%20Agent-2.7.1-3235-x64-deb.zip

For the rest, remains identical and modification required on the same line in install.sh
 
Last edited:
Did one of you actually managed to restore from a backup?

I was able to set everything up properly thanks to the instructions above, backups were running, but then ... I decided to do a DR test, that is: Destroy everything, and restore from the backup ...

It turns out I was missing the data partition (or LVM or something like that, I'm always confused what's the difference). So, after restore, none of my VMs were working anymore. And I had plenty of errors everywhere. So I've decided to not use ABB on Proxmox after all.

Did I do something wrong? Did you manage to successfully restore your Proxmox setup from the ABB backup? Or did I just misunderstand what the backup is intended to backup, and should have restored the data "thing" differently?
 
HelloThisIsFlo said:
Did one of you actually managed to restore from a backup?

I was able to set everything up properly thanks to the instructions above, backups were running, but then ... I decided to do a DR test, that is: Destroy everything, and restore from the backup ...

It turns out I was missing the data partition (or LVM or something like that, I'm always confused what's the difference). So, after restore, none of my VMs were working anymore. And I had plenty of errors everywhere. So I've decided to not use ABB on Proxmox after all.

Did I do something wrong? Did you manage to successfully restore your Proxmox setup from the ABB backup? Or did I just misunderstand what the backup is intended to backup, and should have restored the data "thing" differently?
Click to expand...
I've only used Synology ABB as a safety in case I need to restore and then have the relevant files on hand if/when needed (not full system restore). However, I've just checked the ABB Portal and see that the folder /etc/pve is empty (which is key in restoring anything :( )

Did you see these 2 articles from Synology (Create bootable USB& restore, but fails to boot). I've got a spare node and will try running a full DR backup/restore in the coming weeks
 
Last edited:
rjblake said:
I've only used Synology ABB as a safety in case I need to restore and then have the relevant files on hand if/when needed (not full system restore). However, I've just checked the ABB Portal and see that the folder /etc/pve is empty (which is key in restoring anything :( )

Did you see these 2 articles from Synology (Create bootable USB& restore, but fails to boot). I've got a spare node and will try running a full DR backup/restore in the coming weeks
Click to expand...
Hi @rjblake,

Thanks for following up. I had followed the first link (bootable USB, I used the live ISO, but mostly same thing), however I didn't see the second link and it could indeed have been helpful! Not sure it'd solve the problem, but at a quick glance it seems to cover similar issues

I am very looking forward to hearing the results of your DR test on your spare node Let us know if you managed to recover, and if so, what special steps you took. And if you didn't take any special steps, I'd be curious to know if you have some custom backup config

Anyway, let us know. Looking forward to it!

Thanks!
 
You must log in or register to reply here.
Top Bottom