• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Plesk Task Manager

@gerald

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
19.0.66
/opt/psa/admin/conf/ task-manager.yml

file corrupted or missing


cannot start the Plesk Task MAnager

How can we reinstall this service if the file get corrupted or missing

I try Plesk Repair No luck...

when I check the service

systemctl status plesk-task-manager
● plesk-task-manager.service - Plesk Task Manager Service
Loaded: loaded (/usr/lib/systemd/system/plesk-task-manager.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/plesk-task-manager.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Mon 2025-02-17 00:50:50 UTC; 1s ago
Process: 28989 ExecStart=/usr/lib/plesk-task-manager --config /opt/psa/admin/conf/task-manager.yml --data /var/lib/plesk/task-manager (code=exited, stat>
Main PID: 28989 (code=exited, status=203/EXEC)
CPU: 3ms



please help me
 
What do you have in that file? If it exists, back it up and replace the content with:
YAML:
cat /usr/local/psa/admin/conf/task-manager.yml
# Copyright 1999-2024. WebPros International GmbH. All rights reserved.
concurrency:
  limits:
    # Maximum number of concurrent tasks
    # This limit will not be exceeded regardless of concurrency rules configuration below
    #total: 100
  tags:
    # Concurrency rules
    # Each rule is a mapping of a tag or a tag pattern to an integer limit value.
    # Tag patterns include '*' symbols which match any tag substring.
    # Limit value of -1 means "unlimited", any other limit value ensures that no more
    # than that many tasks with matching tags in their concurrency rules are executed
    # concurrently.
    # Any tag not configured here is treated as having limit value of 1 (no concurrency).
    #event_handler: 5
    #long_task: -1
    #daily_maintenance: -1
timeouts:
  # How often to remove tasks that were not recently updated
  gc:
    # Remove 'success' tasks that are older than
    #successful: 24h
    # Remove 'failure' tasks that are older than
    #failed: 168h
    # Remove all other tasks that are older than
    #incomplete: 168h
    # Check for old tasks once per this period
    #cleanupPeriod: 1h
  process:
    # Process stop timeout (delay between graceful and forced termination)
    #stop: 15s
    # Default process execution timeout (can be overridden via API)
    #execution: 20m
    # How often to check running processes state
    # Depending on platform this may be primary or auxiliary method of process control
    #probePeriod: 1m
log:
  # Logging level, one of: DEBUG, INFO, WARNING, ERROR
  # Daemon --verbosity CLI option takes priority if set
  #level: INFO

If it's missing, create an empty file with the above content.
 
Hi! In addition to the previous reply, there should be "/opt/psa/admin/conf/task-manager.yml.sample" file where you can get the content above.
Also, depending on the errors in "/var/log/plesk/task-manager.log", there can be other causes of the missing/corrupted file (assuming that you don't just see that fact on the terminal but somewhere in the logs or error message appears). So, I'd suggest checking dbus-related errors (e.g. "Cannot connect to systemd dbus: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory") - they mean that the dbus service is not running properly and simple "systemctl restart dbus.socket" + "systemctl restart plesk-task-manager" can help. The other probable cause is that "/var/log/plesk/task-manager.log" may have incorrect permissions/ownership (you'll see "/run/plesk-task-manager/api.sock"-related messages in the log). "/var/log/plesk/task-manager.log" should look like (don't forget to restart task manager service if you are willing to change smth):
# ls -lah /var/log/plesk/task-manager.log
-rw-r----- 1 psaadm psaadm 12K Feb 17 11:18 /var/log/plesk/task-manager.log
 
Thanks I have the task-manager.yml. as above. So that's fine. I checked the task-manager.log it says

ERROR 2025/02/17 00:33:28 Failed to update DB schema: unable to open database file: permission denied

So what should I do now
 
Back
Top