Error when upgrading

S

svendsen

Renowned Member
Apr 18, 2012
61
1
73
Hi Guys,

Have any of you ever seen this error when upgrading Proxmox?

Code: 
Setting up pve-firmware (1.1-3) ...
Setting up pve-qemu-kvm (1.7-8) ...
Setting up qemu-server (3.1-16) ...
Setting up libpve-common-perl (3.0-18) ...
Setting up pve-manager (3.2-4) ...
Restarting PVE Daemon: pvedaemonCan't load '/usr/lib/perl5/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /usr/lib/perl5/auto/Net/SSLeay/SSLeay.so: symbol SSL_get0_next_proto_negotiated, version OPENSSL_1.0.1 not defined in file libssl.so.1.0.0 with link time reference at /usr/lib/perl/5.14/DynaLoader.pm line 184.
 at /usr/share/perl5/PVE/HTTPServer.pm line 16
Compilation failed in require at /usr/share/perl5/PVE/HTTPServer.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HTTPServer.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/APIDaemon.pm line 11.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/APIDaemon.pm line 11.
Compilation failed in require at /usr/bin/pvedaemon line 13.
BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 13.
 failed!
Restarting PVE API Proxy Server: pveproxyCan't load '/usr/lib/perl5/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /usr/lib/perl5/auto/Net/SSLeay/SSLeay.so: symbol SSL_get0_next_proto_negotiated, version OPENSSL_1.0.1 not defined in file libssl.so.1.0.0 with link time reference at /usr/lib/perl/5.14/DynaLoader.pm line 184.
 at /usr/share/perl5/PVE/HTTPServer.pm line 16
Compilation failed in require at /usr/share/perl5/PVE/HTTPServer.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HTTPServer.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/APIDaemon.pm line 11.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/APIDaemon.pm line 11.
Compilation failed in require at /usr/bin/pveproxy line 15.
BEGIN failed--compilation aborted at /usr/bin/pveproxy line 15.
 failed!
Restarting PVE SPICE Proxy Server: spiceproxyCan't load '/usr/lib/perl5/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /usr/lib/perl5/auto/Net/SSLeay/SSLeay.so: symbol SSL_get0_next_proto_negotiated, version OPENSSL_1.0.1 not defined in file libssl.so.1.0.0 with link time reference at /usr/lib/perl/5.14/DynaLoader.pm line 184.
 at /usr/share/perl5/PVE/HTTPServer.pm line 16
Compilation failed in require at /usr/share/perl5/PVE/HTTPServer.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HTTPServer.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/APIDaemon.pm line 11.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/APIDaemon.pm line 11.
Compilation failed in require at /usr/bin/spiceproxy line 15.
BEGIN failed--compilation aborted at /usr/bin/spiceproxy line 15.
 failed!
Restarting PVE Status Daemon: pvestatdCan't load '/usr/lib/perl5/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /usr/lib/perl5/auto/Net/SSLeay/SSLeay.so: symbol SSL_get0_next_proto_negotiated, version OPENSSL_1.0.1 not defined in file libssl.so.1.0.0 with link time reference at /usr/lib/perl/5.14/DynaLoader.pm line 184.
 at /usr/share/perl5/PVE/AccessControl.pm line 8
Compilation failed in require at /usr/share/perl5/PVE/AccessControl.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AccessControl.pm line 8.
Compilation failed in require at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 19.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 19.
Compilation failed in require at /usr/bin/pvestatd line 15.
BEGIN failed--compilation aborted at /usr/bin/pvestatd line 15.
 failed!
Setting up proxmox-ve-2.6.32 (3.2-129) ...
installing proxmox release key: OK
Setting up snmp (5.4.3~dfsg-2.8) ...
                                         
Current status: 0 broken [-1], 0 updates [-30], 35733 new [-1].

After starting up pvedaemon, pvestatd and pveproxy everything seems to work fine though..
 
Good point!
I actually do have Adaptec controller, and did install the maxView Storage Manager. Didn't have any issues with that though - it just worked :)
I still can log in to maxView - so not sure if that is the reason of the Proxmox upgrade errors. Everything seems to work.. just curious about the error messages..
 
Did you read the trouble shooting thread? That's not only about login issues, but also ssl issues!
Just read the thread and create the proper ssl linking. After that your ssl issues should be gone.
 
You must log in or register to reply here.
Top Bottom