Recent content by WebCode

  1. W

    PVE is not working correctly

    Hello. There is a server: CPU: 2x Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz RAM: 32Gb (DDR3 1066 MHz) HDD: 2x500 Gb SATA (LSI RAID) Install it PVE 2.3. # pveversion -v pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1) running kernel: 2.6.32-19-pve proxmox-ve-2.6.32: 2.3-96...
  2. W

    Hangs update of pve-manager

    I'm sorry. It's my fault. The server was mounted NFS partition with shutting down the server.
  3. W

    Hangs update of pve-manager

    Hello. There was a problem updating the system: # aptitude upgradeThe following packages will be upgraded: base-files bind9-host corosync-pve dbus dnsutils fail2ban gnupg gpgv gzip libapache2-mod-perl2 libbind9-60 libcups2 libcurl3 libcurl3-gnutls libdbus-1-3 libdns69 libgssapi-krb5-2...
  4. W

    kernel:Kernel panic - not syncing: Fatal exception

    Oh no! Error manifests itself through time. Migrate one VPS - okay, other - kernel panic :(, reboot... Migrate next VPS - okay, other - kernel panic :(. I'm going to reinstall 10 servers to Proxmox. Migrating to me is very important :(
  5. W

    kernel:Kernel panic - not syncing: Fatal exception

    Hello, I installed the test kernel 2.6.32-13-pve, and it works! Thanks! Thanks! Thanks!
  6. W

    kernel:Kernel panic - not syncing: Fatal exception

    We have 2 servers in the above configurations (dell R210-II - master, R510 - slave). We are migrating container (VPS) from 1 server to another. At the time of starting VPS on the slave server fails with kernel panic. When we downgrade to kernel: 2.6.32-11-pve problem fixed but we want work...
  7. W

    kernel:Kernel panic - not syncing: Fatal exception

    I rolled back my kernel to version "pve-kernel-2.6.32-11-pve_2.6.32-66", migration working and server doesn't go to the state "Kernel Panic". But I don't think that this could be a "solution" to resolve my problem. :(
  8. W

    kernel:Kernel panic - not syncing: Fatal exception

    I have a server that does not fall to panic: Dell R210II. It differs from only R210 CPU: Xeon E31220.
  9. W

    kernel:Kernel panic - not syncing: Fatal exception

    Today, a new server connected to it and got the same problem :( # pveversion -v pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) running kernel: 2.6.32-12-pve proxmox-ve-2.6.32: 2.1-68 pve-kernel-2.6.32-12-pve: 2.6.32-68 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve...
  10. W

    kernel:Kernel panic - not syncing: Fatal exception

    Please: # pveversion -v pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) running kernel: 2.6.32-12-pve proxmox-ve-2.6.32: 2.1-68 pve-kernel-2.6.32-12-pve: 2.6.32-68 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.8-3...
  11. W

    kernel:Kernel panic - not syncing: Fatal exception

    Hello. Sorry for my English :). There was a problem with one server. When the migration on a OpenVZ VPS kernel panic: Message from syslogd@node108 at Jun 11 15:09:01 ... kernel:Oops: 0000 [#1] SMP Message from syslogd@node108 at Jun 11 15:09:01 ... kernel:last sysfs file...