Search results

  1. E

    volblocksize/recordsize in the create vm/ct wizard

    I agree, yes, it is very necessary!
  2. E

    syslog error's pmxcfs and pveproxy

    Dec 1 13:28:39 debian2 pveproxy[25518]: Can't call method "push_write" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 295.
  3. E

    syslog error's pmxcfs and pveproxy

    Hello dear community. Again I found strange messages entering and segmentation faults. But I do not see the logs of login attempts the more the server is on the internal network and uses fail2ban. Because of what may be these messages tell me please? Nov 22 21:32:11 debian pmxcfs[2590]...
  4. E

    syslog error's pmxcfs and pveproxy

    Hello. I have already talked about the problems in which no worker is a web server. But now, after the creation of the cluster logcheck sent me a new message: Oct 29 02:08:37 debian pmxcfs[2594]: [ipcs] crit: connection from bad user 65534! - rejected Oct 29 02:08:37 debian pmxcfs[2594]...
  5. E

    pveproxy worker segfault

    You mean checked using Memtest86+ ? What can be wrong with the memory in the server fairly new strip of RAM as well as other hardware ? Сервер: DELL POWEREDGE C6100 XS23-TY3 4 x NODES 8 x 2.8GHz X5560 96GB
  6. E

    pveproxy worker segfault

    Today I saw this picture again with errors pveproxy, Does anyone have any information on what is this? [1010528.295968] pveproxy worker[20923]: segfault at 4 ip 00007f0d3e465493 sp 00007ffff7885378 error 4 in libqb.so.0.11.1[7f0d3e44e000+1f000] [1027113.910667] pveproxy worker[26488]: segfault...
  7. E

    pveproxy worker segfault

    Hello, everybody! I'm using kernel 3.10.0-2-pve and saw logs segmentation today one of the workers pveproxy. [534952.224767] pveproxy worker[18844]: segfault at 4 ip 00007f0d3e465493 sp 00007ffff7885378 error 4 in libqb.so.0.11.1[7f0d3e44e000+1f000] I also meet periodically such records...
  8. E

    pveproxy worker segfault

    Moved to another forum.
Top Bottom
Back