Server issueing remote console commands

Since a few weeks we suddenly have a lot of log entries concerning show tasks commands issues by the server itself. We however don’t have any idea where it’s coming from. A typical line looks like:

30-01-2005 05:05:06 Remote console command issued by DOMPWW01/SRV/Business: show stat Mem.Allocated.Process

show stat Server.AvailabilityIndex

Server.AvailabilityIndex = 100

1 statistics found

The checked are:

show stat Database.Database.BufferPool.PerCentReadsInBuffer

show stat Mem.Allocated.Process

show stat Server.AvailabilityIndex

show stat Server.CPU.Count

show stat Server.Trans.PerMinute.Peak

show stat Server.Users

show stat Http.CurrentConnections

show stat Mail.TotalRouted

show stat Mail.Delivered

show stat Mail.Dead

show stat Mail.Waiting

It checks each statistic twice (so the bunch above gets repeated right after the last statistic is asked). This whole process runs every 5 minutes, so you can imagine that it generates a lot of log.

Anyone any idea what could cause this?

Subject: Server issueing remote console commands

This sounds like someone has set their Administrator Client to monitor every 5 minutes…Kev

Subject: Server issueing remote console commands

This sounds like someone has set their Administrator Client to monitor every 5 minutes…Kev

Subject: RE: Server issueing remote console commands

It would, but then the line would say:30-01-2005 05:05:06 Remote console command issued by Martijn de Jong/USR/Business: show stat Mem.Allocated.Process

instead it mentions the servername, which makes it look like it’s not an administrator client

Subject: Could be a scheduled agent running on the server issueing remote console cmds to itself

Subject: Could be a scheduled agent running on the server issueing remote console cmds to itself

We were thinking of that too, but one fact makes it unlikely. The show stats starts at exactly the same times (x:00, x:05, x:10 etc) no matter when the server was last restarted. This is, in my opinion, not the behavior of a scheduled agent.

Edit: We actually tested this morning by quitting the agent manager for a while. Didn’t solve it, so that rules out scheduled agents as the cause.