Sponsored Content
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!
 

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
kproplog(1M)						  System Administration Commands					      kproplog(1M)

NAME
kproplog - display the contents of the Kerberos principal update log SYNOPSIS
/usr/sbin/kproplog [-h | -e num] DESCRIPTION
The kproplog displays the contents of the Kerberos principal update log to standard output. This command can be used to keep track of the incremental updates to the principal database, which is enabled by default. The /var/krb5/principal.ulog file contains the update log main- tained by the kadmind(1M) process on the master KDC server and the kpropd(1M) process on the slave KDC servers. When updates occur, they are logged to this file. Subsequently any KDC slave configured for incremental updates will request the current data from the master KDC and update their principal.ulog file with any updates returned. The kproplog command can only be run on a KDC server by someone with privileges comparable to the superuser. It will display update entries for that server only. If no options are specified, the summary of the update log is displayed. If invoked on the master, all of the update entries are also dis- played. When invoked on a slave KDC server, only a summary of the updates are displayed, which includes the serial number of the last update received and the associated time stamp of the last update. OPTIONS
The following options are supported: -h Display a summary of the update log. This information includes the database version number, state of the database, the number of updates in the log, the time stamp of the first and last update, and the version number of the first and last update entry. -e num Display the last num update entries in the log. This is useful when debugging synchronization between KDC servers. -v Display individual attributes per update. An example of the output generated for one entry: Update Entry Update serial # : 4 Update operation : Add Update principal : test@EXAMPLE.COM Update size : 424 Update committed : True Update time stamp : Fri Feb 20 23:37:42 2004 Attributes changed : 6 Principal Key data Password last changed Modifying principal Modification time TL data FILES
/var/krb5/principal.ulog The update log file for incremental propagation. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkdcu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
kpasswd(1), gkadmin(1M), kadmin(1M), kadmind(1M), kdb5_util(1M), kprop(1M), kpropd(1M), kadm5.acl(4), kdc.conf(4), attributes(5), SEAM(5) SunOS 5.10 29 Mar 2004 kproplog(1M)
All times are GMT -4. The time now is 07:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy