Problem with cron jobs

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • Linux localhost 4.18.0-553.53.1.el8_10.x86_64 #1 SMP
  • Web server and version (e.g, Apache 2.4.25):
    • Apache/2.4.65 (Unix)
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • none
  • PHP version (e.g, 8.3):
    • 8.2.29
  • Is this the first time you’ve seen this error? (Yes / No):
    • no
  • When did this problem seem to first start?
    • 2 or 3 releases back
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • hosting at strato
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

In administration overview is a message “Last background job ran 3 months ago. Something seems to be wrong. Check the background job settings.”

I tested it with ajax, webcron, cron - all the same error

Webocc gives after background-job:list a list from 2 to 11229!

Webocc maintance:repair output is attached - also setupcheck

How can I start or delete jobs that have not been run via webocc?
Why are neither ajax, webcron, nor cron working?

I only have very limited access to the environment at Strato, either via FTP or SSH. I can’t schedule a cron job or similar. crontab -l returns “command not found.”

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

- Repair MySQL collation
     - All tables already have the correct collation -> nothing to do
 - Clean tags and favorites
     - 0 tags of deleted users have been removed.
     - 0 tags for delete files have been removed.
     - 0 tag entries for deleted tags have been removed.
     - 0 tags with no entries have been removed.
 - Repair invalid shares
 - Move .step file of updater to backup location
 - Add move avatar background job
     - Repair step already executed
 - Add preview cleanup background jobs
 - Migrate oc_properties table to nextcloud schema
     - oc_properties table does not exist.
 - Migrate oauth2_clients table to nextcloud schema
     - Update the oauth2_access_tokens table schema.
     - Update the oauth2_clients table schema.
     - Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
 - Repair language codes
 - Add log rotate job
 - Clear frontend caches
     - Image cache cleared
     - JS cache cleared
 - Clear every generated avatar
 - Add preview background cleanup job
 - Queue a one-time job to cleanup old backups of the updater
 - Cleanup invalid photocache files for carddav
 - Add background job to cleanup login flow v2 tokens
 - Remove potentially over exposing share links
     - No need to remove link shares.
 - Clear access cache of projects
 - Reset generated avatar flag
 - Keep legacy encryption enabled
 - Check encryption key format
 - Remove old dashboard app config data
 - Add job to cleanup the bruteforce entries
 - Queue a one-time job to check for user uploaded certificates
 - Repair DAV shares
 - Add background job to set the lookup server share state for users
 - Add token cleanup job
 - Clean up abandoned apps
 - Add possibly missing system config
 - Add AI tasks cleanup jobs
 - Queue a job to generate metadata
 - Cache logo dimension to fix size in emails on Outlook
     - Theming is not used to provide a logo
 - Remove legacy ".ocdata" file
 - Add cleanup-deleted-users background job
 - Validate account properties and store phone numbers in a known format for search
     - Queued background to validate account properties.
 - Migrate config keys
 - AppAPI Daemons configuration GPU params update
     - Daemons configuration GPU params updated: 0
 - Fix component of birthday calendars
     - 0 birthday calendars updated.
 - Regenerating birthday calendars to use new icons and fix old birthday events without year
     - Repair step already executed
 - Fix broken values of calendar objects
    0 [>---------------------------    0 [->--------------------------]
] - Registering building of calendar search index as background job
     - Repair step already executed
 - Register building of social profile search index as background job
     - Repair step already executed
 - Registering background jobs to update cache for webcal calendars
     - Added 0 background jobs to update webcal calendars
 - Registering building of calendar reminder index as background job
     - Repair step already executed
 - Register a background job to update rooms and resources
 - Queue jobs to clean up orphan event and contact data
 - Remove activity entries of private events
     - Removed 0 activity entries
 - Clean up old calendar subscriptions from deleted users that were not cleaned-up
    0 [--->------------------------    0 [----->----------------------]
]     - 0 calendar subscriptions without an user have been cleaned up
 - Write default encryption module configuration to the database
 - Fix the share type of guest shares when migrating from ownCloud
 - Copy the share password into the dedicated column
 - Set existing shares as accepted
 - Converts owncloud guests to nextcloud guests
 - Reset the email of all guest accounts
 - Update OAuth token expiration times
 - Force-reset all Text document sessions
 - Initialize migration of background images from dashboard to theming app
 - Add background job to check for backup codes
 - Populating added database structures for workflows

-----------------------------------------------------------
    system:
        ✗ AppAPI-Bereitstellungs-Daemon: Der Standard-Deploy-Daemon von AppAPI ist nicht eingerichtet. Bitte in den Einstellungen einen Stand
ard-Deploy-Daemon registrieren, um externe Apps (Ex-Apps) zu installieren.
        ⚠ Fehler im Protokoll: 1 Warnungen in den Protokollen seit 18. Oktober 2025, 23:20:55
        ✓ Zulässige Administrations-IP-Bereiche: IP-Filterung durch Administration ist nicht aktiv.
        ✓ Brute-Force-Drosselung: Deine Remote-Adresse "2003:fb:…….." ist nicht durch die Brute-Force-Erkennung gedrosselt.
        ✓ Cron-Fehler: Der letzte Cron-Job wurde ohne Fehler ausgeführt.
        ✗ Cron zuletzt ausgeführt: Letzte Hintergrundaufgaben-Ausführung lief Vor 3 Monaten. Etwas scheint nicht in Ordnung zu sein. Check the background job settings.
        ✓ Debug-Modus: Debug-Modus ist deaktiviert.
        ℹ Transaktionale Dateisperre: Die Datenbank wird für transaktionale Dateisperren verwendet. Um die Leistung zu verbessern, konfiguriere bitte Memcache, falls verfügbar.
        ✓ Beginn des Wartungsfensters: Wartungsfenster zur Ausführung von umfangreichen Hintergrundaufgaben liegt zwischen 1:00 UTC und 7:00 UTC
        ℹ Memcache: Es wurde kein Speichercache konfiguriert. Um die Leistung zu verbessern, sofern verfügbar, bitte Memcache konfigurieren.
        ✓ MIME-Type-Migrationen verfügbar: None
        ✓ Architektur: 64-bit
        ✓ Temporärer Platz verfügbar: Das temporäre Verzeichnis ist korrekt konfiguriert:
- 3.9 GiB verfügbar in /tmp (PHP temporäres Verzeichnis)
- 5595.9 GiB verfügbar in /…../nextcloud/tmp (Nextcloud temporäres Verzeichnis)
        ✓ Push-Dienst: Kostenloser Push-Dienst
    dav:
        ✓ DAV-Systemadressbuch: Keine ausstehende Synchronisierung des DAV-Systemadressbuchs
    network:
        ✓ WebDAV-Endpunkt: Der Webserver ist ordnungsgemäß eingerichtet um Dateisynchronisation über WebDAV zu ermöglichen.
        ✓ Datenverzeichnis geschützt
        ✓ Internetverbindung
        ✓ Unterstützung für JavaScript-Quellkarten
        ✓ JavaScript-Modulunterstützung
        ✓ OCS Anbieter-Auflösung
        ✓ .well-known URLs: Der Server ist korrekt für die Bereitstellung von `.well-known`-URLs konfiguriert.
        ✓ Laden der Schriftartdatei
    notifications:
        ✓ Push-Benachrichtigungen – Fair-Use-Richtlinie
    security:
        ✓ Besitzer der App-Ordner: App-Ordner haben den richtigen Besitzenden ""
        ✓ Alte, von der Administration importierte Zertifikate
        ✓ Codeintegrität: Keine veränderten Dateien
        ✓ Für Header weitergeleitet
        ✓ HTTPS-Zugriff und URLs: Du greifst über eine sichere Verbindung auf deine Instanz zu, und deine Instanz erstellt sichere URLs.
        ✓ Alte serverseitige Verschlüsselung: Deaktiviert
        ✓ PHP-Version: Es wird aktuell PHP 8.2.29 verwendet.
        ✓ Zufallsgenerator: Sicher
        ✓ HTTP-Header: Der Server ist korrekt für das Senden von Sicherheitsheadern konfiguriert.
    database:
        ✓ In der Datenbank fehlen Spalten: None
        ✓ In der Datenbank fehlen Indizes: None
        ✓ In der Datenbank fehlen Primärschlüssel: None
        ✓ Datenbank mit ausstehenden Bigint-Migrationen: None
        ✓ MySQL-Zeilenformat: Keine deiner Tabellen verwendet ROW_FORMAT=Compressed
        ✓ MySQL Unicode-Unterstützung: MySQL wird als Datenbank verwendet und unterstützt 4-Byte-Zeichen
        ✓ Größe der Planungsobjekttabelle: Die Größe der Planungsobjekttabelle liegt im akzeptablen Bereich.
        ✓ Datenbankversion: 8.0.36
        ✓ Isolationsstufe der Datenbanktransaktion: Read committed
    config:
        ✓ Standard-Telefonregion: DE
        ✓ E-Mail-Test: Die Test-E-Mail wurde versandt
        ✓ CLI-URL überschreiben: Die Option "overwrite.cli.url" in deiner config.php ist korrekt auf "https://myurl/nextcloud" festgelegt.
        ✓ Zugriffsrechte für die Konfigurationsdatei: Die Nextcloud-Konfigurationsdatei ist beschreibbar
    php:
        ✓ PHP-Standardzeichensatz: UTF-8
        ✓ PHP set_time_limit: Die Funktion ist verfügbar.
        ✓ Freetype: Unterstützt
        ✓ PHP APCu-Konfiguration
        ✓ PHP getenv
        ✓ PHP-Speicherlimit: 512 MB
        ℹ PHP-Module: Dieser Instanz fehlen einige empfohlene PHP-Module. Für eine verbesserte Leistung und bessere Kompatibilität wird dring
end empfohlen, diese zu installieren:
- sysvsem 
        ✓ PHP OPcache: Korrekt konfiguriert
        ✓ PHP-Option "output_buffering": Deaktiviert
        ✓ PHP Imagick-Modul
    ai:
        ✓ Abholgeschwindigkeit für Aufgabenverarbeitung: Keine geplanten Aufgaben in den letzten 14 Tagen.


Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

Enabled:
  - activity: 5.0.0-dev.0
  - admin_audit: 1.22.0
  - app_api: 32.0.0
  - bruteforcesettings: 5.0.0-dev.0
  - calendar: 6.0.2
  - cloud_federation_api: 1.16.0
  - contacts: 8.0.4
  - dashboard: 7.12.0
  - dav: 1.34.2
  - encryption: 2.20.0
  - federatedfilesharing: 1.22.0
  - files: 2.4.0
  - files_sharing: 1.24.0
  - files_trashbin: 1.22.0
  - guests: 4.6.0
  - logreader: 5.0.0-dev.0
  - lookup_server_connector: 1.20.0
  - notifications: 5.0.0-dev.0
  - oauth2: 1.20.0
  - occweb: 0.2.3
  - password_policy: 4.0.0-dev.0
  - privacy: 4.0.0-dev.0
  - profile: 1.1.0
  - provisioning_api: 1.22.0
  - serverinfo: 4.0.0-dev.0
  - settings: 1.15.1
  - text: 6.0.1
  - theming: 2.7.0
  - twofactor_backupcodes: 1.21.0
  - twofactor_totp: 14.0.0
  - updatenotification: 1.22.0
  - user_status: 1.12.0
  - viewer: 5.0.0-dev.0
  - webhook_listeners: 1.3.0
  - workflowengine: 2.14.0
Disabled:
  - circles: 32.0.0 (installed 22.1.1)
  - comments: 1.22.0 (installed 1.12.0)
  - contactsinteraction: 1.13.1 (installed 1.3.0)
  - federation: 1.22.0 (installed 1.12.0)
  - files_downloadlimit: 5.0.0-dev.0 (installed 3.0.0)
  - files_external: 1.24.0
  - files_pdfviewer: 5.0.0-dev.0 (installed 3.0.0)
  - files_reminders: 1.5.0 (installed 1.4.0)
  - files_versions: 1.25.0 (installed 1.15.0)
  - firstrunwizard: 5.0.0-dev.0 (installed 2.11.0)
  - nextcloud_announcements: 4.0.0-dev.0 (installed 1.11.0)
  - photos: 5.0.0-dev.1 (installed 4.0.0-dev.1)
  - recommendations: 5.0.0-dev.0 (installed 1.1.0)
  - related_resources: 3.0.0-dev.0 (installed 1.5.0)
  - sharebymail: 1.22.0 (installed 1.12.0)
  - support: 4.0.0-dev.0 (installed 1.5.0)
  - survey_client: 4.0.0-dev.0 (installed 2.0.0)
  - suspicious_login: 10.0.0-dev.0
  - systemtags: 1.22.0 (installed 1.12.0)
  - twofactor_nextcloud_notification: 6.0.0-dev.0
  - user_ldap: 1.23.0
  - weather_status: 1.12.0 (installed 1.10.0)


Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

How did you set up the cron job?

What happens, when you run the job manually in a console?