I'm using this ssh command:
ssh -fnN -L $LOCALPORT:$REMOTEHOST:$REMOTEPORT $HOST
This creates my ssh connection in the background and forwards that port to the remote host through another host. This is great, and allows me to use my service behind a firewall by connecting to a server which can access both networks.
I need to stop this ssh connection when done, and I'm not sure how.
I'm installing Bugzilla on a new Ubuntu server, and ./checksetup.pl finds one more library I need to install.
So it tells me to run this command:
/usr/bin/perl install-module.pl Math::Random::Secure
When I run it, I get the following error:
ERROR: Using install-module.pl requires that you install "make".
Make is installed (apt-get install make) and I know it's in my $PATH (in /usr/bin/) but I still get that error from install-module.pl.
Do I have to do something special to ensure it has the right path or should the path from my shell be used? Is "make" referring to the make I have installed or could it refer to some perl module instead?
Thanks!
I've got two servers running Ubuntu 10.10 and 10.04.
In the 10.04 server, /etc/php5/fpm contains a php5-fpm.conf. In the 10.10 server, /etc/php5/fpm contains a main.conf.
I'm trying to automate my conf updates, so they need to both use the same file, but I can't figure out how to tell php where the conf should be found.
What I'd like to do is rename main.conf to match the other server's php5-fpm.conf, but I don't want to chance breaking php to do it as it would mean down time for my users.
Thanks!
I've been having some intermittent dns problems with a web server, where certain isp's dns servers don't have my hostnames in cache and fail to look them up. At the same time, queries to opendns for those hostnames resolve correctly. It's intermittent, and it always works fine for me, so it's hard to identify the problem when someone reports connectivity problems to my site.
My website is on a server running linux with Plesk. My dns records are configured with plesk (so my server is its own dns master). Domain name is registered with godaddy.
I'm not real knowledgeable about dns, so I don't really know how to begin with troubleshooting. I've started learning to use dig, but while I can read the manpage to learn the syntax, I don't really know what questions to ask.
Since the problem is intermittent I haven't been able to really catalog many symptoms.
Symptoms I have observed:
Certain people repeatedly reported intermittent problems connecting to my website. This was only from certain networks. (Ex: One guy could connect reliably from his office but not his home.)
Sometimes I notice my browser taking a long time looking up the hostname for my site (Firefox shows a message in the status bar at the bottom). For me this is in the ten second range.
ssh connections from anywhere to my server take a long time to connect but then seem to work fine once connected.
So hopefully the folks on serverfault can point me to a good beginner tutorial for understanding dns, and suggest troubleshooting questions to ask next time one of my users reports connectivity problems.
I've been having some intermittent dns problems with a web server, where certain isp's dns servers don't have my hostnames in cache and fail to look them up. At the same time, queries to opendns for those hostnames resolve correctly. It's intermittent, and it always works fine for me, so it's hard to identify the problem when someone reports connectivity problems to my site.
In trying to figure this out, I've been looking at my logs to see if there are any errors I should know about.
I found thousands of the following messages in my logs, from different ip's, but all requesting similar dns records:
May 12 11:42:13 localhost named[26399]: client 94.76.107.2#36141: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:42:13 localhost named[26399]: client 94.76.107.2#29075: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:42:13 localhost named[26399]: client 94.76.107.2#47924: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:42:13 localhost named[26399]: client 94.76.107.2#4727: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:42:14 localhost named[26399]: client 94.76.107.2#16153: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:42:14 localhost named[26399]: client 94.76.107.2#40267: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:43:35 localhost named[26399]: client 82.209.240.241#63507: query (cache) 'burningpianos.com/MX/IN' denied
May 12 11:43:35 localhost named[26399]: client 82.209.240.241#63721: query (cache) 'burningpianos.org/MX/IN' denied
May 12 11:43:36 localhost named[26399]: client 82.209.240.241#3537: query (cache) 'burningpianos.com/MX/IN' denied
I've read of Dan Kaminsky's dns cache poisoning vulnerability (http://unixwiz.net/techtips/iguide-kaminsky-dns-vuln.html), and I'm wondering if these log records are an attempt by some evildoer to attack my dns server.
There are thousands of records in my logs, all requesting "burningpianos", some for com and some for org, most looking for an mx record. There are requests from multiple ip's, but each ip will request hundreds of times per day.
So this smells to me like an attack. What is the defense against this?
I've got a path in my domain which needs apache to prompt for a password. I'll be using the .htaccess file to do this, so I can protect or unprotect by adding or removing the file.
I need a place to store the password file created by htpasswd. There are a few requirements.
The apache process can access it to do the authentication. It is outside the document root for better security. It doesn't require changing permissions of plesk created directories. (Optionally) it exists somewhere where the owner of the domain can write to it.
This question assumes Plesk 8.6 and that normal Plesk conventions are followed.
Is there a recommended location?