FK
Я кстати ноде экспортер под омниос чуть переписал, надо кому?
Size: a a a
2019 December 09
FK
Там забросили его солярисовскую часть в мастере
СГ
В лучшем случае silver - есть рекомендации по ядрам и частоте?
с оперативой я уже давно понял что ее чем больше тем лучше, еще до обращения к теме SDS.
с оперативой я уже давно понял что ее чем больше тем лучше, еще до обращения к теме SDS.
FK
Да и не только райдз- он и чексуммы считает
СГ
Привет всем, может ли потенциально cisco nexus какими-то настройками ребутать хаотично proxmox? как пример ip igmp snooping querier 10.10.10.10 ?
#вопрос
@Oller22
#вопрос
@Oller22
только если в ядре linux есть ошибка в обработке multicast. Если это окажется так, то нас ждёт новый CVE-2019-11477
СГ
А что кроме фенсинга может инициировать перезагрузку проксмокса без других симптомов?
а сообщения в логах есть?
ОБ
только если в ядре linux есть ошибка в обработке multicast. Если это окажется так, то нас ждёт новый CVE-2019-11477
в syslog резкое начало загрузки. Сейчас логи ушли по времени и непоказательны.
ОБ
Из аномалий отваливающийся nfs. Но он по нагрузке
ОБ
и никогда не вызывал рестарта
СГ
в syslog резкое начало загрузки. Сейчас логи ушли по времени и непоказательны.
какая версия pve? ядра?
ОБ
какая версия pve? ядра?
root@v4:~# uname -a
Linux v4 4.15.18-20-pve #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200) x86_64 GNU/Linux
Linux v4 4.15.18-20-pve #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200) x86_64 GNU/Linux
ОБ
сейчас на последний обновляемся срочно
ОБ
а логи только смотрел вашими коммандами вот только только ушли
ОБ
блин даже показать уже нечего)
ОБ
хоть снова жди падения
ОБ
похоже на резкий ресет
ОБ
[03.12, 23:34] oler222222: Dec 3 10:20:00 v4 systemd[1]: Starting Proxmox VE replication runner...
Dec 3 10:20:25 v4 watchdog-mux[987]: client watchdog expired - disable watchdog updates
Dec 3 10:20:30 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:30 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an opera
ting system or network fault (reason: totem is continuously in gather state). The most common cause
of this message is that the local firewall is configured improperly.
Dec 3 10:20:32 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:32 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an opera
ting system or network fault (reason: totem is continuously in gather state). The most common cause
of this message is that the local firewall is configured improperly.
Dec 3 10:20:33 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:33 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an operating system or network fault (reason: totem is continuously in gather state). The most common cause of this message is that the local firewall is configured improperly.
Dec 3 10:23:25 v4 systemd-modules-load[461]: Inserted module 'iscsi_tcp'
Dec 3 10:23:25 v4 systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 3 10:23:25 v4 systemd[1]: Started Create Static Device Nodes in /dev.
Dec 3 10:23:25 v4 systemd[1]: Mounted RPC Pipe File System.
Dec 3 10:23:25 v4 systemd[1]: Starting pNFS block layout mapping daemon...
Dec 3 10:23:25 v4 systemd[1]: Starting udev Kernel Device Manager...
Dec 3 10:23:25 v4 systemd[1]: Started pNFS block layout mapping daemon.
Dec 3 10:23:25 v4 blkmapd[495]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Dec 3 10:23:25 v4 systemd[1]: Started Flush Journal to Persistent Storage.
Dec 3 10:23:25 v4 systemd-modules-load[461]: Inserted module 'ib_iser'
Dec 3 10:23:25 v4 systemd[1]: Started Set the ии keyboard layout.
Dec 3 10:23:25 v4 kernel: [ 0.000000] Linux version 4.15.18-20-pve (root@nora) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200) ()
Dec 3 10:23:25 v4 systemd[1]: Mounted NFSD configuration filesystem.
[03.12, 23:34] oler222222: Dec 3 10:23:25 v4 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.18-20-pve root=/dev/mapper/pve-root ro quiet
Dec 3 10:23:25 v4 kernel: [ 0.000000] KERNEL supported cpus:
Dec 3 10:23:25 v4 kernel: [ 0.000000] Intel GenuineIntel
Dec 3 10:23:25 v4 kernel: [ 0.000000] AMD AuthenticAMD
Dec 3 10:23:25 v4 kernel: [ 0.000000] Centaur CentaurHauls
Dec 3 10:23:25 v4 kernel: [ 0.000000] x86/fpu: x87 FPU will use FXSAVE
Dec 3 10:23:25 v4 kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Dec 3 10:20:25 v4 watchdog-mux[987]: client watchdog expired - disable watchdog updates
Dec 3 10:20:30 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:30 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an opera
ting system or network fault (reason: totem is continuously in gather state). The most common cause
of this message is that the local firewall is configured improperly.
Dec 3 10:20:32 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:32 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an opera
ting system or network fault (reason: totem is continuously in gather state). The most common cause
of this message is that the local firewall is configured improperly.
Dec 3 10:20:33 v4 corosync[16078]: warning [MAIN ] Totem is unable to form a cluster because of a
n operating system or network fault (reason: totem is continuously in gather state). The most commo
n cause of this message is that the local firewall is configured improperly.
Dec 3 10:20:33 v4 corosync[16078]: [MAIN ] Totem is unable to form a cluster because of an operating system or network fault (reason: totem is continuously in gather state). The most common cause of this message is that the local firewall is configured improperly.
Dec 3 10:23:25 v4 systemd-modules-load[461]: Inserted module 'iscsi_tcp'
Dec 3 10:23:25 v4 systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 3 10:23:25 v4 systemd[1]: Started Create Static Device Nodes in /dev.
Dec 3 10:23:25 v4 systemd[1]: Mounted RPC Pipe File System.
Dec 3 10:23:25 v4 systemd[1]: Starting pNFS block layout mapping daemon...
Dec 3 10:23:25 v4 systemd[1]: Starting udev Kernel Device Manager...
Dec 3 10:23:25 v4 systemd[1]: Started pNFS block layout mapping daemon.
Dec 3 10:23:25 v4 blkmapd[495]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Dec 3 10:23:25 v4 systemd[1]: Started Flush Journal to Persistent Storage.
Dec 3 10:23:25 v4 systemd-modules-load[461]: Inserted module 'ib_iser'
Dec 3 10:23:25 v4 systemd[1]: Started Set the ии keyboard layout.
Dec 3 10:23:25 v4 kernel: [ 0.000000] Linux version 4.15.18-20-pve (root@nora) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200) ()
Dec 3 10:23:25 v4 systemd[1]: Mounted NFSD configuration filesystem.
[03.12, 23:34] oler222222: Dec 3 10:23:25 v4 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.18-20-pve root=/dev/mapper/pve-root ro quiet
Dec 3 10:23:25 v4 kernel: [ 0.000000] KERNEL supported cpus:
Dec 3 10:23:25 v4 kernel: [ 0.000000] Intel GenuineIntel
Dec 3 10:23:25 v4 kernel: [ 0.000000] AMD AuthenticAMD
Dec 3 10:23:25 v4 kernel: [ 0.000000] Centaur CentaurHauls
Dec 3 10:23:25 v4 kernel: [ 0.000000] x86/fpu: x87 FPU will use FXSAVE
Dec 3 10:23:25 v4 kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
СГ
при этом до перезагруки никаких проявлений нехватки памяти, свободного места - нет?
ОБ
при этом до перезагруки никаких проявлений нехватки памяти, свободного места - нет?
места терабайты. киллмемори точно нет
СГ
тогда всё странно, у вас ядро от августа - тот CVE уже в нём поправлен.