Search results

Found Resolved - systemd User Manager activity I think that's no bug, but a feature. I think this problem is solved.

Found Logs flooded with systemd messages: Created slice, Starting Session - Red Hat Customer Portal but you have to change /etc/rsyslog.d/ignore-systemd-session-slice.conf with some logentrys. I don't know if it is wanted when there is no easy solution. My syslog are now bigger but it is not...

Have the same problems :-( (see Question - Many log-entrys after update to Debian 12 and Plesk 18.0.61) When loglevel notice doesn't log mail it's no solution, i only want to remove this user-slices Changing to loglevel info doen't help :-(

Seems nobody can help? Does anybody know where Plesk stores the mailroutes for postfix? The aliases-file is empty? Mailman 2 must have already stated somewhere which mails are routed via mailman and how?

Thank you. Javascript-Common is needed for mailman3-web. But it seems mailman is working without this line. And i think mailman3-web is needed for mailman, even if psa-mailman3-configurator shows no dependencies there. But unfortunately I still have the problem that mailman is not working...

After my update to Debian 12 and Plesk 18.0.61 Update 1 i had a problem with one website I found out, that this website couldn't find his directory /javascript and found out that there is a config at /etc/apache2/conf-available/javascript-common.conf - but this config has a date from 2020 and i...

Sorry, wrong thread - it's Plesk Obsidian :/

After updating from Debian 10 to 11 to 12, I now have mailman3 running on my server I then converted all lists from Mailman2 to Mailman3 following the instructions from mailman. I can access it via the web interface, manage everything etc. When I register on the web interface, I also receive the...

Now that Mailman 3 is supported, I have updated my server from Debian 10 to 11 and then to 12. Now I constantly have entries in the sylog in the following form: and: Are these normal or are there any problems? I do not have these on another Debian 12 system (without Plesk).

Have the same error after Updating to Debian 12 and Plesk 18.0.61 Update 1: Do you found a solution? Can't contact Plesk-Support because i bought my licence at a reseller.