depicus

changing the digital world one bit at a time...

Blants (noun) the rants of a blogger

  1. Worry about who has your data….

    October 13, 2014 by The Man

    Ok this time all the info was publicly available anyway but just remember next time you share your data online it could end up on any web site.

    Screen Shot 2014-10-12 at 18.41.17

    Now chiptiming.co.uk have gone out of their way to enable remote debugging despite everything you are ever told about allowing such things. So would you trust your data with a third party who has no idea on security ?


  2. Ubuntu: using logcheck to check your logs

    April 19, 2014 by The Man

    If you run a little web site like mine or a huge great industrial site you always need to keep an eye on it. One of my favourite tools for that is Logcheck

    Put simply Logcheck will check your log files and send you an email for new events, think tail but in email form.

    To install simply fire up Terminal and type

    sudo apt-get install logcheck

    NB this will install Postfix if not already installed

    Now time to configure

    sudo nano /etc/logcheck/logcheck.conf

    There aren’t many settings so time to set them. This is my basic settings file

    INTRO=0
    REPORTLEVEL="server"
    SENDMAILTO="depicus@example.com"
    MAILASATTACH=0
    FQDN=1
    TMP="/tmp"
    

    Note after changing the config file there is no service to restart, the config is read each time it runs as a Cron job.

    Intro just removes the intro from the top of the email, reportlevel is the amount of detail sent and the rest are left as is. The config file is well commented.

    Now time to set which logs to check.

    sudo nano /etc/logcheck/logcheck.logfiles

    And by default it only has two logs, I am going to add the Apache error log as well

    # these files will be checked by logcheck
    # This has been tuned towards a default syslog install
    /var/log/syslog
    /var/log/auth.log
    /var/log/apache2/error.log
    

    That’s it – now wait for the logs to come in.

    More info here


  3. * Starting web server apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName

    April 19, 2013 by The Man

    If you get this error

    * Starting web server apache2
    apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName

    Simply

    sudo sh -c 'echo "ServerName localhost" >> /etc/apache2/conf.d/name' && sudo service apache2 restart

    Update for 13.10 onwards

    sudo nano /etc/apache2/conf-available/servername.conf

    Then add

    ServerName localhost

    to the file and save then

    sudo a2enconf servername

    and finally restart Apache

    sudo service apache2 reload