Recent content by trumbaut

Issue should be fixed in the meanwhile: the /etc/asl/config file (which is updated by cron every night) now contains the PURGE_LOGS variable: PURGE_LOGS="no" So even without any workaround all should go fine again for now.

Since the /etc/asl/config file is reset every night (by the /etc/cron.hourly/asl cron), the workarounds above doesn't work. While waiting for a permanent fix, you can add if [ -z "$PURGE_LOGS" ]; then PURGE_LOGS="no" fi before the Purge Log section (line 78) in /etc/cron.daily/asl.

Same story here. Error occurs in the following part of /etc/cron.daily/asl due to the missing $PURGE_LOGS variable in /etc/asl/config (which was updated last night): # Purge Logs if [[ "$PURGE_LOGS" != "no" ]]; then DAYS=$PURGE_LOGS # Alerts /usr/bin/find...

Are you sure this will work for a NAT address? Which "src" address should be mentioned in that case: the internal address (10.XXX.YYY.ZZZ) or the public one (EEE.FFFF.GGG.HHH)? At this moment, an "ip route" command only has details about the primary IP address (AAA.BBB.CCC.DDD) which I want to...

I recently started using a floating IP address for my droplet at Digital Ocean, following the instructions at Default Plesk page is shown for a domain assigned on a floating IP address from DigitalOcean. However, after changing subscriptions to the new floating IP (which works fine for the...