FreeNAS 11 Constant High CPU from Python3.6 process

[SweetAndLow]

I checked crontab -l and browsed /etc/cron.d and all are empty or don't exist. I tried from root as well as from a shell in the Plex jail.

What is Plex doing at 2am?

Sent from my XT1096 using Tapatalk

 

[FreeNASBob]

What is Plex doing at 2am?

Nothing that I can discern.

 

[SweetAndLow]

Nothing that I can discern.

When is Plex configured to do it's maintenance?

Sent from my XT1096 using Tapatalk

 

[FreeNASBob]

I'm not aware that there's an option for this. I couldn't find any option that was obvious in the Plex settings and there's nothing in the Plex user's crontab.

 

[Redcoat]

Plex Web Page - Home, Settings, Scheduled Tasks - first topic

 

[FreeNASBob]

Ha! That was it, and right in front of my face too.

 

[joeschmuck]

The RAM usage has still not changed significantly after a day of use. Either something was broken before, or that autosnap.py really had an effect.

While that would be nice to see RAM freed up like this all the time, I wouldn't expect it to stay this way. I think a day of use would be subjective. You might transfer a few thousand files to/from the server and check that RAM utilization again. If it frees up the RAM quickly each time, boy oh boy I want to know. I'm thinking about patching my backup system to see what happens there but right now since it only performs an rsync a few times a day, the RAM untilization is low. I'm not sure I'd see a difference like what you have seen.

 

[halyard]

Found same problem with python3.6 CPU after change from 9.3 to 11.1-RELEASE
in my case it is caused by replication to other freenas 11.

HW configuration is rather low (both NASes same config: ASUS C60M1-I A50, 2x8GB RAM, 6x3TB WD RED, Intel i210, freenas on USB thumb): and based on low spec CPU found that something is not optimal.

Every minute (even is snapshots are set every 4h) set of replication scripts like autorepl.py are running which cause significant CPU load visible behind python3.6, this consume most of CPU on this low HW configuration (this problem was not spotted on version 9, which was running happy for years). In general deltas in snapshots are relatively small and replication of snapshot is matter of minute or two, so observed load is not generated by this, no other CPU intensive setup, no active jails, etc.
Does autorepl.py need to run every minute even if snapshots are set every 4h?

Code:

# grep "started" /var/log/debug.log | tail -5
Dec 18 13:16:39 hostname /autorepl.py: [tools.autorepl:221] Autosnap replication	started
Dec 18 13:17:38 hostname /autorepl.py: [tools.autorepl:221] Autosnap replication	started
Dec 18 13:18:39 hostname /autorepl.py: [tools.autorepl:221] Autosnap replication	started
Dec 18 13:19:38 hostname /autorepl.py: [tools.autorepl:221] Autosnap replication	started
Dec 18 13:20:39 hostname /autorepl.py: [tools.autorepl:221] Autosnap replication	started

 

[D-7]

Hi,
I got the same problem after upgrading.
Seems like alertcli.py is causing it.


Also debug.log looks like this:

Code:

Dec 27 21:59:10 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:00:11 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:01:11 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:02:12 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:03:13 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:04:13 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:05:14 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:06:15 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''

No Jails, no Plugins, no VMs, no Snapshots or Replication tasks, no nothing. Just one Volume shared with SMB and two users.
Any ideas?

Thanks

 

[SweetAndLow]

Hi,
I got the same problem after upgrading.
Seems like alertcli.py is causing it.
View attachment 22075 View attachment 22076

Also debug.log looks like this:

Code:

Dec 27 21:59:10 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:00:11 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:01:11 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:02:12 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:03:13 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:04:13 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:05:14 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''
Dec 27 22:06:15 freenas /alert.py: [ws4py:360] Closing message received (1000) 'b'''

No Jails, no Plugins, no VMs, no Snapshots or Replication tasks, no nothing. Just one Volume shared with SMB and two users.
Any ideas?

Thanks

Open a new thread since this thread was for a different problem and it was solved.