Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Enabling logging for Likewise agents on ESXi/ESX (1026554)

Last Updated: 6/24/2021Categories: How toTotal Views: 68173Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Purpose

Likewise agents are used on ESXi/ESX 4.1, ESXi 5.x and ESXi 6.x to facilitate joining the host to an Active Directory domain and subsequent user authentication attempts.

Logs for Likewise agents are helpful during advanced troubleshooting of ESXi/ESX Active Directory integration, but none of these agents generate a log file by default.

This article describes how to enable logging for the Likewise agents.

Resolution

Note: Enabling Likewise logging increases the space used in /var/log/. This should be only used while diagnosing an issue to prevent out of space issues.

ESXi 6.x

Beginning in ESXi 6.x, the logging for Likewise agents are configured using the command-line.

To view the current Likewise agent logging settings:

Log in to the host as root using the console or SSH.

Start the lwsmd service by running this command:

/etc/init.d/lwsmd start

Type this command to view the current log file location:

/usr/lib/vmware/likewise/bin/lwsm get-log

Type this command to view the current logging level:

/usr/lib/vmware/likewise/bin/lwsm get-log-level

To configure the Likewise agent logging setting:

Log in to the host as root using the console or SSH.

Type this command to set the log file location:

/usr/lib/vmware/likewise/bin/lwsm set-log file /var/log/likewise.log

Type this command to set the logging level:

/usr/lib/vmware/likewise/bin/lwsm set-log-level loglevel

Note: The default logging level is info.

These are the valid logging levels:

always

error

warning

info

verbose

debug

trace

ESX/ESXi 4.1 and ESXi 5.x

netlogond daemon

The netlogond daemon is used to join the ESXi/ESX host to the domain. If it is not running, the host does not stay connected to the domain and the Authentication Service Settings revert to Local AuthenticationAttempts to re-connect to the domain restart the daemon.

To enable logging for the netlogond daemon:

Open the /etc/init.d/netlogond file using a text editor.

Locate the line:

ESXi 4.1:

PROG_ARGS="--start-as-daemon "

ESXi 5.x:

PROG_ARGS="--start-as-daemon--syslog "

Change this line to:

PROG_ARGS="--start-as-daemon --logfile /var/log/netlogond.log --loglevel debug"

Note: For ESXi, if you have a scratch partition created as per Creating a persistent scratch location for ESXi 4.x and 5.x (1033696), modify the line to:

PROG_ARGS="--start-as-daemon --logfile /scratch/log/netlogond.log --loglevel debug "

Notes:

The logfile can be any file and the loglevel can be error, warning, info, verbose or debug.

In ESXi 5.x, you need to copy the file for editing to /tmp (for example, using the command cp /etc/init.d/netlogond/tmp), make the appropriate changes and then copy the file back to the original location.

If the netlogond service is running when the /etc/init.d/netlogond file is modified, it needs to be restarted with the command /etc/init.d/netlogond restart.

lwiod daemon

The lwiod daemon is an SMB client driver. It is responsible for allowing communication between the ESXi/ESX host and the Active Directory domain controller.

To enable logging for the lwiod daemon:

Open the /etc/init.d/lwiod file using the text editor.

Locate the line:

ESXi 4.1:

PROG_ARGS="--start-as-daemon"

ESXi 5.x

PROG_ARGS="--start-as-daemon--syslog "

Change this line to:

PROG_ARGS="--start-as-daemon --logfile /var/log/lwiod.log --loglevel trace"

Note: For ESXi, if you have a scratch partition created as per Creating a persistent scratch location for ESXi 4.x and 5.x (1033696), modify the line to:

PROG_ARGS="--start-as-daemon --logfile /scratch/log/lwiod.log --loglevel trace "

Notes:

The logfile can be any file and the loglevel can be error, warning, info, verbose, trace or debug.

In ESXi 5.x, you need to copy the file for editing to /tmp (for example, using the command cp /etc/init.d/netlogond/tmp), make the appropriate changes and then copy the file back to the original location.

Note: If the lwiod service is running when the /etc/init.d/lwiod file is modified, it needs to be restarted with the command /etc/init.d/lwiod restart.

lsassd daemon

The lsassd daemon allows one to select the Active Directory domain for users when creating permissions on ESXi/ESX. It is also responsible for some login behavior when Active Directory users log in to an ESXi/ESX host at the console or via SSH. If it is not running, no Active Directory users can log in to the system (via the vSphere Client, console or SSH) and only local users can be assigned permissions.

To enable logging for the lsassd daemon:

Open this /etc/init.d/lsassd script file using a text editor.

Locate the line:

For ESXi 4.1:

PROG_ARGS="--start-as-daemon "

For ESXi 5.x:

PROG_ARGS="--start-as-daemon --syslog"

Change this line to:

For ESXi 4.1:

PROG_ARGS="--start-as-daemon --logfile /var/log/lsassd.log --loglevel trace "

For ESXi 5.x:

In ESXi 5.x, default directory for logging is /var/log/. If you reference /var/log/vmwar ethe log capture will NOT get the vmware directory and must either capture the file manually or just re-route it to the /var/logdirectory.

PROG_ARGS="--start-as-daemon --logfile /var/log/lsassd.log --loglevel trace"

Restart the daemons in this order:

/etc/init.d/netlogond restart
/etc/init.d/lwiod restart
/etc/init.d/lsassd restart

Notes:

The logfile can be any file and the loglevel can be error, warning, info, verbose, trace or debug.

In ESXi, if you have a scratch partition created as per Creating a persistent scratch location for ESXi 4.x and 5.x (1033696), modify the line to:

PROG_ARGS="--start-as-daemon --logfile /scratch/log/lsassd.log --loglevel trace "

In ESXi 5.x, you need to copy the file for editing to /tmp (for example, using the command cp /etc/init.d/netlogond /tmp), make the appropriate changes, and then copy the file back to the original location.

Notes:

If the lsassd service is running when the /etc/init.d/lsassd file is modified, it needs to be restarted with the command /etc/init.d/lsassd restart.

To retain the changes made to ESXi after a reboot, see Applying vSphere host configuration changes after an unclean shutdown (2001780).

Related Information

Creating a persistent scratch location for ESXi 4.x/5.x/6.x
Applying vSphere host configuration changes after an unclean shutdown
Active Directory ドメインのアカウントを使用して ESXi ホストにログインすることができない
ESXi/ESX で Likewise エージェントのログを有効にする
为 ESXi/ESX 上的 Likewise 代理启用日志记录

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

VMware ESXi 6.7.x

VMware ESXi 6.5.x

VMware ESXi 6.0.x

Take Our Survey

Support Assistant