Skip to main content

Websites stop working after installation of tomcat 7 thru easyapache

Comments

10 comments

  • cPanelMichael
    Hello :) Could you elaborate further on how your websites are not working? What is output to the Apache error log (/usr/local/apache/logs/error_log) when the websites fail to load? Thank you.
    0
  • q8developer
    send: Connection refused at /usr/local/cpanel/Cpanel/Linux/Netlink.pm line 174
    0
  • cPanelMichael
    [quote="q8developer, post: 1675112">send: Connection refused at /usr/local/cpanel/Cpanel/Linux/Netlink.pm line 174
    To confirm, you see that message in the Apache error log and not the cPanel error log? Do you have any firewall rules or third-party applications installed that could result in that message? Are you using Apache or another web server such as LiteSpeed? Thank you.
    0
  • q8developer
    yaa i have plugin called LogView - 3.5 in WHM to see all log and this is wut i find diff. in the error_log. and yes im using asa5500 firewall as well
    0
  • cPanelMichael
    You may want to review your firewall configuration and verify it's not causing this issue. Thank you.
    0
  • q8developer
    [quote="cPanelMichael, post: 1675241">You may want to review your firewall configuration and verify it's not causing this issue. Thank you.
    Thanx alot it was firewall issue now websites are working fine [COLOR="silver">- - - Updated - - - btw regarding tomcat 7 i install in thru easy apache and now i can see icons for restart servlet server and install servlets i install servlet on one of my websites but still jsp is not working on it www.ihcq8.com/jsptest.jsp
    0
  • cPanelMichael
    I am happy to see the initial issue was resolved are modifying your firewall rules. As far as the second issue, you can open a support ticket and we can verify that a JSP test page works as intended. Post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • q8developer
    Your Request id is: 5183219.
    0
  • cPanelMichael
    To update, this issue was addressed by updating group ownership of the tomcat user to "nobody". Thank you.
    0
  • KurtN.
    Case 108257 has been opened to resolve this issue.
    0

Please sign in to leave a comment.