Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > After upgrading to SAM 6.0, script monitors begin failing Mac OS X servers

After upgrading to SAM 6.0, script monitors begin failing Mac OS X servers

Overview

After upgrading to SAM 6.0, script monitors begin failing Mac OS X Servers. 

Environment

All SAM versions

Resolution

1. Change the SolarWinds.APM.Probes.dll.config file with using the following properties:

<linuxscriptsettings promptwait="2" columncount="200" temporaryscriptfilenameprefix="APM_" id="BugEvents"> CreateFileRetryCount="4"</linuxscriptsettings>SendChunkDelay="1000" SendChunkSize="250"/>

 

Where SendChunkSize is in bytes.

2. Restart the SolarWinds Job Engine v2 service.

 

 

Last modified

Tags

Classifications

Public