4 Replies Latest reply on Jan 18, 2012 10:08 AM by dna411

    IDS Manager web interface is not working

      Hello,

       

      If I want to open the web interface I get the following error message:

       

      Service Temporarily Unavailable

      The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

       

       

      Both Manager and Apache httpd working correctly.

       

      Any idea about what is the problem ?

       

      Thank you for your answers.

        • 1. Re: IDS Manager web interface is not working
          dmease729

          Hi,

           

          Is this a permanent message or is it only present straight after a service reboot?  This message tends to crop up when a server has first been started up as everything is initialising.  If this message remains, try a reboot and see if the message disappears (the time taken for all services to initialise will depend on your server specs).  If it doesnt, I would recommend raising a support case.

          When you say Apache and Manager are working correctly, how are you checking this?

           

          Cheers,

           

          Darren

          • 2. Re: IDS Manager web interface is not working

            Dear Darren,

             

            Thank you for your answer.

             

            We are operating this manager since 3 years. This is a permanent error message, I had restarted the device several times. I had manually checked, and all the services runing.

             

            Also Intruder manager service (right click on the icon) also shows that the manager and apache is runing:

             

            http://i43.tinypic.com/apjlhw.jpg

             

            Thank you.

            • 3. Re: IDS Manager web interface is not working
              dmease729

              Apologies, I have just reread your original post.  Although the services are shown as started, it is saying that either there is planned maintenance downtime (which I assume you would know of) or capacity issues. 

               

              1) How is the disk space looking on your server?

              2) Is there anything in the httpd.log under <app install dir>/App/Apache/Logs/ ?

              3) Is the server used for anything else aside from NSM?

              4) If this has been used for 3 years, when did this issue first occur, and what else happened around the time that the issue first presented?

               

              This message looks to be Apache specific, and to investigate further I would likely spend a bit of time digging around myself.  I would definitely suggest raising a support case.

               

              cheers,

              1 of 1 people found this helpful
              • 4. Re: IDS Manager web interface is not working

                Dear Darren,

                 

                Thank you, I also think it might be an Apache problem.

                 

                The answers for you questions are:

                 

                1, There is around 2.77 Gb free space

                 

                http://i44.tinypic.com/k9c3ls.jpg

                 

                2, Yes, couple of log files:

                 

                http://i44.tinypic.com/9kql8x.jpg

                 

                There is no httpd.log file : http://i42.tinypic.com/8zgvmx.jpg

                 

                 

                The 2011 november ssl file contains this:

                 

                [Wed Nov 23 16:06:06 2011] [notice] Apache/2.2.11 (Win32) mod_ssl/2.2.11 OpenSSL/0.9.8k mod_jk/1.2.28 configured -- resuming normal operations

                [Wed Nov 23 16:06:06 2011] [notice] Server built: Jun  9 2009 13:49:10

                [Wed Nov 23 16:06:06 2011] [notice] Parent: Created child process 4840

                [Wed Nov 23 16:06:06 2011] [notice] Child 4840: Child process is running

                [Wed Nov 23 16:06:06 2011] [notice] Child 4840: Acquired the start mutex.

                [Wed Nov 23 16:06:06 2011] [notice] Child 4840: Starting 250 worker threads.

                [Wed Nov 23 16:06:06 2011] [notice] Child 4840: Starting thread to listen on port 443.

                [Wed Nov 23 16:06:06 2011] [notice] Child 4840: Starting thread to listen on port 80.

                [Wed Nov 23 17:00:32 2011] [warn] pid file C:/IntruShield/Apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?

                [Wed Nov 23 17:00:32 2011] [notice] Apache/2.2.11 (Win32) mod_ssl/2.2.11 OpenSSL/0.9.8k mod_jk/1.2.28 configured -- resuming normal operations

                [Wed Nov 23 17:00:32 2011] [notice] Server built: Jun  9 2009 13:49:10

                [Wed Nov 23 17:00:32 2011] [notice] Parent: Created child process 932

                [Wed Nov 23 17:00:33 2011] [notice] Child 932: Child process is running

                [Wed Nov 23 17:00:33 2011] [notice] Child 932: Acquired the start mutex.

                [Wed Nov 23 17:00:33 2011] [notice] Child 932: Starting 250 worker threads.

                [Wed Nov 23 17:00:33 2011] [notice] Child 932: Starting thread to listen on port 443.

                [Wed Nov 23 17:00:33 2011] [notice] Child 932: Starting thread to listen on port 80.

                 

                3, No

                 

                4, I think it was November 2011.

                 

                I will create a ticket about this.