Ubuntu do-release-upgrade reconnect

Usually I do a release upgrade over the network, using ssh with the command


For some reasons the connection to host I’m upgrading dies.

No panic. Reconnect to the host with ssh. If it does not work, try port 1022.

Then execute the following command:

screen -ls
here is a screen on:
    root/1234.ubuntu-release-upgrade-screen-window   (09/15/2014 07:48:02 AM)    (Detached)
1 Socket in /var/run/screen/S-root.

Now try to reconnect with

screen -d -r root/1234.ubuntu-release-upgrade-screen-window

The connection is established again and you can continue where you were.

How Do I Update The Root Hints Data File for BIND Named Server?

My local nameserver root zone file is outdated. It has no information about IPv6 and recently changed root server IP address.

How do I update my root hints data file on a Linux server?

You can download it:

wget --user=ftp --password=ftp ftp://ftp.rs.internic.net/domain/db.cache -O /etc/bind/db.root

Or you can generate it yourself:

dig +bufsize=1200 +norec NS . @a.root-servers.net | egrep -v ';|^$' | sort > /etc/bind/db.root

After all, refresh the name server:

rndc reload

After all the content of the file looks like this:

.			518400	IN	NS	a.root-servers.net.
.			518400	IN	NS	b.root-servers.net.
.			518400	IN	NS	c.root-servers.net.
.			518400	IN	NS	d.root-servers.net.
.			518400	IN	NS	e.root-servers.net.
.			518400	IN	NS	f.root-servers.net.
.			518400	IN	NS	g.root-servers.net.
.			518400	IN	NS	h.root-servers.net.
.			518400	IN	NS	i.root-servers.net.
.			518400	IN	NS	j.root-servers.net.
.			518400	IN	NS	k.root-servers.net.
.			518400	IN	NS	l.root-servers.net.
.			518400	IN	NS	m.root-servers.net.
a.root-servers.net.	518400	IN	A
a.root-servers.net.	518400	IN	AAAA	2001:503:ba3e::2:30
b.root-servers.net.	518400	IN	A
b.root-servers.net.	518400	IN	AAAA	2001:500:84::b
c.root-servers.net.	518400	IN	A
c.root-servers.net.	518400	IN	AAAA	2001:500:2::c
d.root-servers.net.	518400	IN	A
d.root-servers.net.	518400	IN	AAAA	2001:500:2d::d
e.root-servers.net.	518400	IN	A
f.root-servers.net.	518400	IN	A
f.root-servers.net.	518400	IN	AAAA	2001:500:2f::f
g.root-servers.net.	518400	IN	A
h.root-servers.net.	518400	IN	A
h.root-servers.net.	518400	IN	AAAA	2001:500:1::53
i.root-servers.net.	518400	IN	A
i.root-servers.net.	518400	IN	AAAA	2001:7fe::53
j.root-servers.net.	518400	IN	A
j.root-servers.net.	518400	IN	AAAA	2001:503:c27::2:30
k.root-servers.net.	518400	IN	A
k.root-servers.net.	518400	IN	AAAA	2001:7fd::1
l.root-servers.net.	518400	IN	A
l.root-servers.net.	518400	IN	AAAA	2001:500:3::42
m.root-servers.net.	518400	IN	A
m.root-servers.net.	518400	IN	AAAA	2001:dc3::35

This is a current list of the root name servers.

Cisco err-disable recovery

Did it also happen to you, that a port of a remote switch went to err-disable and you had to drive to that location to reset it?

Or you have users in meeting rooms, who plug in the same network cable in two different switch ports? Nothing happened, spanning-tree portfast bpduguard enable was set.  But the ports went down, and nobody realised it?

You can avoid this problem with the setting

errdisable recovery cause all
errdisable recovery interval 180

With this setting, the switch brings up the port after 180 seconds. If the problem still exists, the port goes into err-disable again. If it is fixed, the port comes up again.

Fortigate CLI Shortcuts

Fortigate offers some helpful features on the command line to position the cursor.

up arrow, CTRL-PPrevious command
 down arrow, CTRL+N Next command
CTRL-A Beginning of line
 CTRL-E End of line
 CTRL-B Back one word
 CTRL-F Forward one word
 CTRL-D Delete current Character
 CTRL-C Abort Command and exit Branch(be careful: CTRL-C is context sensitive. It moves you up to the previous command branch level. If you are already at the top, it logs you out
CTRL-L Clear screen
TABCompletes the current word or iterates through the folioing words
?Possible commands

Delete Applications on a Mac

On a Mac, you basically pull your application, you do not want anymore, into your trash bin. That’s it. But there are always some config files in the ~/Library directory.

To get rid of everything open a terminal and use

mdfind -name "application name"

This gives a list with all files related to the application.

Now delete all the files form the list you got.

sudo rm -rf <line>