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.
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)
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)
: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)
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
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)
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
LEARN ABOUT NETBSD
timedc
TIMEDC(8) BSD System Manager's Manual TIMEDC(8)NAME
timedc -- timed control program
SYNOPSIS
timedc [command [argument ...]]
DESCRIPTION
timedc is used to control the operation of the timed(8) program. It may be used to:
o Measure the differences between machines' clocks,
o Find the location where the master time server is running,
o Enable or disable tracing of messages received by timed(8), and
o Perform various debugging actions.
Without any arguments, timedc will prompt for commands from the standard input. If arguments are supplied, timedc interprets the first argu-
ment as a command and the remaining arguments as parameters to the command. The standard input may be redirected causing timedc to read com-
mands from a file. Commands may be abbreviated; recognized commands are:
? [command ...]
help [command ...]
Print a short description of each command specified in the argument list, or, if no arguments are given, a list of the recognized
commands.
clockdiff host ...
Compute the differences between the clock of the host machine and the clocks of the machines given as arguments.
msite [host ...]
Show the master time server for specified host(s).
trace { on | off }
Enable or disable the tracing of incoming messages to timed(8) in the file /var/log/timed.log.
election host
Asks the daemon on the target host to reset its ``election'' timers and to ensure that a time master has been elected.
quit Exit from timedc.
Other commands may be included for use in testing and debugging timed(8); the help command and the program source may be consulted for
details.
FILES
/var/log/timed.log tracing file for timed
/var/log/timed.masterlog log file for master timed
DIAGNOSTICS
?Ambiguous command
abbreviation matches more than one command
?Invalid command
no match found
SEE ALSO date(1), adjtime(2), icmp(4), timed(8)
R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD.
HISTORY
The timedc command appeared in 4.3BSD.
BSD February 2, 2007 BSD
02-26-2015
