Recent content by Raymond Burns

root@prox-f:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution...

root@prox-f:~# apt update Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB] Ign http://ftp.debian.org stretch InRelease Hit http://ftp.debian.org stretch Release.gpg Hit http://download.proxmox.com stretch InRelease Hit http://ftp.debian.org stretch Release Hit...

I do not have a subscription key. Reading state information... Done The following extra packages will be installed: pve-kernel-4.15 pve-kernel-4.15.15-1-pve The following NEW packages will be installed: pve-kernel-4.15 pve-kernel-4.15.15-1-pve The following packages will be upgraded...

root@prox-f:~# ls -l /etc/apt/sources.list.d/ total 1 -rw-r--r-- 1 root root 66 May 4 07:27 ceph.list -rw-r--r-- 1 root root 67 May 4 07:27 pve-enterprise.list I only have the two repositories. root@prox-f:~# cat /etc/apt/sources.list.d/ceph.list deb...

Not sure what's going on. I have 3 nodes that all have the same issue with inplace upgrade. root@prox-f:~# cat /etc/apt/sources.list deb http://ftp.debian.org/debian stretch main contrib # PVE pve-no-subscription repository provided by proxmox.com, # NOT recommended for production use deb...

OH THANK GOD! systemctl enable ceph-mon@3.service That seems to have worked for some reason. Then I was able to start the service. So maybe the wiki should reverse those. Also, I was under the impression that the service would be listed somewhere in systemd. So after starting manually did...

well this is new... prox-e:~# journalctl -u ceph-osd@34.service -- Logs begin at Wed 2018-03-14 20:18:57 CDT, end at Thu 2018-03-15 07:58:43 CDT. -- Mar 14 20:19:22 prox-e systemd[1]: Starting Ceph object storage daemon... Mar 14 20:19:25 prox-e ceph-osd-prestart.sh[3265]: 2018-03-14...

I have since rebooted several times as I was going through troubleshooting. That should not have removed ceph-mon.3.service

Yes, but I did not do: systemctl start ceph-mon@<MON-ID>.service systemctl enable ceph-mon@<MON-ID>.service The ceph-mon@<MON-ID>.service was not there to be started. Tab completion did not work, and manually setting ceph-mon@3.service did not work. prox-e:~# systemctl start...

I thought I was missing something, so I tried to use pveceph, but no avail. root@prox-e:~# pveceph createmon monitor address '192.168.12.24:6789' already in use by 'mon.3' root@prox-e:~# pveceph install -version jewel download and import ceph repository keys update available package list...

Also, I tried to list ALL of the packages that I have installed but it was too long. Below that is all of the packages using grep. I don't show any conflicting ceph packages. The main reason this is so weird is because it happened to all 4 of my nodes. Which makes me think that it's a bug...

As you can see in the log. I upgraded to the latest Proxmox 4.4 with a working CEPH cluster on 2018-03-11. I made sure the PVE Cluster was healthy, quorum and running fine with the latest packages. Then I proceeded to run the Hammer to Jewel upgrade on 2018-03-13 The only reason I was doing...

also, root@prox-e:~# ceph --version ceph version 10.2.10 (5dc1e4c05cb68dbf62ae6fce3f0700e4654fdbbe)

Also prox-e:~# pveversion -v proxmox-ve: 4.4-107 (running kernel: 4.4.98-6-pve) pve-manager: 4.4-22 (running version: 4.4-22/2728f613) pve-kernel-4.4.35-1-pve: 4.4.35-77 pve-kernel-4.4.59-1-pve: 4.4.59-87 pve-kernel-4.4.44-1-pve: 4.4.44-84 pve-kernel-4.4.67-1-pve: 4.4.67-92...

oh yes, I forgot to list: root@prox-e:~# pvecm status Quorum information ------------------ Date: Wed Mar 14 21:31:51 2018 Quorum provider: corosync_votequorum Nodes: 4 Node ID: 0x00000004 Ring ID: 1/4988 Quorate: Yes Votequorum information...