Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
auto-tx
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
vamp
auto-tx
Commits
e12660cc
Commit
e12660cc
authored
6 years ago
by
Niko Ehrenfeuchter
Browse files
Options
Downloads
Patches
Plain Diff
Show instructions on how to reset performance counters cache in log
Fixes
#61
parent
6148ce7e
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ATxService/AutoTx.cs
+6
-0
6 additions, 0 deletions
ATxService/AutoTx.cs
with
6 additions
and
0 deletions
ATxService/AutoTx.cs
+
6
−
0
View file @
e12660cc
...
...
@@ -321,6 +321,10 @@ namespace ATxService
/// Set up the performance monitor objects (CPU, Disk I/O, ...).
/// </summary>
private
void
InitializePerformanceMonitors
()
{
var
lodctr_msg
=
"Occasionally the performance counters cache becomes corrupted "
+
"and needs to be reset manually. To do this, run the following "
+
"command from a shell with elevated privileges:\n\n lodctr /r\n\n"
;
try
{
_cpu
=
new
Cpu
{
Interval
=
250
,
...
...
@@ -340,6 +344,7 @@ namespace ATxService
}
catch
(
Exception
ex
)
{
Log
.
Error
(
"Unexpected error initializing CPU monitoring: {0}"
,
ex
.
Message
);
Log
.
Error
(
lodctr_msg
);
throw
;
}
...
...
@@ -358,6 +363,7 @@ namespace ATxService
Log
.
Error
(
"Unexpected error initializing PhysicalDisk monitoring: {0}\n"
+
"Please make sure the service account is a member of the local"
+
"group [Performance Monitor Users]!"
,
ex
.
Message
);
Log
.
Error
(
lodctr_msg
);
throw
;
}
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment