fredag den 2. juni 2017

Mouse sensitivity too slow, or low, after upgrade to Ubuntu 17.04

I was unable to change the mouse sensitivity after upgrading to Ubuntu 17.04. It was very low/slow after upgrade.

Changing it in the default mouse app didn't do any difference. And xinput didn't work.

I ended up modifying "/sys/devices/platform/i8042/serio1/sensitivity" and changing the value to 220. It worked immediately.

To make the change work after every reboot, edit '/etc/rc.local' and add this line before the command 'exit 0':

echo -n 220 > /sys/devices/platform/i8042/serio1/sensitivity

My '/etc/rc.local' looks like this:

#!/bin/sh -e
# rc.local
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
# In order to enable or disable this script just change the execution
# bits.
# By default this script does nothing.

echo -n 220 > /sys/devices/platform/i8042/serio1/sensitivity

exit 0

tirsdag den 21. marts 2017

DNS stopped working after Ubuntu 14.04 upgrade to Ubuntu 16.04

1) I resolved it by removing file /etc/resolv.conf:
sudo rm /etc/resolv.conf

2) and creating a new file:
sudo nano /etc/resolv.conf

3) and typing my name server in the file:

Check_MK (OMD) fails showing pnp4nagios graphs after Ubuntu upgrade

When upgrading Ubuntu from version 14.04 to version 16.04 php-cgi version 5 is replaced by version 7. This will cause Check_MK to fail when trying to display pnp4nagios graphs.

1) If you are running OMD, then edit file:
/omd/sites/[YOUR SITE NAME HERE]/etc/apache/php-wrapper

2) and change the path to php-cgi version 7:

# Replace with the path to your FastCGI-enabled PHP executable
#exec /usr/bin/php5-cgi \
exec /usr/bin/php-cgi7.0 \
    -d session.save_handler=files \

3) Then stop and start the OMD site.

mandag den 13. februar 2017

Graylog indices page fails with error 'Reason: Could not get indices. We expected HTTP 200, but got a HTTP -1.'

When many indices are used in Graylog you can experience an error stating that a HTTP -1 response was received.

This error can be caused by a timeout when collecting information about indices.

I changed the timeout to 30 seconds and restarted the graylog web service. Then waited a few minutes and the error was gone:

  • Change timeout settings in /etc/graylog/web/web.conf:
# Global timeout for communication with Graylog server nodes; default: 5s
  • Restart web service:
service graylog-web restart

onsdag den 4. januar 2017

Enable OpenELEC SSH login with keys, and without password, disable local SSH password

1) Connect to OpenELEC using ordinary SSH with user 'root' and password 'openelec'

2) Change directory to .ssh/:

cd .ssh/

3) Generate a pair of ssh keys:

ssh-keygen -t rsa

Accept all default settings by pressing [ENTER].

If you are asked to to overwrite id_rsa press 'y' and [ENTER].

4) Copy the content of the public key ('') into 'authorized_keys':

cat >> authorized_keys

5) Copy 'id_rsa' to the device that you want to log into OpenELEC from, e.g. your mobile phone.

6) Setup the connection on your device using the private key ('id_rsa'). You still need to use the username 'root'. You can rename this file and give it a more useful name. Make sure that you are able to log in without using the password!

7) To disable the local password on OpenELEC/KODI, open settings in KODI and select "Services" on the left hand side. Here you can disable SSH password.

fredag den 26. august 2016

Test connection to site on port 80 and 443 with PowerShell, if port 443 fails, then do trace route

Test a connection to a site on port 80 and 443 every 15 seconds for 99999 times. If connection to port 443 fails the run a trace route to find the problem. A log is written to the desktop (currently logged on user's desktop) which prints date and time for very check made.