Visit Our UNIX and Linux User Community

Operating Systems Solaris Veritas WebLogic Server log files Post 302369690 by TonyFullerMalv on Monday 9th of November 2009 09:36:00 AM
Old 11-09-2009
I suggest you use logrotate(8) and get to do a copytruncate of the log file when rolling it, this overcomes the fact that WebLogic has the inode for the log file permanently open. Logrotate can be optained ready compiled and packaged from Sunfreeware - Free and Open Source Software (FOSS) for Sun Microsystem's Solaris. Also it would be better to put the log files into /var/log so that if the server is rebooted you do not lose the log files and filling up /tmp (and therefore swap) as you will understand has a rather detrimental affect upion Solaris!
 
Test Your Knowledge in Computers #595
Difficulty: Medium
In C, the starting point in the executable program is the prime() function.
True or False?

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

how to check weblogic server status in Unix machine

Hi All,Could anybody help in suggesting how to check the weblogic server status in a Unix machine? ps -ef |grep "startWeblogic.sh" The above command would give the running status but can anyone throw some light how to check if it is in hung/down state. Thanks (1 Reply)
Discussion started by: RSC1985
1 Replies

2. UNIX for Dummies Questions & Answers

difference weblogic server/webserver/app server

Hi All, I am getting confused with the terms below. All I know is an application can be installed on a server. But I see the following terms used in a company. All of them are installed on same Unix box. Could you please help me out in layman terms as to what these exactly means. (PS: I don't... (1 Reply)
Discussion started by: tostay2003
1 Replies

3. Solaris

Problem in deployment in weblogic server in solaris

I am getting following error during deployment in solaris. when i deploy same war in other machine (non-solaris) it works fine. the stacktrace is < ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277738498407> <BEA-149205> <Failed to initialize the... (0 Replies)
Discussion started by: paradesi143
0 Replies

4. UNIX and Linux Applications

Exception in Weblogic Application server

Hi, I have a application running on weblogic server. i am getting these errors in logs very frequently. Could you please suggest any solution for this. -02-09 10:02:32,346 ERROR psn.properties.RemotePropertiesCache - Error occurred while attempting to retrieve property: ... (0 Replies)
Discussion started by: Siddheshk
0 Replies

5. UNIX and Linux Applications

Version of Weblogic server

Hi All, How to find the version of the weblogic server configured? Our server is a Linux based server. Regards Dhivya (1 Reply)
Discussion started by: dhivya.enjoy
1 Replies

6. Shell Programming and Scripting

How can i get the state of weblogic server

Hi, all Now i want write a shell to get the state of weblogic server,and when the Managed Server's state is not ok, after 3 times checking, i will send msg to the system administrator by sms. BTW, my environment is : Linux ,Redhat 5.4 64bit weblogic version: 10.3.3 the count number... (1 Reply)
Discussion started by: wangsk
1 Replies
vxcmdlog(1M)															      vxcmdlog(1M)

NAME
vxcmdlog - administer command logging SYNOPSIS
vxcmdlog [-H] [-l] [-m {on|off}] [-n number] [-s size] DESCRIPTION
The vxcmdlog command is used to administer command logging in Veritas Volume Manager (VxVM). This feature can be used to record all VxVM commands that are issued, and can be used in conjunction with the transaction logging feature (see vxtranslog(1M)). When the current log file reaches a maximum size, it is renamed as a historic log file, and a new current log file is created. A limited number of historic log files is preserved to avoid filling up the file system. Each log file contains a header that records the host name, host ID, and the date and time that the log was created. See the EXAMPLES sec- tion below for a description of the entries that are recorded in a log file. OPTIONS
-H Displays detailed help about the usage of the command. -l Lists current settings for command logging. This shows whether command logging is enabled, the maximum number of historic log files, and the maximum log file size. -m {on|off} Turns command logging on or off. By default, command logging is turned on. -n number Sets the maximum number of historic log files to maintain. The default number is 5. If number is set to no_limit, there is no limit on the number of historic log files that are created. -s size Sets the maximum size to which a command log can grow. (Note that this setting has no effect on existing historic log files.) The suffix modifiers k, m, and g may be used express sizes in kilobytes, megabytes and gigabytes respectively. If no suffix is specified, the default units are kilobytes. If size is set to no_limit, there is no limit on the size of the log file. The size of the command log is checked after an entry has been written so the actual size may be slightly larger than that speci- fied. When the log reaches the specified size, the current command log file, cmdlog, is renamed as the next available historic log file, cmdlog.number, where number is an integer from 1 up to the maximum number of historic log files that is currently defined. If the maximum number of historic log files has been reached, the oldest historic log file is removed, and the current log file is renamed as that file. The default maximum size of the command log file is 1m(1MB). EXAMPLES
Turn on command logging: vxcmdlog -m on Set the maximum command log file size to 512KB: vxcmdlog -s 512k Set the maximum number of historic command log files to 10: vxcmdlog -n 10 The following are sample entries from a command log file: /usr/sbin/vxdctl mode /usr/sbin/vxdisk -q -o alldgs list /etc/vx/diag.d/vxprivutil dumpconfig /dev/vx/rdmp/Disk_4s2 /usr/sbin/vxdisk list SENA0_1 Each entry usually contains a client ID that identifies the command connection to the vxconfigd daemon, the process ID of the command, a time stamp, and the command that was used together with its arguments. If the client ID is 0, as in the third entry shown here, this means that the command did not open a connection to vxconfigd. Note: The client ID is the same as that recorded for the corresponding transactions in the transactions log. FILES
/etc/vx/log Symbolic link to the log directory. This can be redefined if necessary. /etc/vx/log/cmdlog Current command log. /etc/vx/log/cmdlog.number Historic command logs. NOTES
If vxcmdlog records the invocation of a vxmake command that reads object definitions from a description file, vxcmdlog additionally records the contents of the description file. Most command scripts are not logged, but the command binaries that they call are logged. Exceptions are the vxdisksetup, vxinstall, and vxdiskunsetup scripts, which are logged. SEE ALSO
vxtranslog(1M) Veritas Volume Manager Troubleshooting Guide VxVM 5.0.31.1 24 Mar 2008 vxcmdlog(1M)

Featured Tech Videos

All times are GMT -4. The time now is 02:13 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy