# Apache access log request grok failure

**URL:** <https://discuss.elastic.co/t/apache-access-log-request-grok-failure/143823>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 10, 2018, 7:53am UTC](https://discuss.elastic.co/t/apache-access-log-request-grok-failure/143823 "2018-08-10T07:53:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [August 10, 2018, 7:53am UTC](https://discuss.elastic.co/t/apache-access-log-request-grok-failure/143823/1 "2018-08-10T07:53:24Z")

</div>

Hello,

Using the standard apache2 module for Apache access logs, I get

`Provided Grok expressions do not match field value` errors for example with:

`[10/Aug/2018:09:45:56 +0200] 172.30.0.119 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&amp;opts=%7B%22func%22%3A%22get_admin_tasks_html%22%2C%22args%22%3A%22%22%7D&amp;nsp=b5c7d5d4b6f7d0cf0c92f9cbdf737f6a5c838218425e6ae21 HTTP/1.1" 1375`

Log location: `/var/log/httpd/ssl_request_log`

`httpd.x86_64 2.4.6-80.el7.centos.1`

Filebeat 6.3.2 config:

```
- module: apache2
  access:
    enabled: true
    var.paths: ["/var/log/httpd/access_log","/var/log/httpd/ssl_access_log","/var/log/httpd/ssl_request_log"]
  error:
    enabled: true
    var.paths: ["/var/log/httpd/error_log","/var/log/httpd/ssl_error_log"]

```

error.message in Kibana:

`Provided Grok expressions do not match field value: [[10/Aug/2018:09:45:56 +0200] 172.30.0.119 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET /nagiosxi/ajaxhelper.php?cmd=getxicoreajax&amp;opts=%7B%22func%22%3A%22get_admin_tasks_html%22%2C%22args%22%3A%22%22%7D&amp;nsp=b5c7d5d4b6f7d0cf0c92f9cbdf737f6a5c838218425e6ae21 HTTP/1.1" 1375]`

Should I make a GitHub issue?

Grtz

Willem

---

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [August 10, 2018, 3:59pm UTC](https://discuss.elastic.co/t/apache-access-log-request-grok-failure/143823/2 "2018-08-10T15:59:01Z")

</div>

Hi,

You're right, the Apache module doesn't have a grok pattern for the ssl\_request\_log. Please open a GitHub issue.

I reproduced it by installing `httpd.x86_64 2.4.6-80.el7.centos.1` as well as `mod_ssl.x86_64 1:2.4.6-80.el7.centos.1`. It's the later package that installs `/etc/httpd/conf.d/ssl.conf` with the following entry:

```auto
# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 7, 2018, 3:59pm UTC](https://discuss.elastic.co/t/apache-access-log-request-grok-failure/143823/3 "2018-09-07T15:59:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.