Show Password


Emergency UNIX and Linux Support

Please post your urgent questions here for highest visibility. Posting a new thread to this forum requires Bits. We monitor this forum to help people with emergencies, but we do not guarantee response time or answers. This forum is "best effort" only. Members who reply to posts here receive a bonus of 1000 Bits per reply.

Network related issues

👤 Login to reply

Thread Tools Search this Thread Display Modes
Old 09-05-2017
ggayathri ggayathri is offline
Registered User
Join Date: Oct 2008
Last Activity: 23 March 2018, 9:37 AM EDT
Posts: 86
Thanks: 1
Thanked 0 Times in 0 Posts
Network related issues

Oflate we are finding a few servers experiencing severe slowness. What would be the commands that I need to try to postmortem the situation?
Sponsored Links
Old 09-05-2017
jim mcnamara jim mcnamara is offline Forum Staff  
Join Date: Feb 2004
Last Activity: 15 July 2018, 10:19 PM EDT
Location: NM
Posts: 11,435
Thanks: 636
Thanked 1,174 Times in 1,081 Posts
What OS? Your other post mentions AIX. Getting data from the past is really difficult unless you had already set up monitoring or auditing.

If you have detailed logs from applications, sometimes you can infer that application A has been taking longer and longer times to complete.

Many kinds of problems are sporadic or are hard to reproduce. These can only be found by creating monitors before the fact.

Please give us more system details: specific OS, main application(s) for the system.
Example: AIX 7.3, sybase server on SAN.
Sponsored Links
Old 09-06-2017
rbatte1 rbatte1 is offline Forum Staff  
Root armed
Join Date: Jun 2007
Last Activity: 13 July 2018, 1:03 PM EDT
Location: Lancashire, UK
Posts: 3,582
Thanks: 1,590
Thanked 706 Times in 633 Posts
Some wild guesses:-
  • Loss of access to DNS server (slow reverse IP lookup for auditing, so slow login or application)
  • Database locks - hugely dependant on your application
  • Missing database index causing full table scans
  • Poor data queries, e.g. get all records from the database then check each in turn on criteria rather than building the condition into the query
  • Database logs files filling and flushing too slowly
  • Exhausting real memory causing paging (potentially DB consuming too much real memory)
  • Network speed conflict, e.g. if NIC is 10M-half and switch is 100M-full, it will work, but any file transfer will cripple it with lots of dropped packets.
  • IO issues, especially with NFS or an HA cluster if you fail over
  • Scheduled work, e.g. current stock summary
  • Ad-hoc jobs, e.g. current stock summary
  • Resources stealing by another LPAR if the definitions allow it
  • Large write volume to direct disk (e.g. local) rather than cached disk (RAID or SAN etc.)
  • High NFS contention especially with other seemingly unrelated servers

You can see it is a very very VERY wide spread of options so far - and the list is a long way from being exhaustive. You need to be a fair bit more explicit about what you have (including OS) what goes slow, what's happening at the time, what dependencies you have with other servers.

Old 09-06-2017
otheus's Unix or Linux Image
otheus otheus is offline Forum Advisor  
Join Date: Feb 2007
Last Activity: 6 September 2017, 5:43 AM EDT
Location: Innsbruck, Austria
Posts: 2,157
Thanks: 12
Thanked 51 Times in 48 Posts
Most *NIX systems (AIX, Linux, Solaris, BSD) have some kind of system and accounting records. You can run


to see if it is properly deployed on your system. If you run it and get loads of output, you may be in luck. To use it, refer to the man pages. Typically you want to check options for memory and swap usage, CPU usage, and I/O activity.

If it's not installed, consider deploying this first before installing some complex monitoring software; it's a very standard unix utility that has been around for ages, but the implementation and features vary from platform to platform. For Linux install the sysstat package.

On most systems, sar's data is collected through another program which is run as a cronjob. On a typical RedHat/CentOS Linux system, you will find /etc/cron.d/sysstat to contain:

* * * * * root /usr/lib64/sa/sa1 -S XALL 1 1

which I immediately change to

*/5 * * * * root /usr/lib64/sa/sa1 -L -S XALL 10 30

The original form collects data once per minute, which is often simply not enough granularity to get a feel for rapid changes to the system, the kind that cause instability and crashes. Also, if memory becomes extremely sparse, cron might not be able to spawn the job every minute.

My form, however, spawns a new job every 5 minutes. It writes 30 records, one every 10 seconds. The corresponding reports contain enough detail to know very precisely when the problem started. You will need an additional 1.5 GB of disk space on /var/log if you do this.

If you want graphs and pretty output, you may be able to export the data into graphing engines or spreadsheets. Linux's sar has such a program (sadf), and other related projects can slurp of the data and present graphs.
Sponsored Links
👤 Login to reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Network related script kannansoft1985 Shell Programming and Scripting 1 08-28-2014 12:25 AM
Swap space related issues, how to recognise the newly attached disk vamshigvk475 Solaris 2 01-03-2013 11:56 PM
Network related errors samsungsamsung AIX 2 11-22-2010 06:07 PM
Fork syscall and related issues MrUser Programming 2 02-19-2010 07:59 AM

All times are GMT -4. The time now is 01:01 AM.

Unix & Linux Forums Content Copyrightę1993-2018. All Rights Reserved.