Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 581
    • Issues 581
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 47
    • Merge requests 47
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #5550
Closed
Open
Issue created Feb 28, 2020 by Rob@monkfish

CentOS 7 installer clamd service restart message in error when not installing amavisd

Installation of version 3.1.15p3 on CentOS 7 1908 build. Wanted to check out rspamd in place of amavisd/spamassasin. Did not install amavisd or spamassasin, installed rspamd plus redis, seems to be operational. Also installed clamav apparently there is a plugin for rspamd.

installing ispconfig, received [expected] messages on missing items and skipped: [WARN] autodetect for Spamassassin failed Force configure Spamassassin (y,n) [n]: n Skipping Spamassassin [WARN] autodetect for Amavisd failed Force configure Amavisd (y,n) [n]: n Skipping Amavisd

On completion, received [unexpected] error message on restarting services ... Job for clamd@amavisd.service failed because the control process exited with error code. See "systemctl status clamd@amavisd.service" and "journalctl -xe" for details. Installation completed.

I cannot find any evidence that the installer has incorrectly tried to configure an instantiated service unit but I dont think the installer should be trying to restart the service (that doesnt logically exist)

Grateful for comment on this behaviour or perhaps I'm doing something wrong. KR

Rob

Edited Feb 28, 2020 by Rob
Assignee
Assign to
Time tracking