HOSTNAME problems after VZ update

Discussion in 'General Questions' started by HoracioS, Apr 19, 2012.

  1. HoracioS

    HoracioS Kilo Poster

    I´m using Windows 2008 R2 datacenter (6.1.7601 Service Pack 1 Build 7601
    ) with Parallels Virtuozzo Containers 4.6.490.12

    I was updated VZ with the last patch and now, all the containers with Plesk, experiencing the same FTP access problem withe Plesk 10.3.1 and 10.4.4:

    Connected to
    220 Microsoft FTP Service
    331 Password required for XXXXXXXXXX.
    530 User cannot log in, home directory inaccessible.
    ftp: Login failed

    I tried all the solutions in KB and always has the same problem.
    I can see the HOSTNAME is the HARDWARE NODE hostname, not the VPS hostname!!!!!
    When check the IIS FTP binding address, the only option is the HARDWARE NODE IP address, not the VPS address.

    Please help!

    Best regards,
  2. figjam

    figjam New Member

  3. HoracioS

    HoracioS Kilo Poster

    No, it has not fixed the problem.

    Only this article fixed the problem. I cannot believe Parallels not reply this thread before...
    Support people don´t know about it yeat....

    Container hostnames changed after installing hotfix KB2653956 to the Hardware Node
    Article ID: 113779
    Last Review: May, 3 2012
    Parallels Plesk Panel
    Parallels Virtuozzo Containers
    Note: The issue occurs only on Parallels Virtuozzo Containers, not on physical servers.

    After installation of the Microsoft hotfix KB2653956, all containers' hostnames are changed to the hostname of the Hardware Node. As a result, the following issues occur:

    - FTP stops working -- error "530 User cannot log in, home directory inaccessible."

    - RDP stops working
    The issues will be fixed in a future update. You may subscribe to the Parallels Virtuozzo Containers Update mailing list if you wish to receive notifications about the latest product updates, new version announcements, and promotions for Enterprise applications of Parallels Virtuozzo Containers.

    1. Get the containers' original hostnames from configuration files (it is necessary to perform this command on the HW Node):
    vzlist -Hao ctid,hostname > C:\hostnames.txt

    2. Reset all containers' hostnames:
    for /f "tokens=1,2" %i in (C:\hostnames.txt) do vzctl set %i --hostname %j --save

    3. Restart all containers:

    Note: This step will cause service downtime.

    for /f %i in ('vzlist -Ho ctid') do vzctl restart %i

Share This Page