Search results

It is very strange, because I didn't log on to the forum neither that day nor several days before. Probably I logged on before from insecure computer that is located within the network I currently connected, that's why I see my IP address. I'm asking for the server logs info to be sure. Thanks...

Hello, I received a message of 2nd authentication step to this forum. But I didn't logged in to this forum. The forum hasn't even been opened in the browser. It's strange that the IP address shown in the message is mine... The message was created at: Fri, 27 Mar 2020 12:52:09 +0000 The...

There's nothing special in /etc/hosts, there were fresh systems on the nodes. I saw the article, nothing related to the problem there. As everybody mention: `pveceph purge` and subsequent `pveceph init` - makes ceph unusable. I just reinstalled again and did the setup from the first time.

Did someone managed to fix it? I have the same issue: # pveceph init --disable_cephx 1 --network 172.22.255.0/24 # pveceph mon create unable to get monitor info from DNS SRV with service name: ceph-mon Could not connect to ceph cluster despite configured monitors # ceph -s unable to get monitor...

@Alwin Yes, it works now, thanks! But I'm afraid some inconsistencies might remain... So just to be sure, I will recreate cluster node by node, while simultaneously copying data from the shrinking old ceph cluster to a growing new one. By the way, is there any way to do it as I wanted...

I played around with the following commands: # modified monmap ceph-mon -i <NODE> --extract-monmap /tmp/monmap monmaptool --print /tmp/monmap monmaptool --rm mon.<NODE> /tmp/monmap monmaptool --add mon.<NODE> <NODE_IP>:6789 /tmp/monmap monmaptool --print /tmp/monmap ceph-mon -i <NODE>...

Hello, everybody! Serious trouble. `ceph status` hangs, every ceph command hangs! PVE shows "got timeout" reinstalled the node, tried to join the node just by copying keys, but could not create monitor (error: monitor existed), then I removed the monitor from monmap, and that's it all...

Great, thanks for the info! Sure, I've sent /etc/network/interfaces of all the nodes of that cluster in PM.

@spirit Thanks for the suggestion! But as I said, first problem is that it happens occasionally, so I may think everything is ok, but one fine day cluster would not start up. The second thing that I mentioned, is that ifupdown2 ignores 'post-up' statements on no-subscription cluster. So.. no...

@fabian Thanks for the info! Adding '--target' parameter to our creation script fixed it. In case somebody need to fix it quickly, this command works: # qm clone 105 135 --target $HOSTNAME

I actually never tried to run different versions, I usually upgrade all the nodes and reboot them. But I guess it is required, or at list desired since it is stated in the docs. It is recommended to use paid version of Proxmox for critical services. 'Paid' exactly means, that can upgrade from...

@rnmkr I think it has nothing to do with the hostname. It might be a bug, because it was working for sure (100%) under Proxmox 6.0 and it stopped working right after the upgrade to Proxmox 6.1. Sadly, I have upgraded all my clusters, without checking VM creation after the first upgrade. I can...

Hello, I can't create VM from a template neither in the cluster with subscription, nor in cluster without it... I get the same error: # qm clone 105 135 Use of uninitialized value $nodename in hash element at /usr/share/perl5/PVE/Cluster.pm line 724. Use of uninitialized value $nodename in...

I see... Thanks for the info! Ok, moving to systemd rename. I'm sorry for the late answer, but in case you still need it, I've had a chance to check `ifupdown2` again on those servers after they've been upgraded, and yes all the names were correct, no 'rename11' or other inconsistent names...

I have the same issue: seabios repots: boot failed: not a bootable disk Unfortunately it didn't work for me, adding disk via command line gives error: copy failed: command '/usr/bin/qemu-img convert -p -n -f qcow2 -O raw bionic-server-cloudimg-amd64.qcow2...

You're welcome. Can you please explain why udev rules shouldn't be used anymore for renaming? I much more prefer laconic udev one-liners, that are kept in only one file for the whole cluster (this file is distributed between nodes), rather than having to deal with a heap of *.link files...

I don't. I just define them in /etc/network/interfaces. However I do rename physical interfaces r0p1, r0p2, aux0p1, ... using udev rules from their weird default names by their MACs.

Sure: auto lo iface lo inet loopback iface r0p1 inet manual iface r0p2 inet manual iface aux0p1 inet manual iface aux0p2 inet manual iface lan0p1 inet manual iface lan0p2 inet manual auto r0 iface r0 inet static bond-slaves r0p1 r0p2 bond-mode balance-rr bond-miimon 100...

I've had the same issue. In my setup LAN bond is added to the bridge 'vmbr0'. PVE5. I added the line: pre-up sleep 2 to bridge configuration. It's working so far. Didn't need to patch anything.

After installing ifupdown2, I observed odd behavior: my bond 'lan0' was renamed to rename11, and was not configured because of that... Rolled back to ifupdown