MID Server logs and purging

[Raji10]

Hi All,

I am requested to clear the dump logs off the Mid servers which are causing critical out of space issues. May I get some information on which is the appropriate place to look for the logs. Is it stored anywhere else than the 'Logs' on the Mid server in the ServiceNow Instance. Are there any checklist/instruction to identify specific logs to clear. We do not have any archival policy of these server logs. Also, should we clear these logs in the server than just the Servicenow instance.

Also is it possible using file/archive/purge SDM program to do this? If so, please help me with some source of right information.

Thanks & Regards,

Raji.

[Monali Patil]

Hi

You can access entries in the ECC Queue that show agent0.log.0 logs and wrapper.log logs for an individual MID Server.

Regards,

Monali Patil

Developer

[Monali Patil]

Hi,

You can access entries in the ECC Queue that show agent0.log.0 logs and wrapper.log logs for an individual MID Server.

Regards,

Monali patil

Developer

[Ankur Bawiskar]

Hi,

logs are stored in agent0.log0 file in the logs folder of mid server

~\agent\logs\ file path.

I believe you need to have access to that mid server to delete it;

or you can run a command line to delete that file

http://www.john-james-andersen.com/blog/service-now/command-line-execution-with-servicenow-mid-serve...

https://www.oreilly.com/library/view/servicenow-building-powerful/9781788628730/800580fb-bd22-47f8-9...

Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

[tim_broberg]

As Ankur says, mid logs are in agent/logs.

There are two kinds of logs: agent and wrapper.

Both are automatically rotated.

The agent logs rotate at 10MB and there are up to 10 of them, so your maximum exposure is 100MB.

The wrapper logs also rotate, but I think I've seen it happen once ever, so I don't recall how many or how big. They're not chatty logs.

The other place you might pile up files is in the subdirectories of agent/work/monitors/ECCSender/. These are responses that are queued up for later transmission. If you have piles of files there, you should look at the agent log and try to figure out why he's unable to send responses back to the instance.

In any event, you should be looking at south of 1GB per mid server. Are you really that tight for space that you can't afford 1GB, or is something funny going on with these mids?
    - Tim.