# Unable to retrieve log file given the log type 'PEGA'

**URL:** <https://forums.pega.com/t/unable-to-retrieve-log-file-given-the-log-type-pega/1433>\
**Category:** General\
**Tags:** 6-1, healthcare-and-life-sciences, system-administration, senior-system-architect\
**Created:** [May 26, 2021, 5:05am UTC](https://forums.pega.com/t/unable-to-retrieve-log-file-given-the-log-type-pega/1433 "2021-05-26T05:05:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NivethaD16933124](https://avatars.discourse-cdn.com/v4/letter/n/90ced4/32.png) [@NivethaD16933124](https://forums.pega.com/u/NivethaD16933124)\
**Post date:** [May 26, 2021, 5:05am UTC](https://forums.pega.com/t/unable-to-retrieve-log-file-given-the-log-type-pega/1433/1 "2021-05-26T05:05:46Z")

</div>

After the scheduled restart, logs are pointing to a NULL location as shown below.

 ![A snapshot of the logs pointing to a NULL Location.png](https://pega1.discourse-cdn.com/pega/original/2X/b/b8a277bb5297da846eb10ffe076402c2d5ab0965.png)

On click of the null, we are getting the error “Unable to retrieve log file given the log type ‘ALERTSECURITY/dailyRollFile/SERVICES-PAL/ALERT/PEGA’ – please verify that the file appender in the prconfig.xml document use the standard appender names” inspite of all the appenders being present in prlogging.xml.

Neither changes have been made to prlogging.xml nor prconfig.xml in the recent past.

---

<div class="post-metadata">

**Author:** ![NivethaD16933124](https://avatars.discourse-cdn.com/v4/letter/n/90ced4/32.png) [@NivethaD16933124](https://forums.pega.com/u/NivethaD16933124)\
**Post date:** [May 28, 2021, 4:47am UTC](https://forums.pega.com/t/unable-to-retrieve-log-file-given-the-log-type-pega/1433/2 "2021-05-28T04:47:53Z")

</div>

Log storage was running out of memory. Issue is fixed after clearing the memory.