Search results

Last time I did that it disabled the user and I was locked out!

Do you have to create a user with that email in order to do that?

How to I change the notification email for proxmox VE? I don't want or need to change the users email address or the FROM address, I am referring to the recipient or send to address? Thanks, Allen

Yes, we did, and that is what saved from data loss. I am more concerned about prevention in the first place as we are at about 140 tech hours right now into recovery.

NFS share for backups.

I see that, in this case, it wasn't PBS, it was Proxmox that backs up directly to a NAS. But I understand some concepts could carry over.

Well we *THINK* it was because their password for their Windows server and the password for the Proxmox server were the same. (Different usernames, but same actual password. We didn't have it stored anywhere locally.

Recently we had a client that had a machine on their network get ransomware. The virus encrypted every computer on the network, including the Proxmox server. They are in a Windows environment so I am not 100% sure how it spread to Proxmox, but it did. Including to the backups stored on a...

Thanks!

Did you get this setup on your BOSS-S2? Any insights?

Yes, I finished the upgrade, just asking if there is anything to prevent it.

Maybe I will run a reboot command with a 30 minute timer on the ones w/o OOB. Then if it doesn't stay online during the upgrade at least I will have a way to get back in assuming the reboot works fine! :)

I was able to get in and finish the upgrade. My main reason for posting is to see if there is anything I can do to prevent lockups on future upgrades where OOB isn't an option.

root@tch-phy:/etc/network# dmesg | grep eth [ 1.279165] tg3 0000:13:00.0 eth0: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 94:40:c9:13:aa:1c [ 1.279169] tg3 0000:13:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 1.279171] tg3...

root@tch-phy:/etc/network# cat interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory'...

root@tch-phy:~# ifreload -a -d debug: args = Namespace(all=True, currentlyup=False, CLASS=None, iflist=[], noact=False, verbose=False, debug=True, withdepends=False, perfmode=False, nocache=False, excludepats=None, usecurrentconfig=False, syslog=False, systemd=False, force=False...

Just did another one that got stuck here: Warning communications lost with UPS 98% Progress. This one I can still SSH into so not a huge deal (and I do have OOB on this server as well), but not sure why I am running into stuck updates...

I have been doing a number of 6 to 7, and 7 to 8 upgrades without many problems. However today, I encountered an upgrade that got stuck on "Reloading network config on first install" Progress 96%. Luckily, this server (which is remote to me) has out of band (OOB / HPE ILO) and I am not stuck...

Still crashes with 6.5 Kernel. Any other ideas?

Still having instability. Trying 6.5 Kernel.