To export use this command: mysqldump -u USER -p PASSWORD DATABASE > filename.sql To import database from dump file (in this case called filename.sql) use: mysql -u username -p password database_name < filename.sql
After my domain name provider switched to a new system, ssh'ing into new subdomains that I had created and edited in the (new) dns editor became very very slow.
Turns out, that while the old system did not create new ipv6 fields for a new sub domain, the new system does - and adds the address of the local server.
Apparently ssh first tries ipv6 if available. (I discovered this using the verbose option
ssh -vvv). Only after looking up ipv6 and timing out, it tries ipv4.
So, fill in those AAAA records with the proper ipv6 address!
Note: the record with only @ is domain name proper, without
www or another subdomain.
About this error of Apache2:
apr_sockaddr_info_get() failed for server Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Read the documentation about ServerName:
The ServerName directive may appear anywhere within the definition of a server. However, each appearance overrides the previous appearance (within that server).
If no ServerName is specified, the server attempts to deduce the client visible hostname by first asking the operating system for the system hostname, and if that fails, performing a reverse lookup on an IP address present on the system.
If you run the command
hostname, you will possibly see the address Apache is using. If it’s a name that cannot be looked up (check with
host your-hostname) this will likely be the reason Apache complains. If you do have a valid server name, one that can be looked up, use that. (Otherwise you should probably be using localhost.)
To change it without rebooting:
Change it permanently: edit
I wrote this as a reminder that if you can use a valid domain name, there is no need to edit
/etc/hosts (something that is often suggested as a solution).