• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue poppassd.socket error when fresh install Plesk

nethubonline

Regular Pleskian
Server operating system version
AlmaLinux release 9.3
Plesk version and microupdate number
Plesk Obsidian Version 18.0.60
Hi all,

When I fresh install Plesk on AlmaLinux release 9.3, the Plesk can be installed successfully, however I found an error during the installation, you can see Job failed. See "journalctl -xe" for details. during the install progress

Code:
Installing: psa-mail-driver-common-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [246/403]...
Installing: psa-mail-driver-common-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [246/403] Done
Running scriptlet: psa-mail-driver-common-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [246/403] Done
Created symlink /etc/systemd/system/sockets.target.wants/poppassd.socket → /usr/lib/systemd/system/poppassd.socket.
Job failed. See "journalctl -xe" for details.

rpm scriptlet: Created symlink /etc/systemd/system/sockets.target.wants/poppassd.socket → /usr/lib/systemd/system/poppassd.socket.
rpm scriptlet: Job failed. See "journalctl -xe" for details.
Running scriptlet: psa-mail-driver-common-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [246/403] Done
Installing: plesk-task-manager-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [247/403]...
Installing: plesk-task-manager-18.0-2.redhat.9+p18.0.60.0+t240329.0821.x86_64 [247/403] Done

The Plesk is working fine, however users cannot change email password in the webmail, Horde shows error: Failure in changing password for Poppassd Server: No route to host , Roundcube shows error: Could not save new password. Connection error . If I start poppassd.socket, error will be returned
Code:
# systemctl restart poppassd.socket
Job failed. See "journalctl -xe" for details.

# tail /var/log/messages
Apr  3 14:39:30 test.plesk systemd[1]: poppassd.socket: Failed to create listening socket ([::1]:106): Cannot assign requested address
Apr  3 14:39:30 test.plesk systemd[1]: poppassd.socket: Failed to listen on sockets: Cannot assign requested address
Apr  3 14:39:30 test.plesk systemd[1]: poppassd.socket: Failed with result 'resources'.
Apr  3 14:39:30 test.plesk systemd[1]: Failed to listen on poppassd server activation socket.
 
Hi Martin,

Nope, lsof -i tcp:106 returns nothing. And both OS & Plesk is fresh installed, so no other application is occupying the port.

I guess it is related to IPv6 is not enabled, so the poppassd cannot bind [::1]:106 , can Plesk detects and don't use IPv6 for poppassd if IPv6 is not enabled?
 
To put it simply, it's important to make sure that IPv6 is set up correctly on your server. If your server doesn't support IPv6 or you're not planning to use it, you might want to change the settings for the poppassd service so that it listens on the IPv4 address, which is 127.0.0.1. This is just a suggestion based on the information you've provided, and it might help resolve the issue you're facing with the poppassd.socket service.
 
Back
Top