Look carefully as the information may scroll by quickly at times and slowly at others, but you'll be looking for Step 6, then Step 7.Let the dtrace run for about 10 minutes, monitoring the log through use of the 'Mon' command.At the 'DT>' prompt, type 'Mon' and press the Enter key to monitor the process log entries.Press the Enter key to complete the log file specification and start the actual logging.At the 'DT>' prompt, type 'log C:\Logs\AcceleratorServiceSamplingIssue.log', without the single quotes and using the drive letter, folder path and file name of your choice (we just ask that you have the extension as '.log').Press the Enter key to complete the process logging selection.At the 'DT>' prompt, type 'set 2 v', without the single quotes and replacing the number 2 with the number associated with the AcceleratorService process if that number is other than 2.Note that will have to manually type the process name at the next prompt if you don't use the 'v' (for View) option to assign a shortcut process number to each process. Scroll up throgh the listing of processes as needed to locate the AcceleratorService process and note the number associated to it (typically, this would be the number 2).At the 'DT>' prompt, type the letter v and press the Enter key.
Type dtrace at the Command Prompt and press the Enter key.Change the location within the Command Prompt to the EV installation folder (default location on 64-bit OS is 'C:\Program Files (x86)\Enterprise Vault' or on 32-bit OS is 'C:\Program Files\Enterprise Vault').Log onto the CA server as the Vault Service Account (VSA) if you've logged on as some other account.Please run the dtrace from the CA server's Command Prompt as follows: I presume this is the EV server as there are no lines with AcceleratorService threads. I'm looking at the dtrace and see it was run on machine remora.
Is there any other way to kickstart the Sampling : Last Sample or Random Sampling in general via script or otherwise? The Indexing service on the CA server appears to not be started and has an error when attempting to start - does this tie into the Random Sampling system? We've set the thread count lower, changed the cache timeouts, adjusted the Last Sample date back one day, restarted all connected systems but still, the random sampling never seems to start back up again appropriately.
The odd part is that the Sampling : Last First Pass Sample metric is consistently updated? The database tblConfig appears to be stuck with Sampling : Status - Started and the date for Sampling : Last Sample remains the same. This issue started happening a week or so back and we've tried a number of the resolutions available through Symantec's knowledge base that generally work after a restart of the database, Windows updates gets turned back on and restarts the system at 3 AM (during processing) or otherwise and none have kickstarted the Last Sample metric again.
0 kommentar(er)
