Search results

As topic says... I know it has just been released and seems there are some tricky changes involved (dovecot, interface names, etc), but any ETA?

I debugged with strace and apparently is caused by the fact that not having installed any stats tools since now (webalizer\awstats) there is no .stats file in the log folders. The error is caused by trying to delete those non-existent stats file in the generate stats process. This should fix...

Suddenly my traffic usage statistics are not updated. I then tried to regenrate them manually but I get this error. Already tried to run all repairs. Both AWstats and webalizer were uninstalled, Not sure if they are needed to calculate traffic usage? I installed only AWstats anyway, but still...

Percona is already supported, there is even an official how-to in plesk docs. (it's a MySQL drop-in replacement, so...) My question was about the specific MySQL version 8.4. I know 8.0.x is supported. But 8.0 end of life is coming soon and the new LTS on new installs is 8.4.x. So I want to know...

As title says: is 8.4 supported? Anyone tried?

Isn't there anything in the source tha appends the files date to the logs? Maybe finding who adds the .2024_08_29 part will help. Also, I'm using Litespeed Pro as webserver. But it's configured to use Apache logs files by default, so it shouldn't matter.

no they are webserver access_logs

No, this is not my issue. All the domains are correctly configured for logrotate. the logrotate config in /opt/PSA are correct too. logrotate DOES work correctly. it's some other plesk script creating those files. those are not normal system log files. it's plesk creating them. I just need to...

Can you just tell me which plesk script file is involved in the statistics cron or rotating logs? I'll fix it myself. Because those are not generated by logrotate, I already checked by running it manually.

No, they are unlocked and synchronized. Also I don't get why a locked subs shouldn't rotate logs correctly anyway. In fact, they are rotated correctly. But it leaves the uncompressed ones renamed with the date.

Hello, I'm having a weird problem. I have correctly set logrotate to keep latest 30 days of logs and rotate daily. Everything is working and everyday a new log_name.[number].gz is created. However ONLY for 3 domain (out of over 200) i also get an uncompressed version of them named like this in...

Then I don't know what else could be causing it. What I know is that right after the server setup I was receiving mail for my cron in chrooted bash (a script that runs every 4 hours and reports back). Then suddenly it stopped working. Unfortunately when I noticed it the first time it was already...

Yes it does... At least on Deb12. it did for me till 3 days ago. There is even a specific flag in the Plek Mail server settings to Allow users to use sendmails in scripts. If nothing else works i'll just use mini_sendmail or something like that...

I don't know how plesk handles the sendmail usage inside chroot. That's why I wanted some Plesk dev to explain it so I can recreate it as it was before it broke. The only thing I know is that it's possible, because it worked before. So I just need to understand HOW to fix the chroot accordingly...

I made another step by adding the spool folder inside chroot. However I'm now getting: plesk-sendmail[2371173]: S2371173: Unable to get mail user passwd record (0): Success plesk-sendmail[2371173]: S2371173: Unable to get mail group passwd record (0): Success plesk-sendmail[2371173]: S2371173...

That wasn't it. That's only for apache, I'm using litespeed. And anyway it doesn't affect chroot or cron scripts. I'm now in a situation where I manually added /usr/lib/plesk-9.0/postfix-sendmail-wrapper inside the chroot, removed the suid bin on this one only and created a symlink from...

PHP CLI runs chrooted already for cron scripts. That's no problem to add following the update-chroot guide on Plesk KB. OMG. That's probably it. I'll test later and report back. When you add sendmail with update-chroot.sh it gets added wrong. So you need to change the symlink to point to the...

There isn't /usr/sbin/sendmail by default, only if I add it manually with update-chroot.sh. However when adding that way the symlink is broken anyway. When manually fixing the symlink it complains about some other things when passing data to sendmail. There isn't anything on the sbin folder by...

Point 2) of my post. Adding it manually wont work, also there is the setuid bit on the plesk wrapper which is dropped.

No one with this problem?