Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
Официальное хранилище ПО в виде файлов
  • 0

4.0 Alpha 6 Бесконечный перезапуск служб в логе

sashaqwert

Asked by sashaqwert,

 Share

Question

sashaqwert Member

sashaqwert

Posted
Posted (edited)

После обновления до 4.0 Alpha 6 лог забит однотипными сообщениями вида "загружен SSL сертификат для keenetic.pro", "поднят туннель 6in4", "upnp: HTTP listening on port 1900", "upnp: shutting down MiniUPnPd" и т. д.

Фрагмент лога с изменёнными данными (реальные в self-test)

Скрытый текст

[I] Feb  5 16:20:47 ndm: Core::Session: client disconnected.
[I] Feb  5 16:20:47 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:20:47 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:20:47 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:20:47 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:20:47 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:20:49 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:20:49 upnp: HTTP listening on port 1900
[I] Feb  5 16:20:49 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Feb  5 16:20:52 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:20:52 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:20:52 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:20:52 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:20:52 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:20:53 ndm: Http::Nginx: loaded SSL certificate for "example.keenetic.pro".
[I] Feb  5 16:20:53 ndm: Http::Nginx: loaded SSL certificate for "XXXXXXXXXXXXXXX.keenetic.io".
[I] Feb  5 16:20:53 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:20:53 ndm: Core::Session: client disconnected.
[I] Feb  5 16:20:53 ndm: Http::Manager: updated configuration.
[I] Feb  5 16:20:53 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:20:53 ndm: Core::Session: client disconnected.
[I] Feb  5 16:20:59 ndm: Http::Nginx: loaded SSL certificate for "example.keenetic.pro".
[I] Feb  5 16:20:59 ndm: Http::Nginx: loaded SSL certificate for "XXXXXXXXXXXXXXX.keenetic.io".
[I] Feb  5 16:20:59 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:20:59 ndm: Core::Session: client disconnected.
[I] Feb  5 16:20:59 ndm: Http::Manager: updated configuration.
[I] Feb  5 16:20:59 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:20:59 ndm: Core::Session: client disconnected.
[I] Feb  5 16:23:12 ndhcpc: GigabitEthernet1/Vlan3: received ACK for  91.77.XXX.XXX from 91.77.160.1 lease 300 sec.
[I] Feb  5 16:23:12 ndm: Network::Interface::Base: "GigabitEthernet1/Vlan3": "dhcp-client" changed "ipv4" layer state "running" to "pending".
[W] Feb  5 16:23:12 ndm: Dns::Manager: name server 62.112.106.130 is disregarded while public is active.
[W] Feb  5 16:23:12 ndm: Dns::Manager: name server 62.112.113.170 is disregarded while public is active.
[I] Feb  5 16:23:12 ndm: Network::Interface::Base: "GigabitEthernet1/Vlan3": "dhcp-client" changed "ipv4" layer state "pending" to "running".
[I] Feb  5 16:23:12 ndm: Network::InterfaceFlusher: flushed GigabitEthernet1/Vlan3 conntrack and route cache.
[I] Feb  5 16:23:12 ndm: Network::InternetChecker: Internet access lost (status: 0x0000).
[I] Feb  5 16:23:12 ndm: Dns::Secure::DotConfigurator: "System": using "dns.adguard-dns.com:853:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:23:12 https-dns-proxy: Shutting down gracefully. To force exit, send signal again.
[I] Feb  5 16:23:12 ndm: Dns::Secure::DohConfigurator: "System": using "dns.adguard-dns.com:443:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:23:13 ndm: Network::InternetChecker: Internet access detected.
[I] Feb  5 16:23:14 stubby: starting Stubby 0.4.0
[I] Feb  5 16:23:15 upnp: shutting down MiniUPnPd
[I] Feb  5 16:23:15 ndm: Core::Session: client disconnected.
[I] Feb  5 16:23:15 ndm: Network::InterfaceFlusher: flushed GigabitEthernet1 conntrack and route cache.
[I] Feb  5 16:23:15 ndm: Network::InternetChecker: Internet access lost (status: 0x0000).
[I] Feb  5 16:23:15 ndm: Dns::Secure::DotConfigurator: "System": using "dns.adguard-dns.com:853:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:23:15 https-dns-proxy: Shutting down gracefully. To force exit, send signal again.
[I] Feb  5 16:23:15 ndm: Dns::Secure::DohConfigurator: "System": using "dns.adguard-dns.com:443:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:23:15 ndm: Network::InternetChecker: Internet access detected.
[I] Feb  5 16:23:17 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:23:17 upnp: HTTP listening on port 1900
[I] Feb  5 16:23:17 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Feb  5 16:23:17 stubby: starting Stubby 0.4.0
[I] Feb  5 16:23:17 upnp: shutting down MiniUPnPd
[I] Feb  5 16:23:17 ndm: Core::Session: client disconnected.
[I] Feb  5 16:23:17 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:23:17 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:23:17 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:23:17 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:23:17 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:23:19 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:23:19 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:23:19 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:23:19 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:23:19 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:23:19 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:23:19 upnp: HTTP listening on port 1900
[I] Feb  5 16:23:19 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Feb  5 16:25:42 ndhcpc: GigabitEthernet1/Vlan3: received ACK for  91.77.XXX.XXX from 91.77.160.1 lease 300 sec.
[I] Feb  5 16:25:42 ndm: Network::Interface::Base: "GigabitEthernet1/Vlan3": "dhcp-client" changed "ipv4" layer state "running" to "pending".
[W] Feb  5 16:25:42 ndm: Dns::Manager: name server 62.112.106.130 is disregarded while public is active.
[W] Feb  5 16:25:42 ndm: Dns::Manager: name server 62.112.113.170 is disregarded while public is active.
[I] Feb  5 16:25:42 ndm: Network::Interface::Base: "GigabitEthernet1/Vlan3": "dhcp-client" changed "ipv4" layer state "pending" to "running".
[I] Feb  5 16:25:42 ndm: Network::InterfaceFlusher: flushed GigabitEthernet1/Vlan3 conntrack and route cache.
[I] Feb  5 16:25:42 ndm: Network::InternetChecker: Internet access lost (status: 0x0000).
[I] Feb  5 16:25:42 ndm: Dns::Secure::DotConfigurator: "System": using "dns.adguard-dns.com:853:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:25:42 https-dns-proxy: Shutting down gracefully. To force exit, send signal again.
[I] Feb  5 16:25:43 ndm: Dns::Secure::DohConfigurator: "System": using "dns.adguard-dns.com:443:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:25:43 ndm: Network::InternetChecker: Internet access detected.
[I] Feb  5 16:25:45 stubby: starting Stubby 0.4.0
[I] Feb  5 16:25:45 upnp: shutting down MiniUPnPd
[I] Feb  5 16:25:45 ndm: Core::Session: client disconnected.
[I] Feb  5 16:25:45 ndm: Network::InterfaceFlusher: flushed GigabitEthernet1 conntrack and route cache.
[I] Feb  5 16:25:45 ndm: Network::InternetChecker: Internet access lost (status: 0x0000).
[I] Feb  5 16:25:45 ndm: Dns::Secure::DotConfigurator: "System": using "dns.adguard-dns.com:853:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:25:45 https-dns-proxy: Shutting down gracefully. To force exit, send signal again.
[I] Feb  5 16:25:45 ndm: Dns::Secure::DohConfigurator: "System": using "dns.adguard-dns.com:443:94.140.14.14,94.140.15.15" as upstream.
[I] Feb  5 16:25:45 ndm: Network::InternetChecker: Internet access detected.
[I] Feb  5 16:25:47 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:47 upnp: HTTP listening on port 1900
[I] Feb  5 16:25:47 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Feb  5 16:25:47 stubby: starting Stubby 0.4.0
[I] Feb  5 16:25:48 upnp: shutting down MiniUPnPd
[I] Feb  5 16:25:48 ndm: Core::Session: client disconnected.
[I] Feb  5 16:25:48 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:25:48 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:25:48 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:25:48 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:25:48 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:25:50 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved destination 193.0.203.203 (193.0.203.203).
[I] Feb  5 16:25:50 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": use interface GigabitEthernet1/Vlan3 as source.
[I] Feb  5 16:25:50 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": added host route to tunnel destination endpoint 193.0.203.203 via 91.77.160.1.
[I] Feb  5 16:25:50 ndm: Network::Interface::Base: "TunnelSixInFour0": default MTU is 1480.
[I] Feb  5 16:25:50 ndm: Network::Interface::Tunnel4: "TunnelSixInFour0": resolved source  91.77.XXX.XXX.
[I] Feb  5 16:25:50 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:50 upnp: HTTP listening on port 1900
[I] Feb  5 16:25:50 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Feb  5 16:25:53 ndm: Http::Nginx: loaded SSL certificate for "example.keenetic.pro".
[I] Feb  5 16:25:53 ndm: Http::Nginx: loaded SSL certificate for "XXXXXXXXXXXXXXX.keenetic.io".
[I] Feb  5 16:25:53 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:53 ndm: Core::Session: client disconnected.
[I] Feb  5 16:25:53 ndm: Http::Manager: updated configuration.
[I] Feb  5 16:25:53 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:53 ndm: Core::Session: client disconnected.
[I] Feb  5 16:25:59 ndm: Http::Nginx: loaded SSL certificate for "example.keenetic.pro".
[I] Feb  5 16:25:59 ndm: Http::Nginx: loaded SSL certificate for "XXXXXXXXXXXXXXX.keenetic.io".
[I] Feb  5 16:25:59 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:59 ndm: Core::Session: client disconnected.
[I] Feb  5 16:25:59 ndm: Http::Manager: updated configuration.
[I] Feb  5 16:25:59 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Feb  5 16:25:59 ndm: Core::Session: client disconnected.
[I] Feb  5 16:26:04 ndm: Netfilter::Util::Conntrack: flushed 3 IPv6 connections.

И это не шутка: такой длинный лог за 5 минут...

Edited by sashaqwert

1 answer to this question

Recommended Posts

Guest
This topic is now closed to further replies.
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

This site uses cookies. By clicking "I accept" or continuing to browse the site, you authorize their use in accordance with the Privacy Policy.

  I accept