This article explains the reason for the "scsi_reserve: [error] unable to exec sg_persist" error to be logged and indicates that no action is required to resolve the error.
Juniper QFabric customers may see the following error message from the DG syslog when service scsi_reserve status or service --status-all is executed.
service scsi_reserve status
service --status-all
[root@dg0 ~]# grep sg_persist /var/log/messages | tail -3 Feb 12 15:27:17 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:26:26 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:42:19 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist [root@dg0 ~]# service scsi_reserve status ;date [FAILED] Thu Feb 13 11:56:47 UTC 2020 [root@dg0 ~]# grep sg_persist /var/log/messages | tail -3 Feb 13 11:26:26 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:42:19 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:56:47 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist [root@dg0 ~]#
Because the service "scsi_reserve" is also a part of service --status-all , the same message will also be logged to syslog when service --status-all is executed.
[root@dg0 ~]# [root@dg0 ~]# service --status-all acpid is stopped auditd (pid 3683) is running... automount (pid 6670) is running... Avahi daemon is not running Avahi DNS daemon is not running CCIF server running (pid 15748) cman is running. cnm (pid 5903) is running... cpuspeed is stopped crond (pid 8610) is running... drbd driver loaded OK; device status: version: 8.3.8 (api:88/proto:86-94) GIT-hash: d78846e52224fd00562f7c225bcc25b2d422321d build by [email protected], 2010-06-04 08:04:09 m:res cs ro ds p mounted fstype 0:pb_drbddata Connected Primary/Primary UpToDate/UpToDate C /pbdata gfs2 Active GFS2 mountpoints: /pbdata gpm is stopped hald (pid 6550) is running... httpd is stopped Firewall is stopped. ipmi_msghandler module loaded. ipmi_si module loaded. ...truncated... aisexec (pid 7262) is running... portmap (pid 3733) is running... qdiskd is stopped rdisc (pid 20080) is running... clurgmgrd (pid 7403) is running... rpc.idmapd (pid 6461) is running... [FAILED] sfc is running sfcsnmpd is running sfctraphandler is running smartd (pid 8880) is running... openssh-daemon (pid 8500) is running... syslogd (pid 3711) is running... klogd (pid 3714) is running... uuidd dead but pid file exists vsftpd (pid 8567 8560) is running... xfs is stopped xinetd (pid 8512) is running... [root@dg0 ~]# [root@dg0 ~]# grep sg_persist /var/log/messages | tail -3 Feb 13 11:42:19 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:56:47 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:59:45 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist [root@dg0 ~]#
The error log is seen due to "scsi_reserve" service failure. The service fails because the package named " sg3_utils " does not exist in the DG OS and is no longer used in the Juniper QFabric system.
sg3_utils
Since the related "scsi_reserve" service is not being used in the current Juniper QFabric system, the above error logs can be safety ignored.
To suppress these error logs, users can change the related script to be non-executable.
chmod -x /etc/init.d/scsi_reserve
The following excerpt shows that the logs are not seen after the above change is made.
[root@dg0 ~]# grep sg_persist /var/log/messages | tail -3 Feb 13 11:42:19 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:56:47 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:59:45 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist [root@dg0 ~]# chmod -x /etc/init.d/scsi_reserve [root@dg0 ~]# service scsi_reserve status;date scsi_reserve: unrecognized service Thu Feb 13 12:07:12 UTC 2020 [root@dg0 ~]# grep sg_persist /var/log/messages | tail -3 Feb 13 11:42:19 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:56:47 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist Feb 13 11:59:45 <1.5> dg0 scsi_reserve: [error] unable to exec sg_persist [root@dg0 ~]#