Search results

No, it was the UWSGI app that wasn't responding. Apache was working fine. But there's no inherent limitation that makes it a bad idea for us to deploy our new webservers as containers rather than VMs?

Output of pct config: arch: amd64 cores: 4 hostname: fof1 memory: 1024 mp0: local-lvm:vm-114-disk-2,mp=/home,backup=1,size=1T net0: name=eth0,bridge=vmbr0,gw=192.168.100.1,hwaddr=42:6A:E2:C1:3C:FE,ip=192.168.100.231/24,type=veth onboot: 1 ostype: ubuntu protection: 1 rootfs...

I'm concerned about the limitations of LXC containers for production servers. Currently we run our main production servers (web, database, etc) as KVM virtual machines but were considering deploying them in containers in future. We have quite a few small applications running in containers and...

Thanks. That tells me all I need to know. I'm using Proxmox as my workstation OS, so udisks2 was installed by the act of adding XFCE to the install. Will disable the udisks2 service as I almost never use USB disks and have no plans to add storage to my desktop machine.

I'm having a problem that has been reported by other Debian and Ubuntu users that udisksd is using lots of CPU. Right now I'm investigating workarounds rather than solutions so my question is: Is this service essential to Proxmox? What happens if I stop and disable it?

Hi, What's the best way to upgrade from Proxmox 4.4 to something more current, probably 6.0? Our servers are basically default installs and are patched up-to-date. All of our VMs and containers are stored in LVM. We don't use ZFS. Our servers aren't clustered in any way. Thanks, Colin

Was this default already changed in 5.3? It seems to be at least, unless it's just my browser or session remembering some previously used options.

I debugged this by looking in /var/log/auth.log. The unsuccessful logins under Proxmox 4.4 looked like Feb 28 10:19:56 host1 login[19577]: pam_securetty(login:auth): access denied: tty '/dev/pts/0' is not secure ! Feb 28 10:19:59 host1 login[19577]: FAILED LOGIN (1) on '/dev/pts/0' FOR 'root'...

I had this also in Proxmox 4.4 with Ubuntu 18.04 containers, but no longer had the problem under Proxmox 5.3 -- there /dev/tty1 is used instead.

Hi, I created an Ubuntu 18.04 container under Proxmox 4.4 from the supplied template. Didn't supply an SSH key, just a password. But when I try to login on the console I type: root <enter> and then shortly after it says Incorrect login There's never a prompt for the password. How do I...

Reading https://pve.proxmox.com/wiki/Linux_Container#_privileged_containers both Proxmox and the LXC team are recommending that we use unprivileged containers, and stop using privileged containers. So why is not the default?

Thanks. You've confirmed my understanding that the user accounts don't "own" any objects that would be removed by deleting an account.

This is a "Proxmox VE authentication server" realm account, not a Linux user, so the above doesn't apply.

Hi, Our former system adminsitrator left our company; is it safe to delete his Proxmox accounts? These are in the PVE Authentication realm. Don't all the permissions go via roles? And I understand it's not possible for such a user to "own" anything, correct? Thanks, Colin

Hi, Do you plan to make Proxmox Storage Replication work on LVM at some point in the future? Or will it forever be ZFS only? Thanks, Colin

You could just install the unattended-upgrades package and configure it to install security and bug fix updates automatically in /etc/apt/apt.conf.d/50unattended-upgrades