-- Logs begin at Wed 2017-06-14 08:57:30 PDT, end at Wed 2017-06-14 09:51:02 PDT. -- Jun 14 08:57:30 hostname kernel: ACPI: RSDP 0x00000000000FE700 000024 (v02 HPQOEM) Jun 14 08:57:30 hostname kernel: ACPI: XSDT 0x00000000CF417078 000074 (v01 HPQOEM SLIC-BPC 01072009 AMI 00010013) Jun 14 08:57:30 hostname kernel: ACPI: FACP 0x00000000CF41EC40 0000F4 (v04 HPQOEM SLIC-BPC 01072009 AMI 00010013) Jun 14 08:57:30 hostname kernel: ACPI: DSDT 0x00000000CF417180 007AC0 (v02 HPQOEM SLIC-BPC 00000008 INTL 20051117) Jun 14 08:57:30 hostname kernel: ACPI: FACS 0x00000000CF512F80 000040 Jun 14 08:57:30 hostname kernel: ACPI: APIC 0x00000000CF41ED38 000072 (v03 HPQOEM SLIC-BPC 01072009 AMI 00010013) Jun 14 08:57:30 hostname kernel: ACPI: SSDT 0x00000000CF41EDB0 000102 (v01 AMICPU PROC 00000001 MSFT 03000001) Jun 14 08:57:30 hostname kernel: ACPI: MCFG 0x00000000CF41EEB8 00003C (v01 HPQOEM SLIC-BPC 01072009 MSFT 00000097) Jun 14 08:57:30 hostname kernel: ACPI: HPET 0x00000000CF41EEF8 000038 (v01 HPQOEM SLIC-BPC 01072009 AMI. 00000004) Jun 14 08:57:30 hostname kernel: ACPI: ASF! 0x00000000CF41EF30 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240) Jun 14 08:57:30 hostname kernel: ACPI: SSDT 0x00000000CF41EFD0 005270 (v01 COMPAQ WMI 00000001 MSFT 03000001) Jun 14 08:57:30 hostname kernel: ACPI: SLIC 0x00000000CF424240 000176 (v01 HPQOEM SLIC-BPC 00000001 00000000) Jun 14 08:57:30 hostname kernel: ACPI: TCPA 0x00000000CF4243B8 000032 (v02 APTIO4 NAPAASF 00000001 MSFT 01000013) Jun 14 08:57:30 hostname kernel: ACPI: DMAR 0x00000000CF4243F0 0000B0 (v01 ALASKA A M I 00000001 INTL 00000001) Jun 14 08:57:30 hostname kernel: ACPI: 3 ACPI AML tables successfully acquired and loaded Jun 14 08:57:30 hostname kernel: Jun 14 08:57:30 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Jun 14 08:57:30 hostname kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Jun 14 08:57:30 hostname kernel: #2 Jun 14 08:57:30 hostname kernel: #3 Jun 14 08:57:30 hostname kernel: PCCT header not found. Jun 14 08:57:30 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Jun 14 08:57:30 hostname kernel: ACPI: Dynamic OEM Table Load: Jun 14 08:57:30 hostname kernel: ACPI: SSDT 0x00000000EFCE6800 00038C (v01 AMI IST 00000001 MSFT 03000001) Jun 14 08:57:30 hostname kernel: ACPI: Dynamic OEM Table Load: Jun 14 08:57:30 hostname kernel: ACPI: SSDT 0x00000000EFCF39C0 000084 (v01 AMI CST 00000001 MSFT 03000001) Jun 14 08:57:30 hostname kernel: ACPI: Enabled 3 GPEs in block 00 to 3F Jun 14 08:57:30 hostname kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Jun 14 08:57:30 hostname kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 Jun 14 08:57:30 hostname kernel: ------------[ cut here ]------------ Jun 14 08:57:30 hostname kernel: WARNING: CPU: 0 PID: 1 at /build/linux-_Y6dJL/linux-4.8.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 Jun 14 08:57:30 hostname kernel: x86/mm: Found insecure W+X mapping at address c00a0000/0xc00a0000 Jun 14 08:57:30 hostname kernel: Modules linked in: Jun 14 08:57:30 hostname kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-55-generic #58-Ubuntu Jun 14 08:57:30 hostname kernel: Hardware name: Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.29 04/04/2016 Jun 14 08:57:30 hostname kernel: dab5a967 b47fcda0 00200286 f08afe70 da3dc0c5 f08afeb4 daa3c224 f08afea0 Jun 14 08:57:30 hostname kernel: da07222a daa3c1ec f08afed4 00000001 daa3c224 000000e1 da068811 000000e1 Jun 14 08:57:30 hostname kernel: f08aff34 80000000 00000000 f08afec0 da072296 00000009 00000000 f08afeb4 Jun 14 08:57:30 hostname kernel: Call Trace: Jun 14 08:57:30 hostname kernel: [] dump_stack+0x58/0x73 Jun 14 08:57:30 hostname kernel: [] __warn+0xea/0x110 Jun 14 08:57:30 hostname kernel: [] ? note_page+0x6a1/0x880 Jun 14 08:57:30 hostname kernel: [] warn_slowpath_fmt+0x46/0x60 Jun 14 08:57:30 hostname kernel: [] note_page+0x6a1/0x880 Jun 14 08:57:30 hostname kernel: [] ptdump_walk_pgd_level_core+0x1f5/0x300 Jun 14 08:57:30 hostname kernel: [] ptdump_walk_pgd_level_checkwx+0x16/0x20 Jun 14 08:57:30 hostname kernel: [] mark_rodata_ro+0xfd/0x130 Jun 14 08:57:30 hostname kernel: [] kernel_init+0x2c/0x100 Jun 14 08:57:30 hostname kernel: [] ? schedule_tail+0x11/0x50 Jun 14 08:57:30 hostname kernel: [] ret_from_kernel_thread+0xe/0x24 Jun 14 08:57:30 hostname kernel: [] ? rest_init+0x70/0x70 Jun 14 08:57:30 hostname kernel: ---[ end trace a5a068ac37783387 ]--- Jun 14 08:57:32 hostname systemd[1]: squid.service: Unit cannot be reloaded because it is inactive. Jun 14 08:57:34 hostname systemd-tmpfiles[586]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jun 14 08:57:40 hostname systemd-udevd[599]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Jun 14 08:57:40 hostname systemd-udevd[603]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Jun 14 09:00:05 hostname logd[1359]: [1359]: WARN: Core dumps could be lost if multiple dumps occur. Jun 14 09:00:05 hostname logd[1359]: [1359]: WARN: Consider setting non-default value in /proc/sys/kernel/core_pattern (or equivalent) for maximum supportability Jun 14 09:00:05 hostname logd[1359]: [1359]: WARN: Consider setting /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability Jun 14 09:00:07 hostname smartd[1356]: Device: /dev/sdb [SAT], 3 Currently unreadable (pending) sectors Jun 14 09:00:07 hostname smartd[1356]: Device: /dev/sdb [SAT], 3 Offline uncorrectable sectors Jun 14 09:00:07 hostname systemd[1438]: nginx.service: Failed at step EXEC spawning /usr/sbin/nginx: No such file or directory Jun 14 09:00:07 hostname systemd[1]: Failed to start A high performance web server and a reverse proxy server. Jun 14 09:00:07 hostname systemd[1]: nginx.service: Failed with result 'exit-code'. Jun 14 09:00:08 hostname systemd[1]: squid.service: Unit cannot be reloaded because it is inactive. Jun 14 09:00:08 hostname NetworkManager[1316]: [1497456008.7037] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono Jun 14 09:00:10 hostname NetworkManager[1316]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Jun 14 09:00:11 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': SERVFAIL Jun 14 09:00:11 hostname kernel: audit_printk_skb: 54 callbacks suppressed Jun 14 09:00:11 hostname systemd[1]: binkd.service: Failed with result 'exit-code'. Jun 14 09:00:11 hostname systemd[1]: binkd.service: Failed with result 'exit-code'. Jun 14 09:00:11 hostname systemd-udevd[1629]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:11 hostname systemd[1]: binkd.service: Failed with result 'exit-code'. Jun 14 09:00:12 hostname NetworkManager[1316]: [1497456012.0417] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Jun 14 09:00:12 hostname systemd[1]: binkd.service: Failed with result 'exit-code'. Jun 14 09:00:12 hostname systemd[1]: binkd.service: Failed with result 'exit-code'. Jun 14 09:00:12 hostname systemd[1]: binkd.service: Start request repeated too quickly. Jun 14 09:00:12 hostname systemd[1]: Failed to start FidoTech TCP/IP mailer. Jun 14 09:00:12 hostname systemd[1]: binkd.service: Failed with result 'start-limit-hit'. Jun 14 09:00:15 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': SERVFAIL Jun 14 09:00:15 hostname dnsmasq[1793]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:15 hostname dnsmasq[1793]: FAILED to start up Jun 14 09:00:16 hostname NetworkManager[1316]: [1497456016.2495] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:16 hostname postfix/postfix-script[2018]: warning: group or other writable: /usr/lib/postfix/./libpostfix-tls.so.1 Jun 14 09:00:16 hostname postfix/postfix-script[2019]: warning: group or other writable: /usr/lib/postfix/./libpostfix-global.so.1 Jun 14 09:00:16 hostname postfix/postfix-script[2020]: warning: group or other writable: /usr/lib/postfix/./libpostfix-util.so.1 Jun 14 09:00:16 hostname postfix/postfix-script[2021]: warning: group or other writable: /usr/lib/postfix/./libpostfix-master.so.1 Jun 14 09:00:16 hostname postfix/postfix-script[2022]: warning: group or other writable: /usr/lib/postfix/./sbin/lmtp Jun 14 09:00:16 hostname postfix/postfix-script[2023]: warning: group or other writable: /usr/lib/postfix/./libpostfix-dns.so.1 Jun 14 09:00:16 hostname postfix/postfix-script[2024]: warning: group or other writable: /usr/lib/postfix/sbin/./lmtp Jun 14 09:00:16 hostname NetworkManager[1316]: [1497456016.4838] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:16 hostname systemd-udevd[2052]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:16 hostname dnsmasq[2085]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:16 hostname dnsmasq[2085]: FAILED to start up Jun 14 09:00:16 hostname postfix/postfix-script[2102]: warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ Jun 14 09:00:16 hostname NetworkManager[1316]: [1497456016.8974] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:17 hostname NetworkManager[1316]: [1497456017.2521] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:17 hostname systemd-udevd[2162]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:17 hostname dnsmasq[2165]: warning: no upstream servers configured Jun 14 09:00:17 hostname systemd[1]: squid.service: Unit cannot be reloaded because it is inactive. Jun 14 09:00:17 hostname dnsmasq[2247]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:17 hostname dnsmasq[2247]: FAILED to start up Jun 14 09:00:18 hostname NetworkManager[1316]: [1497456018.1429] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:18 hostname NetworkManager[1316]: [1497456018.4100] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:18 hostname systemd-udevd[2287]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:18 hostname dnsmasq[2321]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:18 hostname dnsmasq[2321]: FAILED to start up Jun 14 09:00:18 hostname NetworkManager[1316]: [1497456018.7864] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:18 hostname NetworkManager[1316]: [1497456018.7867] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:18 hostname systemd-udevd[2336]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:18 hostname dnsmasq[2369]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:18 hostname dnsmasq[2369]: FAILED to start up Jun 14 09:00:19 hostname NetworkManager[1316]: [1497456019.0515] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:19 hostname NetworkManager[1316]: [1497456019.2441] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:19 hostname systemd-udevd[2391]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:19 hostname dnsmasq[2424]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:19 hostname dnsmasq[2424]: FAILED to start up Jun 14 09:00:19 hostname NetworkManager[1316]: [1497456019.5905] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:19 hostname NetworkManager[1316]: [1497456019.8576] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:19 hostname systemd-udevd[2532]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:20 hostname dnsmasq[2599]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:20 hostname dnsmasq[2599]: FAILED to start up Jun 14 09:00:20 hostname NetworkManager[1316]: [1497456020.1761] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:20 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:20 hostname NetworkManager[1316]: [1497456020.3747] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:20 hostname systemd-udevd[2813]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:20 hostname dnsmasq[2877]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:20 hostname dnsmasq[2877]: FAILED to start up Jun 14 09:00:20 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:20 hostname NetworkManager[1316]: [1497456020.9580] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:21 hostname NetworkManager[1316]: [1497456021.1686] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:21 hostname systemd-udevd[3154]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:21 hostname dnsmasq[3187]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:21 hostname dnsmasq[3187]: FAILED to start up Jun 14 09:00:21 hostname NetworkManager[1316]: [1497456021.3022] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:21 hostname NetworkManager[1316]: [1497456021.3025] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:21 hostname systemd-udevd[3202]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:21 hostname dnsmasq[3235]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:21 hostname dnsmasq[3235]: FAILED to start up Jun 14 09:00:21 hostname NetworkManager[1316]: [1497456021.6539] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:21 hostname NetworkManager[1316]: [1497456021.8799] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:21 hostname systemd-udevd[3250]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:22 hostname dnsmasq[3284]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:22 hostname dnsmasq[3284]: FAILED to start up Jun 14 09:00:22 hostname NetworkManager[1316]: [1497456022.1965] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:22 hostname NetworkManager[1316]: [1497456022.3593] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:22 hostname systemd-udevd[3299]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:22 hostname dnsmasq[3332]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:22 hostname dnsmasq[3332]: FAILED to start up Jun 14 09:00:22 hostname NetworkManager[1316]: [1497456022.6072] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:22 hostname NetworkManager[1316]: [1497456022.7574] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:22 hostname systemd-udevd[3347]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:22 hostname dnsmasq[3380]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:22 hostname dnsmasq[3380]: FAILED to start up Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.0766] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.2760] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:23 hostname systemd-udevd[3395]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:23 hostname dnsmasq[3451]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:23 hostname dnsmasq[3451]: FAILED to start up Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.5610] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.7200] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:23 hostname systemd-udevd[3661]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.8720] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:23 hostname dnsmasq[3724]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:23 hostname dnsmasq[3724]: FAILED to start up Jun 14 09:00:23 hostname NetworkManager[1316]: [1497456023.8723] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:23 hostname systemd-udevd[3765]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:24 hostname dnsmasq[3832]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:24 hostname dnsmasq[3832]: FAILED to start up Jun 14 09:00:24 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:24 hostname NetworkManager[1316]: [1497456024.2417] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:24 hostname NetworkManager[1316]: [1497456024.4151] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:24 hostname systemd-udevd[4060]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:24 hostname dnsmasq[4093]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:24 hostname dnsmasq[4093]: FAILED to start up Jun 14 09:00:24 hostname NetworkManager[1316]: [1497456024.5436] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:24 hostname NetworkManager[1316]: [1497456024.5438] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:24 hostname systemd-udevd[4170]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:24 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:24 hostname dnsmasq[4226]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:24 hostname dnsmasq[4226]: FAILED to start up Jun 14 09:00:24 hostname NetworkManager[1316]: [1497456024.8190] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:25 hostname NetworkManager[1316]: [1497456025.0238] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:25 hostname systemd-udevd[4433]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:25 hostname dnsmasq[4466]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:25 hostname dnsmasq[4466]: FAILED to start up Jun 14 09:00:25 hostname NetworkManager[1316]: [1497456025.2764] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:25 hostname NetworkManager[1316]: [1497456025.4226] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:25 hostname systemd-udevd[4481]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:25 hostname dnsmasq[4514]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:25 hostname dnsmasq[4514]: FAILED to start up Jun 14 09:00:25 hostname NetworkManager[1316]: [1497456025.6998] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:25 hostname NetworkManager[1316]: [1497456025.8734] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:25 hostname systemd-udevd[4529]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:26 hostname dnsmasq[4562]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:26 hostname dnsmasq[4562]: FAILED to start up Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.1665] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.3218] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:26 hostname systemd-udevd[4577]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:26 hostname dnsmasq[4610]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:26 hostname dnsmasq[4610]: FAILED to start up Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.4617] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.4623] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:26 hostname systemd-udevd[4625]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:26 hostname dnsmasq[4658]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:26 hostname dnsmasq[4658]: FAILED to start up Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.7033] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.8537] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:26 hostname systemd-udevd[4675]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:26 hostname dnsmasq[4734]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.9947] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:26 hostname dnsmasq[4734]: FAILED to start up Jun 14 09:00:26 hostname NetworkManager[1316]: [1497456026.9951] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:27 hostname systemd-udevd[4807]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:27 hostname dnsmasq[4852]: failed to create listening socket for 10.42.0.1: Address already in use Jun 14 09:00:27 hostname dnsmasq[4852]: FAILED to start up Jun 14 09:00:27 hostname NetworkManager[1316]: [1497456027.3312] dnsmasq-manager: dnsmasq exited with error: Network access problem (address in use, permissions) (2) Jun 14 09:00:27 hostname ModemManager[1323]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Jun 14 09:00:27 hostname ModemManager[1323]: Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port Jun 14 09:00:27 hostname NetworkManager[1316]: [1497456027.5314] device (bridge0): Activation: failed for connection 'Bridge connection 1' Jun 14 09:00:27 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:27 hostname systemd-udevd[5115]: Could not generate persistent MAC address for bridge0: No such file or directory Jun 14 09:00:27 hostname named[1463]: binding TCP socket: address in use Jun 14 09:00:29 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:29 hostname named[1463]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled Jun 14 09:00:48 hostname systemd[1]: Failed to start Network Manager Wait Online. Jun 14 09:00:48 hostname systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'. Jun 14 09:00:48 hostname iscsid[6180]: iSCSI logger with pid=6184 started! Jun 14 09:00:48 hostname iscsid[6184]: iSCSI daemon with pid=6185 started! Jun 14 09:00:49 hostname dhcrelay[6144]: No servers specified. Jun 14 09:00:49 hostname dhcrelay[6144]: Jun 14 09:00:49 hostname dhcrelay[6144]: If you think you have received this message due to a bug rather Jun 14 09:00:49 hostname dhcrelay[6144]: than a configuration issue please read the section on submitting Jun 14 09:00:49 hostname dhcrelay[6144]: bugs on either our web page at www.isc.org or in the README file Jun 14 09:00:49 hostname dhcrelay[6144]: before submitting a bug. These pages explain the proper Jun 14 09:00:49 hostname dhcrelay[6144]: process and the information we find helpful for debugging.. Jun 14 09:00:49 hostname dhcrelay[6144]: Jun 14 09:00:49 hostname dhcrelay[6144]: exiting. Jun 14 09:00:49 hostname systemd[1]: isc-dhcp-relay.service: Failed with result 'exit-code'. Jun 14 09:00:49 hostname kernel: ipmi_si: Could not set up I/O space Jun 14 09:01:03 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:01:16 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:01:16 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:01:16 hostname lightdm[6413]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 14 09:01:18 hostname lightdm[6413]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 14 09:01:19 hostname systemd-udevd[6984]: Could not generate persistent MAC address for virbr0: No such file or directory Jun 14 09:01:20 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:01:20 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:01:44 hostname maas.networks.monitor[6170]: [info] Networks monitoring service: Process ID 6170 assumed responsibility. Jun 14 09:01:48 hostname pulseaudio[7420]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Jun 14 09:01:48 hostname pulseaudio[7420]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Jun 14 09:01:49 hostname asterisk[6145]: radcli: rc_read_config: rc_read_config: can't open /etc/radiusclient-ng/radiusclient.conf: No such file or directory Jun 14 09:01:49 hostname asterisk[6145]: radcli: rc_read_config: rc_read_config: can't open /etc/radiusclient-ng/radiusclient.conf: No such file or directory Jun 14 09:01:49 hostname at-spi-bus-laun[7550]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Jun 14 09:01:49 hostname org.a11y.Bus[7425]: Activating service name='org.a11y.atspi.Registry' Jun 14 09:01:50 hostname org.a11y.Bus[7425]: Successfully activated service 'org.a11y.atspi.Registry' Jun 14 09:01:52 hostname mate-session[7304]: WARNING: Unable to find provider '' of required component 'dock' Jun 14 09:01:57 hostname maas.import-images[6152]: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/ Jun 14 09:01:59 hostname named[1463]: zone 0.0.10.in-addr.arpa/IN: zone serial (425) unchanged. zone may fail to transfer to slaves. Jun 14 09:01:59 hostname named[1463]: zone 0.42.10.in-addr.arpa/IN: zone serial (425) unchanged. zone may fail to transfer to slaves. Jun 14 09:01:59 hostname named[1463]: zone 122.168.192.in-addr.arpa/IN: zone serial (425) unchanged. zone may fail to transfer to slaves. Jun 14 09:01:59 hostname named[1463]: zone 6.4.0.5.1.0.3.c.4.0.2.0.1.0.6.2.ip6.arpa/IN: zone serial (425) unchanged. zone may fail to transfer to slaves. Jun 14 09:01:59 hostname named[1463]: zone maas/IN: zone serial (425) unchanged. zone may fail to transfer to slaves. Jun 14 09:01:59 hostname FaxQueuer[6780]: MODEM /dev/faxCAPI appears to be wedged Jun 14 09:02:00 hostname pulseaudio[7729]: [pulseaudio] pid.c: Daemon already running. Jun 14 09:02:01 hostname maas.service_monitor[6152]: [info] Service 'ntp' has been restarted. Its current state is 'on' and 'running'. Jun 14 09:02:02 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:02:02 hostname maas.dhcp.probe[6170]: [error] Can't initiate DHCP probe; no RPC connection to region. Jun 14 09:02:03 hostname maas.bootsources[6152]: [info] Updated boot sources cache. Jun 14 09:02:03 hostname maas.bootresources[6152]: [info] Started importing of boot images from 1 source(s). Jun 14 09:02:03 hostname maas.import-images[6152]: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/ Jun 14 09:02:07 hostname maas.bootresources[6152]: [info] Importing images from source: http://images.maas.io/ephemeral-v3/daily/ Jun 14 09:02:08 hostname wnck-applet[7815]: Negative content width -5 (allocation 1, extents 3x3) while allocating gadget (node button, owner GtkToggleButton) Jun 14 09:02:08 hostname trashapplet[7906]: Allocating size to GtkImage 0x81c120f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Jun 14 09:02:10 hostname maas.refresh[6152]: [info] Refreshing rack controller hardware information. Jun 14 09:02:12 hostname pulseaudio[7667]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out Jun 14 09:02:16 hostname maas.bootresources[6152]: [info] Finished importing of boot images from 1 source(s). Jun 14 09:02:17 hostname org.blueman.Mechanism[1288]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Jun 14 09:02:17 hostname org.blueman.Mechanism[1288]: Unable to init server: Could not connect: Connection refused Jun 14 09:02:17 hostname org.blueman.Mechanism[1288]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Jun 14 09:02:17 hostname org.blueman.Mechanism[1288]: Unable to init server: Could not connect: Connection refused Jun 14 09:02:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:02:18 hostname blueman-mechani[8011]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Jun 14 09:02:24 hostname trashapplet[7906]: Allocating size to GtkImage 0x81c120f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Jun 14 09:02:25 hostname clock-applet[7924]: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./gobject/gsignal.c:2523: signal 'size_request' is invalid for instance '0x80a0ec48' of type 'GtkLabel' Jun 14 09:02:25 hostname clock-applet[7924]: Negative content width -5 (allocation 1, extents 3x3) while allocating gadget (node button, owner GtkToggleButton) Jun 14 09:03:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:03:33 hostname maas.refresh[6152]: [error] http error [400] Jun 14 09:04:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:05:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:05:46 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:05:46 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:05:47 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:05:47 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:05:53 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:05:53 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:05:54 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:05:54 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:06:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:07:00 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:07:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:07:30 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:07:30 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:07:31 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:07:31 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:07:34 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:07:34 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:07:35 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:07:35 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:08:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:08:26 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:27 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:27 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:27 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:38 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:38 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:39 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:08:39 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:08:43 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:44 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:48 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:53 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:53 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:08:54 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:08:54 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:09:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:10:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:11:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:12:01 hostname maas.dhcp.probe[6170]: [error] Can't initiate DHCP probe; no RPC connection to region. Jun 14 09:12:01 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:12:14 hostname systemd-tmpfiles[12839]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jun 14 09:12:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:13:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:14:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:15:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:16:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:17:02 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:17:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:17:19 hostname org.debian.apt[1288]: 09:17:19 AptDaemon [INFO]: Initializing daemon Jun 14 09:17:19 hostname org.debian.apt[1288]: /usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: PackageKitGlib was imported without specifying a version first. Use gi.require_version('PackageKitGlib', '1.0') before import to ensure that the right version gets loaded. Jun 14 09:17:19 hostname org.debian.apt[1288]: from gi.repository import PackageKitGlib as pk Jun 14 09:17:19 hostname org.debian.apt[1288]: 09:17:19 AptDaemon [INFO]: InstallPackages() was called: dbus.Array([dbus.String('caja-share'), dbus.String('samba')], signature=dbus.Signature('s')) Jun 14 09:17:20 hostname org.debian.apt[1288]: 09:17:20 AptDaemon.Trans [INFO]: Queuing transaction /org/debian/apt/transaction/16f9fd1581d54ae79e1575ff079b2f25 Jun 14 09:17:20 hostname org.debian.apt[1288]: 09:17:20 AptDaemon.Worker [INFO]: Simulating trans: /org/debian/apt/transaction/16f9fd1581d54ae79e1575ff079b2f25 Jun 14 09:17:20 hostname org.debian.apt[1288]: 09:17:20 AptDaemon.Worker [INFO]: Committing packages: dbus.Array([dbus.String('caja-share'), dbus.String('samba')], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')) Jun 14 09:17:26 hostname org.debian.apt[1288]: 09:17:26 AptDaemon.Worker [INFO]: Processing transaction /org/debian/apt/transaction/16f9fd1581d54ae79e1575ff079b2f25 Jun 14 09:18:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:18:20 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:20 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:21 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:18:21 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:18:33 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:33 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:33 hostname URfkill[16904]: Persistence file could not be loaded: No such file or directory Jun 14 09:18:33 hostname URfkill[16904]: Reading of RFKILL events failed Jun 14 09:18:33 hostname URfkill[16904]: failed to setup input device monitor Jun 14 09:18:33 hostname NetworkManager[1316]: Source ID 13 was not found when attempting to remove it Jun 14 09:18:33 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:35 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:36 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:36 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:36 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:36 hostname kernel: cgroup: new mount options do not match the existing superblock, will be ignored Jun 14 09:18:36 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:36 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:18:52 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:19:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:20:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:21:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:22:00 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:22:00 hostname maas.dhcp.probe[6170]: [error] Can't initiate DHCP probe; no RPC connection to region. Jun 14 09:22:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:23:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:23:27 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:23:27 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:24:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:25:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:26:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:27:02 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:27:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:28:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:28:27 hostname systemd[1]: samhain.service: Start operation timed out. Terminating. Jun 14 09:28:27 hostname systemd[1]: Failed to start samhain.service. Jun 14 09:28:27 hostname systemd[1]: samhain.service: Failed with result 'timeout'. Jun 14 09:28:56 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:28:56 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:29:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:29:28 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:29:45 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:29:45 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:29:47 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:29:47 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:29:48 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:29:49 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:30:09 hostname smartd[1356]: Device: /dev/sdb [SAT], 3 Currently unreadable (pending) sectors Jun 14 09:30:09 hostname smartd[1356]: Device: /dev/sdb [SAT], 3 Offline uncorrectable sectors Jun 14 09:30:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:31:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:32:03 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:32:03 hostname maas.dhcp.probe[6170]: [error] Can't initiate DHCP probe; no RPC connection to region. Jun 14 09:32:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:33:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:34:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:35:16 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:36:18 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:37:01 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:37:19 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:38:17 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:38:44 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:38:45 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:38:45 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:38:45 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:39:06 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:39:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:39:32 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:39:32 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:39:33 hostname systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter. Jun 14 09:39:33 hostname systemd[1]: amavis.service: Failed with result 'exit-code'. Jun 14 09:40:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:41:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:41:59 hostname maas.dhcp.probe[6170]: [error] Can't initiate DHCP probe; no RPC connection to region. Jun 14 09:41:59 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:42:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:43:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:44:15 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:45:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:46:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:46:59 hostname maas.boot_image_download_service[6170]: [error] Can't initiate image download, no RPC connection to region. Jun 14 09:47:14 hostname maas.service_monitor_service[6170]: [error] Can't update service statuses, no RPC connection to region. Jun 14 09:47:15 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:47:15 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:47:15 hostname systemd[1]: maas-proxy.service: Supervising process 6751 which is not our child. We'll most likely not notice when it exits. Jun 14 09:47:19 hostname maas.networks.monitor[6155]: [info] Networks monitoring service: Process ID 6155 assumed responsibility.