Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Replacing syslog-ng with rsyslog on Workspace ONE (78186)

Last Updated: 3/26/2020Categories: TroubleshootingTotal Views: 6563Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Sending log files to the remote syslog server fails.

Cause

This issue occurs because the syslog-ng is not able to send over the log files to remote syslog server.

Resolution

This is a known issue affecting:

VMware Workspace ONE 19.03

VMware Workspace ONE 20.01

Currently, there is no resolution.

Workaround

To work around this issue:

Note: Ensure that the Configurator (8443) syslog configuration on each node is disabled.

SSH into each vIDM-Access node as root.

Stop syslog-ng by running this command:

/etc/init.d/syslog stop

Download the attached rsyslog-5.10.1-0.13.1.x86_64.rpm and copy on the vIDM nodes.

Install the rpm package by running this command:

rpm -i rsyslog-5.10.1-0.13.1.x86_64.rpm

Replace the /etc/sysconfig/syslog with the attached syslog (the only change in the syslog file is syslog-ng being replaced by rsyslog). This ensures that rsyslog will run on boot up.

Replace the /etc/rsyslog.conf file with the attached rsyslog.conf making the following modifications first:

a. Replace IP with your external syslog host (double at-sign is used for TCP port forwarding, it says anything from syslog for TCP will be redirected to 10.143.106.158:514). @@10.143.106.158:514
b. Replace IP with your external syslog host (single at-sign is used for UDP port forwarding, it says anything from syslog for UDP will be redirected to 10.143.106.158:514)

Note: The assumption here is that the remote syslog server is running on the port 514. If the port is different please change that accordingly.

Run this command:

chkconfig syslog

This should say 'syslog on'.

Start rsyslog by running this command:

/etc/init.d/syslog start

Run this command:

ps -ef | grep -i syslog

You should see an output similar to:

root 18326 1 0 20:39 ? 00:00:00 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

syslog

rsyslog

rsyslog-5.10.1-0.13.1.x86_64

Additional Resources

KB
•
ATTO atto_cim ESXi ホスト CIM プロバイダの概要 (78129)

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

Related Versions:

Take Our Survey

Support Assistant