Bug ID 471827: Firstboot early syslog-ng log: /var/run/httpd.pipe does not exist

Last Modified: Apr 28, 2025

Affected Product(s):
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.4 HF3

Opened: Jul 15, 2014

Severity: 3-Major

Symptoms

Early syslog-ng starts up with a config file that references /var/run/httpd.pipe, but it does not exist and syslog-ng logs the following: <date> <host> notice syslog-ng: Error opening file for reading; filename=\'/var/run/httpd.pipe\', error=\'No such file or directory (2)\'

Impact

There is no actual impact due to this behavior because: (1) syslog-ng is restarted with the correct syslog-ng configuration later in the boot. (2) httpd is not started until later which means there is no actual usage of /var/run/httpd.pipe.

Conditions

First boot of a newly installed system uses a different syslog-ng.conf file, but only on the first boot of a newly installed system. After first boot, the real syslog-ng config file is used. The following log appears in /var/log/boot.log [only in 11.x releases]: Sep 4 10:17:35 localhost notice syslog-ng: Error opening file for reading; filename=\'/var/run/httpd.pipe\', error=\'No such file or directory (2)\'

Workaround

None

Fix Information

Prior to starting the early syslog-ng, create the missing file /var/run/httpd.pipe. This also happens later when etc/init.d/syslog-ng is run, but does nothing because the early syslog-ng startup script creates the missing file.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips