Facebook
Twitter
kevinjansen
Basic Pleskian
- Server operating system version
- Almalinux 8
- Plesk version and microupdate number
- 18.0.60
Hi All,
We are in the middle of the migration from and discovered something that is not working anymore.
We used the Centos to Almalinux8 convert tool. And everything runs smoothly. But now we got in contact with a few customers that tried to upload/publish websites and got weird errors during the publish. After clicking a few times on publish it eventually syncs.
When reproducing the customer experience i see the following error in the /var/log/secure
May 7 18:11:01 server133 proftpd: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory
May 7 18:11:01 server133 proftpd: pam_systemd(proftpd:session): Failed to connect to system bus: No such file or directory
We are using sftp, the customer auth is set to chrooted, but also tested it with other options.
We did not have this issue on Centos and also the remaining servers on Centos do not have this error in the logs.
Not sure if this error is the actual problem, since if you publish 500 files, half of them succeed, and the other half dont. Clicking republish retries to do the missing files, and in the end they are all in sync. Also checked some other configuration files, and its not the common error about max_ip_connections, that is already set to unlimted.
Any directions? Else we are going to open a support ticket with server access for support.
Kind regards,
Kevin
We are in the middle of the migration from and discovered something that is not working anymore.
We used the Centos to Almalinux8 convert tool. And everything runs smoothly. But now we got in contact with a few customers that tried to upload/publish websites and got weird errors during the publish. After clicking a few times on publish it eventually syncs.
When reproducing the customer experience i see the following error in the /var/log/secure
May 7 18:11:01 server133 proftpd: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory
May 7 18:11:01 server133 proftpd: pam_systemd(proftpd:session): Failed to connect to system bus: No such file or directory
We are using sftp, the customer auth is set to chrooted, but also tested it with other options.
We did not have this issue on Centos and also the remaining servers on Centos do not have this error in the logs.
Not sure if this error is the actual problem, since if you publish 500 files, half of them succeed, and the other half dont. Clicking republish retries to do the missing files, and in the end they are all in sync. Also checked some other configuration files, and its not the common error about max_ip_connections, that is already set to unlimted.
Any directions? Else we are going to open a support ticket with server access for support.
Kind regards,
Kevin
