Custom Query (1365 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (178 - 180 of 1365)

Ticket Resolution Summary Owner Reporter
#1542 fixed update-smart-drivedb doesn't kill it's gpg-agent and throws errors on systems with root on NFS Christian Franke rwofyiyj.awdawdq
Description

I use smartd daemon on machines with root filesystem.

update-smart-drivedb doesn't kill it's gpg-agent process and tries to remove it's home dir (line 494). On NFS it doesn't work. Directory cannot be removed because nfs preserves delete open sockets/files. (script would have to rm -rf the directory twice)

This error causes stderr message which creates additional mail (false positive) when cron is configured to send mail.

This small patch kills the gpg-agent and allows for error free $gnupgtmp deletion.

diff -c backup /usr/sbin/update-smart-drivedb
*** backup	2021-11-04 14:29:14.665707108 +0100
--- /usr/sbin/update-smart-drivedb	2021-11-04 14:31:08.927219722 +0100
***************
*** 491,496 ****
--- 491,497 ----
      echo "$out" >&2
    fi
  
+   kill $(ps ax | awk '$5=="gpg-agent" && /smartmontools/{print $2}')
    rm -f -r "$gnupgtmp"
    return $r

Reproducible: Always

Steps to Reproduce:

  1. run /etc/cron.monthly/smartmontools-update-drivedb on machine with root on NFS

Actual Results:

LC_ALL=C /etc/cron.monthly/smartmontools-update-drivedb
rm: cannot remove '/var/db/smartmontools/.gnupg.139163.tmp': Directory not empty

Script executes normal but has problem deleting it's gpg directory.

Expected Results: There should be no stderr output when scripts executes normally.

Script doesn't delete it's temporary directory.

#1538 invalid smartd gets confused about which drive is reporting temperature changes? Jimmie
Description

OS: OpenSUSE Leap 15.3 (x86-64) smartmontools version 7.0-6.1

I've received a number of smartd email notifications over the past few weeks. Every time, the system journal suggests that smartd detected a temperature change on /dev/sda but that an error was logged against /dev/nvme.

My system has two SSDs: /dev/sda: Samsung 850 EVO /dev/nvme0: SK Hynix P31

The following warning/error was logged by the smartd daemon today:

   Device: /dev/nvme0, number of Error Log entries increased from 11 to 12
   Device info:
   SHGP31-1000GM-2, S/N:XXXXXX, FW:41060C20

The system journal from that timestamp shows the following:

smartd[1511]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 [Raw 26] to 73 [Raw 27]
smartd[1511]: Device: /dev/nvme0, number of Error Log entries increased from 11 to 12
smartd[1511]: Sending warning via <mail> to xxxxxxxx@xxxxxxxx ...
smartd[1511]: Warning via <mail> to xxxxxx@xxxxxxxx: successful

For some reason, it looks like smartd logged the error against /dev/nvme0?

#1537 fixed Add new drives to database: TOSHIBA HDWR480 Christian Franke TheDragonFire961
Description

The following drive is not in the database.

TOSHIBA HDWR480

This drive's family is the existing Toshiba X300 family. Other new drives include the HDWR440 and HDWR460. See attachment for a smartctl printout.

While I don't have a sample, there is also now a HDWR31E, which is a 14 TB version of the HDWR31J which is already in the database.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.