This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1876195

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876195

Title:
  /var is filed with errors logs (from network) until it is over 60 Gb
  sized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I installed Ubuntu 20.04 a few days ago, at release.
  Yesterday I got a warning about low remaining space on disk. Unable to access 
my files I restarted my computer.
  Ubuntu failed to boot and I got the code :

  [    10.688299] ccp 0000:0a:00.2: sev command 0x4 timed out, disabling PSP
  [    10.688353] cpp 0000:0a:00.2: SEV: failed to get status. Error: 0x0

  I started Ubuntu with Advanced options and try repair my packages. It warned 
me I had not enough space to do that so I deleted part of my files in root 
mode, which allowed me to restart.
  I ran the disk analyser which show me I had a 60 gigabytes /var directory.
  ls -lSh /var/log command show :

  total 50G
  -rw-r-----  1 syslog            adm              50G avril 29 23:53 syslog
  -rw-r-----  1 syslog            adm              21M avril 29 23:38 kern.log
  -rw-r-----  1 syslog            adm              13M avril 26 00:00 kern.log.1
  -rw-r-----  1 syslog            adm             4,5M avril 29 00:00 syslog.1
  -rw-r-----  1 syslog            adm             1,3M avril 25 00:00 
syslog.5.gz
  -rw-r--r--  1 root              root            1,2M avril 29 19:18 dpkg.log
  -rw-r-----  1 syslog            adm             795K avril 28 00:00 
syslog.2.gz
  -rw-rw-r--  1 root              utmp            286K avril 24 00:20 lastlog
  -rw-r-----  1 syslog            adm             279K avril 26 00:00 
syslog.4.gz
  -rw-r-----  1 syslog            adm             134K avril 27 00:00 
syslog.3.gz
  -rw-r--r--  1 root              root            102K avril 23 09:33 
bootstrap.log
  -rw-r--r--  1 root              adm              92K avril 29 23:37 dmesg
  -rw-r--r--  1 root              adm              92K avril 29 23:20 dmesg.0
  -rw-r-----  1 syslog            adm              80K avril 25 23:30 auth.log.1
  -rw-r--r--  1 root              root             57K avril 29 20:15 
Xorg.1.log.old
  -rw-------  1 root              root             54K avril 29 23:37 boot.log
  -rw-------  1 root              root             45K avril 25 00:00 boot.log.4
  -rw-r-----  1 syslog            adm              44K avril 29 23:39 auth.log
  -rw-r--r--  1 root              root             39K avril 29 23:38 Xorg.1.log
  -rw-r--r--  1 root              root             38K avril 29 23:38 Xorg.0.log
  -rw-r--r--  1 root              root             38K avril 29 00:28 
alternatives.log
  -rw-r--r--  1 root              root             32K avril 24 00:20 faillog
  -rw-rw-r--  1 root              utmp             22K avril 29 23:38 wtmp
  -rw-------  1 root              root             21K avril 29 00:00 boot.log.1
  -rw-r--r--  1 root              adm              21K avril 29 20:21 dmesg.2.gz
  -rw-r--r--  1 root              adm              21K avril 29 23:18 dmesg.1.gz
  -rw-r--r--  1 root              adm              21K avril 29 20:16 dmesg.4.gz
  -rw-r--r--  1 root              adm              21K avril 29 20:19 dmesg.3.gz
  -rw-r--r--  1 root              root             17K avril 29 23:20 
Xorg.0.log.old
  -rw-r--r--  1 root              root             11K avril 24 02:46 
fontconfig.log
  -rw-------  1 root              root             11K avril 27 00:00 boot.log.2
  -rw-------  1 root              root             11K avril 26 00:00 boot.log.3
  -rw-r-----  1 root              adm             6,1K avril 28 23:06 
apport.log.1
  drwxr-xr-x  2 root              root            4,0K avril 29 19:18 apt
  drwxr-xr-x  2 root              root            4,0K avril 29 00:00 cups
  drwxr-xr-x  2 root              root            4,0K avril 29 23:23 
dist-upgrade
  drwx--x--x  2 root              gdm             4,0K oct.   7  2019 gdm3
  drwxr-xr-x  3 root              root            4,0K avril 23 09:36 hp
  drwxr-xr-x  2 root              root            4,0K avril 23 21:31 installer
  drwxr-sr-x+ 3 root              systemd-journal 4,0K avril 23 21:39 journal
  drwxr-xr-x  2 root              root            4,0K sept.  5  2019 openvpn
  drwx------  2 root              root            4,0K avril 23 09:32 private
  drwx------  2 speech-dispatcher root            4,0K janv. 19 19:26 
speech-dispatcher
  drwxr-x---  2 root              adm             4,0K avril 24 13:46 
unattended-upgrades
  -rw-rw-r--  1 root              tistus          1,2K avril 29 23:20 
gpu-manager-switch.log
  -rw-r--r--  1 root              root            1,2K avril 29 23:37 
gpu-manager.log
  -rw-r-----  1 root              adm              363 avril 24 22:48 
apport.log.2.gz
  -rw-r-----  1 root              adm                0 avril 29 23:20 apport.log
  -rw-rw----  1 root              utmp               0 avril 23 09:32 btmp
  -rw-------  1 root              root               0 avril 23 09:33 
ubuntu-advantage.log

  syslog became syslog.1 after a restart but is still 50G

  I paste the result of command sudo tail -150 /var/log/syslog.1 in the file 
TraceSyslog1.txt
  And the result of the command sudo  journalctl -n5000 >TraceJournal.txt is 
the file TraceJournal.txt

  In logs I found numerous network problems such as :
  Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.
  That indicate network manager may be the cause of all that ?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 00:00:53 2020
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.1 dev enp6s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp6s0 scope link metric 1000 
   192.168.1.0/24 dev enp6s0 proto kernel scope link src 192.168.1.89 metric 100
  IwConfig:
   enp6s0    no wireless extensions.
   
   lo        no wireless extensions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME                 UUID                                  TYPE      
TIMESTAMP   TIMESTAMP-REAL               AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH                                   ACTIVE  DEVICE  STATE     
 ACTIVE-PATH                                         SLAVE  FILENAME            
                                                    
   Connexion filaire 1  4f71136b-f5ed-30df-9367-5b31df52de55  ethernet  
1588283836  jeu. 30 avril 2020 23:57:16  yes          -999                  no  
      /org/freedesktop/NetworkManager/Settings/1  yes     enp6s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --     
/run/NetworkManager/system-connections/Connexion filaire 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE      STATE      IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
                               CONNECTION           CON-UUID                    
          CON-PATH                                           
   enp6s0  ethernet  connected  full              limited           
/org/freedesktop/NetworkManager/Devices/2  Connexion filaire 1  
4f71136b-f5ed-30df-9367-5b31df52de55  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo      loopback  unmanaged  unknown           unknown           
/org/freedesktop/NetworkManager/Devices/1  --                   --              
                      --
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN    
   running  1.22.10  connected  started  full          enabled     enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to