• State Not Answered
  • Replies 3 replies
  • Subscribers 10 subscribers
  • Views 3937 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Appian 18.3 installation issue - Configure Apache with Appian

Nilesh Raman

Hi All,

I have installed Appian 18.3 on one of the linux machine. Appian and tomcat configured properly and all the services started successfully. But when configuring Apache webserver with Appian I am not able to start the Apache services. I followed each and every step thoroughly as per the documentation "docs.appian.com/.../Configuring_Apache_Web_Server_with_Appian.html" but getting below error:

[core:notice] [pid 9513] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0

 [suexec:notice] [pid 9513] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

[ssl:warn] [pid 9513] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)

[jk:warn] [pid 9513] No JkLogFile defined in httpd.conf. Using default /etc/httpd/logs/mod_jk.log

 [jk:warn] [pid 9513] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status

 [jk:emerg] [pid 9513] Initializing shm:/etc/httpd/logs/jk-runtime-status.9513 errno=13. Unable to start due to shared memory failure.

[jk:emerg] [pid 9513] Initializing shm:/etc/httpd/logs/jk-runtime-status.9513 errno=13. Unable to start due to shared memory failure.

 

Has anyone configured Apache with Appian successfully? If yes, then please let provide the steps or any documentation you did to configure. As forum documentation is not helping me to configure it successfully.

 

Thanks in advance.

  Discussion posts and replies are publicly visible

  • 0
    A Score Level 2

    Hi,

    I am able to configure Apache with Appian 18.3 recently. I did use the same configuration which I have been using in my Appian-JBoss setup previously (As per the Appian documentation link).

    From the warnings in your setup, it looks like SSL cert issues (mod_ssl) problems. Can you dig into this more.

    Can you check if your issue is same as described in this link.

     

  • 0 in reply to Mangesh Vidhale
    Thanks for replying Mangesh.

    I tried to configure by removing all the property for https but it didn't worked with http also so SSL cert only is not only the issue. I will try to configure from previous version documentation and see if it helps.
  • 0
    Hi All,

    I am able to start my Apache service now by disabling the SElinux temporarily but when I try to access the URL as "https://server.com/suite" it gives me "503 Service unavailable" page.

    Below is the error I ma getting in mod_jk.log :
    [Tue Nov 06 14:17:16.876 2018] [22378:139776027064448] [info] jk_open_socket::jk_connect.c (735): connect to ::1:8009 failed (errno=111)
    [Tue Nov 06 14:17:16.876 2018] [22378:139776027064448] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1019): Failed opening socket to (::1:8009) (errno=111)
    [Tue Nov 06 14:17:16.876 2018] [22378:139776027064448] [error] ajp_send_request::jk_ajp_common.c (1659): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
    [Tue Nov 06 14:17:16.876 2018] [22378:139776027064448] [info] ajp_service::jk_ajp_common.c (2669): (node1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [info] jk_open_socket::jk_connect.c (735): connect to ::1:8009 failed (errno=111)
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1019): Failed opening socket to (::1:8009) (errno=111)
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [error] ajp_send_request::jk_ajp_common.c (1659): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [info] ajp_service::jk_ajp_common.c (2669): (node1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [error] ajp_service::jk_ajp_common.c (2689): (node1) connecting to tomcat failed.
    [Tue Nov 06 14:17:16.976 2018] [22378:139776027064448] [info] service::jk_lb_worker.c (1514): service failed, worker node1 is in error state
    [Tue Nov 06 14:17:17.077 2018] [22378:139776027064448] [info] service::jk_lb_worker.c (1566): Forcing recovery once for 1 workers
    [Tue Nov 06 14:17:17.077 2018] [22378:139776027064448] [info] jk_open_socket::jk_connect.c (735): connect to ::1:8009 failed (errno=111)
    [Tue Nov 06 14:17:17.077 2018] [22378:139776027064448] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1019): Failed opening socket to (::1:8009) (errno=111)
    [Tue Nov 06 14:17:17.077 2018] [22378:139776027064448] [error] ajp_send_request::jk_ajp_common.c (1659): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
    [Tue Nov 06 14:17:17.077 2018] [22378:139776027064448] [info] ajp_service::jk_ajp_common.c (2669): (node1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] jk_open_socket::jk_connect.c (735): connect to ::1:8009 failed (errno=111)
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1019): Failed opening socket to (::1:8009) (errno=111)
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [error] ajp_send_request::jk_ajp_common.c (1659): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] ajp_service::jk_ajp_common.c (2669): (node1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [error] ajp_service::jk_ajp_common.c (2689): (node1) connecting to tomcat failed.
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] service::jk_lb_worker.c (1514): service failed, worker node1 is in error state
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] service::jk_lb_worker.c (1594): All tomcat instances are busy or in error state
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [error] service::jk_lb_worker.c (1599): All tomcat instances failed, no more workers left
    [Tue Nov 06 14:17:17.177 2018] [22378:139776027064448] [info] jk_handler::mod_jk.c (2806): Service error=0 for worker=LoadBalancer
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.