Skip to main content

diskspace issues


If the disk space usage is 95%-100% then we will delete old log files
[root@localhost ~]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             3.8G  1.9G  1.8G  52% /
/dev/sda1              46M  9.2M   35M  22% /boot
tmpfs                 506M     0  506M   0% /dev/shm
/dev/sda3              14G  14G    0G  100% /home

du -kh (disk usage)

[root@localhost ~]# du -sh /home
1.8G    /home

[root@localhost bea10.3]# du -sh *
181M    jdk160_05
211M    jrockit_160_05
28K     logs
100M    modules
24K     registry.dat
8.0K    registry.xml
19M     user_projects
556K    utils
429M    wlserver_10.3

delete old log files
/home/bea10.3/user_projects/domains/sherkhan/servers/AdminServer/logs

rm -rf Adminserver.log00001  Adminserver.log00002 Adminserver.log00003
rm -rf Adminserver.out00001 Adminserver.out00002 Adminserver.out00003
rm -rf access.log00001 access.log00002 access.log00003

/home/bea10.3/user_projects/domains/sherkhan/servers/ms1/logs

rm -rf ms1.log00001
rm -rf ms1.out00001
or zip the log files
/home/bea10.3/user_projects/domains/sherkhan/servers/AdminServer/logs
gzip -r *
/home/bea10.3/user_projects/domains/sherkhan/servers/AdminServer
gzip -r logs


High cpu utilization:

top (linux)
prstat (solaris)

top - 07:45:22 up  3:03,  3 users,  load average: 0.16, 0.33, 0.17
Tasks: 113 total,   2 running, 109 sleeping,   0 stopped,   2 zombie
Cpu(s):  0.0%us,  0.7%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   1035400k total,  1020348k used,    15052k free,    77688k buffers
Swap:  2040212k total,        0k used,  2040212k free,   483724k cached

ps -ef | grep 9523

If you find any zombie process count >50 raise a ticket to solaris admins
If any java processes are occupying 95-100% cpu usage then check the log files for any continuous looping messages or jdbc transaction time outs.
fix the problem and kill manged  server using kill -9 pid and restart the service instance.

Application logs files not rotating issue:

check the diskspace if it is full then delete old logs
check whether log4j properties file set in classpath

Comments

Post a Comment

Popular posts from this blog

Weblogic upgrade server from 10.1.3.4 to 10.3.6

Important points: Different weblogic servers and supported java versions : Oracle WebLogic 10.3.5.0 supports Sun JDK 1.6.0_24. Oracle WebLogic 10.3.6.0, supports the Oracle JDK 1.7.0 Oracle WebLogic 12.1.3 supports Oracle JDK 1.7.0_55+ (1.7.0_67) Oracle WebLogic 12.2.1 (12R2) supports JDK 1.8 Upgrade Weblogic server from 10.1.3.4 to 10.3.6 by applying the Patch: 13529623. step.1 Shut down all WebLogic processes you want to upgrade such as: Node Manager Admin Server All Managed Servers step.2 Download and installed a new version of JDK 1.7+. After installing Verifying the JDK Version java –version Note: A plus sign '+' after the version number indicates that this and its subsequent versions are supported. step.3 Download this patch set for Oracle WebLogic 10.3.6.0: Patch 13529623 (p13529623_1036_Generic.zip) Unzip the file in a temporary location and confirm the extracted contains this file: wls1036_upgrade_generic.jar step.4 Running OUI to Upgrade an Existing WebLogic Server to...
Post a Comment
Read more

Server subsystem failed. Reason: java.lang.NumberFormatException: null java.lang.NumberFormatException: null

<BEA-000386> Server subsystem failed. Reason: java.lang.NumberFormatException: null java.lang.NumberFormatException: null         at java.lang.Integer.parseInt(Integer.java:417)         at java.lang.Integer.parseInt(Integer.java:499)         at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1097)         at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:242)         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) This mostly happens when LDAP files are corrupted under the ../domain-name/server/AdminServer/data/ldap/ directory. A possible cause of corruption is when space on server is full. When the associated volume is full (100%)...
Post a Comment
Read more

Error: unable to obtain lock file

<Server failed. Reason: There are 1 nested errors: weblogic.management.ManagementException: Unable to obtain lock on C:\bea10.3\user_projects\domains\sherkhan\servers\AdminServer\tmp\AdminServer.lok. Server may already be running         at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)         at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)         at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:73)         at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:459)         at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:164)         at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:711)         at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:482)       ...
Post a Comment
Read more