SYSTEM ALERT : high : Not enough space to load conent to SHM after upgrading PA820 to PanOS 10.0.3

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

SYSTEM ALERT : high : Not enough space to load conent to SHM after upgrading PA820 to PanOS 10.0.3

L2 Linker

Dear all.

 

I upgraded last night to PanOS 10.0.3 and this morning I'm getting error messages from the firewall:

 

SYSTEM ALERT : high : Not enough space to load conent to SHM

 

admin@xxx> show system disk-space

Filesystem Size Used Avail Use% Mounted on
/dev/root 9.5G 2.7G 6.4G 30% /
none 2.0G 68K 2.0G 1% /dev
/dev/sda5 19G 4.1G 14G 23% /opt/pancfg
/dev/sda6 7.6G 2.0G 5.2G 29% /opt/panrepo
tmpfs 2.0G 2.0G 4.7M 100% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/sda8 172G 115G 48G 71% /opt/panlogs

 

tmpfs is indeed full.

All the usual recommendations around full disk are about other partitions.

Anybody seen similar issues?

 

Regards,

    Andreas

10 REPLIES 10

L3 Networker

Hi,

 

Can you try as per below KB.

 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClaJCAS

 

try to clean temporary files and not imp files to spare disk usage.

 

Best Regards,

Suresh

 

Sureshreddymudhireddy

Hi Suresh,

 

This seems to be a different situation.

Normal file systems are fine.

 

It is just a problem with tmpfs

 

Regards,

    Andreas

@idelconsulting 

 

You might need to open tac case for this as they might need to delete some files from root

 

 

 

Regards

MP

Help the community: Like helpful comments and mark solutions.

@idelconsulting 

 

Also this should not cause any performance issues on the PA.

Are you experiencing any issue on PA due to this?

Seems tmpfs is a temporary partition in PA.

Try a reboot

 

Regards

MP

Help the community: Like helpful comments and mark solutions.

Hi MP18,

 

I have a TAC case open but so far not much info.

Initially these messages disappeared after a while, but today they resurfaced.

Seems to be kind of a pattern.

Not sure about the impact:

Will ask TAC again what exactly this means and the possible impact: Not enough space to load conent to SHM

 

Receive TimeTypeConfig VersionGenerate TimeSeverityDescription
2021/02/02 08:03:22SYSTEM02021/02/02 08:03:22highNot enough space to load conent to SHM
2021/02/02 07:43:18SYSTEM02021/02/02 07:43:18highNot enough space to load conent to SHM
2021/02/02 07:23:30SYSTEM02021/02/02 07:23:30highNot enough space to load conent to SHM
2021/02/02 07:03:08SYSTEM02021/02/02 07:03:08highNot enough space to load conent to SHM
2021/02/02 06:43:14SYSTEM02021/02/02 06:43:14highNot enough space to load conent to SHM
2021/02/02 05:08:32SYSTEM02021/02/02 05:08:32highNot enough space to load conent to SHM
2021/02/02 04:28:11SYSTEM02021/02/02 04:28:11highNot enough space to load conent to SHM
2021/02/02 03:53:13SYSTEM02021/02/02 03:53:13highNot enough space to load conent to SHM
2021/02/02 03:33:17SYSTEM02021/02/02 03:33:17highNot enough space to load conent to SHM
2021/02/02 03:13:09SYSTEM02021/02/02 03:13:09highNot enough space to load conent to SHM
2021/02/02 02:53:29SYSTEM02021/02/02 02:53:29highNot enough space to load conent to SHM
2021/02/02 02:33:28SYSTEM02021/02/02 02:33:28highNot enough space to load conent to SHM
2021/02/02 02:18:14SYSTEM02021/02/02 02:18:14highNot enough space to load conent to SHM
2021/02/02 01:58:11SYSTEM02021/02/02 01:58:11highNot enough space to load conent to SHM
2021/02/02 01:38:26SYSTEM02021/02/02 01:38:26highNot enough space to load conent to SHM
2021/02/02 01:18:19SYSTEM02021/02/02 01:18:19highNot enough space to load conent to SHM
2021/02/02 00:58:29SYSTEM02021/02/02 00:58:29highNot enough space to load conent to SHM
2021/02/02 00:38:21SYSTEM02021/02/02 00:38:21highNot enough space to load conent to SHM
2021/01/31 12:08:25SYSTEM02021/01/31 12:08:25highNot enough space to load conent to SHM
2021/01/31 11:48:14SYSTEM02021/01/31 11:48:14highNot enough space to load conent to SHM
2021/01/31 11:28:23SYSTEM02021/01/31 11:28:23highNot enough space to load conent to SHM
2021/01/31 11:08:25SYSTEM02021/01/31 11:08:25highNot enough space to load conent to SHM
2021/01/31 10:18:21SYSTEM02021/01/31 10:18:21highNot enough space to load conent to SHM
2021/01/31 09:58:21SYSTEM02021/01/31 09:58:21highNot enough space to load conent to SHM
2021/01/31 09:08:30SYSTEM02021/01/31 09:08:30highNot enough space to load conent to SHM
2021/01/31 08:48:10SYSTEM02021/01/31 08:48:10highNot enough space to load conent to SHM
2021/01/31 08:28:25SYSTEM02021/01/31 08:28:25highNot enough space to load conent to SHM
2021/01/31 07:23:25SYSTEM02021/01/31 07:23:25highNot enough space to load conent to SHM
2021/01/31 07:03:21SYSTEM02021/01/31 07:03:21highNot enough space to load conent to SHM
2021/01/31 06:43:22SYSTEM02021/01/31 06:43:22highNot enough space to load conent to SHM
2021/01/31 06:23:36SYSTEM02021/01/31 06:23:36highNot enough space to load conent to SHM
2021/01/31 06:03:21SYSTEM02021/01/31 06:03:21highNot enough space to load conent to SHM
2021/01/31 05:43:10SYSTEM02021/01/31 05:43:10highNot enough space to load conent to SHM
2021/01/31 05:23:26SYSTEM02021/01/31 05:23:26highNot enough space to load conent to SHM
2021/01/31 05:03:24SYSTEM02021/01/31 05:03:24highNot enough space to load conent to SHM
2021/01/31 04:43:16SYSTEM02021/01/31 04:43:16highNot enough space to load conent to SHM

 

Regards,

    Andreas

Hi,

 

I have a TAC case open but so far didn't receive any details about the potential impact.

initially the messages disappeared, but resurfaced again today.

Seems to be some kind of a pattern.

 

I'll chase TAC for the possible impact.

 

Receive TimeTypeConfig VersionGenerate TimeSeverityDescription
2021/02/02 08:03:22SYSTEM02021/02/02 08:03:22highNot enough space to load conent to SHM
2021/02/02 07:43:18SYSTEM02021/02/02 07:43:18highNot enough space to load conent to SHM
2021/02/02 07:23:30SYSTEM02021/02/02 07:23:30highNot enough space to load conent to SHM
2021/02/02 07:03:08SYSTEM02021/02/02 07:03:08highNot enough space to load conent to SHM
2021/02/02 06:43:14SYSTEM02021/02/02 06:43:14highNot enough space to load conent to SHM
2021/02/02 05:08:32SYSTEM02021/02/02 05:08:32highNot enough space to load conent to SHM
2021/02/02 04:28:11SYSTEM02021/02/02 04:28:11highNot enough space to load conent to SHM
2021/02/02 03:53:13SYSTEM02021/02/02 03:53:13highNot enough space to load conent to SHM
2021/02/02 03:33:17SYSTEM02021/02/02 03:33:17highNot enough space to load conent to SHM
2021/02/02 03:13:09SYSTEM02021/02/02 03:13:09highNot enough space to load conent to SHM
2021/02/02 02:53:29SYSTEM02021/02/02 02:53:29highNot enough space to load conent to SHM
2021/02/02 02:33:28SYSTEM02021/02/02 02:33:28highNot enough space to load conent to SHM
2021/02/02 02:18:14SYSTEM02021/02/02 02:18:14highNot enough space to load conent to SHM
2021/02/02 01:58:11SYSTEM02021/02/02 01:58:11highNot enough space to load conent to SHM
2021/02/02 01:38:26SYSTEM02021/02/02 01:38:26highNot enough space to load conent to SHM
2021/02/02 01:18:19SYSTEM02021/02/02 01:18:19highNot enough space to load conent to SHM
2021/02/02 00:58:29SYSTEM02021/02/02 00:58:29highNot enough space to load conent to SHM
2021/02/02 00:38:21SYSTEM02021/02/02 00:38:21highNot enough space to load conent to SHM
2021/01/31 12:08:25SYSTEM02021/01/31 12:08:25highNot enough space to load conent to SHM
2021/01/31 11:48:14SYSTEM02021/01/31 11:48:14highNot enough space to load conent to SHM
2021/01/31 11:28:23SYSTEM02021/01/31 11:28:23highNot enough space to load conent to SHM
2021/01/31 11:08:25SYSTEM02021/01/31 11:08:25highNot enough space to load conent to SHM
2021/01/31 10:18:21SYSTEM02021/01/31 10:18:21highNot enough space to load conent to SHM
2021/01/31 09:58:21SYSTEM02021/01/31 09:58:21highNot enough space to load conent to SHM
2021/01/31 09:08:30SYSTEM02021/01/31 09:08:30highNot enough space to load conent to SHM
2021/01/31 08:48:10SYSTEM02021/01/31 08:48:10highNot enough space to load conent to SHM
2021/01/31 08:28:25SYSTEM02021/01/31 08:28:25highNot enough space to load conent to SHM
2021/01/31 07:23:25SYSTEM02021/01/31 07:23:25highNot enough space to load conent to SHM
2021/01/31 07:03:21SYSTEM02021/01/31 07:03:21highNot enough space to load conent to SHM
2021/01/31 06:43:22SYSTEM02021/01/31 06:43:22highNot enough space to load conent to SHM
2021/01/31 06:23:36SYSTEM02021/01/31 06:23:36highNot enough space to load conent to SHM
2021/01/31 06:03:21SYSTEM02021/01/31 06:03:21highNot enough space to load conent to SHM
2021/01/31 05:43:10SYSTEM02021/01/31 05:43:10highNot enough space to load conent to SHM
2021/01/31 05:23:26SYSTEM02021/01/31 05:23:26highNot enough space to load conent to SHM
2021/01/31 05:03:24SYSTEM02021/01/31 05:03:24highNot enough space to load conent to SHM
2021/01/31 04:43:16SYSTEM02021/01/31 04:43:16highNot enough space to load conent to SHM

 

Regards,

   Andreas

Quick update:

After upgrading to 10.0.4 these messages didn't come up again.

 

But I still didn't receive any update from TAC regarding a possible operational impact.

Looks like a typo. I assume it should say content and not conent.

Unfortunately unclear which content and what is the impact.

 

Regards,

   Andreas

I see these messages on 820 running 10.0.4.

Hi,

 

Was there any conclusion from TAC regarding these message, impact and/or solution?

 

 

TAC was saying that this could happen if new signatures are deployed while reports are still being generated depending on older signatures.

So basically the older signatures are kept around while the reports are generated and these are filling up the space.

  • 7707 Views
  • 10 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!