Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    C
    @benapetr That's great - thank you for clarifying - really looking forward to the next release!
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    okynnorO
    I have a nasty problem of my own creation. I hope the community can help me as I have a lot of data stored in this iscsi repository. It all started because my hardware RAID had failed on my Dell PowerEdge R630. I decided to restart the server. It didn't fix the problem, of course. But the server did work with just one 1 remaining drive. Thinking that I need to rebuilt the RAID array, I put two new SSDs in and proceeded to format them to use Software RAID (after setting HBA & ACHI on then PowerEdge). No problem...the reinstall went well. Now, when I tried to reattach the iScsi repository, it showed me that there was "No Storage Repository Detected". I then went to the Terminal in XCP-NG to run the following command to see if the iscsi repository was still available (I didn't reformat the repository) [17:31 xenserver-tiger ~]# iscsiadm -m discovery -t sendtargets -p 192.168.1.5 192.168.1.5:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2 172.16.0.1:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2 [17:31 xenserver-tiger ~]# That would tell me that the repository still exists (I think) I've tried every thing that I can think of to reconnect them. I do not want to lose all my VMs that are inside that iScsi repository. Is there a way to reattach them from the Terminal? Other things d
  • 3k Topics
    30k Posts
    T
    @Pilow, I saw your update that the affected backups show SUCCESS in XOA, are present on the remote, and have been restored successfully. Given that, your suggestion about the report being generated before the final status is available seems reasonable. Bastien’s delay test looks like a useful way to check that. You mentioned the first day after applying it was clear, although with the issue appearing intermittently, it would probably take several days of reports to know whether it helped. I also saw your later test: one- and two-second delays still produced interrupted reports, while three seconds appeared to work over two days. The team has since merged a five-second delay. If you’re still seeing the original mismatch, can you confirm whether your current XO build includes that change? That would help establish whether there’s another timing issue, or whether the fix simply hasn’t reached the installation yet. For the next occurrence, it may help to keep the email timestamp and the run log for that same job, particularly if only one VM in a larger job is marked interrupted in the report. Posting those alongside the XO version would give the team something specific to compare. On a related note, Mail Backup X could be useful as a separate routine if you also want backups of your email accounts. It’s a convenient tool that works across the spectrum and is compatible with IMAP-based email accounts, offers incremental backups and encryption support.
  • Our hyperconverged storage solution

    57 Topics
    843 Posts
    C
    @ronan-a said: @ccooke As said by @poddingue , your network is not isolated. You must change that to protect your pool. We are aware of this issue and we will change this behavior in a future release to block LINSTOR controller and satellite access from the outside (probably in December). Also we will use TLS to add another security layer. Right. I missed that warning - I was going from https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview which doesn't look to link to the XOSTOR documentation with the warning. Does this need a full reinstall effectively, or can I recover it? I see the warning is you can't have hypervisors with any public IPs - that will need a little re-engineering for my small test cluster. I know you can change the IP addresses for linstor after installing xostor - does that resolve the issue, or is there no way to secure it when the hypervisor is on a public IP? Could I not just add some firewall rules for now? Thanks for the reply.
  • 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.