How to fix: sosreport: No space left on device error ?

Suppose you are collecting sosreport and you are getting an error message “No space left on device”

And you want to change the default storage location of sosreport on server now.

Hence in this article we will look how to change the default sosreport location on server.

I. Issue

[root@ngelinux001 ~]# sosreport
sosreport (version 3.3)

This command will collect diagnostic and configuration information from
this Red Hat Enterprise Linux system and installed applications.

An archive containing the collected information will be generated in
/var/tmp/sos.m_268Q and may be provided to a Red Hat support
representative.

Any information provided to Red Hat will be treated in accordance with
the published support policies at:

  https://access.redhat.com/support/

The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.

No changes will be made to system configuration.

Press ENTER to continue, or CTRL-C to quit.

Please enter your first initial and last name [SSE_IDT]:
Please enter the case id that you are generating this report for []:

 Setting up archive ...
 Setting up plugins ...
 Running plugins. Please wait ...

  Running 41/89: logs...
 No space left on device while collecting plugin data

You have new mail in /var/spool/mail/
[root@ngelinux001~]#

 

II. Solution
Now we can run sosreport with destination directory in options where to save the output at different location.

[root@ngelinux001 ~]# sosreport --tmp-dir /var/sosreport

sosreport (version 3.3)

This command will collect diagnostic and configuration information from
this Red Hat Enterprise Linux system and installed applications.

An archive containing the collected information will be generated in
/var/sosreport/sos.QXjHa7 and may be provided to a Red Hat support
representative.

Any information provided to Red Hat will be treated in accordance with
the published support policies at:

  https://access.redhat.com/support/

The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.

No changes will be made to system configuration.

Press ENTER to continue, or CTRL-C to quit.

Please enter your first initial and last name [SSE_IDT]:
Please enter the case id that you are generating this report for []:

 Setting up archive ...
 Setting up plugins ...


 Running plugins. Please wait ...

  Running 1/89: acpid...
  Running 2/89: anaconda...
  Running 3/89: anacron...
  Running 4/89: ata...
  Running 5/89: auditd...
  Running 6/89: block...
  Running 7/89: boot...
  Running 8/89: ceph...
  Running 9/89: cgroups...
  Running 10/89: chrony...
  Running 11/89: corosync...
  Running 12/89: cron...
  Running 13/89: dbus...
  Running 14/89: devicemapper...
  Running 15/89: devices...
  Running 16/89: dlm...
  Running 17/89: dmraid...
  Running 18/89: etcd...
  Running 19/89: filesys...
  Running 20/89: firewalld...
  Running 21/89: gdm...
  Running 22/89: general...
  Running 23/89: grub2...
  Running 24/89: hardware...
  Running 25/89: hpasm...
  Running 26/89: hts...
  Running 27/89: i18n...
  Running 28/89: infiniband...
  Running 29/89: ipmitool...
  Running 30/89: java...
  Running 31/89: kernel...
  Running 32/89: keyutils...
  Running 33/89: kpatch...
  Running 34/89: krb5...

Leave a Reply

Your email address will not be published.