Le 11/01/2016 10:08, Eneko Lacunza a écrit :
This is a failed upgrade report from last friday.
We have a 4-node Proxmox cluster, with 3 of them running ceph MON and
3 osd daemons each. All nodes are updated last PVE 3.4 :
node1: vms + ceph mon + 3xceph osd
node2: vms + ceph mon + 3xceph osd
Hi Alain,
El 11/01/16 a las 10:40, Alain Péan escribió:
Le 11/01/2016 10:08, Eneko Lacunza a écrit :
This is a failed upgrade report from last friday.
[...]
This node2 server is a Dell T610, do you think the 4.2.2-1 kernel was
faulty for this server? Maybe updating the wiki with the last PVE
Hi all,
This is a failed upgrade report from last friday.
We have a 4-node Proxmox cluster, with 3 of them running ceph MON and 3
osd daemons each. All nodes are updated last PVE 3.4 :
node1: vms + ceph mon + 3xceph osd
node2: vms + ceph mon + 3xceph osd
node3: vms + ceph mon + 3xceph osd
Le 11/01/2016 11:21, Eneko Lacunza a écrit :
Thanks for sharing, I have updated wiki with the command to search the
latest kernel and the current latest kernel version:
https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0#Install_the_new_kernel
I saw, yes, it's fine. When I have to install a
Hi all,
We have a PVE 3.2 node at a customer that has started to log some Perl
warnings to syslog:
Jan 11 12:33:42 gorbea pvestatd[217188]: WARNING: Hexadecimal number >
0x non-portable at /usr/share/perl5/PVE/Tools.pm line 795,
line 1.
Jan 11 12:33:42 gorbea pvestatd[217188]:
Hi,
simply make a reboot, this is a small, uncritical, but quite annoying
"bug" where the fix wasn't backported to 3.2 when it was discovered (out
of date).
3.4 should fix this completely, also 4.0+. But as it occurs only about
after 2-3 Years uptime you should have been able to upgrade
Thanks a lot for the hint Thomas, this was funny to learn! ;)
# uptime
14:24:14 up 509 days, 6 min, 3 users, load average: 3,34, 3,26, 3,19
El 11/01/16 a las 13:07, Thomas Lamprecht escribió:
Hi,
simply make a reboot, this is a small, uncritical, but quite annoying
"bug" where the fix
