I don’t know why, but at one of my servers the domains.list file gets erased every x weeks. So after some weeks they are missing in the httpd.conf and the domains will not work.
Before I figure out what causes it, this is a little piece of code to fix the list and rewrite httpd:
for d in `ls /home/user/domains`; do echo $d >> /usr/local/directadmin/data/users/user/domains.list; done /usr/local/directadmin/custombuild/build rewrite_confs
Since DirectAdmin works with ‘per e-mail account send limits’ some things can work out pretty annoying.
In this case the customer sent 1000 e-mails (not SPAM) and want to send e-mail number 1001. But, changing the limit to 2000 will result in a
Please set a limit between 1 and 1000
Despite the fact of the “Zero is unlimited”, if you enter 0 it will give:
You cannot set an unlimited send limit
So I ended up to search in the files and remove the usage by hand:
rm -f /etc/virtual/domain.com/usage/info
Now the usage is removed and the customer is able to send another 1000 e-mails. Which still is not solved but for now it’s done.
In addition to my previous post about removing WooCommerce products, I just used the same snippet to remove 400k bbPress replies.
With this query you can remove all the replies:
DELETE relations.*, taxes.*, terms.* FROM wp_term_relationships AS relations INNER JOIN wp_term_taxonomy AS taxes ON relations.term_taxonomy_id=taxes.term_taxonomy_id INNER JOIN wp_terms AS terms ON taxes.term_id=terms.term_id WHERE object_id IN (SELECT ID FROM wp_posts WHERE post_type='reply'); DELETE FROM wp_postmeta WHERE post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'reply'); DELETE FROM wp_posts WHERE post_type = 'reply';
And use this to empty all bbPress topics:
DELETE relations.*, taxes.*, terms.* FROM wp_term_relationships AS relations INNER JOIN wp_term_taxonomy AS taxes ON relations.term_taxonomy_id=taxes.term_taxonomy_id INNER JOIN wp_terms AS terms ON taxes.term_id=terms.term_id WHERE object_id IN (SELECT ID FROM wp_posts WHERE post_type='topic'); DELETE FROM wp_postmeta WHERE post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'topic'); DELETE FROM wp_posts WHERE post_type = 'topic';
Worked like a charm! Now all bbPress topics and replies are deleted.
I found this handy SQL query to easily remove all the products and related stuff from a WordPress WooCommerce.
DELETE relations.*, taxes.*, terms.* FROM wp_term_relationships AS relations INNER JOIN wp_term_taxonomy AS taxes ON relations.term_taxonomy_id=taxes.term_taxonomy_id INNER JOIN wp_terms AS terms ON taxes.term_id=terms.term_id WHERE object_id IN (SELECT ID FROM wp_posts WHERE post_type='product'); DELETE FROM wp_postmeta WHERE post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'product'); DELETE FROM wp_posts WHERE post_type = 'product';
Sed is a brilliant function to delete or replace strings. I often used sed for replacing (a group of) words or deleting lines.
How to remove a line containing a string in sed:
sed -i '/string/d' /home/admin/filename.txt
How to replace a string in sed:
sed -i 's/#Port 22/Port 12340/g' /etc/ssh/sshd_config
How to remove white lines from ie a .ini file with sed:
sed -i '/^\s*$/d' /usr/local/directadmin/conf/directadmin.conf
Because i keep forgetting how to remove the on behalf when sending mails with the php mailer this snippet.
in /etc/exim.conf (above primary_hostname)
untrusted_set_sender = * no_local_from_check
# service exim restart
I found this little snippet elsewhere and find it very usefull to use in my own scripts for statistiscs:
free -m | awk 'NR==2{printf "Memory Usage: %s/%sMB (%.2f%)\n", $3,$2,$3*100/$2 }'
df -h | awk '$NF=="/"{printf "Disk Usage: %d/%dGB (%s)\n", $3,$2,$5}'
top -bn1 | grep load | awk '{printf "CPU Load: %.2f\n", $(NF-2)}'
It returns something like:
Memory Usage: 2340/24000MB (9.75%)
Disk Usage: 40/100GB (40%)
CPU Load: 0.04
This simple but effective script makes a back-up of the target SQL database and deletes databases older then 90 days. I keep the folder synchronized with other systems so the customer can reach his database with 90 days retention himself.
#!/bin/bash
cd /backups
user="mysql_user"
passwd="password"
host="localhost"
db_name="mysql_database"
backup_path="/backups"
date=$(date +"%d-%b-%Y")
umask 177
# dump the database
mysqldump --user=$user --password=$passwd --host=$host $db_name > $backup_path/$db_name-$date.sql
# zip contents
zip $db_name-$date.zip $db_name-$date.sql
# remove old backups
find $backup_path/* -mtime +90 -exec rm {} \;
echo done
Of course, instead of setting the username/passwd variables in the script itself you can read the DirectAdmin credentials with:
source /usr/local/directadmin/conf/mysql.conf
Migrating Magento is pretty easy. Most of the times you only need to sync the files and export/import the database. But to automate such a process to test a lot, you can use a bash script to make things easier.
I often use this bash script (or similar) to migrate a Magento shop from one server to another:
#!/bin/bash echo dumping sql ssh root@10.0.0.1 -p 7685 "mysqldump -u magento_user -ppassword magento_db > /home/magento.sql" echo rsync files /usr/bin/rsync --exclude 'app/etc/local.xml' --exclude 'media/.htaccess' --exclude 'app/etc/config.xml' -a --delete -e "ssh -p 7685" root@10.0.0.1:/home/domain.com/. /home/user/domains/domain.com/public_html/. echo rsync db /usr/bin/rsync -a --delete -e "ssh -p 7685" root@10.0.0.1:/home/magento_db.sql /home/user/domains/domain.com/ echo importing db source /usr/local/directadmin/conf/mysql.conf mysql -u $user -p$passwd new_magentodb < /home/user/domains/domain.com/magento.sql echo restoring permissions chown -R user:user /home/user/domains/domain.com/public_html chown user:user /home/user/domains/domain.com/magento.sql echo done
This script is executed on the new server, which is loaded with DirectAdmin. The old server (10.0.0.1) is plain CentOS 6.5. I added the rsa-key.pub to the authorized keys on the old server, so this server is able to execute commands as root without entering a password.
The port on the old server is 7685, that’s why you find it in the ssh and rsync commands.
I exclude the local.xml because on the new server I had to change the MySQL credentials. The media/.htaccess file gave problems on the new DirectAdmin server as well, so I had to change it and exclude the file from future rsyncs.
After running this script the Magento webshop is migrated from the old server to the new DirectAdmin server and works perfectly!
Sometimes WordPress can’t update itself or the plug-ins. This often happens after the installation has been moved or the username has been changed.
Downloading update from https://downloads.wordpress.org/release/wordpress-4.3.1-no-content.zip… Download failed.: Destination directory for file streaming does not exist or is not writable. Installation Failed
The solution is to fix the WP_TEMP_DIR in the wp-config.php. The full path looks like this on a DirectAdmin server:
define('WP_TEMP_DIR', '/home/username/domains/example.com/public_html/wp-content/uploads');
If the folder exists, and is writable for your user, WordPress will be able to update itself again.