Troubleshooting (Ubuntu) - Revision history

Sstrutt: Removed GoogleAdLinkUnitBanner

2016-09-26T13:34:19Z

Removed GoogleAdLinkUnitBanner

← Older revision		Revision as of 13:34, 26 September 2016
Line 114:		Line 114:
	See http://ubuntuforums.org/showthread.php?t=1660916 for further info		See http://ubuntuforums.org/showthread.php?t=1660916 for further info


	~~{{GoogleAdLinkUnitBanner}}~~

	[[Category:Ubuntu]]		[[Category:Ubuntu]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]
	[[Category:Bash]]		[[Category:Bash]]

Sstrutt: /* Packages */ Added "Add EOL Repository"

2014-03-21T08:49:35Z

Packages: Added "Add EOL Repository"

@@ Line 72: / Line 72: @@
 * '''The following packages have been kept back'''
 ** Package manager can hold back updates because they will cause conflicts, or sometimes because they're major kernel updates.  Running <code>aptitude safe-upgrade</code> normally seems to force kernel updates through.
 == Reboot Required? ==

Sstrutt: /* No NIC */ Minor update

2013-12-12T13:40:51Z

No NIC: Minor update

← Older revision		Revision as of 13:40, 12 December 2013
Line 8:		Line 8:
	# Use <code> dmesg \| grep -i eth </code> to ascertain what's been detected at boot time		# Use <code> dmesg \| grep -i eth </code> to ascertain what's been detected at boot time
	# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file		# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file
	# Alternatively, force the ''new'' NIC to be <~~ocde~~>eth0</code> by editing the <code>/etc/udev/rules.d/70-persistent-net.rules</code> file		# Alternatively, force the ''new'' NIC to be <code>eth0</code> by editing the <code>/etc/udev/rules.d/70-persistent-net.rules</code> file
			#* You'll need to reboot the server for changes to take effect

	== File System ==		== File System ==

Sstrutt: /* No NIC */ Added alternate method

2013-10-29T08:56:29Z

No NIC: Added alternate method

← Older revision		Revision as of 08:56, 29 October 2013
Line 8:		Line 8:
	# Use <code> dmesg \| grep -i eth </code> to ascertain what's been detected at boot time		# Use <code> dmesg \| grep -i eth </code> to ascertain what's been detected at boot time
	# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file		# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file
			# Alternatively, force the ''new'' NIC to be <ocde>eth0</code> by editing the <code>/etc/udev/rules.d/70-persistent-net.rules</code> file

	== File System ==		== File System ==

Sstrutt: /* File System */ Added "Recover Deleted Files"

2013-02-06T14:23:49Z

File System: Added "Recover Deleted Files"

@@ Line 43: / Line 43: @@
 # The arrays should now be being sync'ed, check progress by monitoring <code>/proc/mdstat</code>
 #* <code> more /proc/mdstat </code>
 == SSH ==

Sstrutt: Corrected link error

2013-02-06T14:20:19Z

Corrected link error

← Older revision		Revision as of 14:20, 6 February 2013
Line 1:		Line 1:
	'''For performance problems related load, see [[High System Load]]'''		'''For performance problems related load, see [[High_System_Load_(Ubuntu)\|High System Load]]'''

	== Network ==		== Network ==

Sstrutt: Moved "High System Load" to dedicated page and added "Firewall"

2012-10-11T21:08:10Z

Moved "High System Load" to dedicated page and added "Firewall"

Show changes

Sstrutt: Changed footer Ad to LinkUnit

2012-09-05T11:11:49Z

Changed footer Ad to LinkUnit

← Older revision		Revision as of 11:11, 5 September 2012
Line 427:		Line 427:
	If when using the above tools you're presented with disk/devices names of <code>dm-0</code>, <code>dm-1</code>, etc., which won't mean much. These are LVM logical devices, to understand what they map to use		If when using the above tools you're presented with disk/devices names of <code>dm-0</code>, <code>dm-1</code>, etc., which won't mean much. These are LVM logical devices, to understand what they map to use
	<pre>lvdisplay\|awk '/LV Name/{n=$3} /Block device/{d=$3; sub(".*:","dm-",d); print d,n;}'</pre>		<pre>lvdisplay\|awk '/LV Name/{n=$3} /Block device/{d=$3; sub(".*:","dm-",d); print d,n;}'</pre>

	~~{{GoogleAdBanner}}~~

	== Network ==		== Network ==
Line 491:		Line 489:
	To see which packages caused this to be set, inspect the contents of...		To see which packages caused this to be set, inspect the contents of...
	/var/run/reboot-required.pkgs		/var/run/reboot-required.pkgs

			{{GoogleAdLinkUnitBanner}}

	[[Category:Ubuntu]]		[[Category:Ubuntu]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]
	[[Category:Bash]]		[[Category:Bash]]

Sstrutt: /* High System Load */ Further supporting info for utils

2012-07-30T13:01:39Z

High System Load: Further supporting info for utils

Show changes

Sstrutt: /* High System Load */ Added other tools

2012-07-16T15:28:02Z

High System Load: Added other tools

← Older revision		Revision as of 15:28, 16 July 2012
Line 11:		Line 11:
	So in the above, as of 14:28:49 hrs the server has been up for 9 days 22 hours odd, has 1 user logged in, and the system load averages for the past 1, 5, and 15 minutes are shown.		So in the above, as of 14:28:49 hrs the server has been up for 9 days 22 hours odd, has 1 user logged in, and the system load averages for the past 1, 5, and 15 minutes are shown.

	The load average for a given period indicates how many processes were running or in a uninterruptable (waiting for IO) state. What's bad depends on your system, for a single CPU system a load average greater than 1 could be considered bad as there are more processes running than CPU's to service them.		The load average for a given period indicates how many processes were running or in a uninterruptable (waiting for IO) state. What's bad depends on your system, for a single CPU system a load average greater than 1 could be considered bad as there are more processes running than CPU's to service them. Though if you expect peaks in load, then a high load over the last minute might not concern, whereas over 15mins it would.

	=== <code>top</code> ===		=== <code>top</code> ===
	The <code>top</code> command allows some basic insight into the system's performance, and is akin to the Task Manager in Windows.		The <code>top</code> command allows some basic insight into the system's performance, and is akin to the Task Manager in Windows. It probably won't provide the answer as to what the problem is, but it will probably allow you to focus in on the process(es) that are causing grief.

	<pre>		<pre>
Line 120:		Line 120:


	=== Identify Process Causing High System Load ===		==== Identify Process Causing Occassional High System Load ====
	If the high load is constant, just fire up <code>top</code> and see if there is a specific process to blame, or if your stuck waiting for disk or network IO.		If the high load is constant, just fire up <code>top</code> and see if there is a specific process to blame, or if your stuck waiting for disk or network IO.

Line 145:		Line 145:
	<pre>crontab -e		<pre>crontab -e
	1 * * * * /bin/bash /home/user/load_log</pre>		1 * * * * /bin/bash /home/user/load_log</pre>

			=== Other Tools ===

			* <code> vmstat </code>
			** http://www.linuxcommand.org/man_pages/vmstat8.html
			** Principally used for reporting on virtual memory statistics
			* <code> mpstat </code>
			** http://www.linuxcommand.org/man_pages/mpstat1.html
			** Reports basic processor stats
			* <code> iostat </code>
			** http://sebastien.godard.pagesperso-orange.fr/man_iostat.html
			** Provides disk IO statistics - part of <code>sysstat</code> package

			If when using the above tools you're presented with disk/devices names of <code>dm-0</code>, <code>dm-1</code>, etc., which won't mean much. These are LVM logical devices, to understand what they map to use
			<pre>lvdisplay\|awk '/LV Name/{n=$3} /Block device/{d=$3; sub(".*:","dm-",d); print d,n;}'</pre>

	== Network ==		== Network ==