1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Cannot allocate memory (errno = 12)

Discussion in 'Plesk for Linux - 8.x and Older' started by net64, Apr 10, 2006.

  1. net64

    net64 Guest

    my server went down this morning and my message logs were filled with messasges like theese:

    relaylock: /var/qmail/bin/relaylock: Unable to connect to the mysql database, relay will work in closed
    mode & white list will not work

    smtp: fork failed: Cannot allocate memory (errno = 12)

    service smtp: too many consecutive fork failures

    pop3: fork failed: Cannot allocate memory (errno = 12)

    Can anyone tell me what they think is going on and how to fix this?

  2. net64

    net64 Guest

    more info

    What I am trying to figure out is was this an internal thing gone awry or was it some kind of outside attack?

    When I looked at my messages.1 log for
    the previous day there are a ton of these messages...

    warning: can't get client address: Connection reset by peer

    My memory allocation seems fine now after restart, so I don't think that is the issue....

    Also when looking in /var/log/secure I am seeing this message over and over with various addresses:

    START: smtp pid=29824 from=

    Ever seen this problem before and how do I fix it?

    Any Help is appreciated!!
    My apologies for being new at this...