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

10.4.4 Update #13 - issue

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by Jayson, Jan 23, 2012.

  1. Jayson

    Jayson Basic Pleskian

    26
    23%
    Joined:
    May 10, 2005
    Messages:
    95
    Likes Received:
    0
    Hi everyone,

    This is just a fyi on the auto update that ran for me on Jan 20th.
    Centos 5.7 64bit
    php 5.2.x
    mysql 5.x

    Checking up on customer complaints I found many domains loading default plesk pages. After generating a support ticket I tried various options including what was recommended by support, where I was told I had modified some DNS records that did not update and I should run.

    /usr/local/psa/admin/bin/dnsmng --update <domain>
    usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain>

    Unfortunately it did not correct the problem. What I found was the default hosting ip address for a domain had changed and its dns was updated by adding new records. However, I made no changes to any dns records prior to the failure. In the end, since I have less than 120 domains on the server, I just went through each one individually with my browser testing who fails. Looking at the DNS on failed I see original zone records and new ones. I changed the hosting ip back to what it was and removed the new zone records and the domain instantly resolved.

    I probably could have just removed a set of zone records and dnsmng and httpdmng the domain, but this worked.

    Also, I started to get quota rejections on email as new limits of 500mb were suddenly enforced on some domains with mailboxes larger than 1GB. It would appear the hosting service changed?

    My worry now is with the minor updates. I requested clarification on how this could happen and I was told minor updates would not cause this problem. Do most people have this option enabled, or disabled?

    Regards,
     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,242
    Location:
    Novosibirsk, Russia
    Could you please provide me support ticket ID? I will check it.
     
  3. Jayson

    Jayson Basic Pleskian

    26
    23%
    Joined:
    May 10, 2005
    Messages:
    95
    Likes Received:
    0
    Sure, #1307088 Everything is working fine although I must admit some apprehension in regards to the next MU.
     
  4. Frater

    Frater Regular Pleskian

    18
     
    Joined:
    Oct 17, 2011
    Messages:
    173
    Likes Received:
    3
    I have minor updates enabled, because we got a pre-installed VM with Plesk...
    Another VM is still on 10.2 and that one seems to be running much better.

    This same micro-update (#13) wrote a new /etc/postfix/master.cf and, because it had port 587 enabled, created a conflict with another daemon using that port.

    Someone drank too much wodka?
     
Loading...