Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    B
    @bvitnik ok that's cool, didn't know it could do that
  • 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
    P
    @florent { "data": { "mode": "full", "reportWhen": "failure" }, "id": "1794881400002", "jobId": "0ffa03e5-e750-43ad-b66c-0495405fe068", "jobName": "BCK_Running", "message": "backup", "scheduleId": "0c8bba34-e5f1-4f58-9c38-11b514358383", "start": 1794881400002, "status": "interrupted", "tasks": [ { "id": "0mwk21luf-5zyntw173ie", "start": 1794881402583, "status": "success", "tasks": [ { "id": "0mwk21mr0-y3gazw087kf", "start": 1794881403757, "status": "success", "end": 1794881405281, "result": "459e3a05-f508-e85d-5cc4-387155dc304b", "message": "snapshot" }, { "id": "0mwk21nyt-imr121bpgle", "start": 1794881405333, "status": "success", "tasks": [ { "id": "0mwk21nzt-bqf4lzdvlkt", "start": 1794881405369, "status": "success", "end": 1794881441678, "result": { "size": 3268086272 }, "message": "transfer", "data": { "progress": 0 } } ], "end": 1794881441822, "message": "export", "data": { "id": "0927f4dc-4476-4ac3-959a-bc37e85956df", "type": "remote", "isFull": true } }, { "id": "0mwk22gs1-zazmiofst3r", "start": 1794881442673, "status": "success", "tasks": [ { "id": "0mwk22h6r-uo87g3emm6", "start": 1794881443203, "status": "success", "end": 1794881499852, "result": { "size": 3268086272, "id": "8d6704b6-e005-f300-47e7-be2e9ea21a5c", "liveMounts": [] }, "message": "transfer", "data": { "progress": 100 } }, { "id": "0mwk23owd-9ik1ccu4ln", "start": 1794881499853, "status": "success", "end": 1794881504936, "message": "vmstart" } ], "end": 1794881507491, "message": "health check", "data": { "progress": 0 } }, { "id": "0mwk23ut6-ah9rc68q15o", "start": 1794881507514, "status": "success", "end": 1794881507850, "result": { "removedFiles": [], "changedFiles": [], "merge": false, "size": 0 }, "message": "clean-vm" } ], "end": 1794881507852, "message": "backup VM", "data": { "id": "a6cc5035-c18c-8f35-e197-b7e55c9cab8a", "type": "VM", "name_label": "1-pihole", "progress": 0 } }, { "id": "0mwk23v2t-gatlyfjkc7l", "start": 1794881507861, "status": "pending", "tasks": [ { "id": "0mwk23v9q-d160t2rhy9k", "start": 1794881508110, "status": "success", "end": 1794881510136, "result": "e3625624-81ba-5913-4e69-cca7f5bb5016", "message": "snapshot" }, { "id": "0mwk23wx8-x8bm3je4ztt", "start": 1794881510252, "status": "success", "tasks": [ { "id": "0mwk23wyy-cfs4vlwf58q", "start": 1794881510315, "status": "success", "end": 1794881836648, "result": { "size": 31518195712 }, "message": "transfer", "data": { "progress": 0 } } ], "end": 1794881836755, "message": "export", "data": { "id": "0927f4dc-4476-4ac3-959a-bc37e85956df", "type": "remote", "isFull": true } }, { "id": "0mwk2axif-lzd7nijq25i", "start": 1794881837607, "status": "pending", "tasks": [ { "id": "0mwk2ayix-bhm2oqxo1zc", "start": 1794881838922, "status": "pending", "message": "transfer", "data": { "progress": 62 } } ], "message": "health check", "data": { "progress": 0 } } ], "message": "backup VM", "data": { "id": "8b921e1c-5cb2-a3d8-6c13-eb9dcf73f993", "type": "VM", "name_label": "1-Romy", "progress": 0 } } ], "infos": [ { "data": { "vms": [ "a6cc5035-c18c-8f35-e197-b7e55c9cab8a", "8b921e1c-5cb2-a3d8-6c13-eb9dcf73f993", "235d2a6a-89a5-845d-9310-11938e65a95e", "6f5c2553-2150-bd34-db9e-2830820247f1" ] }, "message": "vms" } ] } Here are the 3 VMs that ran, the fourth one is XOce that did not run. [image: image.jpeg] I'l test the backups to see if they are OK, then I'l try with node 24.
  • 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.