Use both the ServerName and ServerAlias directives in your virtualhost definition. You would do something like:
See Apache Docs – ServerAlias Directive.
Linux command-line ftp defaults to using active-mode FTP. Try switching to passive mode with the pass command:
me@ip-10-a-b-c:~$ ftp ftp.drupal.org
Name (ftp.drupal.org:me): anonymous
331 Please specify the password.
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
500 Illegal PORT command.
"In use" as in with an active connection, or that programs are listening on? Or both?
Run sudo netstat -lp in your terminal; this will tell you what ports are open to receive connections, and what programs are listening on them. Try sudo netstat -p for the same thing, plus currently-active connections.
This is coming from the MOTD (Message Of The Day). The MOTD is pieced together from the commands in /etc/update-motd.d. The specific message comes from running /etc/update-motd.d/90-updates-available.
I have seen this happen on systems where after running sudo apt-get update and packages are kept back
The following packages have been kept back:
First the lecture:
Rule Number Zero: If you do not understand what something does, DO NOT TOUCH IT
Deleting files "to save space" with no concept of what you are doing will anger the operating system gods, resulting problems similar to what you are now experiencing (Things break. Fixing them is often non-trivial).
Now the sympathetic assistance:
Add the other names with ServerAlias.
You can use any of those 2 formats or a mixture:
ServerAlias aaa.example.com bbb.example.com ccc.example.com
The directive is valid only in VirtualHost section.
If you want to use the GUI, try clicking Places -> Connect to Server.... For Service Type choose Windows share, and fill out the fields like so:
Then download your file from the window. If you want to use a command-line interface, smbclient uses a FTP-like interface (get, put, etc.):
~$ smbclient //192.168.1.66/...
When you specify host=localhost, mysql client will try to login to mysql server using unix named pipe which requires a .sock file.
This can be bypassed by specifying host=127.0.0.1. This will make mysql client use TCP to connect to the server.
Taken from MySQL's documentation:
mysql --host=127.0.0.1 --port=3306 --user=your_uname --password=your_pass
I've ended up here more than once so I thought I'd provide an updated answer based on my own experience after using the answers here. Thanks especially to @danorton and @orj for their answers.
This script has been tested on Upstart 1.5 running on Ubuntu 12.04 with Nginx 1.0.11 and Passenger 3.0.11. If you're not using Passenger you may need to play around ...
A socket file doesnt actually contain data, it transports it.. It is a special, unusual type of file created with special system calls/commands. It is not an ordinary file.
It is like a pipe the server and the clients can use to connect and exchange requests and data. Also, it is only used locally. Its significance is merely as an agreed rendezvous ...
Copy this code into a new file /etc/fail2ban/filter.d/sshd-root.conf:
# Read common prefixes. If any customizations available -- read them from
before = common.conf
_daemon = sshd
failregex = ^%(__prefix_line)sFailed (?:password|publickey) for root from <HOST>(?: port \d*)?(?: ssh\d*)?$
To only show folders over 1GB in size:
du -h --threshold=1G
You may also want to order by size, to easily find the biggest ones.
du -h --threshold=1G | sort -h
(Works on: Ubuntu/Mint.
Does not work on: OSX or RHEL 6.2)
Another one of these "fine" Ubuntu-bugs... Check Ubuntu Bug #634387: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/634387
I deleted the files "/etc/motd.tail" and "/etc/motd.tail.old" and did a logout / login to re-genereate a propper /etc/motd.
A socket is a special pseudo-file used for data transmission by reading and writing, not data storage.
The socket file is created when the service is started and removed when the service is terminated. The location of the file is defined in /etc/my.cnf like so:
A better alternative is to install CNTLM, which is an NTLM proxy that presents itself as an ordinary web proxy.
It's quite easy to install from .deb (trivial dependencies adduser and libc6 which should be on every system ever) and configure. Once you have it installed, you just tell apt-get to use proxy localhost:3128.
This solution has two advantages:
Confirm that mysqld.sock doesn't exist
sudo find / -type s | grep mysqld.sock
Check that your /etc/mysql/my.cnf file agrees that the file should be /var/run/mysqld
socket = /var/run/mysqld/mysqld.sock
and if it does then
sudo mkdir -p /var/run/mysqld
sudo chown mysql /var/run/mysqld/
sudo service mysql restart
but I suspect your problem lies ...
Postfix can run in a chroot (by default in /var/spool/postfix) or not. If it is, it will try to open /var/spool/postfix/var/run/saslauthd/mux for sasl authentication. If it's not, it will try to open /var/run/saslauthd/mux
It seems that, for some reason, your postfix instance was running in a chroot, and it's not anymore. It's odd, but that's what I guess ...
It seems there was a bug in the 9.1 packages, but it should be fixed.
As indicated in the linked thread the issue could be resolved by running :
update-alternatives --remove postmaster.1.gz /usr/share/postgresql/9.1/man/man1/postmaster.1.gz
and then reinstalling postgresql-9.1:
apt-get install -f
apt-get install --reinstall postgresql-9.1
The ldif for ldapmodify has a different syntax than a regular ldif.
For example: if you want to add the 'foo' entry with value 'bar' you should write your ldif like this:
This ldif will add the attribute foo with value bar, ...
First of all, init scripts are supposed to be run
when you are not logged in as root( when logged-in user is sudo enabled)
Secondly, when you run sudo /etc/init.d/nginx start ==> it fires the master nginx process as root and worker processes as the user you specified in your nginx.conf user directive(eg. www-data)
Can you confirm if ...
That's just cron running the cronjobs. It opens (and then closes) a PAM session for the appropriate user when it executes commands. Based on the timestamps, you have a cronjob which executes every minute.
The column displays CPU time spent per process rather than real time. I can't see if this is specified in the man page but here is some copy-pastage from about.com:
Total CPU time the task has used since it started. If cumulative mode is on, this also includes the CPU time used by the process's children which have died. You can set cumulative mode ...
Upstart does not support symlinks because they might point to a file on a partition that is not loaded at boot time.
I have gotten around this in my own project by putting the conf files in /etc/init/myscripts and then binding that to a directory in my repository. mount --bind /etc/init/myscripts ~/code/repo/initscripts.
Add this to /etc/fstab and the ...
After some general confusion about permissions the OP realized that the problem wasn't that he didn't have permissions and paths rights but that AppArmor was preventing MySQL from reading and writing to the new location.
This is his solution:
First stop MySQL so nothing weird happens while you're fiddling:
$ sudo stop mysql
Then move all the database ...
If you have SSH opened to the Internet you WILL see hack attempts where scripties will try to crack that password.
Possible mitigation steps:
Do not allow root login via SSH (su after login if needed)
Have a VERY strong password (think passphrase - 10 or more characters)
Use key authentication for SSH and turn off password auth
Install fail2ban to block ...
How did you generate those LDIF files? structuralObjectClass is one of the internal values in OpenLDAP and user - even administrator - cannot normally modify those.
Either remove those structuralObjectClass lines from your LDIF or import the entries back with slapadd (I bet you generated the LDIF files with slapcat).
In my case, running mysqld_safe created a new mysqld.sock file.
$ cd /etc/init.d/
You'll probably won't get prompt back, but if you restart your session, a mysqld.sock file will be somewhere. Find it with
$ sudo find / -type s | grep mysqld.sock
If you want to know on a linux system if your mysqld is really reading this particular file I would recommend strace:
strace -e trace=open mysqld
This will show you all the files that get opened by the mysqld process during startup. In our case:
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib64/libpthread.so.0", O_RDONLY) = 3