|
1
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
2
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': adding an RR at 'HP1920G-INFO.tambosi.blz' A
|
|
3
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': adding an RR at 'HP1920G-INFO.tambosi.blz' DHCID
|
|
4
|
Aug 31 16:27:36 250403ssalase dhcpd: DHCPREQUEST for 192.168.1.173 (192.168.1.1) from 5c:8a:38:94:78:67 (HP1920G-INFO) via eth1
|
|
5
|
Aug 31 16:27:36 250403ssalase dhcpd: DHCPACK on 192.168.1.173 to 5c:8a:38:94:78:67 (HP1920G-INFO) via eth1
|
|
6
|
Aug 31 16:27:36 250403ssalase dhcpd: Added new forward map from HP1920G-INFO.tambosi.blz to 192.168.1.173
|
|
7
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
8
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': deleting rrset at '173.1.168.192.in-addr.arpa' PTR
|
|
9
|
Aug 31 16:27:36 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': adding an RR at '173.1.168.192.in-addr.arpa' PTR
|
|
10
|
Aug 31 16:27:36 250403ssalase dhcpd: Added reverse map from 173.1.168.192.in-addr.arpa. to HP1920G-INFO.tambosi.blz
|
|
11
|
Aug 31 16:28:22 250403ssalase dhcpd: DHCPDISCOVER from a0:d3:c1:2d:ed:69 via eth1
|
|
12
|
Aug 31 16:28:23 250403ssalase dhcpd: DHCPOFFER on 192.168.1.176 to a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
13
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
14
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': adding an RR at '250403winfo01.tambosi.blz' A
|
|
15
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': adding an RR at '250403winfo01.tambosi.blz' DHCID
|
|
16
|
Aug 31 16:28:23 250403ssalase dhcpd: DHCPREQUEST for 192.168.1.176 (192.168.1.1) from a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
17
|
Aug 31 16:28:23 250403ssalase dhcpd: DHCPACK on 192.168.1.176 to a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
18
|
Aug 31 16:28:23 250403ssalase dhcpd: Added new forward map from 250403winfo01.tambosi.blz to 192.168.1.176
|
|
19
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
20
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': deleting rrset at '176.1.168.192.in-addr.arpa' PTR
|
|
21
|
Aug 31 16:28:23 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': adding an RR at '176.1.168.192.in-addr.arpa' PTR
|
|
22
|
Aug 31 16:28:23 250403ssalase dhcpd: Added reverse map from 176.1.168.192.in-addr.arpa. to 250403winfo01.tambosi.blz
|
|
23
|
Aug 31 16:28:29 250403ssalase ntpd_intres[998]: host name not found: 0.debian.pool.ntp.org
|
|
24
|
Aug 31 16:28:29 250403ssalase ntpd_intres[998]: host name not found: 1.debian.pool.ntp.org
|
|
25
|
Aug 31 16:28:29 250403ssalase ntpd_intres[998]: host name not found: 2.debian.pool.ntp.org
|
|
26
|
Aug 31 16:28:29 250403ssalase ntpd_intres[998]: host name not found: 3.debian.pool.ntp.org
|
|
27
|
Aug 31 16:29:51 250403ssalase dhcpd: DHCPDISCOVER from a0:d3:c1:2d:ed:69 via eth1
|
|
28
|
Aug 31 16:29:52 250403ssalase dhcpd: DHCPOFFER on 192.168.1.175 to a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
29
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': update unsuccessful: 250403winfo01.tambosi.blz: 'name not in use' prerequisite not satisfied (YXDOMAIN)
|
|
30
|
Aug 31 16:29:52 250403ssalase dhcpd: DHCPREQUEST for 192.168.1.175 (192.168.1.1) from a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
31
|
Aug 31 16:29:52 250403ssalase dhcpd: DHCPACK on 192.168.1.175 to a0:d3:c1:2d:ed:69 (250403winfo01) via eth1
|
|
32
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
33
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': deleting rrset at '250403winfo01.tambosi.blz' A
|
|
34
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone 'tambosi.blz/IN': adding an RR at '250403winfo01.tambosi.blz' A
|
|
35
|
Aug 31 16:29:52 250403ssalase dhcpd: Added new forward map from 250403winfo01.tambosi.blz to 192.168.1.175
|
|
36
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: signer "250403ssalase.tambosi.blz" approved
|
|
37
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': deleting rrset at '175.1.168.192.in-addr.arpa' PTR
|
|
38
|
Aug 31 16:29:52 250403ssalase named[612]: client 127.0.0.1#8344/key 250403ssalase.tambosi.blz: updating zone '1.168.192.in-addr.arpa/IN': adding an RR at '175.1.168.192.in-addr.arpa' PTR
|
|
39
|
Aug 31 16:29:52 250403ssalase dhcpd: Added reverse map from 175.1.168.192.in-addr.arpa. to 250403winfo01.tambosi.blz
|
|
40
|
Aug 31 16:29:52 250403ssalase named[612]: error (network unreachable) resolving '_kerberos._tcp.RODARI.BLZ/SRV/IN': 2001:500:2f::f#53
|
|
41
|
Aug 31 16:29:52 250403ssalase named[612]: error (network unreachable) resolving '_kerberos._tcp.RODARI.BLZ/SRV/IN': 2001:500:1::803f:235#53
|
|
42
|
Aug 31 16:29:52 250403ssalase named[612]: error (network unreachable) resolving '_kerberos-master._udp.RODARI.BLZ/SRV/IN': 2001:7fe::53#53
|
|
43
|
Aug 31 16:29:52 250403ssalase named[612]: error (network unreachable) resolving '_kerberos-master._udp.RODARI.BLZ/SRV/IN': 2001:7fd::1#53
|
|
44
|
Aug 31 16:30:01 250403ssalase CRON[1871]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi)
|
|
45
|
Aug 31 16:30:01 250403ssalase CRON[1872]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
|
|
46
|
Aug 31 16:30:05 250403ssalase kadmind[619]: kadmind: starting...
|
|
47
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO USING CONF FILE /etc/octofuss-client/server.conf
|
|
48
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO 127.0.0.1
|
|
49
|
Aug 31 16:30:28 250403ssalase twistd3[617]: DEBUG Getting upgrades for 250403ssalase.school.fuss.bz.it
|
|
50
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO No upgrades to be managed
|
|
51
|
Aug 31 16:30:28 250403ssalase twistd3[617]: DEBUG Getting scripts
|
|
52
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO No scripts to be executed
|
|
53
|
Aug 31 16:30:28 250403ssalase twistd3[617]: DEBUG Getting printers
|
|
54
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO No printers to configure
|
|
55
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO Syncing privileges
|
|
56
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO Starting remote install check...
|
|
57
|
Aug 31 16:30:28 250403ssalase twistd3[617]: INFO No packages
|
|
58
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'detectportal.firefox.com/A/IN': 2001:500:3::42#53
|
|
59
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'detectportal.firefox.com/AAAA/IN': 2001:500:3::42#53
|
|
60
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'detectportal.firefox.com/A/IN': 2001:503:a83e::2:30#53
|
|
61
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns4-64.akam.net/A/IN': 2001:500:d937::30#53
|
|
62
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns4-64.akam.net/AAAA/IN': 2001:500:d937::30#53
|
|
63
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns7-66.akam.net/A/IN': 2001:500:d937::30#53
|
|
64
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns7-66.akam.net/AAAA/IN': 2001:500:d937::30#53
|
|
65
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns5-65.akam.net/A/IN': 2001:500:d937::30#53
|
|
66
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns1-240.akam.net/A/IN': 2001:500:d937::30#53
|
|
67
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns1-240.akam.net/AAAA/IN': 2001:500:d937::30#53
|
|
68
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-258.awsdns-32.com/A/IN': 2600:9000:5302:6000::1#53
|
|
69
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-258.awsdns-32.com/A/IN': 2600:9000:5300:2100::1#53
|
|
70
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-679.awsdns-20.net/AAAA/IN': 2600:9000:5303:1600::1#53
|
|
71
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-258.awsdns-32.com/A/IN': 2600:9000:5304:a000::1#53
|
|
72
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-258.awsdns-32.com/A/IN': 2600:9000:5306:e000::1#53
|
|
73
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-1655.awsdns-14.co.uk/AAAA/IN': 2001:502:ad09::3#53
|
|
74
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'firefox.com/DS/IN': 2001:502:1ca1::30#53
|
|
75
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-1655.awsdns-14.co.uk/AAAA/IN': 2600:9000:5303:8e00::1#53
|
|
76
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-1655.awsdns-14.co.uk/AAAA/IN': 2600:9000:5305:d100::1#53
|
|
77
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'ns-1655.awsdns-14.co.uk/AAAA/IN': 2600:9000:5307:1200::1#53
|
|
78
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'com/DNSKEY/IN': 2001:503:d414::30#53
|
|
79
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'mozilla.com/DS/IN': 2001:503:c27::2:30#53
|
|
80
|
Aug 31 16:30:33 250403ssalase named[612]: error (network unreachable) resolving 'snippets.cdn.mozilla.net/AAAA/IN': 2600:1401:2::f0#53
|
|
81
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-206.awsdns-25.com/A/IN': 2001:502:8cc::30#53
|
|
82
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-206.awsdns-25.com/AAAA/IN': 2001:502:8cc::30#53
|
|
83
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/A/IN': 2001:500:40::1#53
|
|
84
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-772.awsdns-32.net/A/IN': 2001:502:8cc::30#53
|
|
85
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/AAAA/IN': 2001:500:40::1#53
|
|
86
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/A/IN': 2001:500:c::1#53
|
|
87
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/AAAA/IN': 2001:500:c::1#53
|
|
88
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/A/IN': 2001:500:f::1#53
|
|
89
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/AAAA/IN': 2001:500:f::1#53
|
|
90
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1537.awsdns-00.co.uk/A/IN': 2401:fd80:400::1#53
|
|
91
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/A/IN': 2001:500:48::1#53
|
|
92
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/AAAA/IN': 2001:500:48::1#53
|
|
93
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1537.awsdns-00.co.uk/AAAA/IN': 2401:fd80:400::1#53
|
|
94
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/A/IN': 2001:500:b::1#53
|
|
95
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1507.awsdns-60.org/AAAA/IN': 2001:500:b::1#53
|
|
96
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1537.awsdns-00.co.uk/A/IN': 2600:9000:5303:8000::1#53
|
|
97
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-772.awsdns-32.net/A/IN': 2600:9000:5303:2200::1#53
|
|
98
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/AAAA/IN': 2001:503:39c1::30#53
|
|
99
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/A/IN': 2001:503:39c1::30#53
|
|
100
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/AAAA/IN': 2001:502:7094::30#53
|
|
101
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/A/IN': 2001:502:7094::30#53
|
|
102
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/AAAA/IN': 2001:503:d2d::30#53
|
|
103
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/A/IN': 2001:503:d2d::30#53
|
|
104
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/AAAA/IN': 2001:501:b1f9::30#53
|
|
105
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/A/IN': 2001:501:b1f9::30#53
|
|
106
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'a1089.d.akamai.net/AAAA/IN': 2600:1480:1::c1#53
|
|
107
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1306.awsdns-35.org/AAAA/IN': 2600:9000:5306:6300::1#53
|
|
108
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1713.awsdns-22.co.uk/A/IN': 2600:9000:5307:1a00::1#53
|
|
109
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-1713.awsdns-22.co.uk/A/IN': 2600:9000:5303:9600::1#53
|
|
110
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-525.awsdns-01.net/A/IN': 2600:9000:5305:4100::1#53
|
|
111
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-377.awsdns-47.com/AAAA/IN': 2600:9000:5306:ef00::1#53
|
|
112
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-525.awsdns-01.net/A/IN': 2600:9000:5307:8100::1#53
|
|
113
|
Aug 31 16:30:34 250403ssalase named[612]: error (network unreachable) resolving 'ns-377.awsdns-47.com/A/IN': 2600:9000:5306:ef00::1#53
|