Manually restarting Active Directory related services on ESXi 5.5 displays the message: /var/lock/subsys: No such file or directory
search cancel

Manually restarting Active Directory related services on ESXi 5.5 displays the message: /var/lock/subsys: No such file or directory

book

Article ID: 305202

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • When you manually run the commands to restart the Active Directory related services (I/O Redirector, Network Login Server, and Local Security Authentication Server), you see output similar to:

    /var/lock # /etc/init.d/lwiod restart
    Stopping Likewise IO Manager Service...ok
    Starting Likewise IO Manager Servicetouch: /var/lock/subsys/lwiod: No such file or directory
    ...ok
    /var/lock # /etc/init.d/lsassd restart
    Stopping Likewise Identity and Authentication Service...ok
    Starting Likewise Identity and Authentication Servicetouch: /var/lock/subsys/lsassd: No such file or directory
    ...ok
    /var/lock # /etc/init.d/netlogond restart
    Stopping Likewise Site Affinity Service...ok
    Starting Likewise Site Affinity Authentication Servicetouch: /var/lock/subsys/netlogond: No such file or directory
    ...ok


  • Listing the directories located in /var/lock does not list the /subsys directory.
  • The services do restart after the commands are run.
  • If you manually create the /var/lock/subsys directory, you no longer see the error messages when restarting services on the command line.


Environment

VMware vSphere ESXi 5.5

Resolution

This is a known issue affecting ESXi 5.5.

These are residual messages from previous versions of ESXi and can be safely ignored.

To work around this issue, manually create the /var/lock/subsys directory to prevent the messages from appearing when restarting these Active Directory related services: I/O Redirector (lwiod), Network Login Server (netlogond), and Local Security Authentication Server (lsassd).

To manually create the /var/lock/subsys directory:

  1. Open an SSH session to the affected ESXi host and log in as root.

  2. Change directory to /var/lock by running the command:

    cd /var/lock

  3. Create the subsys directory by running the command:

    mkdir subsys

  4. Restart the Active Directory related services and verify the messages no longer appear.


Additional Information



ESXi 5.5 で Active Directory の関連サービスを手動で再起動すると、次のメッセージが表示される:/var/lock/subsys: No such file or directory