My default explanation now is that somehow jetty or ubuntu supplied the
wrong IP's for logging.
Bill
On 1/18/18 1:45 AM, Bill wrote:
Does anyone watch the spiders? I actually feed them by using
interesting math to derive file creation times that I publish,
unrelated to the actual file, in or
It looks like wireshark doesn't display the pid, but it will give useful
info if I see another probe in the server log.
Thanks!
On 01/19/2018 12:46 AM, Bill wrote:
I haven't watched the wire for a long time, I guess it'd be possible
to filter for packets going to my website. No action in the
I haven't watched the wire for a long time, I guess it'd be possible to
filter for packets going to my website. No action in the log. Ideally a
monitor process would filter and check the process id on the spot.
Taking a look at wireshark.
On 01/18/2018 11:20 PM, Simone Bordet wrote:
Hi,
On
Hi,
On Thu, Jan 18, 2018 at 10:45 AM, Bill wrote:
>
> Does anyone watch the spiders?
[snip]
Have you tried using wireshark to know the client socket being opened
and the lsof/ss/netstat on your machines to understand what process
opened that socket ?
--
Simone Bordet
http://cometd.org
ht
