search for: sysquery

Displaying 4 results from an estimated 4 matches for "sysquery".

Did you mean: sqlquery
2003 Oct 23
3
/var partition overflow (due to spyware?) in FreeBSD default install
...n't explain all of the symptoms we were seeing. This afternoon, I examined the machines and discovered the problem: full /var partitions caused by huge /var/log/messages files. Inspection of the files reveals hundreds of thousands of messages of the form: Oct 23 16:00:07 victim named[326]: sysquery: no addrs found for root NS (ns0.opennic.glue) Oct 23 16:00:07 victim named[326]: sysquery: no addrs found for root NS (ns1.opennic.glue) Oct 23 16:00:07 victim named[326]: sysquery: no addrs found for root NS (ns3.opennic.glue) Oct 23 16:00:07 victim named[326]: sysquery: no addrs found for roo...
1998 Jun 24
0
Bind log question
In my /var/log/messages file, in recent days I have been receiving numerous messages such as: Jun 23 15:02:50 OUR-HOST named[577]: sysquery: nslookup reports danger (dns.SUBNET1.OTHER.DOMAIN.AAA.BBB.CCC.in-addr.arpa) Jun 23 15:02:51 OUR-HOST named[577]: sysquery: nslookup reports danger (HOST2.SUBNET2.OTHER.DOMAIN.AAA.BBB.CCC.in-addr.arpa) Jun 23 15:02:51 OUR-HOST named[577]: sysquery: nslookup reports danger (dns.SUBNET3.OTHER.D...
2003 Nov 13
2
What could be on udp:48152
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm running stock FreeBSD with services running: samba (connections allowed only from local network), lpd (same), bind (all interfaces), apache (all), zope (local) This machine is home gateway/http/printserver. Recently some strange things happened as my printer all of sudden started to print stuff when nobody prints... luckily (or
2001 Mar 03
0
kernel & automount errors in messages log
...13]: Forwarding source address is [0.0.0.0].1024 Feb 26 18:56:10 Nemesis named: named startup succeeded Feb 26 18:56:10 Nemesis named[614]: group = named Feb 26 18:56:10 Nemesis named[614]: user = named Feb 26 18:56:10 Nemesis named[614]: Ready to answer queries. Feb 26 18:56:10 Nemesis named[614]: sysquery: nlookup error on ? Feb 26 18:56:10 Nemesis sshd: Starting sshd: Feb 26 18:56:11 Nemesis sshd: succeeded Feb 26 18:56:11 Nemesis sshd: ^[[60G Feb 26 18:56:11 Nemesis sshd[622]: Server listening on 0.0.0.0 port 22. Feb 26 18:56:11 Nemesis sshd[622]: Generating 768 bit RSA key. Feb 26 18:56:11 Nemes...