Re: hfaxd filling my logs with `-> Got a: 127.0.0.1[13] (how to stop this??)
"David C. Rankin" <[email protected]> Fri, 27 Oct 2017 13:53:29 -0500
| Newsgroups | gmane.comp.telephony.fax.hylafax.user |
|---|---|
| Organization | Rankin Law Firm, PLLC |
| Message-ID | <[email protected]> |
On 10/27/2017 11:33 AM, Aidan Van Dyk wrote: > Looks like one server is capturing "LOG_DEBUG" to system logs, and the other > isn't. The "Got a: <ip/port>" is a LOG_DEBUG message on in the EPTR command. > There are a smattering of LOG_DEBUG syslogs in the code, those could probably > be removed. > > If you had hfaxd's ServerTracing set to something more chatty (such as 0x33) > you would probably see who (network wise) had connected and issued the EPRT > command. > > a. > Aidan, Thanks for the reply. I've been pulling my hair out on this. I wonder if it could be the Sharp Copier (older M355N) I have attached to the network. It has a separate fax module (and also supports network delivery of faxes) and it also a network scan-to-pdf via a ftp link to a samba share on the server (that's all on port 22, so it shouldn't matter). I wonder if it has a 20 sec ping or something that is checking to make sure the a network link is up and is somehow triggering the logging? I'll have to find the manual and see if any of its communications are over the same port. Oh that would be frustrating if a dang copier was pinging the hylafax port. Right now, the copier is asleep and I'm not getting any of the annoying logs. So I guess the plan going forward is to increase ServerTracing for hfaxd to try and identify who the culprit is. I think I have an understanding of what to do. When I up ServerTracing to 0x33, will it provide information I can identify the culprit with?, or will it be some cryptic bitfield I have to find a reference for? -- David C. Rankin, J.D.,P.E. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null *To learn about commercial HylaFAX(tm) support, mail [email protected].*