• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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 Error during update

Bence98

New Pleskian
Hi All,

I got an error regarding the system update. Could someone help me with this issue?
I attached the log.

Thank you in advance.
Best regards,
Bence
 

Attachments

  • update error.zip
    4.6 KB · Views: 3
error: gpg required but not found!

Install package gnupg or at least gpg: apt-get install gnupg.
 
To devs: Could be nice to add a dependency in psa-spamassassin to prevent this; spamassassin unfortunately only has this as Recommended.
 
Hi,
Thank you for your reply. I ran these command this is the output:
apt-get install gnupg
apt-get install gpg
1667749204158.png
and I try this one also, this is the output:
sa-update --nogpg
1667749371177.png
I am a little bit confuse and I don't know why it is not working.
Do you have any clue?

BR,
Bence
 
Hello!
Could you try:
apt-get clean plesk installer remove --component spamassassin apt-get -f install apt-get install gpg plesk installer add --component spamassassin
 
Hello!
Could you try:
apt-get clean plesk installer remove --component spamassassin apt-get -f install apt-get install gpg plesk installer add --component spamassassin
Hi,
Thank you for your comment, I tried it, and here you can find the log.
 

Attachments

  • log.zip
    4.2 KB · Views: 3
Hi @Bence98,
Seems that the reinstallation of SpamAssassin didn't help you. Most likely the packages are not configured now.
You can check it by running:
dpkg -l | grep spamassassin
dpkg -l | grep sa-compile
The packages will be marked either with iU or iF flags.

There can be 2 different issues here.
1st one:
1. Try to log in to under another user in CLI, e.g.:
su plesk.test
Check if you can switch to it or you get an error like:
su: Module is unknown

2. Go back to the root user and check the file /var/log/auth.log, there can be something like:
q-server CRON[30816]: PAM unable to dlopen(pam_limits.so-session): /lib/security/pam_limits.so-session: Cannot open shared object file <C3><B6>: File or directory not found q-server CRON[30816]: PAM adding faulty module: pam_limits.so-session

If you see smth like that there can be a misconfiguration of /etc/pam.d/common-session file.

Try to fix it like that:
  1. Create a backup of /etc/pam.d/common-session file.
    cp -p /etc/pam.d/common-session /root/common-session_backup
  2. Edit /etc/pam.d/common-session file so it looks like mine:
    #
    # /etc/pam.d/common-session - session-related modules common to all services
    #
    # This file is included from other service-specific PAM config files,
    # and should contain a list of modules that define tasks to be performed
    # at the start and end of sessions of *any* kind (both interactive and
    # non-interactive).
    #
    # As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
    # To take advantage of this, it is recommended that you configure any
    # local modules either before or after the default block, and use
    # pam-auth-update to manage selection of other modules. See
    # pam-auth-update(8) for details.

    # here are the per-package modules (the "Primary" block)
    session [default=1] pam_permit.so
    # here's the fallback if no module succeeds
    session requisite pam_deny.so
    # prime the stack with a positive return value if there isn't one already;
    # this avoids us returning an error just because nothing sets a success code
    # since the modules above will each just jump around
    session required pam_permit.so
    # The pam_umask module will set the umask according to the system default in
    # /etc/login.defs and user settings, solving the problem of different
    # umask settings with different shells, display managers, remote sessions etc.
    # See "man pam_umask".
    session optional pam_umask.so
    # and here are more per-package modules (the "Additional" block)
    session required pam_unix.so
    session optional pam_systemd.so
    # end of pam-auth-update config
  3. To fix packages run the command below:
    apt-get install -f

2nd one:
The issue can be related to the bash script being interpreted by the wrong shell, e.g. /bin/sh.
1. Check the shell:
grep spamassassin /etc/passwd [B]debian-spamd[/B]:x:111:117::/var/lib/spamassassin:[B]/bin/sh[/B]

2. Try to change the shell and complete the installation:
usermod -s /bin/bash debian-spamd
apt-get install -f
 
Hi Yaroslav_T,

Thank you for your message.
I tried all the solutions that you wrote here, but they didn't help.
I attached the log.
Do you have any idea? I don't have any clue.

Thank you in advance!

Best regards,
Bence
 

Attachments

  • error.zip
    19.4 KB · Views: 1
Back
Top