Forum Discussion

spider328's avatar
spider328
Level 4
8 years ago

OpsCenter Login page not coming up

Hi guys,

Have restarted OpsCenter several times (opsadmin.sh stop/start) and rebooted the server but login page still hanging.

No error message on screen. Just waiting for opscenter....

Telnet on port 443 shows that the port is open so this tells me that the webservice is up and running.

 

 

 

  • spider328's avatar
    spider328
    8 years ago

    Thanks for sharing your idea. 

    It was not a certificate issue since we could  not even get to the point where the page would mention that there is a problem with the certificate.

    We looked at /var/log/messages:pr 27 15:23:40 evpla504 abrtd: Directory 'ccpp-2017-04-27-15:23:25-6227' creation detected
    Apr 27 15:23:40 evpla504 abrtd: Package 'VRTSOpsCenterServer' isn't signed with proper key
    Apr 27 15:23:40 evpla504 abrtd: 'post-create' on '/var/spool/abrt/ccpp-2017-04-27-15:23:25-6227' exited with 1
    Apr 27 15:23:40 evpla504 abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2017-04-27-15:23:25-6227'
    Apr 27 19:36:40 evpla504 abrtd: Got signal 15, exiting
    Apr 27 19:38:22 evpla504 abrtd: Init complete, entering main loop
    Apr 27 20:12:39 evpla504 abrt[5471]: Write error: No space left on device
    Apr 27 20:12:39 evpla504 abrt[5471]: Error writing '/var/spool/abrt/ccpp-2017-04-27-20:12:27-3411.new/coredump'
    Apr 27 20:38:46 evpla504 abrt[7351]: Write error: No space left on device
    Apr 27 20:38:47 evpla504 abrt[7351]: Error writing '/var/spool/abrt/ccpp-2017-04-27-20:38:34-5688.new/coredump'
    within the last coredump, the process that killed it was: /prd/nbu/OpsCenter/SYMCOpsCenterServer/jre/bin/java

    Found this article:

    https://www.veritas.com/support/en_US/article.000035896

    GENERAL ERROR: Job data collection from NetBackup module errors out - java.lang.OutOfMemoryError: Java heap space

     

    We also noticed that the server is maxing the CPU resource. 

    We doubled the Java heap size and restarted OpsCenter. This resolved the issue.

    .

     

     

     

     

4 Replies

Sort By
  • Tape_Archived's avatar
    Tape_Archived
    Moderator
    8 years ago

    Please check if you see any certificate warning, you may have to add an exception in the browser in that case. Also check if something is blocking that address with your security team.

    Please review the logs under /installed_path/OpsCenter/gui/logs for more information on the error.

    • spider328's avatar
      spider328
      Level 4
      8 years ago

      Thanks for sharing your idea. 

      It was not a certificate issue since we could  not even get to the point where the page would mention that there is a problem with the certificate.

      We looked at /var/log/messages:pr 27 15:23:40 evpla504 abrtd: Directory 'ccpp-2017-04-27-15:23:25-6227' creation detected
      Apr 27 15:23:40 evpla504 abrtd: Package 'VRTSOpsCenterServer' isn't signed with proper key
      Apr 27 15:23:40 evpla504 abrtd: 'post-create' on '/var/spool/abrt/ccpp-2017-04-27-15:23:25-6227' exited with 1
      Apr 27 15:23:40 evpla504 abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2017-04-27-15:23:25-6227'
      Apr 27 19:36:40 evpla504 abrtd: Got signal 15, exiting
      Apr 27 19:38:22 evpla504 abrtd: Init complete, entering main loop
      Apr 27 20:12:39 evpla504 abrt[5471]: Write error: No space left on device
      Apr 27 20:12:39 evpla504 abrt[5471]: Error writing '/var/spool/abrt/ccpp-2017-04-27-20:12:27-3411.new/coredump'
      Apr 27 20:38:46 evpla504 abrt[7351]: Write error: No space left on device
      Apr 27 20:38:47 evpla504 abrt[7351]: Error writing '/var/spool/abrt/ccpp-2017-04-27-20:38:34-5688.new/coredump'
      within the last coredump, the process that killed it was: /prd/nbu/OpsCenter/SYMCOpsCenterServer/jre/bin/java

      Found this article:

      https://www.veritas.com/support/en_US/article.000035896

      GENERAL ERROR: Job data collection from NetBackup module errors out - java.lang.OutOfMemoryError: Java heap space

       

      We also noticed that the server is maxing the CPU resource. 

      We doubled the Java heap size and restarted OpsCenter. This resolved the issue.

      .