Christian Riesen » System Administration http://christianriesen.com Life and work in the information and communication age Mon, 12 Jul 2010 10:39:53 +0000 en hourly 1 http://wordpress.org/?v=3.0 Debian Killall Command http://christianriesen.com/2010/04/debian-killall-command/ http://christianriesen.com/2010/04/debian-killall-command/#comments Thu, 08 Apr 2010 10:39:35 +0000 Christian Riesen http://christianriesen.com/?p=180 After running into this yet again today, here is how you get the killall command on a modern Debian distribution:

aptitude install psmisc

Works perfectly fine on lenny. Hopefully I never have to look this up again.

Feel free to Flattr this post at flattr.com, if you like it.

flattr this!

]]> http://christianriesen.com/2010/04/debian-killall-command/feed/ 0 GoDaddy SSL Certificate and Apache http://christianriesen.com/2009/12/godaddy-ssl-certificate-and-apache/ http://christianriesen.com/2009/12/godaddy-ssl-certificate-and-apache/#comments Wed, 02 Dec 2009 08:51:32 +0000 Christian Riesen http://christianriesen.com/?p=99 The company I work for ran into a small problem with an SSL certificate from GoDaddy. For some reason it worked flawlessly on most machines but a fresh install of Firefox and most smart phones didn’t like it at all. Asking the GoDaddy support was a rather long waste of time. They actually told me it was installed correctly which sent me off track immediately.

After running around and already considering going with another (much more expensive) certificate, I stumbled across DigiCert’s SSL Certificate Tester. Entering the hostname for the certificate checked it and voila, I found something wrong. Between the server certificate and the intermediate certificate there was a break in the chain. Why this worked still on my browser (without installing the certificate) and many others, but not on a fresh install is still not exactly clear, but that clearly was a problem. Without a proper chain, the browser would show nasty messages about this page not being secure and so on. Some of the customers are banks so they were not very happy about that message, considering this was a new feature for the page that should increase security not decrease it.

So I went back to the GoDaddy page and looked everything over again. The installation instructions lead to how to install them on apache. Now considering everything else went right, there is one specific point where it failed. The instructions tell you to get the intermediate certificate bundle from their repository and then point to that file on your server using the SSLCertificateChainFile directive. Browsing to that page shows you a lot of files, and if you have no other pointers it might get slightly confusing.

For apache, what you need is the file called gd_bundle.crt to have the correct one. It’s in the first section of the page called “Godaddy Certificate Chain”. Save it on your server, point the SSLCertificateChainFile directive to it and you are all set. If you use a different file, say for example one of the lower ones, you get these chain breaking effects.

A flaw in the directions in my opinion, but hopefully this post will remedy some of it for people running into the same troubles.

Feel free to Flattr this post at flattr.com, if you like it.

flattr this!

]]> http://christianriesen.com/2009/12/godaddy-ssl-certificate-and-apache/feed/ 0 wget in php http://christianriesen.com/2009/10/wget-in-php/ http://christianriesen.com/2009/10/wget-in-php/#comments Sun, 25 Oct 2009 13:12:16 +0000 Christian Riesen http://christianriesen.com/?p=92 Ok, this is far from what wget is capable of, but most people do only need one function for wget. Enter url, get content. Especially during the setup phase this is often needed and sometimes wget is not available or libraries are missing. For those that have a working php installation but no working wget, this little script does exactly that, download a file and save it locally. This little helper has done valuable services for me now a few times, so here it is for anyone to use.

<?php
// wget substitute
if ($argc != 2) {
?>
This works a bit like wget. Just run it with the url as argumnet
<?php
    exit;
}

$url = $argv[1];
$filename = basename($url);

file_put_contents($filename,file_get_contents($url));

echo PHP_EOL. 'Written file ' . $filename . PHP_EOL;

Usage is rather simple now:
php wget.php URL

Feel free to Flattr this post at flattr.com, if you like it.

flattr this!

]]> http://christianriesen.com/2009/10/wget-in-php/feed/ 1 (128)Network is unreachable: connect to listener on [::]:80 http://christianriesen.com/2009/10/128network-is-unreachable-connect-to-listener-on-80/ http://christianriesen.com/2009/10/128network-is-unreachable-connect-to-listener-on-80/#comments Thu, 15 Oct 2009 11:24:53 +0000 Christian Riesen http://christianriesen.com/?p=87 Apache has been giving me some interesting errors lately. In debugging I have come across a bunch of these in the otherwise largely ignored errors log.

(128)Network is unreachable: connect to listener on [::]:80
(128)Network is unreachable: connect to listener on [::]:443

So what does it mean? No idea. But I found the solution in the end to be to change the listen config.

Before: Listen 80
After: Listen 0.0.0.0:80

Same for 443 and you wont see those messages ever again. Oh and this happened under Solaris 10 by the way, never saw this on any other machine.

Feel free to Flattr this post at flattr.com, if you like it.

flattr this!

]]> http://christianriesen.com/2009/10/128network-is-unreachable-connect-to-listener-on-80/feed/ 0