Sponsored Content
Full Discussion: Messages in /var/adm
Top Forums UNIX for Dummies Questions & Answers Messages in /var/adm Post 7444 by loadc on Wednesday 26th of September 2001 12:16:41 PM
Old 09-26-2001
Time adj

Hello-

See if you have a time daemon of some sort running, this'll be xntpd or timed. If so, it's on by defautl and is trying to correct your system time by ticks and is not config'd to talk to a timeserver of any use to you. It failed to do the tick adj., not a hardware filure from what I can tell, you just may not care to sync to a timeserver and keep your own time, if so, turn off the daemon and set your date.
 

10 More Discussions You Might Find Interesting

1. Solaris

/var/adm/messages- Help

Solaris 8/ sun 420R Checked /var/adm/messages file and got the following message: Dec 4 16:40:05 serverXYZ ConfigProvider: get_pkg_instdate: getdate failed for the standard C locale (7) Does anyone know what this means? Looked up getdate but do not understand.... Thanks. (1 Reply)
Discussion started by: finster
1 Replies

2. Solaris

/var/adm/messages

I'm running a Solaris 9 box with Oracle databases on it. I'm getting the following messages in my /var/adm/messages log "Jun 24 12:30:32 sundb01 bootpd: IP address not found: xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is DHCP IP addresses of Windows 2000 workstations in the organisation. ... (2 Replies)
Discussion started by: soliberus
2 Replies

3. UNIX for Dummies Questions & Answers

/var/adm/messages

Hi, No log entry is found in messages files. The file size is 0. We are using Solaris 9. Anyone knows what could be wrong. (3 Replies)
Discussion started by: FrankC
3 Replies

4. Solaris

/var/adm/messages

Hello Friends, I am geting the folowing error in /var/adm/message is it disl related problem? if yes.. how to check all the disk are perfect or not? Sep 15 06:01:12 scsi: WARNING: /pci@1f,700000/scsi@2/sd@2,0 (sd7): Sep 15 06:01:12 Error for Command: write(10) Error Level:... (5 Replies)
Discussion started by: bullz26
5 Replies

5. Solaris

Info req: /var/adm/messages - Kern.warning - different ID messages

Hi all, where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)? Thanks in advance Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies

6. Solaris

/var/adm/messages

Check message file and result posted below. Can anyone tell me what this is a sign of, what does it mean? server1% more messages.0 Dec 02 09:35:06 server1 bsd-gw: Inval id protocol request (65): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA^\\2... (6 Replies)
Discussion started by: finster
6 Replies

7. Solaris

diff b/w /var/log/syslog and /var/adm/messages

hi sirs can u tell the difference between /var/log/syslogs and /var/adm/messages in my working place i am having two servers. in one servers messages file is empty and syslog file is going on increasing.. and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

8. UNIX for Advanced & Expert Users

/var/adm/messages vs /var/log/messages

The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux. I checked the log level in Linux and they seem OK. Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies

9. Shell Programming and Scripting

trying get the last /var/adm/messages

grep \"^`date "+%b %d %T"`\" /var/adm/messages | egrep \"emerg|alert|crit|err|warning\ but get an output like this ksh: alert: not found ksh: crit: not found ksh: err: not found ksh: warning": not found grep: can't open "19" grep: can't open "16:27:16"" (1 Reply)
Discussion started by: arch12
1 Replies

10. Solaris

Difference between /var/log/syslog and /var/adm/messages

Hi, Is the contents in /var/log/syslog and /var/adm/messages are same?? Regards (3 Replies)
Discussion started by: vks47
3 Replies
TIMED(8)						    BSD System Manager's Manual 						  TIMED(8)

NAME
timed -- time server daemon SYNOPSIS
timed [-M] [-t] [-d] [-i network] [-n network] [-F host1 host2 ...] DESCRIPTION
This is a time server daemon and is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with the time of other machines in a local area network running timed 8. 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 service provided by timed is based on a master-slave scheme. When timed 8 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 perform 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 program. If the machine running the master crashes, then the slaves will elect a new master from among slaves running with the -M flag. A timed running without the -M or -F flags will remain a slave. The -t flag enables timed to trace the messages it receives in the file /var/log/timed.log. Tracing can be turned on or off by the program timedc(8). The -d flag is for debugging the daemon. It causes the program to not put itself into the back- ground. Normally timed checks for a master time server on each network to which it is connected, except as modified by the options described below. It will request synchronization service from the first master server located. If permitted by the -M flag, it will provide synchro- nization service on any attached networks on which no current master server was detected. Such a server propagates the time computed by the top-level master. The -n flag, followed by the name of a network which the host is connected to (see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -n flag appears, that network name is added to a list of valid networks. All other networks are ignored. The -i flag, followed by the name of a network to which the host is connected (see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -i flag appears, that network name is added to a list of net- works to ignore. All other networks are used by the time daemon. The -n and -i flags are meaningless if used together. Timed 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. If it finds masters on more than one network, it chooses one network on which to be a "slave," and then periodically checks the other net- works to see if the masters there have disappeared. One way to synchronize a group of machines is to use an NTP daemon to synchronize the clock of one machine to a distant standard or a radio receiver and -F hostname to tell its timed daemon 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. WARNING
If two or more time daemons, whether timed, NTP, try to adjust the same clock, temporal chaos will result. 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), timedc(8), R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD. HISTORY
The timed daemon appeared in 4.3BSD. 4.3 Berkeley Distribution June 6, 1993 4.3 Berkeley Distribution
All times are GMT -4. The time now is 05:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy