Messaging Gateway

 View Only
  • 1.  tomcat error

    Posted Jan 30, 2009 10:17 AM

    hello everybody.

    Please, I need a help. I set my brightmail gateway 7.7 to not use "demo certificate" and now my control center console don´t open anymore. It works when I try using http://my_ip_server:41080 but the control center closes in a few seconds whit Tomcat error. The server was already rebooted.

    Thanks in advance.

     

    Goto



  • 2.  RE: tomcat error
    Best Answer

    Posted Feb 02, 2009 07:58 AM

    Hi Goto,

     

    You should be able to do the following, although it doesn't really seem to be working for me :(

     

    Log into the appliance via ssh or physically at the console and run the command 'http on'.  Now run the command 'service controlcenter restart'.  When the service is running again you should now be able to log in using http, the standard http port(80) and not (41080).  Login to the appliance, change the certificate settings back to the way they were and save them.  You should now be able to shut http access off the same way you turned it on and you should be back where you started.

     

    Let us know how it goes for you, if it doesn't work out there might possibly be a bug with the command...

     

    Kevin



  • 3.  RE: tomcat error

    Posted Feb 02, 2009 08:08 AM

    Hello Kevin.

     

    Thanks... it´s alive. :smileyvery-happy:

    I re-forced the option "Demo Certificate" and did worked.

    It´s sound like a control center´s bug.

    thank you very much...!

     

     

    Message Edited by Goto on 02-02-2009 11:10 AM


  • 4.  RE: tomcat error

    Posted Feb 02, 2009 08:28 AM

    Hi Goto,

     

    Great news!  So how did you ifix it in the end?  Did you need to enable http access from the cli?  If so how did you then connect to the Control Center, did you connect to the standard http port(80) or did you need to use 41080?

     

    I'm having a hard time reproducing this myself, but if it's fixed for you that's good. :)

     

    Kevin



  • 5.  RE: tomcat error

    Posted Feb 02, 2009 09:30 AM

    Hi Kevin.

    I just set "http on" to access http://my_server_ip:41080. In this case, my connection was interrupted in a few seconds, but the time was enought to force use "demo certificate" again and save.

    I used set-control-center-port-443 in the command prompt too. This may be a bug...I guess....

     



  • 6.  RE: tomcat error

    Posted Feb 02, 2009 11:16 AM

     

    FYI, on a side note, previous to version 7.7 the SBG was accessd via the web browser with https on port 41443(eg. https:\\ip:41443).  If you upgraded to version 7.7 you would still access via the same url.  If you set up a new 7.7 Control Center appliance you access it via the standard https port 443, eg. https:\\ip. The 'set-control-center-port-443' command was designed for customers who have upgraded from earlier versions of the SBG but want the Control Cener to use secure http on port 443 instead of port 41443.

     

    Kevin



  • 7.  RE: tomcat error

    Posted Feb 02, 2009 11:37 AM

    Yep Kevin.

    In my case, it´s a new instalation. But I tried everything.