How to fix a Log monitoring failure due to lack of permissions with the files to be monitored?
Execute log monitoring with sudo permission
Steps to enable Sudo permission for Log monitoring:
LogMonitorTest::$hostName:$portNo=$hostName,-auto,-host $hostIp -port $portNo -lines 0:0 -rotatingFile false -alertFile $unconfigured -overwrittenFile false -rolloverFile false -searchPattern $unconfigured -useUTF8 false -useUTF16 false -excludePattern none -uniqueMatch false -caseSensitive false -encodeFormat none -ddFreq 1:1 -use_sudo false -sudo_path none -rptName $hostName -mCount 1,300
Cedric Carter
How to fix a Log monitoring failure due to lack of permissions with the files to be monitored?
Execute log monitoring with sudo permission
Steps to enable Sudo permission for Log monitoring:
LogMonitorTest::$hostName:$portNo=$hostName,-auto,-host $hostIp -port $portNo -lines 0:0 -rotatingFile false -alertFile $unconfigured -overwrittenFile false -rolloverFile false -searchPattern $unconfigured -useUTF8 false -useUTF16 false -excludePattern none -uniqueMatch false -caseSensitive false -encodeFormat none -ddFreq 1:1 -use_sudo false -sudo_path none -rptName $hostName -mCount 1,300
Administrator
Execute log monitoring with sudo permission
Steps to enable Sudo permission for Log monitoring:
LogMonitorTest::$hostName:$portNo=$hostName,-auto,-host $hostIp -port $portNo -lines 0:0 -rotatingFile false -alertFile $unconfigured -overwrittenFile false -rolloverFile false -searchPattern $unconfigured -useUTF8 false -useUTF16 false -excludePattern none -uniqueMatch false -caseSensitive false -encodeFormat none -ddFreq 1:1 -use_sudo false -sudo_path none -rptName $hostName -mCount 1,300
-
Finding eG Agent version
-
Delete and Acknowledge alarms
-
Updating nick names
-
Changing IP address of a monitored component
-
Changing IP address of remote agent and external agent
-
Inside view metrics are not collected by eG
-
Error 1067
-
Agent stopped running
-
eG agent auto-startup
-
Remote agent connection issue
See all 77 topics