Recent content by tgoetten

Just wanted to let everyone know that i was unable to fix this issue :-(

Hi Ebprz, did you fix your issue? Or is it still open? Thomas

Hi, did you find a solution for your problem? I have a quite similar one, see here : https://forum.proxmox.com/threads/mysql-not-starting-in-lxc-container.27443/ Thomas

Hi, i've set up a LXC container running Debian 8 along with MySQL. Everything was fine until i did a restart. Now mysql is not started automatically during boot. A manual try "service mysql start" has the following result: Job for mysql.service failed. See 'systemctl status mysql.service' and...

no one?

Hi, after i upgraded the host system (proxmox 3 -> 4) i am havin problems with my email archive solution. I already asked for help at the specific forum. It seems like this is an container problem instead of a software problem. I have my groupware, which is Zimbra installed on the same machine...

Hi Dietmar, you are right about the package version ~ # dpkg -l lxc-pve Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name...

Hi Dietmar, here is the output lxcfs.service - FUSE filesystem for LXC Loaded: loaded (/lib/systemd/system/lxcfs.service; enabled) Active: active (running) since Tue 2015-12-08 11:24:23 CET; 2h 0min ago Main PID: 1071 (lxcfs) CGroup: /system.slice/lxcfs.service └─1071...

Hi everyone, i'm facing a problem while trying to start all of my lxc containers. # lxc-start -n lxc-container1 -F lxc-start: conf.c: mount_autodev: 1175 No such file or directory - Failed mounting tmpfs onto /dev lxc-start: conf.c: tmp_proc_mount: 3687 No such file or directory - failed to...

Is it really just an Apparmor issue? I tried the above mentioned solution to add lxc.aa_profile: unconfined. At first the error for postfix went away. But on Ubuntu based machines i get error messages when logging in via ssh as root on my VPS : Server refused to allocate pty stdin: is not a...

Any news on this? I tried to disable Apparmor (service apparmor stop) and restarted the guest - but the permission problems still persist. How do i (temporarily) disable apparmor completly?

I'm facing the same problem. After a successfull upgrade to version 4 i get this error message on all of my guests.So how do i enable "globally" that the guest are able to use postfix?