revert from proxmox 8 to 7

I know you're panicking, but take a deep breath and search the forums; the answers are probably here for you.
Madscientist said:
/dev/mapper/pve-root is 100% full
Click to expand...
for this, use du -sx to drill down on your file system and identify what consumed all space. then delete whats not needed; its probably in /var/log but could be elsewhere.

Madscientist said:
these r the new interface which changed its name, but unable to figure out corresponding name in v 7
Click to expand...

That is... unfortunate.

you can use ethtool to identify connection speed, etc; Assuming you know what physical nic is connected to what switch port, you'd just have to figure it out. lspci will show you what are the NIC make/models if you're not getting what you need from ethtool.

It would be a good idea to draw a diagram of whats connected to what, it would help you figure it out.
 
total 83469464
drwxr-xr-x 17 root root 4096 Nov 27 00:00 .
drwxr-xr-x 11 root root 4096 Nov 22 2022 ..
-rw-r--r-- 1 root root 825 Nov 26 01:05 alternatives.log
-rw-r--r-- 1 root root 15677 Nov 25 23:50 alternatives.log.1
-rw-r--r-- 1 root root 119 Aug 13 08:50 alternatives.log.2.gz
-rw-r--r-- 1 root root 496 May 28 2023 alternatives.log.3.gz
-rw-r--r-- 1 root root 204 Feb 15 2023 alternatives.log.4.gz
-rw-r--r-- 1 root root 525 Jan 31 2023 alternatives.log.5.gz
-rw-r--r-- 1 root root 2589 Dec 31 2022 alternatives.log.6.gz
drwxr-xr-x 2 root root 4096 Nov 26 00:00 apt
-rw-r----- 1 root adm 28672 Nov 28 07:58 auth.log
-rw-r----- 1 root adm 57317 Nov 26 00:00 auth.log.1
-rw-r----- 1 root adm 2935 Nov 18 23:17 auth.log.2.gz
-rw-r----- 1 root adm 2978 Nov 11 23:17 auth.log.3.gz
-rw-r----- 1 root adm 3740 Nov 4 23:17 auth.log.4.gz
-rw-rw---- 1 root utmp 0 Nov 1 00:00 btmp
-rw-rw---- 1 root utmp 0 Oct 1 00:00 btmp.1
drwxrws--T 2 ceph ceph 4096 Nov 27 00:00 ceph
drwxr-x--- 2 _chrony _chrony 4096 Dec 1 2022 chrony
drwxr-xr-x 2 root root 4096 Nov 16 2022 corosync
-rw-r----- 1 root adm 7936 Nov 28 07:17 cron.log
-rw-r----- 1 root adm 372 Nov 26 00:00 cron.log.1
-rw-r----- 1 root adm 3847354 Nov 25 23:49 daemon.log
-rw-r----- 1 root adm 3635120 Nov 19 00:00 daemon.log.1
-rw-r----- 1 root adm 71446 Nov 12 00:00 daemon.log.2.gz
-rw-r----- 1 root adm 80483 Nov 5 00:00 daemon.log.3.gz
-rw-r----- 1 root adm 77526 Oct 29 00:00 daemon.log.4.gz
-rw-r----- 1 root adm 4537 Nov 25 23:24 debug
-rw-r----- 1 root adm 4537 Aug 13 08:50 debug.1
-rw-r----- 1 root adm 1002 May 28 2023 debug.2.gz
-rw-r----- 1 root adm 2181 Feb 15 2023 debug.3.gz
-rw-r----- 1 root adm 2954 Feb 10 2023 debug.4.gz
-rw-r--r-- 1 root root 0 Nov 26 00:00 dpkg.log
-rw-r--r-- 1 root root 503141 Nov 25 23:54 dpkg.log.1
-rw-r--r-- 1 root root 1800 Aug 13 08:16 dpkg.log.2.gz
-rw-r--r-- 1 root root 5408 May 28 2023 dpkg.log.3.gz
-rw-r--r-- 1 root root 1997 Feb 19 2023 dpkg.log.4.gz
-rw-r--r-- 1 root root 1401 Jan 30 2023 dpkg.log.5.gz
-rw-r--r-- 1 root root 35230 Dec 15 2022 dpkg.log.6.gz
-rw-r--r-- 1 root root 2049472 Nov 25 23:49 faillog
-rw-r--r-- 1 root root 1364 Nov 25 23:49 fontconfig.log
drwxr-xr-x 2 root root 4096 May 18 2021 glusterfs
drwxr-xr-x 19 root root 4096 Nov 27 08:54 ifupdown2
drwxr-sr-x+ 3 root systemd-journal 4096 Dec 1 2022 journal
-rw-r----- 1 root adm 42669842432 Nov 28 07:59 kern.log
-rw-r----- 1 root adm 2543624 Nov 26 00:00 kern.log.1
-rw-r----- 1 root adm 1199 Nov 3 08:12 kern.log.2.gz
-rw-r----- 1 root adm 6602 Oct 28 19:41 kern.log.3.gz
-rw-r----- 1 root adm 6316 Oct 21 23:58 kern.log.4.gz
-rw-rw-r-- 1 root utmp 18701432 Nov 28 07:58 lastlog
drwxr-xr-x 2 root root 4096 Jul 4 2022 lxc
-rw-r----- 1 root adm 16738 Nov 25 23:48 mail.info
-rw-r----- 1 root adm 14569 Nov 18 04:20 mail.info.1
-rw-r----- 1 root adm 2165 Nov 11 04:20 mail.info.2.gz
-rw-r----- 1 root adm 2490 Nov 4 04:20 mail.info.3.gz
-rw-r----- 1 root adm 2523 Oct 28 04:20 mail.info.4.gz
-rw-r----- 1 root adm 63061 Nov 27 08:54 mail.log
-rw-r----- 1 root adm 18513 Nov 26 00:00 mail.log.1
-rw-r----- 1 root adm 2185 Nov 18 04:20 mail.log.2.gz
-rw-r----- 1 root adm 2165 Nov 11 04:20 mail.log.3.gz
-rw-r----- 1 root adm 2490 Nov 4 04:20 mail.log.4.gz
-rw-r----- 1 root adm 221706 Nov 25 23:49 messages
-rw-r----- 1 root adm 147 Nov 12 00:10 messages.1
-rw-r----- 1 root adm 142 Nov 5 00:10 messages.2.gz
-rw-r----- 1 root adm 1301 Nov 3 08:12 messages.3.gz
-rw-r----- 1 root adm 6720 Oct 28 19:41 messages.4.gz
drwxr-xr-x 2 root root 4096 Nov 27 00:00 openvswitch
drwx------ 2 root root 4096 Dec 1 2022 private
drwxr-xr-x 3 root root 4096 Dec 1 2022 pve
-rw-r--r-- 1 root root 40784 Nov 28 05:29 pveam.log
-rw-r--r-- 1 root root 51925 Oct 28 01:37 pveam.log.0
-rw-r----- 1 root adm 55 Nov 27 00:00 pve-firewall.log
-rw-r----- 1 root adm 537 Nov 27 00:00 pve-firewall.log.1
-rw-r----- 1 root adm 189 Nov 26 00:00 pve-firewall.log.2.gz
-rw-r----- 1 root adm 121 Nov 25 00:00 pve-firewall.log.3.gz
-rw-r----- 1 root adm 121 Nov 24 00:00 pve-firewall.log.4.gz
-rw-r----- 1 root adm 121 Nov 23 00:00 pve-firewall.log.5.gz
-rw-r----- 1 root adm 121 Nov 22 00:00 pve-firewall.log.6.gz
-rw-r----- 1 root adm 124 Nov 21 00:00 pve-firewall.log.7.gz
drwx------ 2 www-data www-data 4096 Nov 27 00:00 pveproxy
lrwxrwxrwx 1 root root 39 Nov 25 23:48 README -> ../../usr/share/doc/systemd/README.logs
drwxr-xr-x 3 root root 4096 Dec 1 2022 runit
drwxr-x--- 2 root adm 4096 Aug 10 2022 samba
-rw-r----- 1 root adm 42783801344 Nov 28 07:59 syslog
-rw-r----- 1 root adm 6693195 Nov 26 00:00 syslog.1
-rw-r----- 1 root adm 88294 Nov 19 00:00 syslog.2.gz
-rw-r----- 1 root adm 80929 Nov 12 00:00 syslog.3.gz
-rw-r----- 1 root adm 93229 Nov 5 00:00 syslog.4.gz
-rw-r----- 1 root adm 2219 Nov 26 01:05 user.log
-rw-r----- 1 root adm 1540 Nov 26 00:00 user.log.1
-rw-r----- 1 root adm 84 Aug 13 08:50 user.log.2.gz
-rw-r----- 1 root adm 568 May 28 2023 user.log.3.gz
-rw-r----- 1 root adm 118 Feb 15 2023 user.log.4.gz
drwxr-xr-x 2 root root 4096 Nov 3 08:11 vzdump
-rw-rw-r-- 1 root utmp 200448 Nov 28 07:58 wtmp

this is the log directory, i think syslog, and kern.log consuming the disk, i tried to delete these two files , but access denied


i figure out of the nic changed to new name , i am digging more on it, problem is i am unable to write changes on interface file, as disk is full.... first need to clean the log , any advise ?
 
you cannot remove syslog in place.

begin with looking AT your syslog and see what is spamming it. Once your confident you dont need any of it, you can zero it like so:
echo "" > /var/log/syslog

Bear in mind that if you dont stop/fix whatever is spamming your log, it will just fill up again.
 
syslog

2023-11-30T07:46:34.201393+05:30 pve-3 kernel: [369661.410755] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T07:46:34.201394+05:30 pve-3 kernel: [369661.410795] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T07:46:34.201395+05:30 pve-3 kernel: [369661.410828] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T07:46:34.201395+05:30 pve-3 kernel: [369661.410859] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T07:46:34.201396+05:30 pve-3 kernel: [369661.412442] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T07:46:34.201397+05:30 pve-3 kernel: [369661.412492] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T07:46:34.201398+05:30 pve-3 kernel: [369661.412537] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T07:46:34.201398+05:30 pve-3 kernel: [369661.412576] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T07:46:34.201399+05:30 pve-3 kernel: [369661.413386] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T07:46:34.201400+05:30 pve-3 kernel: [369661.413426] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T07:46:34.201400+05:30 pve-3 kernel: [369661.413458] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T07:46:34.205386+05:30 pve-3 kernel: [369661.413522] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T07:46:34.205387+05:30 pve-3 kernel: [369661.415121] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T07:46:34.205388+05:30 pve-3 kernel: [369661.415170] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T07:46:34.205393+05:30 pve-3 kernel: [369661.415217] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T07:46:34.205394+05:30 pve-3 kernel: [369661.415256] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T07:46:34.205395+05:30 pve-3 kernel: [369661.416091] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T07:46:34.205395+05:30 pve-3 kernel: [369661.416129] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T07:46:34.205396+05:30 pve-3 kernel: [369661.416169] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T07:46:34.205396+05:30 pve-3 kernel: [369661.416206] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T07:46:34.209387+05:30 pve-3 kernel: [369661.417789] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T07:46:34.209389+05:30 pve-3 kernel: [369661.417839] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T07:46:34.209390+05:30 pve-3 kernel: [369661.417884] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T07:46:34.209391+05:30 pve-3 kernel: [369661.417924] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T07:46:34.209392+05:30 pve-3 kernel: [369661.418759] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T07:46:34.209394+05:30 pve-3 kernel: [369661.418797] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T07:46:34.209395+05:30 pve-3 kernel: [369661.418836] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T07:46:34.209395+05:30 pve-3 kernel: [369661.418874] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T07:46:34.209396+05:30 pve-3 kernel: [369661.420455] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T07:46:34.209396+05:30 pve-3 kernel: [369661.420506] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T07:46:34.209397+05:30 pve-3 kernel: [369661.420551] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode

kern.log

2023-11-30T08:03:36.661386+05:30 pve-3 kernel: [370683.875784] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T08:03:36.661387+05:30 pve-3 kernel: [370683.875838] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T08:03:36.661388+05:30 pve-3 kernel: [370683.875884] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T08:03:36.661388+05:30 pve-3 kernel: [370683.875925] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T08:03:36.661389+05:30 pve-3 kernel: [370683.876837] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T08:03:36.661390+05:30 pve-3 kernel: [370683.876880] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T08:03:36.661394+05:30 pve-3 kernel: [370683.876913] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T08:03:36.661394+05:30 pve-3 kernel: [370683.876944] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T08:03:36.665388+05:30 pve-3 kernel: [370683.878581] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T08:03:36.665390+05:30 pve-3 kernel: [370683.878635] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T08:03:36.665391+05:30 pve-3 kernel: [370683.878680] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T08:03:36.665391+05:30 pve-3 kernel: [370683.878722] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T08:03:36.665392+05:30 pve-3 kernel: [370683.879644] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T08:03:36.665392+05:30 pve-3 kernel: [370683.879685] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T08:03:36.665393+05:30 pve-3 kernel: [370683.879721] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T08:03:36.665394+05:30 pve-3 kernel: [370683.879753] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T08:03:36.665398+05:30 pve-3 kernel: [370683.881381] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T08:03:36.665399+05:30 pve-3 kernel: [370683.881433] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T08:03:36.665399+05:30 pve-3 kernel: [370683.881480] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T08:03:36.665400+05:30 pve-3 kernel: [370683.881521] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T08:03:36.665401+05:30 pve-3 kernel: [370683.882373] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T08:03:36.665403+05:30 pve-3 kernel: [370683.882427] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T08:03:36.669386+05:30 pve-3 kernel: [370683.882463] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T08:03:36.669387+05:30 pve-3 kernel: [370683.882496] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T08:03:36.669388+05:30 pve-3 kernel: [370683.884173] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T08:03:36.669388+05:30 pve-3 kernel: [370683.884224] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T08:03:36.669389+05:30 pve-3 kernel: [370683.884306] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode
2023-11-30T08:03:36.669390+05:30 pve-3 kernel: [370683.884371] i40e 0000:b1:00.1 ens5f1: entered promiscuous mode
2023-11-30T08:03:36.669390+05:30 pve-3 kernel: [370683.885240] bnxt_en 0000:b2:00.0 ens4f0np0: left promiscuous mode
2023-11-30T08:03:36.669394+05:30 pve-3 kernel: [370683.885281] bnxt_en 0000:b2:00.1 ens4f1np1: left promiscuous mode
2023-11-30T08:03:36.669395+05:30 pve-3 kernel: [370683.885319] i40e 0000:b1:00.0 ens5f0: left promiscuous mode
2023-11-30T08:03:36.669396+05:30 pve-3 kernel: [370683.885356] i40e 0000:b1:00.1 ens5f1: left promiscuous mode
2023-11-30T08:03:36.673388+05:30 pve-3 kernel: [370683.887000] bnxt_en 0000:b2:00.0 ens4f0np0: entered promiscuous mode
2023-11-30T08:03:36.673390+05:30 pve-3 kernel: [370683.887051] bnxt_en 0000:b2:00.1 ens4f1np1: entered promiscuous mode
2023-11-30T08:03:36.673390+05:30 pve-3 kernel: [370683.887097] i40e 0000:b1:00.0 ens5f0: entered promiscuous mode


it seems to me it all related to network interface card mismatch or driver mismatch ....... not sure.... any advise .... i already cleared the log ...
 
2023-12-05T20:29:32.984124+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:32.978+0530 7f9c722ff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
2023-12-05T20:29:32.984138+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:32.978+0530 7f9c722ff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
2023-12-05T20:29:32.984152+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:32.978+0530 7f9c722ff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
2023-12-05T20:29:32.984165+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:32.978+0530 7f9c722ff6c0 -1 monclient: keyring not found
2023-12-05T20:29:32.984178+05:30 pve-3 ceph-crash[2036]: [errno 13] RADOS permission denied (error connecting to the cluster)
2023-12-05T20:29:33.055385+05:30 pve-3 ceph-crash[2036]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-11-25T17:51:38.807915Z_02ab151a-7b8d-4b87-a775-4b317b3795d4 as client.admin failed: 2023-12-05T20:29:33.050+0530 7f041acff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
2023-12-05T20:29:33.055437+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:33.050+0530 7f041acff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
2023-12-05T20:29:33.055451+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:33.050+0530 7f041acff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
2023-12-05T20:29:33.055462+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:33.050+0530 7f041acff6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
2023-12-05T20:29:33.055473+05:30 pve-3 ceph-crash[2036]: 2023-12-05T20:29:33.050+0530 7f041acff6c0 -1 monclient: keyring not found
2023-12-05T20:29:33.055487+05:30 pve-3 ceph-crash[2036]: [errno 13] RADOS permission denied (error connecting to the cluster)
2023-12-05T20:30:31.815783+05:30 pve-3 pveproxy[1660859]: worker exit
2023-12-05T20:30:31.837029+05:30 pve-3 pveproxy[4659]: worker 1660859 finished
2023-12-05T20:30:31.837076+05:30 pve-3 pveproxy[4659]: starting 1 worker(s)
2023-12-05T20:30:31.839993+05:30 pve-3 pveproxy[4659]: worker 1670262 started
2023-12-05T20:33:00.137624+05:30 pve-3 pvedaemon[416373]: <root@pam> successful auth for user 'root@pam'
2023-12-05T20:34:15.226777+05:30 pve-3 pvedaemon[405840]: <root@pam> starting task UPID:pve-3:001981D3:01798728:656F3BEF:vncshell::root@pam:
2023-12-05T20:34:15.228747+05:30 pve-3 pvedaemon[1671635]: starting termproxy UPID:pve-3:001981D3:01798728:656F3BEF:vncshell::root@pam:
2023-12-05T20:34:15.290850+05:30 pve-3 pvedaemon[417496]: <root@pam> successful auth for user 'root@pam'
2023-12-05T20:34:15.327168+05:30 pve-3 systemd[1]: Started session-105.scope - Session 105 of User root.


after a lot of struggle, and reinstalling the ifupdown2 (some reason ifupdow2 got corrupted ) the third server started, but is this any error in ceph ? kindly guide ? or any mistake ?
 
You must log in or register to reply here.
Top Bottom