Sponsored Content
Full Discussion: Response Times
Operating Systems Linux Red Hat Response Times Post 302936630 by rsheikh01 on Thursday 26th of February 2015 08:28:51 PM
Old 02-26-2015
Response Times

Hello all. Let me qualify my question by saying that I am struggling with how to ask the question I am semi green but have no issue reading up if pointed in the right direction. Please be gentle!

A RHEL server 6.2. Hosts a statistical application that has some web apps and batch programming interface.

Problem:
Lately we moved offices.
1) Now logging in via PuTTy via ssh was taking long so a poweruser set useDNS No that speed up login
2) Issue: Once we start our application (web app) login speed is fine but any action that requires a response such as navigating, open file, it hour clocks and either ends in error, or in some cases after 5 minutes renders back the requested item.
- RAM is 65 GB, 45GB is free (from Top)
- Load at most 1.35 usually around .5 avg.
- Dedicated to host one application
- At most 2-3 concurrent sessions expected but see only 1
- tracert was 1ms
- Ping replies w/o data loss
- Putty session -ssh- connects in seconds
I have run some commands and their output are listed below
Code:
[rsas@lazer ~]$ host -t a lazer.aii-3.com
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host -t ns lazer.aii-3.com
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host -t mx lazer.aii-3.com
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host -a lazer.aii-3.com
Trying "lazer.aii-3.com"
;; connection timed out; trying next origin
Trying "lazer.aii-3.com.aii-3.com"
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host -6 lazer.aii-3.com
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host 10.20.18.140
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ host -v -t a lazer.aii-3.com
Trying "lazer.aii-3.com"
;; connection timed out; trying next origin
Trying "lazer.aii-3.com.aii-3.com"
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ dig +trace lazer.aii-3.com

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4 <<>> +trace lazer.aii-3.com
;; global options: +cmd
;; connection timed out; no servers could be reached
[rsas@lazer ~]$ dig +noall +answer lazer.aii-3.com
;; connection timed out; no servers could be reached

I am not sure how to proceed. Any guidance/insight is deeply appreciated.Smilie
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

response of a for loop?!

Dear guys, I don't know the response of a for loop in this situation: suppose that file1 is an empty file. and i make a for loop as : for i in `cat file1` What will be the response of the for loop: 1- will an error message apear 2- or the for loop simply will not run,and it will escape... (2 Replies)
Discussion started by: marwan
2 Replies

2. AIX

how would you know your server was rebooted 3 times or 5 times

Is there such location or command to know how many times did you reboot your server in that particular day?in AIX. (3 Replies)
Discussion started by: kenshinhimura
3 Replies

3. IP Networking

Traceroute response

I have 20 servers I installed an application to that is returning message " wrong dispatcher or port " when starting agents. They all have the same dispatcher ip and going through the same port number. After verifying there are no application issues, we figured it was firewall related. The Firewall... (1 Reply)
Discussion started by: HFJ
1 Replies

4. AIX

Ping response

:confused:Hi, In linux if ping to a system from a linux server it shows ping time=0.120ms how we can achive this in aix. i need this for a latency check. Thanks in advance. (5 Replies)
Discussion started by: vjm
5 Replies

5. Programming

Problem with implementing the times() function in C (struct tms times return zero/negative values)

Hello, i'm trying to implement the times() function and i'm programming in C. I'm using the "struct tms" structure which consists of the fields: The tms_utime structure member is the CPU time charged for the execution of user instructions of the calling process. The tms_stime structure... (1 Reply)
Discussion started by: g_p
1 Replies

6. Post Here to Contact Site Administrators and Moderators

UNIX.com response times

Friends, Admins, Countrymen, for a few days now, this site is incredibly dragging its feet again - 40 plus sec to open e.g. "New Topics" or "Home", 24 + for "subscribed Threads". For a comparison: subsecond response for wikipedia, Englisch ⇔ Deutsch Worterbuch - leo.org: Startseite, or similar.... (18 Replies)
Discussion started by: RudiC
18 Replies

7. Shell Programming and Scripting

Choosing VPN server based on server response times

Hello all, I am using the VPN provider Private Internet Access. I am using the Raspberry Pi 4 with 4GB of RAM, performance on this upgraded board is great. Anyways I am connecting to its service using systemd's openvpn-client @ US_New_York_City.service I wonder if I can create a... (5 Replies)
Discussion started by: haloslayer255
5 Replies
TIMED(8)						    BSD System Manager's Manual 						  TIMED(8)

NAME
timed -- time server daemon SYNOPSIS
timed [-dtM] [-i network | -n network] [-F host ...] DESCRIPTION
The timed utility is a time server daemon which is normally invoked at boot time from the rc.conf(5) file. It synchronizes the host's time with the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences using the ICMP timestamp request message. The following options are available: -d Enable debugging mode; do not detach from the terminal. -i network Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed. This option may be specified multiple times to add more than one network to the list. -F host ... - Create a list of trusted hosts. - Can take one or more parameters. - timed will only accept trusted hosts as masters. If it finds an untrusted host claiming to be master, timed will suppress incom- ing messages from that host and call for a new election. - Use real host names (resolvable by RDNS) not aliases (eg in named(8) parlance: use A names, not C names). - Use full names eg time1.domain.com not time1. - -F automatically includes the functionality of -M (so -M does not need to asserted). - If -F is not specified, all hosts on connected networks are treated as trustworthy. -M Allow this host to become a timed master if necessary. -n network Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed. This option may be specified multiple times to add more than one network to the list. -t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running with the timedc(8) utility. The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei- ther flag is specified, timed will listen on all connected networks. A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust- worthy. The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per- form the needed corrections on the host's clock. It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F flags. At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags, it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that network. One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio receiver and -F hostname to tell its timed to trust only itself. Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print- ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. A time daemon can correct the result. Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on more than one network and eventually chose to become a slave on the other network. WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock. The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate. There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol- low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log. FILES
/var/log/timed.log tracing file for timed /var/log/timed.masterlog log file for master timed SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), networks(5), ntpd(8), timedc(8) R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD. HISTORY
The timed utility appeared in 4.3BSD. BSD
February 11, 2008 BSD
All times are GMT -4. The time now is 01:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy