Search results

As I can only get into mel-pm2 via screen + keyboard at the moment, this is some of the fun in journalctl on that node:

More fun and broken things - when trying to view the Cluster information on the Web UI of mel-pm (aka node 1): Also, when looking at /etc/pve/nodes/mel-pm2/ on mel-pm, there's zero content:

Trying again to join the cluster together - after adding the Join information to the second node, the output I get is: Establishing API connection with host '172.31.1.1' Login succeeded. check cluster join API version Request addition of this node Join request OK, finishing setup locally...

Hi all, I have a two node cluster that started misbehaving a couple of days ago.... No matter what I did, I couldn't get things back up and happy again. The second node always hung on starting pveproxy in the `pvecm updatecerts` command. Once that hung, I wasn't able to recover. As the second...

That saved me a bit of time - thanks... I was just looking at the example figuring out what is what. It does work, but you still need to set the Shutdown timeout to 1 - otherwise the two tasks will block each other. Keeping the shutdown timeout to 1, and that script as a hookscript does seem...

I did not - just testing again now.... Doesn't seem to make a difference... 1 or 3 doesn't seem to make a difference - I set it to 3 to give me chance to bring up the logs.... It still just fails though.... Hitting STOP has always worked, but I always hit Shutdown out of habit.... So I...

Yeah, I guess that the key is that I want it to work the same way no matter which way it's called..... so it looks like the hook might be an idea...

Oh, if I changed the shutdown timeout to 3, I get the following error when sending a shutdown: Looks like the hookscript might be the way to go.

Ahhhh h- I've seen that a million times and it never occurred to me :) For the sake of the Google results: That in theory should be fine if I set it to like 3 seconds. I'll have a play with it, and if that doesn't fit, I'll go with the hookscript route....

Is there one per VM though? I thought there was only a global one? I'll take a look at the hooks though - that might work as a workaround...... even though its ugly ;)

Hi all, So I'm running a Cisco virtual appliance in a proxmox VM - and these things are not designed to shut down at all. There's no command to tell it to shutdown, nor is there any way to install an agent or have it use acpi etc. As such, telling a node to reboot will always hang on this VM...

What's the new 'localnetwork' thing with ACLs etc?

How do you do this if you have two nodes in a cluster?

Yep - I've been waiting patiently and staying subscribed to this thread in the hope of getting that notification one day soon ;)

I just want to add to this - you don't need to add the EFI Disk if you don't want to use secure boot and your VMs disk has an 'EFI System Partition'. It'll complain, but still boot properly.

I edited `/etc/mail/spamassassin/init.pre` and commented out the Hashcash line. It allows things to work, but probably needs an update that resolves this properly.

hahaha yeah - I do that too - but I use node_exporter on the proxmox setup and prometheus / grafana as well. It's the workaround I've come to use :)

That's great news all round. Myself, I have very little interest in migration between 'datacenters' - but even just being able to view the stats between different clusters (or single node clusters too) in different locations. My hobby stuff has had machines donated in two different datacentres...

@fabian I wonder if we're any closer to this in the 2+ years of this thread?

Just to follow up on this - I haven't had a network failure at all since blacklisting those modules. The onboard NIC is now functioning as I'd expect. The Intel team seems to indicate a BIOS problem - but I'm not sure who to relay this to at Intel who would be in that area...