SAP Knowledge Base Article - Preview

2043096 - Getting a "400 Bad Request" when testing the status pages of the Relay Server running on Linux/Apache - SQL Anywhere

Symptom

  • Opening one of the following URLs results in the HTTP 400 Bad Request error (displayed as HTML source code)
         http://localhost/cli/iarelayserver/
         http://localhost/srv/iarelayserver/
         http://localhost/admin/iarelayserver/
         http://localhost/mon/iarelayserver/
  • Both processes "httpd" and "rshost" are running under the same account.
  • The directives "LoadModule" and "LocationMatch" for the Relay Server were correctly made in the configuration file (httpd.conf) of the Apache web server.
  • The Apache web server had logged in "error_log" amongst others lines like the following
       ... [error] [client 127.0.0.1] Failed to attach to Relay Server state store, pid: 1906
       ... [error] [client 127.0.0.1] File does not exist: /var/www/html/srv
  • In the "messages" log file many of the following lines were logged
       ... kernel: type=1400 audit(1405518280.235:8): avc:  denied  { rmdir } for  pid=1906 comm="httpd" name=".MobiLink" dev=dm-0 ino=2486570 scontext=system_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=dir


Read more...

Environment

  • SAP SQL Anywhere 16.0
    SAP SQL Anywhere 12.0
    Sybase SQL Anywhere 11.0
  • Linux OS
  • Apache web server

Product

SAP SQL Anywhere 16.0 ; SAP Sybase SQL Anywhere 12.0 ; Sybase SQL Anywhere 11.0

Keywords

RedHat, SUSE, relay, server, SQL, Anywhere, SQLAny, SQA, request, error, Linux, Apache, HTTP, errors, requests, , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.