03-31-2010
Please post the contents of syslog.conf before and after the change.
If (and only if) the new syslog.conf is valid, are you in a position to reboot the server?
Btw. There are established techniques for dealing with the size of /var/adm/messages . Giving it space to grow unbounded is not one of them. Renaming the file is not one either. You are dealing with an open file from an active process.
On most systems the system logging process will fail if the log file tries to exceed 2 Gb or if /var/adm runs out of disc space.
How big is the original /var/adm/messages file which may have prompted you to try to relocate the log?
Last edited by methyl; 03-31-2010 at 08:22 PM..
Reason: assorted clarifications
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Just want to check with all of you out there what does the following warning means in my "messages" file in /var/adm
the warning is Prevous Time Adjustment Incomplete , does it mean my hard ware is faulty if so which piece of hardware it is ? (1 Reply)
Discussion started by: owls
1 Replies
2. Solaris
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
3. Solaris
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
4. UNIX for Dummies Questions & Answers
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
5. Solaris
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
6. Solaris
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
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
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
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
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
reboot(8) System Manager's Manual reboot(8)
NAME
reboot - Restarts the machine
SYNOPSIS
/usr/sbin/reboot [-dlnq]
DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are
logged in, use the reboot command.
The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login
accounting file, /var/adm/wtmp.
The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard-
ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically
checked. If the start-up activities are successful, the system comes up in the default run-level.
You must have root privileges to use this command. Using the -n flag can result in file system damage.
FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog
Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log
the reboot using syslog
EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the
shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l
This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system
abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes.
FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon
RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8)
Functions: reboot(2), sync(2), syslog(3) delim off
reboot(8)