> nginx: [emerg] unknown directive "log_by_lua_block" in
> /etc/nginx/conf.d/microservice.conf:8
> nginx: configuration file /etc/nginx/nginx.conf test failed
You need nginx lua/openresty module, but I'm not sure if Centos (community
version) repository has it.
You might need to build it yourse
config
> > file /etc/nginx/conf.d/microservice.conf
> > I want to capture full request/response body logging in nginx.
>
> Since you question is related to a third-party module, I'd recommend
> to get support in a appropriate mailing list.
>
>
Thanks Sergey for
t/response body logging in nginx.
Since you question is related to a third-party module, I'd recommend
to get support in a appropriate mailing list.
Thank you.
--
Sergey A. Osokin
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
Hi,
I am running nginx version: nginx/1.24.0 as reverse proxy on CentOS Linux
release 7.9.2009 (Core). I have the below config
file /etc/nginx/conf.d/microservice.conf
I want to capture full request/response body logging in nginx.
# cat /etc/nginx/conf.d/microservice.conf
server
Is there a way to have nginx log the response body?
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
You should verify that /run/nginx.pid actually exists and contains the PID
of the master nginx process on your Rocky Linux system.
I think that adding the "create 0640 nginx root" line to the logrotate
config file would not help. You can issue the "kill -USR1 " where you
replace "" with the PID o
Hi Vincent,
hope you're doing well.
On Sun, Sep 04, 2022 at 01:22:20PM +0200, Vincent M. wrote:
> Hello,
>
> The logs are working fine but once a day, nginx stop loging access and
> then the file log file is empty.
> So every day I have to restart my nginx server in order to get the logs.
> It'
On my Rocky Linux 9, I have found this file /etc/logrotate.d/nginx
/var/log/nginx/*log {
daily
rotate 10
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
/bin/kill -USR1 `cat /run/nginx.pid 2>/dev/null` 2>/dev/null ||
true
endscript
This sounds like your log rotation process is not signalling nginx to write
a new log. I don't know Rocky Linux, so I can't be specific in further
suggestions.
~ Frank
On Sun, Sep 4, 2022 at 7:24 AM Vincent M. wrote:
> Hello,
>
> The logs are working fine but once a day, nginx stop loging acc
Hello,
The logs are working fine but once a day, nginx stop loging access and
then the file log file is empty.
So every day I have to restart my nginx server in order to get the logs.
It's on a Rocky Linux 9 with Nginx 1.20.1
Never seen that before, what should I check?
Thanks,
Vincent.
___
Did you find the solution to your question?
Regards
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,290112,294877#msg-294877
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org
On 17/3/22 10:02 am, Sergey A. Osokin wrote:
References:
[1] https://mailman.nginx.org/pipermail/nginx/2018-January/055490.html
[2] https://nginx.org/en/docs/debugging_log.html
Hello Sergey,
Coincidentally I have made a small progress on resolving the problems and
discovered at least a part
Hi Jeremy,
hope you're doing well these days.
On Wed, Mar 16, 2022 at 03:36:03PM +0800, Jeremy Ardley wrote:
> Hi,
>
> I'm attempting to implement an IMAP proxy using ngx_mail module.
>
> How do I enable logging inside a mail {} stanza, or indeed anywhere
> other
Hi,
I'm attempting to implement an IMAP proxy using ngx_mail module.
How do I enable logging inside a mail {} stanza, or indeed anywhere
other than an http {} stanza which doesn't seem to log any mail {}
related traffic.
Secondly, the reason I want to log activity is because the m
Hi,
hope you're doing well these days.
On Mon, Oct 04, 2021 at 07:22:02AM -0400, petecooper wrote:
> Hello.
>
> Per the documentation:
>
> > $ssl_cipher
> > returns the name of the cipher used for an established SSL connection.
>
> This means `$ssl_cipher` returns e.g `TLS_CHACHA20_POLY1305_SH
Hello.
Per the documentation:
> $ssl_cipher
> returns the name of the cipher used for an established SSL connection.
This means `$ssl_cipher` returns e.g `TLS_CHACHA20_POLY1305_SHA256`.
Is it possible to return the corresponding hex value e.g. `0x1303` instead?
Thank you, and best wishes.
Post
Hi,
If we use ignore_invalid_headers and underscores_in_headers to allow those
non-compliant headers, is there a way to log such violations while letting
them through?
Thanks!
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listi
Hey Chinmay!
Use tcpdump or tshark.
Patrick
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Is there a way to log individual websocket messages going through a nginx
server setup to proxy websocket as explained here
https://nginx.org/en/docs/http/websocket.html ?
-Chinmay
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/m
Hello!
On Thu, Oct 29, 2020 at 06:23:59PM +0530, Vikas Kumar wrote:
> Do you have a recommendation on what handlers are suitable for my use case?
In nginx itself, proper approach to count in-flight request would
be:
1. Increment the counter only if no module's cleanup handler is installed
Do you have a recommendation on what handlers are suitable for my use case?
Thanks.
On Wed, Oct 28, 2020 at 6:59 PM Maxim Dounin wrote:
> Hello!
>
> On Wed, Oct 28, 2020 at 02:14:40PM +0530, Vikas Kumar wrote:
>
> > I'm writing an Nginx plugin (using Openresty Lua) which increments a
> > counte
Hello!
On Wed, Oct 28, 2020 at 02:14:40PM +0530, Vikas Kumar wrote:
> I'm writing an Nginx plugin (using Openresty Lua) which increments a
> counter when a request is received (in ACCESS phase) and decrements the
> counter when request is processed (in LOG phase) in order to keep track of
> in-fl
I'm writing an Nginx plugin (using Openresty Lua) which increments a
counter when a request is received (in ACCESS phase) and decrements the
counter when request is processed (in LOG phase) in order to keep track of
in-flight requests.
I've seen some cases where the counter increments but does not
> I need a HTTP proxy that can handle requests for a single upstream server,
> but also log request headers, raw request body, response headers and raw
> response body for each request. Preferably this should be logged to a
> separate daily logfile (with date-stamped filename), with timestamps, but
the exact format isn't important.
I understand that nginx doesn't provide full logging like this out of
the box, so I was wondering if it would be difficult to add. Is there a
single well-defined point in the code where an upstream request is ready
to be sent, and a point where the re
server must
> initiate session logging upon start up." So my question is: Are there any
> NGINX documentation or resource that shows NGINX starts logging as soon
> as it's started before any requests are handled?
Imho for that to be true you would need to run nginx in debug mode
I'm going over some Web Server STIGs (referenced here:
https://www.stigviewer.com/stig/web_server_security_requirements_guide/) to
make sure my NGINX web server is configured to comply with those security
requirements. One of the requirements is that "The web server must initiate
sessi
? By slowly ramping up
traffic you will be able to see when and how the site transitions from healthy
to unhealthy.
Sent from my iPhone
> On Jul 16, 2019, at 8:48 AM, heythisisom wrote:
>
> Hi Maxim,
>
> Thank you for your suggestion. I understand that enabling/disabling loggi
Hi Maxim,
Thank you for your suggestion. I understand that enabling/disabling logging
introduces extra CPU overhead. However, I will start to monitor the listen
queue with the ss command and debug the Issue further.
Thanks,
Om
Posted at Nginx Forum:
https://forum.nginx.org/read.php
al number of queued connection requests in the
listening socket queue when the issue happens. Assuming you are
using Linux, try "ss -nlt" see queue sizes and numbers of
currently queue connection requests.
> Only when I disable logging in nginx I could see this Issue happen. Onc
y the Instance I
run has 2 VCPUs hence It translates to 4 workers. The listen queue length of
my backend is sufficiently high i.e. 4096 and I have set my somaxconn
parameter to 32768. So I think everything with respect to the backend seems
fine.
Only when I disable logging in nginx I could see this
y the Instance I
run has 2 VCPUs hence It translates to 4 workers. The listen queue length of
my backend is sufficiently high i.e. 4096 and I have set my somaxconn
parameter to 32768. So I think everything with respect to the backend seems
fine.
Only when I disable logging in nginx I could see this
; <http://example.com:514>,tag=nginx_error debug;*
>
> The problem here is that, when I remove the above line from my nginx.conf,
> the request processing time is becoming very high and It leads to client
> timeout ( returns HTTP 460 ).
>
> When I enable logging in my
rom my nginx.conf,
the request processing time is becoming very high and It leads to client
timeout ( returns HTTP 460 ).
When I enable logging in my nginx.conf, I do not get HTTP 460 at all. But,
there's an extra overhead introduced which Increases the CPU Utilization.
What I suspect is tha
Hello!
On Thu, Oct 18, 2018 at 08:12:00AM -0400, wld75 wrote:
> I have verified the nginx.conf and found no abnormality in logging section:
> please see below from the nginx.conf.
> i can see all requests for upload requests only in the access.log, but
> download request not ap
Hello,
Thanks for your support.
I have verified the nginx.conf and found no abnormality in logging section:
please see below from the nginx.conf.
i can see all requests for upload requests only in the access.log, but
download request not appeared.
##
# Logging Settings
mind when looking into
access logs:
1. Requests are logged into access log once the request is
complete. This may take a while in some cases.
2. Logging details can be configured in nginx.conf, and may vary
widely from a configuration to configuration. In particular,
logging can be dis
Hi,
I have a server running for client to download and upload files, however i
am only able to see the upload request logs and download requests not
captured in the access.log file.
Thanks for advance.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,281572,281572#msg-281572
___
Hi,
I am sending QUIT signal to master process and it is terminating nginx also,
but I am not able to get any logs for to verify for gracefully exit.
I am using debug log level in http context as mentioned below.
error_log /etc/nginx/logs/ferror.log debug;
Sending signal to the NGINX master pro
well? So in the /mirror location, I added access_log
> > directive, but the log file was created, but no logs were produced.
> >
> > Is logging currently limited to only the original request?
>
> By default, subrequests are not logged. If you want them to be
> logged, consider
.
>
> Is logging currently limited to only the original request?
By default, subrequests are not logged. If you want them to be
logged, consider the "log_subrequest" directive
(http://nginx.org/r/log_subrequest).
--
Maxim Dounin
http://mdounin.ru/
Hi,
I have used ngx_http_mirror_module to create mirrors. I would like to log
these requests as well? So in the /mirror location, I added access_log
directive, but the log file was created, but no logs were produced.
Is logging currently limited to only the original request?
Best,
Jay
I made a module called ipscrub that does this: http://www.ipscrub.org. It
hashes the IP address with an ephemeral salt, so that you can match up
requests from the same IP (using the hash), but each time the salt cycles,
it becomes impossible to match an IP address with a hash in the logs.
Posted a
W dniu 06.03.2018 o 09:24, Maxim Konovalov pisze:
> Hi Grzegorz,
>
> [..]
3. I think that $tcpinfo_* aren't supported in stream. Is
there any reason for this?
>>>
>>> There's a number of http module features still missing in
>>> stream. This is one of them.
>>
>> I can offer virtual (and
Hi Grzegorz,
[..]
>>> 3. I think that $tcpinfo_* aren't supported in stream. Is
>>> there any reason for this?
>>
>> There's a number of http module features still missing in
>> stream. This is one of them.
>
> I can offer virtual (and real if in Poland) beer for adding this.
> :)
>
Just wonder
too. Do you think you could add that?
Also it would be really usefull to have access_log_connect and
access_log_upstream_connect directives in addition to access_log that enable
logging things on connect and upstream connect, not only on disconnect.
>> 3. I think that $tcpinfo_* aren&#
Hello,
On Thu, Mar 01, 2018 at 04:06:09AM +0100, Grzegorz Kulewski wrote:
> Hello,
>
> 1. How can I log the IP and (especially) the port used by nginx (proxy) to
> connect to upstream when stream module is used?
> 2. Can I somehow get a log entry also/instead at stream connection setup
> time,
Hello,
1. How can I log the IP and (especially) the port used by nginx (proxy) to
connect to upstream when stream module is used?
2. Can I somehow get a log entry also/instead at stream connection setup time,
not only after it ends?
3. I think that $tcpinfo_* aren't supported in stream. Is there
> streams are logged in /var/log/nginx/stream-access.log; UDP streams are
> not.
> >
> > FWIW, client application behavior and tcpdump both show that the upstream
> > UDP server is sending a response that makes it through nginx proxy to the
> > client just fine.
> &
nd tcpdump both show that the upstream
> UDP server is sending a response that makes it through nginx proxy to the
> client just fine.
>
> Is this lack of UDP stream access_log logging expected, or should I open a
> new bug?
>
> If you need to see more details to show exactly what
k of UDP stream access_log logging expected, or should I open a
new bug?
If you need to see more details to show exactly what I'm doing, let me know
which details would be helpful.
Thanks!
David
___
nginx mailing list
nginx@nginx.org
http://mailm
On 17 Jan 2018, at 4:38, Maxim Dounin wrote:
On Tue, Jan 16, 2018 at 12:23:31PM -0800, Luis E. Muñoz wrote:
⋮
Given how I've not seen any mention to logging in the various
documents
that describe SMTP/IMAP/POP proxying, [⋯]
The error_log directive as available in the core module work
he mail client
> with the backend server its connection was sent to). I've tried the
> `access_log` / `error_log` directives at various places in the
> configuration, to no avail.
>
> HTTP/HTTPS logging works as usual.
>
> Given how I've not seen any mentio
aces in the
configuration, to no avail.
HTTP/HTTPS logging works as usual.
Given how I've not seen any mention to logging in the various documents
that describe SMTP/IMAP/POP proxying, I believe the functionality for
this does not currently exist. This logging is very important for
trou
odule.c something could be added to logwhen an OCSP query takes place (without requiring a debug log).OCSP requests are expected to happen on regular basis when OCSPStapling is enabled, and logging them all to the error log mightnot be a good idea. Rather, it logs if there are any errors. Wha
le.c something could be added to log
>when an OCSP query takes place (without requiring a debug log).
OCSP requests are expected to happen on regular basis when OCSP
Stapling is enabled, and logging them all to the error log might
not be a good idea. Rather, it logs if there are any errors.
I've spent a bit of time setting up my server with SSL, and checking for OCSP stapling to be working - couldn't work out why it wasn't sending the OCSP reply but it's as I was querying the server as the first hit before it had primed the response. This isn't mentioned in the online docs as to how i
Let me reply with a link:
http://nginx.org/en/docs/http/ngx_http_split_clients_module.html
You can either use split_clients to change upstream or to trigger
logging with 'if' option of 'access_log'
On 19.09.2017 21:17, mblancett wrote:
I am looking for ways to target ever
The long term goal here is to replay some small amount (like 0.05%) of
> requests into a separate test environment. Currently I’m logging the entire
> request to ramdisk and using an every minute logrotation script in python to
> get the small proportion of requests I need, then using python ‘
here is to replay some small amount (like 0.05%) of
requests into a separate test environment. Currently I’m logging the entire
request to ramdisk and using an every minute logrotation script in python to
get the small proportion of requests I need, then using python ‘requests’ to
replay them against
So as you guys said: it's a normal behavior of nginx and the problem is how
can I monitor response time exactly?because, when I request a static link (a
jpeg i.e), it take about 3s to completely download, but request_time still
0.000, and because it's a HIT request so I dont have upstream_response
ros.
- reading the time (gettimeofday()) will itself take about 30 nanoseconds.
These are al intervals that are too small to be visible to the 1ms
granularity of the request_time logging.
My experience has been that very busy webservers running on even five
year old hardware
will consistently log
e 1ms granularity
of the request_time logging.
My experience has been that very busy webservers running on even five year old
hardware
will consistently log 0ms request time for cache hits. If I saw anything
different I'd be wondering
what was wrong with the environment.
Peter
On Jun 22, 2017
Hello!
On Thu, Jun 22, 2017 at 05:53:04AM -0400, jindov wrote:
> I've configured for nginx to cache static like jpeg|png. The problem is if
> request with MISS status, it will show a non-zero value request_time, but if
> a HIT request, the request_time value is 0.000.
This is expected behaviour.
Hi guys,
I've configured for nginx to cache static like jpeg|png. The problem is if
request with MISS status, it will show a non-zero value request_time, but if
a HIT request, the request_time value is 0.000.
This is an nginx bug and is there anyway to resolve it.
My log format
```
log_format c
I wanted to see if there was a way to log a request and response in
separate file, so that I end up with something like this:
request_1.log
response_1.log
request_2.log
response_2.log
request_3.log
response_3.log
..
Is there a way to do this ?
Joel
__
I am still having issues with the config, can you take a look at my short
config and see where my confusion lies ? Changed the stream block to http
and think I did the rest correct but still complains about log_format and
not sure if my proxy_pass or any of the rest of it is bad.
Joel
On Tue, Apr
Just set up a server {} block that accepts TLS connections. This is exactly
what proxy_pass is for :) You can log whatever HTTP data you need via Nginx
(just as your log_format and content_by_lua block does), and then
proxy_pass that traffic to your upstream as normal. Stream blocks are for
arbitra
What I am trying to do is create an open proxy that listens to TLS from
many servers and de-crypts the traffic with the appropriate keys, log the
de-crytped request / response then re-encrypt with different certs and send
to an upstream server. My thought was theat a stream block would help me
acco
No. stream {} and http {} blocks are mutually exclusive.
What exactly are you trying to accomplish with stream?
On Tue, Apr 25, 2017 at 11:46 AM, Joel Parker
wrote:
> so can I have a hierarchy like this ?
>
> http {
> // log format
> stream {
> server {
> // acc
so can I have a hierarchy like this ?
http {
// log format
stream {
server {
// access log
}
}
}
On Tue, Apr 25, 2017 at 1:38 PM, Robert Paprocki <
rpapro...@fearnothingproductions.net> wrote:
> What you're doing doesn't quite make sense. You're tryi
What you're doing doesn't quite make sense. You're trying to log HTTP data
inside a stream block. That doesn't work. There's no such concept of
$status, $http_referer, etc, inside a stream {} block.
Have a read of the log_format docs:
http://nginx.org/en/docs/http/ngx_http_log_module.html#log_form
I am trying to log all request / response in a stream with a lua script I
found in git hub and am having issues figuring out where to put the
log_format directive. Here is what I currently have :
stream {
log_format bodylog '$remote_addr - $remote_user [$time_local] '
'"$request" $statu
this might be helpful -
http://stackoverflow.com/questions/12315832/how-to-fix-nginx-throws-400-bad-request-headers-on-any-header-testing-tools/17289826#comment16555393_12315832
On Wed, Apr 19, 2017 at 7:53 PM, Jeff Dyke wrote:
> untested, but if you set error_log to the correct level, it should
untested, but if you set error_log to the correct level, it should log
there as it likely received a > 300 response from the backends. I don't
think you want these in your access logs, but i am suprised you don't get
some sort of non < 400 response in those logs. But it's been a long day
On W
Will it not be logged as a timeout either in access or error/log ?
On 20 April 2017 at 03:46, aT wrote:
> HI ,
>
> Is there a way to log all incoming requests on Nginx .
>
> Regardless of them being served or not .
>
> For example, In case of surge of crawler hits , if the upstream backend
> ca
HI ,
Is there a way to log all incoming requests on Nginx .
Regardless of them being served or not .
For example, In case of surge of crawler hits , if the upstream backend
cannot perform and requests hang , nginx will not log any such failed
request .
How can we log them to have more detail
Hi, I use Nginx with Passenger and the problem I have is that I get "some"
application log entries in /var/log/nginx/error.log.
The problem is that the log is turned off and also pointing to another
location (/mnt/nginx/logs/):
My configs:
nginx.conf
http
error_log /mnt/nginx/logs/err
Thank you! I've got it all set up now, thanks for the pointer to $
EscapeControlCharactersOnReceive
On Thu, Feb 25, 2016 at 6:25 PM, Ekaterina Kukushkina wrote:
> Hello CJ,
>
>
> > On 26 Feb 2016, at 00:50, CJ Ess wrote:
> >
> > I would really like to output my nginx access log to syslog in a t
Hello CJ,
> On 26 Feb 2016, at 00:50, CJ Ess wrote:
>
> I would really like to output my nginx access log to syslog in a tab
> delimited format.
>
> I'm using the latest nginx and rsyslogd 7.2.5
>
> I haven't found an example of doing this, I'm wondering if/how to add tabs to
> the format i
I would really like to output my nginx access log to syslog in a tab
delimited format.
I'm using the latest nginx and rsyslogd 7.2.5
I haven't found an example of doing this, I'm wondering if/how to add tabs
to the format in the log_format directive
And also if there is anything I need to do to
On Sat, Feb 20, 2016 at 02:11:38PM +0500, Muhammad Rehan wrote:
Hi there,
> Thanks for the reply, I have setup the directives such that rate is 30r/s
> and burst is 10. So, my question is; why are these requests being limited
> when averaging at 10.2 while I have set the rate to 30r/s in req_limi
Thanks for the reply, I have setup the directives such that rate is 30r/s
and burst is 10. So, my question is; why are these requests being limited
when averaging at 10.2 while I have set the rate to 30r/s in req_limit_zone?
On Feb 20, 2016 11:37 AM, "aT" wrote:
> excess: 10.200 in above log mean
excess: 10.200 in above log means that the requests are being limited as
they are averaging at 10.2 requests / second .
Storage size is defined with a unit , For example zone=one:10m . This
means 10 MB .
I hope it helped.
On Sat, Feb 20, 2016 at 12:54 AM, Muhammad Rehan
wrote:
> Hi, I am st
Hi, I am still looking for reply. Does anyone know about this?
On Feb 18, 2016 12:33 AM, "Muhammad Rehan"
wrote:
> Hey folks,
>
> I would like to ask what does the 10.200 right after 'excess:' indicate in
> the following log? Is this storage size in MBs for zone? I am really
> confused about that
Hey folks,
I would like to ask what does the 10.200 right after 'excess:' indicate in
the following log? Is this storage size in MBs for zone? I am really
confused about that; I have gone through documentation pretty well but not
able to find these attributes used in error logs.
*2014/11/20 17:28
Hello!
On Mon, Jan 11, 2016 at 11:21:35PM -0500, tammini wrote:
> Does that mean once a websocket connection is opened successfully, any
> subsequent requests sent on that connection cannot be logged ?
No HTTP requests can be sent into a connection which was upgraded
to a WebSocket connection.
Only time you see a log for a web socket connection is when it get
disconnected. So you will not see a log when it connects, transfer data
over it.
On Mon, Jan 11, 2016 at 8:21 PM, tammini
wrote:
> Does that mean once a websocket connection is opened successfully, any
> subsequent requests sent
Does that mean once a websocket connection is opened successfully, any
subsequent requests sent on that connection cannot be logged ?
Thanks.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263878,263938#msg-263938
___
nginx mailing list
ngi
Hello!
On Wed, Jan 06, 2016 at 09:11:54AM -0500, tammini wrote:
> Is it possible to log websocket requests in nginx access log ? Or is this
> logging restricted only to http requests ?
WebSocket requests are no different from other HTTP requests -
they just establish a WebSocket conn
Is it possible to log websocket requests in nginx access log ? Or is this
logging restricted only to http requests ?
tammini
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263878,263878#msg-263878
___
nginx mailing list
nginx@nginx.org
http
Hi,
I'm using the Nginx 1.8.0 rpm found on
http://nginx.org/packages/centos/7/x86_64/RPMS/ with a config that has
been working fine so far with Nginx 1.6.x.
The problem is that sometimes I get 500 Internal Server Errors but even
though have the line "error_log /var/log/nginx/error.log warn;" in
n
hi,
is there a way to log access (ip, date, size of payload) within the
stream-module?
i found error - log configurable for the stream only so far.
cheers,
mex
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,261411,261411#msg-261411
___
>>>> On Wed, Jun 24, 2015 at 7:03 AM, Vladimir Homutov wrote:
>>>>>> On Wed, Jun 24, 2015 at 06:12:49AM -0400, Danomi Czaski wrote:
>>>>>> Hello,
>>>>>>
>>>>>> On Sun, Jun 21, 2015 at 8:19 AM, Andrew H
ed, Jun 24, 2015 at 06:12:49AM -0400, Danomi Czaski wrote:
> >> >> Hello,
> >> >>
> >> >> On Sun, Jun 21, 2015 at 8:19 AM, Andrew Holway
> >> >> wrote:
> >> >> > Hallo!
> >> >> >
> >> >> >
t;> >>
>> >> On Sun, Jun 21, 2015 at 8:19 AM, Andrew Holway
>> >> wrote:
>> >> > Hallo!
>> >> >
>> >> > Using rsyslog I have set up a logging socket and confirmed that its
>> >> > working
>
rew Holway
> >> wrote:
> >> > Hallo!
> >> >
> >> > Using rsyslog I have set up a logging socket and confirmed that its
> >> > working
> >> > by piping in some stuff to "logger -u /dev/log"
> >> > nginx/1.8.0 does not se
On Wed, Jun 24, 2015 at 7:03 AM, Vladimir Homutov wrote:
> On Wed, Jun 24, 2015 at 06:12:49AM -0400, Danomi Czaski wrote:
>> Hello,
>>
>> On Sun, Jun 21, 2015 at 8:19 AM, Andrew Holway
>> wrote:
>> > Hallo!
>> >
>> > Using rsyslog I have
On Wed, Jun 24, 2015 at 06:12:49AM -0400, Danomi Czaski wrote:
> Hello,
>
> On Sun, Jun 21, 2015 at 8:19 AM, Andrew Holway
> wrote:
> > Hallo!
> >
> > Using rsyslog I have set up a logging socket and confirmed that its working
> > by piping in some stuff to
Hello,
On Sun, Jun 21, 2015 at 8:19 AM, Andrew Holway
wrote:
> Hallo!
>
> Using rsyslog I have set up a logging socket and confirmed that its working
> by piping in some stuff to "logger -u /dev/log"
> nginx/1.8.0 does not seem to be dumping in logs however. The nginx
1 - 100 of 170 matches
Mail list logo
