Forum Discussion

Genericus's avatar
Genericus
Moderator
6 years ago

OpsCenter systemprofile java# files - management, cleanup, etc

So, my OpsCenter server crashed today ( I just updated to 8.1.2 ) and it was due to the C: drive filling up! Bunches of java## files in C:\Windows\System32\config\systemprofile - if you use OpsCente...
8
OpsCenter
TIPS
  • Genericus's avatar
    Genericus
    6 years ago

    Found this gem: https://www.veritas.com/support/en_US/article.100044146.html

    Problem

    After install or upgrade of OpsCenter to version 8.1.2 on Linux or Windows, the java0.log file continues to grow in size until it fills up the file system.

    The location of the java0.log file:
    Linux:  /root/java0.log
    Windows:  C:\Windows\System32\config\systemprofile\java0.log

      Solution

    1.)  Edit the log.conf file, adding the following lines:
148.LogManagerResetFlag=true
147.LogManagerResetFlag=true

The location of the log.conf file:
Linux:  /opt/SYMCOpsCenterServer/config/log.conf
Windows:  <install_path>\OpsCenter\server\config\log.conf


2.)  Then the OpsCenter services need to be restarted to read in the changes. 

The services can be bounced by using the following commands:
Linux:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop 
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Windows:
<install_path>\OpsCenter\server\bin\opsadmin.bat stop
<install_path>\OpsCenter\server\bin\opsadmin.bat start

     

Genericus's avatar
Genericus
Moderator

Found this gem: https://www.veritas.com/support/en_US/article.100044146.html

Problem

After install or upgrade of OpsCenter to version 8.1.2 on Linux or Windows, the java0.log file continues to grow in size until it fills up the file system.

The location of the java0.log file:
Linux:  /root/java0.log
Windows:  C:\Windows\System32\config\systemprofile\java0.log

  Solution

1.)  Edit the log.conf file, adding the following lines:
148.LogManagerResetFlag=true
147.LogManagerResetFlag=true

The location of the log.conf file:
Linux:  /opt/SYMCOpsCenterServer/config/log.conf
Windows:  <install_path>\OpsCenter\server\config\log.conf


2.)  Then the OpsCenter services need to be restarted to read in the changes. 

The services can be bounced by using the following commands:
Linux:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop 
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Windows:
<install_path>\OpsCenter\server\bin\opsadmin.bat stop
<install_path>\OpsCenter\server\bin\opsadmin.bat start

 

quebek's avatar
quebek
Moderator
6 years ago

Thanks for brining that up ... 

I recovered 41GB by doing so and was close to fill up system drive!!

 

======EDIT=====

What a shame I can't click KUDO on this ... most likely due to subject being solved....