Search results

  1. M

    ksm-control-daemon is being helt back

    jessie (currently) defaults to the (optional) systemd. Much like SLES12 defaults to btrfs but also supports stable filesystems Does that mean that proxmox has dropped support for sysvinit entirely? That doesn't seem right. Even so, seems like a tiny change to the Services.pm could easily...
  2. M

    ksm-control-daemon is being helt back

    Thanks. I tried that but it did only tell me the same thing. However I have since figured out theres a weird systemd dependency lingering now (WHY?), which I managed to resolve. Am now digging into PVE/Services.pm and Tools.pm to replace calls to the nonexistant "systemctl" binary Status: was...
  3. M

    ksm-control-daemon is being helt back

    I'm looking at this The following packages have been kept back: ksm-control-daemon after the upgrade to debian8 and dpkg reports as ii ksm-control-daemon 1.1-1 all The KSM tuning daemon Question is, is there a poettering-free version...
  4. M

    Jessie and 3.10.0 OpenVZ kernel and the future

    amongst others, this one: http://andrea.corbellini.name/2015/02/20/are-lxc-and-docker-secure/ relevant bit: this is because if you are uid 0 (root) inside the container (meaning that you are also root on the host!) you have access to /proc (which is not emulated). So you either need...
  5. M

    Jessie and 3.10.0 OpenVZ kernel and the future

    Are lxc containers going to be enforced to be unprivileged? Because as far as I know thats the only way to make lxc even somewhat acceptable security wise? Without it any attacker managing to start a shell in a container via remote code execution in $insert_php_application_here basically has...
  6. M

    networking painfully slow after upgrade to 3.4

    aight compiled the drivers. attempted the no-reboot approach (where you run the autorun.sh the driver comes with in a screen session) but the server did not come back. I had to soft-reboot it, but it started up just fine and I am now seing the transfer rates I was expecting. I had started to...
  7. M

    networking painfully slow after upgrade to 3.4

    thanks for the offer but since I have never used dkms, I guess I'll stick to known methods (compile, blacklist old one, mkinitrd, reboot). I read somebody else recommending doing rmmod [old] + modprobe [new] in a screen session (since the ssh session will be terminated) but I have my doubts...
  8. M

    networking painfully slow after upgrade to 3.4

    just an FYI, the weird situation continues. I suppose it actually is a firmware/driver issue and will now try to compile drivers. another short night for me...
  9. M

    networking painfully slow after upgrade to 3.4

    sortof... dmesg|grep rtl r8169 0000:04:00.0: firmware: requesting rtl_nic/rtl8168e-2.fw
  10. M

    networking painfully slow after upgrade to 3.4

    the command you gave doesnt work like that ;) however: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards Control: I/O+ Mem+ BusMaster+...
  11. M

    networking painfully slow after upgrade to 3.4

    hm.. this is very weird. I get like 2mb/s if I download something from a Hetzner-internal server to mine. I can download files from my server just fine with like 10mb/s but file transfers TO my server from outside hetzners network are very slow. This leads me to conclude that its not...
  12. M

    networking painfully slow after upgrade to 3.4

    Hi, recently upgraded my old 2.3 server to 3.4 and am now finding that the networking is just painfully slow (Im talking 200kb/s here!). First things first: lspci| grep -i real 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet...
  13. M

    Backup in Large VM Environment

    I would also recommend sticking to in-VM targeted backups of required data only. This has the advantage that you can schedule scripts like "stop psql, rsync backup, start psql" (unless you have a proper transaction log setup that is...) which isn't as easy from the outside. As for backups...
  14. M

    Debian 8 openvz template

    be very careful when you upgrade debian 7 to 8. The upgrade may or may not switch to systemd. You can always remove the Poettering-crap later on, but you might get it on your system and weird init systems tend to cause problems with openvz (Upstart didnt work at all when it was new).
  15. M

    Yubikey Configuration with PVE

    Just a general thought: you might wish to consider twice, whether you want your ability to log into PVE to be dependant on the availability of the yubico service! Imo it is a MUCH better idea to use the static password mode and have a short password (like 4-8chars) that you memorize yourself...
  16. M

    ceph sata disks recommendations

    You can just use whichever you want, however there are some things you might consider: - don't go for 5400rpm drives. These shouldnt even be sold anymore but for some reason still are... avoid those, they are awfully slow. Go for 7200rpm - avoid WD green series drives and similar. Whenever a...
  17. M

    Proxmox 3.4 Install on HP Microserver Error

    Im not sure about the proxmox installer, but I know that the debian installer currently has NO support for EFI. For debian there's custom/fixed beta netinst CD images with EFI support added, but that wont help you here. I suppose turning on BIOS-emulation would be your easiest workaround...
  18. M

    best monitoring solution for proxmox? Zabbix vs Nagios

    If you want (GUI-)autodiscovery I would strongly suggest you take a look at check_mk because it just might be exactly what youre looking for. Technically its a nagios plugin, but its really its entirely own monitoring solution, that just happens to run on top of the nagios core (possibly the...
  19. M

    Is running proxmox from a usb drive possible?

    You can do that, no problem. Be wary of those things though, usb flash drives (and CF cards for that matter) tend to have abysmal lifespans (1 day to 1 year, depending on your luck)
  20. M

    best monitoring solution for proxmox? Zabbix vs Nagios

    just use whichever you prefer or the one that integrates better into your IT environment (Youd want to be monitoring everything.). Also a general reminder that nagios is quasi-dead. You want icinga(2) instead, which is a fork / vast improvement over the 1-man project nagios.