Search results

I found that I did not check the output properly. 2 of the IP addresses in question did resolve to a name thus they did not show up in the iptables -L as IP adresses but as DNS records. Sorry, for raising an issue which in fact an error by me. Nevertheless I did find a bug in the version...

I have blocked some spammer IPs using a custom rule and run the activation script. At first I added 2 IPs and checked with IPtables -L Everything was as expected Then I added another 3 addresses and checked that the activation script lists the appropriate drop lines. After running the activation...

As I said this is a workaround and it will survive updates of watchdog releases which still may contain the bug. Also I I doubt that you exactly looked at the issue. /run is a volatile file system thus it is rebuilt at boot time and so you need to recreate the symlink at every boot. Also a...

My workaround to the problem is a symlink via cron entry like this crontab -e @Reboot ln -s /run/spamassassin.pid /run/spamd.pid

One could also create a link from /run/spamassassin.pid to /run/spamd.pid but it would be required to be recreated at every boot. I found that there was a mismatch on Ubuntu with spamassassin's pidfile between /etc/default/spamassasssin and the systemd service in...

The plesk watchdog module has an adapted service monitoring which I don't want to miss so I re-installed the watchdog. To solve the issue with the nagging rkhunter messages I also installed the rkhunter module from the ubuntu archives and disabled the security scan part in plesk's watchdog...

As there doesn't seem to be a solution to my problems I made up my mind and removed the watchdog module as described here: Resolved - rkhunter.conf file I then used the tutorial at https://www.server-world.info/en/note?os=Ubuntu_16.04&p=rkhunter to install rkhunter outside of plesk to get more...

So I disabled the setting to send reports and run rkhunter manually with -c --rwo. I also added the xinetd services to rkhunter.conf.local and disabled the warnings about the shared memory segment. Alas: every time I run rkhunter I still get the full report via email. I also cannot disable the...

Tnanks a lot for the quick reply. I applied the bug fix for the spamassassin service and at least this issue is gone. Is there also a solution to get rid of the warning about the change to rkhunter.conf? I see the recommendation on the forum is to remove and reinstall the module but then if I...

Sorry for forgetting some details. I am running Plesk 17.8.11 update 10 on Ubuntu 16.04 LTS on a vServer. I have seen the thread about what watchdog warnings can be safely ignored. My question though is: how can I get rid of the obfuscating output and just concentrate on the real issues. One of...

I have added the watchdog extension (rkhunter 1.4.4) to get more security on my server. Alas the output contains a lot of information which obfuscates the real issues thus making it likely to miss something important. On the help page it says that option --rwo can show warnings only. Q1: Can I...

same issue here. Thanks for the workaround. Plesks security module for dovecot definitely needs an update for the new dovecot settings.

/tmp has the regular settings otherwise I would have a lot of other issues too. drwxrwxrwt 2 root root 16384 Feb 16 13:21 /tmp

In the meantime I have upgraded my vServer from a single core to a dual core. The problem with the tmp file creation still exists though. As the dovecot mailing list does not show active discussions on the topic I assume that the problem is with the plesk modification of dovecot. I am using...

Did you check /etc/cron.d/kcare-cron? If you remove the entry with kcarectl --auto-update the message should go away. If you do not want to delete the kcare-cron file, just make a subdir in /etc/cron.d and move it there. Or edit the file and just comment the action line.

As the error message says it already tries to access /tmp/devocot.imap. Thus there must be some default to /tmp. Nonetheless I give your suggestion a try to see if the error will go away.

Occasionally get the following error from dovecot imap on my ubuntu 16.04TLS vServer with the latest ples 17.5.3 dovecot: service=imap, user=xxx@yyyy, ip=[::1]. Error: Temp file creation to /tmp/dovecot.imap. failed: No such file or directory: From the dovecot forum I found: Sometimes Dovecot...

I found: cat /etc/cron.d/kcare-cron 31 */4 * * * root /usr/bin/kcarectl --auto-update It seems that disabling the extension does not properly clean up the cron job, so I deleted it manually

same problem with me. I did enable the kernel care service just to find that it does not work with vServer kernels. I disabled it again in the plesk extensions but the service still sends notifications "Unknown Kernel (Ubuntu 4.4.0-042stab120.11)"

My plesk panel shows a security advice: Plesk is not secured with a valid SSL/TLS certificate If I try to update I get the following error: Error: Execution letsencrypt-hostname.sh has failed with exit code 1, stdout: , stderr: [2017-05-20 09:16:16] ERR [extension/letsencrypt] Execution of...