-
Notifications
You must be signed in to change notification settings - Fork 54
No access web GUI since apply patch 6.1-8 (to) 6.1-11 #49
Comments
Ok, I have reinstall my pve-manager with
And now seems fine, I can access to web manager with 6.1-8 version. But, when I test the 6.1-8 script with test, I have always fail.
$ patch_apply / --dry-run --batch Best regards, |
apt upgrade says me new version and install 6.1-11 manager version. Script always fail (seems normal) |
Except script not working with 6.1.11 , I see that there is a new compression algorithm at the |
Script always fail for 6.1-11 |
New version of proxmox released, 6.2-4. Script always fail. |
Please use 6.2-4: #50 (comment) |
Hello,
I have a Proxmox version 6.1-8 and git clone the pve-patches, I put "bash pve-5.4-5-diff-backup-addon apply" and I have this return :
root@ns3080769:~/pve-patches# bash pve-5.4-5-diff-backup-addon apply
Proxmox VE 5.4-5 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, ayufan@ayufan.eu
checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 40632 (offset 10747 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 116 (offset 44 lines).
Hunk #2 succeeded at 155 (offset 45 lines).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5613 (offset 271 lines).
Hunk #2 FAILED at 5688.
Hunk #3 succeeded at 6458 (offset 474 lines).
1 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 FAILED at 494.
Hunk #2 FAILED at 780.
Hunk #3 succeeded at 1404 with fuzz 1 (offset 70 lines).
Hunk #4 succeeded at 1450 (offset 70 lines).
2 out of 4 hunks FAILED
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 FAILED at 398.
1 out of 1 hunk FAILED
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #1 FAILED at 8.
Hunk #2 FAILED at 171.
Hunk #3 succeeded at 636 (offset -101 lines).
Hunk #4 FAILED at 795.
Hunk #5 FAILED at 981.
Hunk #6 FAILED at 993.
Hunk #7 succeeded at 953 with fuzz 2 (offset -51 lines).
5 out of 7 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 319 (offset 23 lines).
Hunk #2 succeeded at 414 (offset 58 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 243 with fuzz 2 (offset 6 lines).
Hunk #2 FAILED at 347.
1 out of 2 hunks FAILED
FAILED to apply!
My VMs work but, now I can't access to my web manager, and pve-proxy fail...
root@ns3080769:~/pve-patches# pveproxy start
unknown file 'priv/acme/plugins.cfg' at /usr/share/perl5/PVE/Cluster.pm line 474.
Compilation failed in require at /usr/share/perl5/PVE/API2/ACMEAccount.pm line 13.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ACMEAccount.pm line 13.
Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 23.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 23.
Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 16.
Compilation failed in require at /usr/bin/pveproxy line 11.
BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Please help.
Best regards,
DECIGrade
The text was updated successfully, but these errors were encountered: