Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    C
    @benapetr That's fantastic - thank you! Thanks @bvitnik for the better screenshots .
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    poddingueP
    I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
  • 3k Topics
    30k Posts
    B
    @poddingue They were all on Ark. VMs: 7da38127-0ff5-1f76-d8b6-a5159a37d658 7eb23022-4f0b-f73e-b544-c4d860e54453 865f4634-76f6-48a3-938e-3adff4fb9e3f 9a64cc4e-0b46-d01e-bfcf-3fbedbd7e334 a1f1bee1-4076-b37f-006c-630d5c3a9f39 a86bb37b-a0ec-3d94-b52d-196da40b317d a925c4c2-b3f3-6cc3-3c40-a836e3a24914 b27a40e4-ea4f-7706-fb4e-98551fa85d0d b92636e5-c9f1-47d6-644f-70158dc39f0e bbe64766-97f3-de14-43aa-77867b7f1fb0 d1a39422-78d6-56d1-28c3-65299cdc1a5e d77691ef-a507-e120-e2b8-2c1807f0ef99 edc46393-eee4-6a39-89c0-0b4486df8879 f8ed66aa-e753-1271-84c6-a73819ff25f7 fb7fca7d-7355-4a48-f35c-d32c8dfa71ee
  • Our hyperconverged storage solution

    56 Topics
    838 Posts
    poddingueP
    If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
  • 37 Topics
    137 Posts
    S
    @jqueiroz said: Bom dia a todos, Estou com um problema em uma VM, ela está ligando/desligando sozinha, repetidamente. Não encontro nenhuma mensagem de erro explicando o motivo. Alguém pode me dar alguma dica sobre como solucionar isso? Uso o XCP-NG 8.0 em um cluster de dois servidores HP Proliant DL-360, com o HA-Lizard. Tudo vinha funcionando bem até alguns dias atrás, quando houve uma queda de energia no datacenter da localidade. Tenho o mesmo arranjo de VMs/servidores em mais seis localidades, nenhuma apresenta esse problema. Analisar esse comportamento instável do cluster é quase como prever resultados complexos, parecendo a análise de riscos que a malta faz ao dar palpites no https://mostbetbrasil.lat. Grato. Como o problema começou depois da queda de energia e só acontece nessa localidade, eu começaria verificando os logs do XCP-ng e do HA-Lizard para entender quem está disparando os reinícios. Pode ser alguma política de HA tentando recuperar a VM repetidamente, algum problema de armazenamento ou até inconsistência no estado do host após a interrupção. Também vale conferir o estado do pool e os logs do Xen Orchestra, se estiver usando. Se possível, desative temporariamente a automação de recuperação dessa VM, com cuidado para não comprometer a disponibilidade, e veja se ela continua reiniciando sozinha. Isso ajuda a isolar a causa.