Come controllo e risolvo una anomalia sulla mia ADSL ?

Networking, configurazione della connessione, periferiche e condivisione di rete, ecc.

Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda mai_nat » lunedì 25 febbraio 2019, 13:53

Uso in multiboot UbuntuMate18.04 e Kubuntu18.04
Uso per la connessione una linea ADSL che penso di aver configurato allo stesso modo sui due sistemi.
Solo quando uso Kubuntu riscontro una interruzione di collegamento della linea ADSL; l'interruzione in oggetto interviene in modo saltuario e generalmente dopo pochi minuti che ho avviato il pc; può sopraggiungere a metà di un update-upgrade come di altre fasi e, dopo una attesa anche si diversi minuti, l'unico azione (che io conosco) che mi permette di ripristinare il regolare funzionamento è fare un "reboot"
In condizione di funzionamento corretto ho una situazione di questo tipo:
Codice: Seleziona tutto
nat@nat-SSD:~$ ping -c 4 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.608 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.532 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.533 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.532 ms

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3058ms
rtt min/avg/max/mdev = 0.532/0.551/0.608/0.036 ms
nat@nat-SSD:~$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=13.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=13.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=12.9 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 12.993/13.782/15.208/0.877 ms
nat@nat-SSD:~$ ping -c 4 google.it
PING google.it (216.58.205.131) 56(84) bytes of data.
64 bytes from mil04s27-in-f3.1e100.net (216.58.205.131): icmp_seq=1 ttl=54 time=11.9 ms
64 bytes from mil04s27-in-f3.1e100.net (216.58.205.131): icmp_seq=2 ttl=54 time=12.3 ms
64 bytes from mil04s27-in-f3.1e100.net (216.58.205.131): icmp_seq=3 ttl=54 time=12.2 ms
64 bytes from mil04s27-in-f3.1e100.net (216.58.205.131): icmp_seq=4 ttl=54 time=11.9 ms

--- google.it ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 11.980/12.136/12.348/0.204 ms
nat@nat-SSD:~$

mentre in presenza della anomalia ho questa situazione:
Codice: Seleziona tutto
nat@nat-SSD:~$ ping -c 4 192.168.1.1
connect: La rete non è raggiungibile
nat@nat-SSD:~$ ping -c 4 8.8.8.8
connect: La rete non è raggiungibile
nat@nat-SSD:~$ ping -c 4 google.it
ping: google.it: Errore temporaneo nella risoluzione del nome
nat@nat-SSD:~$

Questo è il mio ifconfig:
Codice: Seleziona tutto
nat@nat-SSD:~$ ifconfig
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 151.33.45.134  netmask 255.255.255.255  broadcast 151.33.45.134
        inet6 fe80::3285:a9ff:fe3e:6efe  prefixlen 64  scopeid 0x20<link>
        ether 30:85:a9:3e:6e:fe  txqueuelen 1000  (Ethernet)
        RX packets 12967  bytes 12663575 (12.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11234  bytes 1173140 (1.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 11

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Loopback locale)
        RX packets 393  bytes 29691 (29.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 393  bytes 29691 (29.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nat@nat-SSD:~$

Quello che vedo è che ora, in presenza di funzionamento regolare, la mia linea enp3s0 è arrivata a un valore di collisioni = 11 ( in condizione di anomalia ho visto tale valore a 54 ) ma va da se che a me questo valore non dice nulla, anche se resta un bell'indizio (per chi ci capisca qualche cosa ). Naturalmente ho provato a disconnettere e richiedere la connessione senza risolvere nulla.

Mi rivolgo quindi al forum per chiedere che altro posso controllare per capire/risolvere quanto accade.
Un saluto da nat
Ultima modifica di mai_nat il domenica 24 marzo 2019, 18:07, modificato 1 volta in totale.
mai_nat
Prode Principiante
 
Messaggi: 191
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Mate/Kde
Distribuzione: Umate18.04 Kubuntu18.04
Sesso: Maschile

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Sam9999 » lunedì 25 febbraio 2019, 14:08

La configurazione è in DHCP o dedicata? Inoltre usi network manager o netplan.
-------------
S. @-M.
-------------
Avatar utente
Sam9999
Entusiasta Emergente
Entusiasta Emergente
 
Messaggi: 1525
Iscrizione: giugno 2014
Località: BO
Desktop: Studio Xfce
Distribuzione: Ubuntu 19.04 (Disco Dingo)

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda pachisapiu » lunedì 25 febbraio 2019, 14:19

usi wifi o ethernet ?
pachisapiu
 

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda mai_nat » lunedì 25 febbraio 2019, 15:02

pachisapiu ha scritto:usi wifi o ethernet ?
Ho una comunissima ADSL con il cavetto in rame. Non uso wifi ma ethernet con un modem D-Link modello DSL-320B
Sam9999 ha scritto:La configurazione è in DHCP o dedicata? Inoltre usi network manager o netplan.

La configurazione è quella che nasce da una "normale" istallazione di Kubuntu18.04 fatta da usb.
La caratterizzazione che ho attualmente e che posso controllare e/o modificare con:
Impostazioni di sistema --> connessioni
è presente la sola connessione via cavo 1 con questi valori:
1) Configurazione generale = valori di default (la spunta è su connetti automaticamente se disponibile)
2) Cablata = valori di default
3) Protezione 802.1x = valori di default
4) IPv4 = Metodo: Automatico (solo indirizzi ) Server DNS: 208.67.222.222,208.67.220.220
5) IPv6= Metodo: Ignorato

( Nota finale: Perdonami l'ignoranza ma netplan non so neanche cosa sia :cry: )
:ciao: nat
edit: le collisioni ( vedi ifconfig ) sono passate da 11 a 19 !
Ultima modifica di mai_nat il domenica 24 marzo 2019, 17:58, modificato 1 volta in totale.
mai_nat
Prode Principiante
 
Messaggi: 191
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Mate/Kde
Distribuzione: Umate18.04 Kubuntu18.04
Sesso: Maschile

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Sam9999 » lunedì 25 febbraio 2019, 15:08

Connessione ethernet in dhcp con network manager, dns non in dhcp.

Quando non pinchi hai provato a disabilitare e riabilitare la rete ?

Una cosa che non mi torna è coma mai pinghi 192.168.1.1 come gateway quando il tuo ip è 151.33.45.134 ...

Il comando "arp -a" che cosa ti dice ?
-------------
S. @-M.
-------------
Avatar utente
Sam9999
Entusiasta Emergente
Entusiasta Emergente
 
Messaggi: 1525
Iscrizione: giugno 2014
Località: BO
Desktop: Studio Xfce
Distribuzione: Ubuntu 19.04 (Disco Dingo)

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda mai_nat » lunedì 25 febbraio 2019, 15:25

Sam9999 ha scritto:Connessione ethernet in dhcp con network manager, dns non in dhcp.

Puoi essere più chiaro che non capisco.

Sam9999 ha scritto:Quando non pinchi hai provato a disabilitare e riabilitare la rete ?
mai_nat ha scritto:Naturalmente ho provato a disconnettere e richiedere la connessione senza risolvere nulla.

Sam9999 ha scritto:Una cosa che non mi torna è coma mai pinghi 192.168.1.1 come gateway quando il tuo ip è 151.33.45.134 ...

Proprio per capire se è un problema localizzato da pc a modem o da modem a IP

Sam9999 ha scritto:Il comando "arp -a" che cosa ti dice ?

Codice: Seleziona tutto
nat@nat-SSD:~$ arp -a
_gateway (192.168.1.1) associato a 90:94:e4:f9:c7:f6 [ether] su enp3s0
nat@nat-SSD:~$


Sulle collisioni che aumentano hai qualche idea ?

Edit:
Non voglio fare una mancanza di rispetto per chi è intervenuto, che ringrazio , ma quanto mi piacerebbe sentire l'opinione di @thece .... :sisi:
Ultima modifica di mai_nat il domenica 24 marzo 2019, 18:01, modificato 2 volte in totale.
mai_nat
Prode Principiante
 
Messaggi: 191
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Mate/Kde
Distribuzione: Umate18.04 Kubuntu18.04
Sesso: Maschile

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Sam9999 » lunedì 25 febbraio 2019, 15:29

Quanti pc in rete? é una rete casalinga?

In network manager al punto 4) prova a mettere in manuale tutto e come IP ne metti uno nel range 192.168.1.xx, come mask 255.255.255.0 e come gateway il 192.168.1.1, poi dopo sconnetti e ti riconnetti o riavvia e controlla con "ifconfig" che tutto sia a posto, e se naviga.
Mi sorge il dubbio, non è che è una macchina virtuale ?
-------------
S. @-M.
-------------
Avatar utente
Sam9999
Entusiasta Emergente
Entusiasta Emergente
 
Messaggi: 1525
Iscrizione: giugno 2014
Località: BO
Desktop: Studio Xfce
Distribuzione: Ubuntu 19.04 (Disco Dingo)

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda pachisapiu » lunedì 25 febbraio 2019, 15:47

mai_nat Immagine ha scritto:Uso per la connessione una linea ADSL che penso di aver configurato allo stesso modo sui due sistemi.

mai_nat Immagine ha scritto: Non uso wifi ma ethernet
Scusa ma se usi ethernet non c'è nulla da configurare , colleghi il cavo e vai ...

@Sam9999 : ha la 18.04 quindi usa netplan
pachisapiu
 

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Sam9999 » lunedì 25 febbraio 2019, 16:06


@Sam9999 : ha la 18.04 quindi usa netplan


Si certo ma se
Codice: Seleziona tutto
  renderer: NetworkManager
  renderer: networkd
-------------
S. @-M.
-------------
Avatar utente
Sam9999
Entusiasta Emergente
Entusiasta Emergente
 
Messaggi: 1525
Iscrizione: giugno 2014
Località: BO
Desktop: Studio Xfce
Distribuzione: Ubuntu 19.04 (Disco Dingo)

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Stealth » lunedì 25 febbraio 2019, 16:07

Sam9999 Immagine ha scritto: ... Una cosa che non mi torna è coma mai pinghi 192.168.1.1 come gateway quando il tuo ip è 151.33.45.134 ...

:ciao:
Avatar utente
Stealth
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 16054
Iscrizione: gennaio 2006
Desktop: Gnome
Distribuzione: Ubuntu 18.04 LTS

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda mai_nat » martedì 19 marzo 2019, 17:30

Vi propongo un aggiornamento.
Come già detto, ( interviene sempre e solo con Kubuntu18.04 ) in modo assolutamente casuale e sporadico si è ripresentata l' anomalia.
Se con il funzionamento corretto ho questa condizione:
Codice: Seleziona tutto
at@nat-SSD:~$ ifconfig
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 151.33.63.139  netmask 255.255.255.255  broadcast 151.33.63.139
        inet6 fe80::3285:a9ff:fe3e:6efe  prefixlen 64  scopeid 0x20<link>
        ether 30:85:a9:3e:6e:fe  txqueuelen 1000  (Ethernet)
        RX packets 10  bytes 1307 (1.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43  bytes 8012 (8.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Loopback locale)
        RX packets 109  bytes 8435 (8.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 109  bytes 8435 (8.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nat@nat-SSD:~$

in presenza del difetto ho quest'altra condizione
Codice: Seleziona tutto
nat@nat-SSD:~$ ifconfig
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::3285:a9ff:fe3e:6efe  prefixlen 64  scopeid 0x20<link>
        ether 30:85:a9:3e:6e:fe  txqueuelen 1000  (Ethernet)
        RX packets 45695  bytes 49932833 (49.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 35463  bytes 3906609 (3.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 108

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Loopback locale)
        RX packets 501  bytes 37433 (37.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 501  bytes 37433 (37.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nat@nat-SSD:~$
dove si manifesta la sconnessione della linea inet ( forse a causa di collisions 108 ? )

per completezza fornisco le ultime righe di dmesg in presenza della anomalia
Codice: Seleziona tutto
[    6.158317] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[    6.215433] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[    6.215516] caller os_map_kernel_space+0x86/0xb0 [nvidia] mapping multiple BARs
[    7.774903] r8169 0000:03:00.0 enp3s0: link up
[    7.774911] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[  881.404017] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
nat@nat-SSD:~$

nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.

Chi sa mettere un po' di luce in quanto mi accade ?
mai_nat
Prode Principiante
 
Messaggi: 191
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Mate/Kde
Distribuzione: Umate18.04 Kubuntu18.04
Sesso: Maschile

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda Sam9999 » martedì 19 marzo 2019, 20:14

Ma sei in DHCP o con IP fisso ?
Perché hai lo stesso IP del router al quale ti dovresti connettere.

Se sei in IP fisso è da cambaire IP.... sul router controllare il range IP che puo' dare.
-------------
S. @-M.
-------------
Avatar utente
Sam9999
Entusiasta Emergente
Entusiasta Emergente
 
Messaggi: 1525
Iscrizione: giugno 2014
Località: BO
Desktop: Studio Xfce
Distribuzione: Ubuntu 19.04 (Disco Dingo)

Re: Come controllo e risolvo una anomalia sulla mia ADSL ?

Messaggioda mai_nat » giovedì 25 aprile 2019, 10:09

Sam9999 ha scritto:Ma sei in DHCP o con IP fisso ?

DHCP come pensavo di aver già da tempo chiarito:
mai_nat ha scritto:La configurazione è quella che nasce da una "normale" istallazione di Kubuntu18.04 fatta da usb.
La caratterizzazione che ho attualmente e che posso controllare e/o modificare con:
Impostazioni di sistema --> connessioni
è presente la sola connessione via cavo 1 con questi valori:
1) Configurazione generale = valori di default (la spunta è su connetti automaticamente se disponibile)
2) Cablata = valori di default
3) Protezione 802.1x = valori di default
4) IPv4 = Metodo: Automatico (solo indirizzi ) Server DNS: 208.67.222.222,208.67.220.220
5) IPv6= Metodo: Ignorato


Stamane sono riuscito ad "isolare" il momento del default mentre era in corso un aggiornamento eseguito con sudo apt update && sudo apt dist-upgrade. Dopo aver accertato la "sparizione" della connessione ho spento. Avendo un multiboot K1804 Umate18.04 e Umate16.04, ho riavviato da Umate18.04 e ho recuperato il file /var/log/syslog da K1804, (che à l'unico SO su cui lamento il problema,) e ho postato la parte che va dalla accensione allo spegnimento.
Codice: Seleziona tutto
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0903] device (enp3s0): carrier: link connected
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0912] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0916] policy: auto-activating connection 'Connessione via cavo 1'
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0925] device (enp3s0): Activation: starting connection 'Connessione via cavo 1' (cf0b4e1d-aa1f-3ea3-924c-93a6239174a6)
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0926] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0927] manager: NetworkManager state is now CONNECTING
Apr 25 09:46:20 nat-SSD kernel: [    7.392529] r8169 0000:03:00.0 enp3s0: link up
Apr 25 09:46:20 nat-SSD kernel: [    7.392536] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0942] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0945] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0951] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Apr 25 09:46:20 nat-SSD NetworkManager[827]: <info>  [1556178380.0967] dhcp4 (enp3s0): dhclient started with pid 1098
Apr 25 09:46:20 nat-SSD dhclient[1098]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x5c105847)
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.kde.ActivityManager' requested by ':1.7' (uid=1000 pid=1105 comm="kded5 [kdeinit5]                                  " label="unconfined")
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.kde.ActivityManager'
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Config timer connecting...
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Setting the name of  0x56439e7f6ac0  to  "org.kde.ActivityManager.Resources.Scoring"
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Creating directory:  "/home/nat/.local/share/kactivitymanagerd/resources/"
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: KActivities: Database connection:  "kactivities_db_resources_140146865969152_readwrite"
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]:     query_only:          QVariant(qlonglong, 0)
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]:     journal_mode:        QVariant(QString, "wal")
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]:     wal_autocheckpoint:  QVariant(qlonglong, 100)
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]:     synchronous:         QVariant(qlonglong, 1)
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Setting the name of  0x56439e84da30  to  "org.kde.ActivityManager.RunApplication"
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Setting the name of  0x56439e852e50  to  "org.kde.ActivityManager.ActivityTemplates"
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Service started, version: 7.0.0
Apr 25 09:46:20 nat-SSD org.kde.ActivityManager[1027]: Cleaning up...
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.kde.kglobalaccel' requested by ':1.12' (uid=1000 pid=1121 comm="/usr/bin/kaccess " label="unconfined")
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='ca.desrt.dconf' requested by ':1.15' (uid=1000 pid=1139 comm="/usr/bin/gsettings set org.gnome.desktop.a11y.appl" label="unconfined")
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'ca.desrt.dconf'
Apr 25 09:46:20 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.26' (uid=1000 pid=1105 comm="kded5 [kdeinit5]                                  " label="unconfined")
Apr 25 09:46:20 nat-SSD systemd[1]: Starting Daemon for power management...
Apr 25 09:46:20 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 25 09:46:20 nat-SSD systemd[1]: Started Daemon for power management.
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.kde.kglobalaccel'
Apr 25 09:46:20 nat-SSD ModemManager[782]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0': not supported by any plugin
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.kde.KScreen' requested by ':1.7' (uid=1000 pid=1105 comm="kded5 [kdeinit5]                                  " label="unconfined")
Apr 25 09:46:20 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1203 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
Apr 25 09:46:20 nat-SSD systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 25 09:46:20 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Successfully called chroot.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Successfully dropped privileges.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Successfully limited resources.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Running.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Canary thread running.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Watchdog thread running.
Apr 25 09:46:20 nat-SSD systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Successfully made thread 1203 of process 1203 (n/a) owned by '1000' high priority at nice level -11.
Apr 25 09:46:20 nat-SSD rtkit-daemon[1204]: Supervising 1 threads of 1 processes of 1 users.
Apr 25 09:46:20 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.kde.KScreen'
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Connected output 589 to CRTC 586
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: Detected XRandR 1.5
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: Event Base:  89
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: Event Error:  147
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandR::setConfig
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Requested screen size is QSize(1366, 768)
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Needed CRTCs:  1
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Actions to perform:
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Primary Output: true
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011#011Old: 588
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011#011New: 589
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Change Screen Size: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Disable outputs: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Change outputs: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Enable outputs: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: RRSetOutputPrimary
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011New primary: 589
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandR::setConfig done!
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: RRNotify_OutputChange
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Output:  588
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011CRTC:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Mode:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Rotation:  "Rotate_0"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Connection:  "Disconnected"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Subpixel Order:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: RRNotify_OutputChange
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Output:  589
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011CRTC:  586
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Mode:  590
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Rotation:  "Rotate_0"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Connection:  "Connected"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Subpixel Order:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: RRScreenChangeNotify
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Window: 31457284
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Root: 607
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Rotation:  "Rotate_0"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Size ID: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Size:  1366 768
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011SizeMM:  413 232
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: RRNotify_OutputChange
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Output:  588
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011CRTC:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Mode:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Rotation:  "Rotate_0"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Connection:  "Disconnected"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Subpixel Order:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: RRNotify_OutputChange
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Output:  589
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011CRTC:  586
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Mode:  590
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Rotation:  "Rotate_0"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Connection:  "Connected"
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xcb.helper: #011Subpixel Order:  0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandROutput 588 update
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_connected: 1
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_crtc QObject(0x0)
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011CRTC: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011MODE: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Connection: 1
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Primary: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Output 588 : connected = false , enabled = false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandROutput 589 update
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_connected: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_crtc XRandRCrtc(0x55c2af31ef70)
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011CRTC: 586
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011MODE: 590
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Connection: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Primary: true
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Output 589 : connected = true , enabled = true
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandROutput 588 update
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_connected: 1
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_crtc QObject(0x0)
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011CRTC: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011MODE: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Connection: 1
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Primary: false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Output 588 : connected = false , enabled = false
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: XRandROutput 589 update
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_connected: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011m_crtc XRandRCrtc(0x55c2af31ef70)
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011CRTC: 586
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011MODE: 590
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Connection: 0
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: #011Primary: true
Apr 25 09:46:20 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Output 589 : connected = true , enabled = true
Apr 25 09:46:21 nat-SSD spice-vdagent[1243]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Apr 25 09:46:21 nat-SSD dbus-daemon[795]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.35' (uid=1000 pid=1221 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper)
Apr 25 09:46:21 nat-SSD org.kde.KScreen[1027]: kscreen.xrandr: Emitting configChanged()
Apr 25 09:46:21 nat-SSD org.kde.powerdevil.discretegpuhelper: QDBusArgument: read from a write-only object
Apr 25 09:46:21 nat-SSD org.kde.powerdevil.discretegpuhelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Apr 25 09:46:21 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
Apr 25 09:46:21 nat-SSD dbus-daemon[795]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.35' (uid=1000 pid=1221 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper)
Apr 25 09:46:21 nat-SSD org.kde.powerdevil.backlighthelper[795]: powerdevil: no kernel backlight interface found
Apr 25 09:46:21 nat-SSD org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Apr 25 09:46:21 nat-SSD org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Apr 25 09:46:21 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Apr 25 09:46:21 nat-SSD avahi-daemon[828]: Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::3285:a9ff:fe3e:6efe.
Apr 25 09:46:21 nat-SSD avahi-daemon[828]: New relevant interface enp3s0.IPv6 for mDNS.
Apr 25 09:46:21 nat-SSD avahi-daemon[828]: Registering new address record for fe80::3285:a9ff:fe3e:6efe on enp3s0.*.
Apr 25 09:46:21 nat-SSD kernel: [    9.016231] kauditd_printk_skb: 11 callbacks suppressed
Apr 25 09:46:21 nat-SSD kernel: [    9.016232] audit: type=1400 audit(1556178381.709:22): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/sys/devices/system/node/" pid=1276 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 25 09:46:21 nat-SSD kernel: [    9.019550] audit: type=1400 audit(1556178381.709:23): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/etc/mysql/my.cnf.fallback" pid=1276 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 25 09:46:21 nat-SSD kernel: [    9.036520] audit: type=1400 audit(1556178381.729:24): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/sys/devices/system/node/" pid=1277 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Supervising 1 threads of 1 processes of 1 users.
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Successfully made thread 1335 of process 1203 (n/a) owned by '1000' RT at priority 5.
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Supervising 2 threads of 1 processes of 1 users.
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Supervising 2 threads of 1 processes of 1 users.
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Successfully made thread 1336 of process 1203 (n/a) owned by '1000' RT at priority 5.
Apr 25 09:46:22 nat-SSD rtkit-daemon[1204]: Supervising 3 threads of 1 processes of 1 users.
Apr 25 09:46:22 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.47' (uid=1000 pid=1203 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
Apr 25 09:46:22 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.gnome.GConf' requested by ':1.40' (uid=1000 pid=1337 comm="/usr/lib/x86_64-linux-gnu/pulse/gconf-helper " label="unconfined")
Apr 25 09:46:22 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.gnome.GConf'
Apr 25 09:46:22 nat-SSD set-cpufreq[830]: Setting powersave scheduler for all CPUs
Apr 25 09:46:23 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.kde.kuiserver' requested by ':1.21' (uid=1000 pid=1174 comm="/usr/bin/plasmashell " label="unconfined")
Apr 25 09:46:23 nat-SSD org.kde.kuiserver[1027]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Apr 25 09:46:23 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.kde.kuiserver'
Apr 25 09:46:23 nat-SSD org.kde.kuiserver[1027]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Apr 25 09:46:23 nat-SSD dhclient[1098]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0x5c105847)
Apr 25 09:46:23 nat-SSD dhclient[1098]: DHCPREQUEST of 151.33.25.111 on enp3s0 to 255.255.255.255 port 67 (xid=0x4758105c)
Apr 25 09:46:23 nat-SSD dhclient[1098]: DHCPOFFER of 151.33.25.111 from 192.168.1.1
Apr 25 09:46:23 nat-SSD dhclient[1098]: DHCPACK of 151.33.25.111 from 192.168.1.1
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5448] dhcp4 (enp3s0):   address 151.33.25.111
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5448] dhcp4 (enp3s0):   plen 32 (255.255.255.255)
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5448] dhcp4 (enp3s0):   gateway 192.168.1.1
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5448] dhcp4 (enp3s0):   lease time 60
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5448] dhcp4 (enp3s0):   hostname 'host-151-33-25-111'
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5449] dhcp4 (enp3s0):   nameserver '193.70.152.15'
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5449] dhcp4 (enp3s0):   nameserver '212.52.97.15'
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5449] dhcp4 (enp3s0): state changed unknown -> bound
Apr 25 09:46:23 nat-SSD avahi-daemon[828]: Joining mDNS multicast group on interface enp3s0.IPv4 with address 151.33.25.111.
Apr 25 09:46:23 nat-SSD avahi-daemon[828]: New relevant interface enp3s0.IPv4 for mDNS.
Apr 25 09:46:23 nat-SSD avahi-daemon[828]: Registering new address record for 151.33.25.111 on enp3s0.IPv4.
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5459] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5472] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5483] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5488] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 25 09:46:23 nat-SSD dhclient[1098]: bound to 151.33.25.111 -- renewal in 26 seconds.
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5546] manager: NetworkManager state is now CONNECTED_SITE
Apr 25 09:46:23 nat-SSD nm-dispatcher: req:2 'up' [enp3s0]: new request (1 scripts)
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5548] policy: set 'Connessione via cavo 1' (enp3s0) as default for IPv4 routing and DNS
Apr 25 09:46:23 nat-SSD nm-dispatcher: req:2 'up' [enp3s0]: start running ordered scripts...
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5550] device (enp3s0): Activation: successful, device activated.
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5556] manager: startup complete
Apr 25 09:46:23 nat-SSD NetworkManager[827]: <info>  [1556178383.5559] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 25 09:46:23 nat-SSD systemd[1]: Started Network Manager Wait Online.
Apr 25 09:46:23 nat-SSD systemd[1]: Reached target Network is Online.
Apr 25 09:46:23 nat-SSD systemd[1]: Started crash report submission daemon.
Apr 25 09:46:23 nat-SSD systemd[1]: Starting Daily apt download activities...
Apr 25 09:46:23 nat-SSD systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Apr 25 09:46:23 nat-SSD systemd[1]: Starting LSB: disk temperature monitoring daemon...
Apr 25 09:46:23 nat-SSD systemd[1]: kerneloops.service: Found left-over process 1457 (kerneloops) in control group while starting unit. Ignoring.
Apr 25 09:46:23 nat-SSD systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 25 09:46:23 nat-SSD systemd[1]: Started LSB: disk temperature monitoring daemon.
Apr 25 09:46:23 nat-SSD systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Apr 25 09:46:23 nat-SSD systemd[1]: Reached target Multi-User System.
Apr 25 09:46:23 nat-SSD systemd[1]: Reached target Graphical Interface.
Apr 25 09:46:23 nat-SSD systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
Apr 25 09:46:23 nat-SSD systemd[1]: Starting Update UTMP about System Runlevel Changes...
Apr 25 09:46:23 nat-SSD whoopsie[1451]: [09:46:23] Using lock path: /var/lock/whoopsie/lock
Apr 25 09:46:23 nat-SSD nm-dispatcher: req:3 'connectivity-change': new request (1 scripts)
Apr 25 09:46:23 nat-SSD systemd[1]: Started Update UTMP about System Runlevel Changes.
Apr 25 09:46:23 nat-SSD whoopsie[1451]: [09:46:23] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 25 09:46:23 nat-SSD whoopsie[1451]: [09:46:23] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 25 09:46:23 nat-SSD whoopsie[1451]: [09:46:23] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 25 09:46:23 nat-SSD nm-dispatcher: req:3 'connectivity-change': start running ordered scripts...
Apr 25 09:46:24 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.44' (uid=1000 pid=1174 comm="/usr/bin/plasmashell " label="unconfined")
Apr 25 09:46:24 nat-SSD systemd[1]: Starting PackageKit Daemon...
Apr 25 09:46:24 nat-SSD PackageKit: daemon start
Apr 25 09:46:24 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Apr 25 09:46:24 nat-SSD systemd[1]: Started PackageKit Daemon.
Apr 25 09:46:24 nat-SSD systemd-resolved[708]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Apr 25 09:46:25 nat-SSD fstrim[850]: /media/app_home: 19,1 GiB (20506472448 bytes) trimmed
Apr 25 09:46:25 nat-SSD fstrim[850]: /: 29,7 GiB (31914606592 bytes) trimmed
Apr 25 09:46:25 nat-SSD systemd[1]: Started Discard unused blocks.
Apr 25 09:46:25 nat-SSD PackageKit: get-updates transaction /1045_dcecbeea from uid 1000 finished with success after 550ms
Apr 25 09:46:36 nat-SSD PackageKit: get-updates transaction /1046_bcabbaec from uid 1000 finished with success after 3196ms
Apr 25 09:46:38 nat-SSD systemd[1]: Started Daily apt download activities.
Apr 25 09:46:38 nat-SSD systemd[1]: Starting Daily apt upgrade and clean activities...
Apr 25 09:46:38 nat-SSD systemd[1]: Started Daily apt upgrade and clean activities.
Apr 25 09:46:38 nat-SSD systemd[1]: Startup finished in 3.623s (kernel) + 22.555s (userspace) = 26.179s.
Apr 25 09:46:47 nat-SSD pulseaudio[1203]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Apr 25 09:46:47 nat-SSD PackageKit: get-updates transaction /1047_bbdedaad from uid 1000 finished with success after 516ms
Apr 25 09:46:48 nat-SSD systemd-timesyncd[717]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Apr 25 09:46:50 nat-SSD dhclient[1098]: DHCPREQUEST of 151.33.25.111 on enp3s0 to 192.168.1.1 port 67 (xid=0x4758105c)
Apr 25 09:46:50 nat-SSD dhclient[1098]: DHCPACK of 151.33.25.111 from 192.168.1.1
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5259] dhcp4 (enp3s0):   address 151.33.25.111
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5259] dhcp4 (enp3s0):   plen 32 (255.255.255.255)
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5259] dhcp4 (enp3s0):   gateway 192.168.1.1
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5260] dhcp4 (enp3s0):   lease time 60
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5260] dhcp4 (enp3s0):   hostname 'host-151-33-25-111'
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5260] dhcp4 (enp3s0):   nameserver '193.70.152.15'
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5260] dhcp4 (enp3s0):   nameserver '212.52.97.15'
Apr 25 09:46:50 nat-SSD NetworkManager[827]: <info>  [1556178410.5260] dhcp4 (enp3s0): state changed bound -> bound
Apr 25 09:46:50 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=827 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 25 09:46:50 nat-SSD systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 25 09:46:50 nat-SSD dhclient[1098]: bound to 151.33.25.111 -- renewal in 32 seconds.
Apr 25 09:46:50 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 25 09:46:50 nat-SSD systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 25 09:46:50 nat-SSD nm-dispatcher: req:1 'dhcp4-change' [enp3s0]: new request (1 scripts)
Apr 25 09:46:50 nat-SSD nm-dispatcher: req:1 'dhcp4-change' [enp3s0]: start running ordered scripts...
Apr 25 09:46:53 nat-SSD kernel: [   40.415162] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
Apr 25 09:47:09 nat-SSD systemd[1]: Starting Stop ureadahead data collection...
Apr 25 09:47:09 nat-SSD systemd[1]: Started Stop ureadahead data collection.
Apr 25 09:47:22 nat-SSD dhclient[1098]: DHCPREQUEST of 151.33.25.111 on enp3s0 to 192.168.1.1 port 67 (xid=0x4758105c)
Apr 25 09:47:39 nat-SSD dhclient[1098]: message repeated 3 times: [ DHCPREQUEST of 151.33.25.111 on enp3s0 to 192.168.1.1 port 67 (xid=0x4758105c)]
Apr 25 09:47:51 nat-SSD NetworkManager[827]: <info>  [1556178471.1078] dhcp4 (enp3s0): state changed bound -> expire
Apr 25 09:47:51 nat-SSD NetworkManager[827]: <info>  [1556178471.1399] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 1098
Apr 25 09:47:51 nat-SSD NetworkManager[827]: <info>  [1556178471.1400] dhcp4 (enp3s0): state changed expire -> done
Apr 25 09:47:51 nat-SSD NetworkManager[827]: <info>  [1556178471.1402] device (enp3s0): scheduling DHCPv4 restart in 120 seconds, 3 tries left (reason: lease expired)
Apr 25 09:47:52 nat-SSD avahi-daemon[828]: Withdrawing address record for 151.33.25.111 on enp3s0.
Apr 25 09:47:52 nat-SSD avahi-daemon[828]: Leaving mDNS multicast group on interface enp3s0.IPv4 with address 151.33.25.111.
Apr 25 09:47:52 nat-SSD NetworkManager[827]: <info>  [1556178472.4673] manager: NetworkManager state is now CONNECTED_SITE
Apr 25 09:47:52 nat-SSD avahi-daemon[828]: Interface enp3s0.IPv4 no longer relevant for mDNS.
Apr 25 09:47:52 nat-SSD dbus-daemon[795]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=827 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 25 09:47:52 nat-SSD whoopsie[1451]: [09:47:52] Cannot reach: https://daisy.ubuntu.com
Apr 25 09:47:52 nat-SSD whoopsie[1451]: [09:47:52] offline
Apr 25 09:47:52 nat-SSD systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 25 09:47:52 nat-SSD dbus-daemon[795]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 25 09:47:52 nat-SSD systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 25 09:47:52 nat-SSD nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Apr 25 09:47:52 nat-SSD nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Apr 25 09:47:54 nat-SSD PackageKit: get-updates transaction /1048_aabbeead from uid 1000 finished with success after 526ms
Apr 25 09:48:03 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Activating service name='org.kde.kdeconnect' requested by ':1.21' (uid=1000 pid=1174 comm="/usr/bin/plasmashell " label="unconfined")
Apr 25 09:48:03 nat-SSD org.kde.kdeconnect[1027]: kdeconnect.core: KdeConnect daemon starting
Apr 25 09:48:03 nat-SSD org.kde.kdeconnect[1027]: kdeconnect.core: onStart
Apr 25 09:48:03 nat-SSD dbus-daemon[1027]: [session uid=1000 pid=1027] Successfully activated service 'org.kde.kdeconnect'
Apr 25 09:48:03 nat-SSD org.kde.kdeconnect[1027]: kdeconnect.core: KdeConnect daemon started
Apr 25 09:48:03 nat-SSD org.kde.kdeconnect[1027]: kdeconnect.core: Broadcasting identity packet
Apr 25 09:48:05 nat-SSD systemd[1]: Stopped Unattended Upgrades Shutdown.
Apr 25 09:48:05 nat-SSD systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Apr 25 09:48:05 nat-SSD systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Apr 25 09:48:05 nat-SSD systemd[1]: Stopping ACPI event daemon...
Apr 25 09:48:05 nat-SSD systemd[1]: Stopping PackageKit Daemon...

Mi pare quasi di apprezzare che sia una azione "di sistema" e/o quasi fatta con un timeout, ma la mia ignoranza è grande, molto grande....
Per completezza ho scoperto che per "risolvere l'anomalia" oltre allo spegnimento è sufficiente mettre il SO in sospensione e al ripristino, anche immediato, la connessione è ripristinata. Ne consegue che il fatto di "capire" cosa succede è oramai solo un fatto di puntiglio...
Un saluto da nat
mai_nat
Prode Principiante
 
Messaggi: 191
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Mate/Kde
Distribuzione: Umate18.04 Kubuntu18.04
Sesso: Maschile


Torna a Connessione e configurazione delle reti

Chi c’è in linea

Visualizzano questa sezione: 0 utenti registrati e 2 ospiti