- 0 replies
- 28 views
- Add Reply
- ceph crash archive <ID>: Archives single crash entry (will not appear in Proxmox GUI anymore)
- ceph crash archive-all: Archives all crash entries (no longer appear in the Proxmox GUI)
- ceph crash info <ID >: Show details about the specific crash
- ceph crash stat: Shows the number of crashes since Ceph installation
- ceph crash rm <ID>: Deletes a single crash entry
- ceph crash prune <DAYS>: Deletes crashes older than <DAYS> days
- 0 replies
- 40 views
- Add Reply
- 0 replies
- 21 views
- Add Reply
Matrix.Phoenix.lol - An open network for secure, decentralised communication
So we decided to give our users the opportunity to join in the secure communication!
Our matrix server address: matrix.phoenix.lol
This is the address you must enter into the Element program settings. Which is available for all platforms!
We also have our web version available, which you can use from any device! Web version: element.phoenix.lol
Matrix communication technology is an encrypted bunker for your messages, rooms, private and public chats! Communication is carried out both within one server and between servers! Each server is decentralized!
Register yourself, invite your friends, raise your nodes in the network!
Contact me via matrix: https://matrix.to/#/@fox:matrix.phoenix.lol
Proxmox GUI remove old Ceph Health Warnings
If you have solved a problem with Proxmox and Ceph, e.g. the crash of a monitor or OSD deamon has been noted and corrected, the error message often remains in the Proxmox web GUI. These log entries in the GUI are crash logs of the underlying Ceph system. The Ceph crash command can be used to manage Ceph crash logs:
List Ceph crashes
root@pve-01:~# ceph crash ls
ID ENTITY NEW
2020-10-26_15:18:33.471228Z_1e218df6-0c92-4269-8e03-3bf6564e9aac mon.pve-03
2020-10-26_15:29:58.556281Z_1cda3f71-d4a1-47e2-83e9-a08285d2e041 mon.pve-02
Hide Ceph Crashes from the Proxmox GUI
After archiving, the crashes are still viewable with ceph crash ls.
Ceph crash commands
Removing a ProxMox Cluster
Removing a ProxMox Cluster
Sometimes it is necessary to delete the created Proxmox cluster and create a new one. There are instructions on the network, but they are not suitable - after deletion the cluster does not work, but the old nodes hang gray (inactive) and it is not possible to assemble a new cluster.
First of all, we stop the cluster
rm -fr /etc/pve/nodes/*
systemctl stop pve-cluster
systemctl stop corosync
We are starting the cluster again in single mode
pmxcfs -l
Delete config files
rm /etc/pve/corosync.conf
rm -r /etc/corosync/*
We kill a single process, preferably several times.
killall pmxcfs
pmxcfs: no process found
e delete the list of nodes from the server, otherwise they will hang around there “dead”.
rm -fr /etc/pve/nodes
Let's turn on the cluster and enjoy life!
systemctl start corosync
systemctl start pve-cluster
Restart web muzzle
service pveproxy restart
