3 Replies Latest reply on Mar 16, 2020 7:22 AM by john_reynolds

    Error 8.0.3 on premise: Unable to start httpd service

    vasu.bhardwaj Novice

      Hello .

       

      On Jive 8.0.3 , i am receiving an error

      Starting httpd.....no process found. See logs: /usr/local/jive/var/logs/jive-httpd.out

       

      but when i checked logs

       

      jive-httpd.out only says:

      jive_cli no process found after startup

       

      is there any work around or ASAP fix , as its for production system.

       

       

       

      Thanks,

      Vasu

        • Re: Error 8.0.3 on premise: Unable to start httpd service
          jgoldhammer Jive SME

          what says following command:

          /etc/init.d/jive status

            • Re: Error 8.0.3 on premise: Unable to start httpd service
              vasu.bhardwaj Novice

              the following commands show's

               

              cache                            stopped                 disabled

              docconverter                stopped                 disabled

              eae                               running=29211           enabled

              ingress-replicator         stopped                 disabled

              search                          running=29308           enabled

              webapp                        running=29338           enabled

              httpd                             stopped                 enabled

               

              i am running jive on suse linux enterprise 12

                • Re: Error 8.0.3 on premise: Unable to start httpd service
                  john_reynolds Guru

                  Vasu, just a note, if this is for a production system, you should open a SEV 1 Production support ticket with Aurea.

                   

                  If you are saying this system has been running for a long time (months, years), then all of a sudden stopped working, you should check other aspects of the environment like network status, firewall, DNS, filesystem issues, database connectivity

                   

                  And perform a full system restart, possibly even server reboots to re-base the support troubleshooting.