<!–
Thanks for reporting issues back to ownCloud! This is the issue tracker of ownCloud, if you have any support question please check out ownCloud support and maintenance information for customers
This is the bug tracker for the Server component. Find other components at core/.github/CONTRIBUTING.md at master · owncloud/core · GitHub
For reporting potential security issues please see ownCloud security policies and information
To make it possible for us to help you please fill out below information carefully.
Before reporting any issues please make sure that you’re using the latest available version for your major branch (e.g. 9.0.x), see Changelog - ownCloud
**–> **
### Steps to reproduce
1.
2.
3.
### Expected behaviour
Tell us what should happen
Normal CPU usage
### Actual behaviour
Tell us what happens instead
High (100%) CPU usage
### Server configuration
Operating system:
Freenas
Web server:
Database:
PHP version:
ownCloud version: (see ownCloud admin page)
ownCloud 9.1.2 (stable)
Updated from an older ownCloud or fresh install:
fresh install
Where did you install ownCloud from:
Freenas GUI Plugin page.
Signing status (ownCloud 9.0 and above):
I can sign in with no problem.
** **Login as admin user into your ownCloud and access ** **http://example.com/index.php/settings/integrity/failed ** **paste the results into https://gist.github.com/ and puth the link here.** 'No errors have been found.' **
The content of config/config.php:
```
Log in to the web-UI with an administrator account and click on
‘admin’ → ‘Generate Config Report’ → ‘Download ownCloud config report’
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.
Can’t find this in OwnCloud Web GUI accesed through Freenas.
**or **
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder
Command not recognized in OwnCloud FreeNas Jail.
ATTENTION: Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove all host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.
```
List of activated apps:
Crashplan
Plex
** **If you have access to your command line run e.g.:** **sudo -u www-data php occ app:list** **from within your ownCloud installation folder.** **
Are you using external storage, if yes which one: local/smb/sftp/…
Yes -
/Mnt/Archiefoud
/Mnt/Archiefnieuw
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…
no
### Client configuration
Browser:
Chrome
Operating system:
Freenas
### Logs
#### Web server error log
```
Insert your webserver log here
```
#### ownCloud log (data/owncloud.log)
** **Insert your ownCloud log here** https://www.dropbox.com/s/426orw8o7rh8lx9/owncloud.log?dl=0 **
#### Browser log
** **Insert your browser log here, this could for example include:** I do not understand. **a) The javascript console log** **b) The network log ** **c) ...** **
Owncloud runs at 100% in Freenas. Uses high CPU, even when not used. Can’t figure out why.
see - Dropbox
Thanks,
Dion