Subscribe
Accepted Solution

SDU - Problem to start SnapDrived on RedHat Linux.

Hi Folk,

I'm trying to start snapdrive on RedHat 5.5 and I have the following problem :
>> snapdrived start
Fatal error: Assertion detected in production code: ../sbl/Operation.cpp:173: Test 'osAssistants.size() == 1' failed

I tried a lot of things without success (with and without HTTPS, I checked 4094 and 4095 ports…)

My conf is RHEL 5 update 5 x64. SnapDrive 4.2. HUK 5.3 with qlogic FC HBA.
An Oracle RAC is installed on this system.

Any hints ?

Regards,
Mathias

Please find the sd-trace.log below :
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'autosupport-enabled=off'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'default-transport=fcp'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'multipathing-type=NativeMPIO'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'fstype=ext3'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'vmtype=none'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-filer=off'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-dfm=off'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-viadmin=off'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-sdu-daemon=off'
12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'enable-alua=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'autosupport-enabled=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'default-transport=fcp'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'multipathing-type=NativeMPIO'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'fstype=ext3'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'vmtype=none'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-filer=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-dfm=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-viadmin=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-sdu-daemon=off'
12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'enable-alua=off'
12:26:49 04/26/11 [f7f0e6c0]i,2,40,getVirtualInstance: Virtual Interface == NULL.
12:26:49 04/26/11 [f7f0e6c0]i,2,6,"-Initializing VM Assistants
"
12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.154419): /sbin/lvm version
12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.208817): Output:
File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
  LVM version:     2.02.56(1)-RHEL5 (2010-02-08)
  Library version: 1.02.39-RHEL5 (2009-11-11)
  Driver version:  4.11.5
12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.209763): /sbin/lvm version
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.263112): Output:
File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
  LVM version:     2.02.56(1)-RHEL5 (2010-02-08)
  Library version: 1.02.39-RHEL5 (2009-11-11)
  Driver version:  4.11.5
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.263399): lvm help --driverloaded y
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.317535): Output:
File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived
File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived
  Available lvm commands:
  Use 'lvm help <command>' for more information
  
  dumpconfig      Dump active configuration
  formats         List available metadata formats
  help            Display help for commands
  lvchange        Change the attributes of logical volume(s)
  lvconvert       Change logical volume layout
  lvcreate        Create a logical volume
  lvdisplay       Display information about a logical volume
  lvextend        Add space to a logical volume
  lvmchange       With the device mapper, this is obsolete and does nothing.
  lvmdiskscan     List devices that may be used as physical volumes
  lvmsadc         Collect activity data
  lvmsar          Create activity report
  lvreduce        Reduce the size of a logical volume
  lvremove        Remove logical volume(s) from the system
  lvrename        Rename a logical volume
  lvresize        Resize a logical volume
  lvs             Display information about logical volumes
  lvscan          List all logical volumes in all volume groups
  pvchange        Change attributes of physical volume(s)
  pvresize        Resize physical volume(s)
  pvck            Check the consistency of physical volume(s)
  pvcreate        Initialize physical volume(s) for use by LVM
  pvdata          Display the on-disk metadata for physical volume(s)
  pvdisplay       Display various attributes of physical volume(s)
  pvmove          Move extents from one physical volume to another
  pvremove        Remove LVM label(s) from physical volume(s)
  pvs             Display information about physical volumes
  pvscan          List all physical volumes
  segtypes        List available segment types
  vgcfgbackup     Backup volume group configuration(s)
  vgcfgrestore    Restore volume group configuration
  vgchange        Change volume group attributes
  vgck            Check the consistency of volume group(s)
  vgconvert       Change volume group metadata format
  vgcreate        Create a volume group
  vgdisplay       Display volume group information
  vgexport        Unregister volume group(s) from the system
  vgextend        Add physical volumes to a volume group
  vgimport        Register exported volume group with system
  vgmerge         Merge volume groups
  vgmknodes       Create the special files for volume group devices in /dev
  vgreduce        Remove physical volume(s) from a volume group
  vgremove        Remove volume group(s)
  vgrename        Rename a volume group
  vgs             Display information about volume groups
  vgscan          Search for all volume groups
  vgsplit         Move physical volumes into a new or existing volume group
  version         Display software and driver version information
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,2,sbl_init:VmAssistant::initAssistants 0
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing File System Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing SCSI Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing OS Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.321052): cat /etc/SuSE-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.322931): Output:
cat: /etc/SuSE-release: No such file or directory
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.323119): cat /etc/SuSE-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.325381): Output:
cat: /etc/SuSE-release: No such file or directory
12:26:50 04/26/11 [f7f0e6c0]v,2,26,OsAssistant::initAssistants: Couldn't init assistant.  Error:
12:26:50 04/26/11 [f7f0e6c0]i,2,6,Operation::addErrorReport: (1) OsAssistant:OsAssistant 6 1082:Initialization of OsAssistant failed: cat: /etc/SuSE-release: No such file or directory


12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.325777): cat /etc/redhat-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.328010): Output:
redhat release 5
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.332753): cat /etc/SuSE-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.334570): Output:
cat: /etc/SuSE-release: No such file or directory
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.334643): cat /etc/redhat-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.336891): Output:
redhat release 5
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.336958): cat /etc/redhat-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.339244): Output:
redhat release 5
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 1 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing Host Cluster Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing Multipathing Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.340094): /etc/init.d/multipathd status
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.350678): Output:
multipathd (pid  3083) is running...
12:26:50 04/26/11 [f7f0e6c0]v,2,26,MpAssistant::initAssistants: Couldn't init assistant.  Error:
12:26:50 04/26/11 [f7f0e6c0]i,2,6,Operation::addErrorReport: (1) MpAssistant:MpAssistant 6 1082:Initialization of MpAssistant failed:

12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.351092): cat /etc/SuSE-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.353351): Output:
cat: /etc/SuSE-release: No such file or directory
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.353420): cat /etc/redhat-release
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.355656): Output:
redhat release 5
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.355855): /etc/init.d/multipathd status
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.366346): Output:
multipathd (pid  3083) is running...
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.366416): lsmod | grep multipath
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.370722): Output:
dm_multipath           56921  2 dm_round_robin
scsi_dh                42177  1 dm_multipath
dm_mod                101649  51 dm_multipath,dm_raid45,dm_zero,dm_log
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 1 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing HBA Assistants
"
12:26:50 04/26/11 [f7f0e6c0]v,2,6,Initialized vmwarefcp
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.371277): /sbin/lsmod | grep iscsi
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.375246): Output:
12:26:50 04/26/11 [f7f0e6c0]v,2,26,HbaAssistant::initAssistants: Couldn't init assistant.  Error:
12:26:50 04/26/11 [f7f0e6c0]i,2,6,Operation::addErrorReport: (1) HbaAssistant:HbaAssistant 6 1082:Initialization of HbaAssistant failed: LinuxiscsiHbaAssistant: iscsi module is not loaded


12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.375675): /sbin/lsmod | grep iscsi
12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.379480): Output:
12:26:50 04/26/11 [f7f0e6c0]v,2,26,HbaAssistant::initAssistants: Couldn't init assistant.  Error:
12:26:50 04/26/11 [f7f0e6c0]i,2,6,Operation::addErrorReport: (2) HbaAssistant:HbaAssistant 6 1082:Initialization of HbaAssistant failed: LinuxiscsiHbaAssistant: iscsi module is not loaded


12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 2 Error Report objects
12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying VM Assistant versions
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying File System Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying Multipathing Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying Host Cluster Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying OS Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying SCSI Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying HBA Assistant version
"
12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing ONTAPI
"
12:26:50 04/26/11 [f7f0e6c0]v,2,18,FilerZephyr::startup: done => 0
12:26:50 04/26/11 [f7f0e6c0]F,0,0,Fatal error: Assertion detected in production code: ../sbl/Operation.cpp:173: Test 'osAssistants.size() == 1' failed
[root@aora11g1 netapp_linux_host_utilities_5_2]#

Re: SDU - Problem to start SnapDrived on RedHat Linux.

Hi Mathias,

Funny, I got the same issue today.

My configuration is a little bit different with CentOS 5.6 but error message is the same:

"Fatal error: Assertion detected in production code: ../sbl/Operation.cpp:173: Test 'osAssistants.size() == 1' failed"

The way I fixed it:

  • edit /etc/redhat-release file
  • replace string "CentOS release 5.6 (Final)"
  • by "Red Hat Enterprise Linux Server release 5.6 (Tikanga)"
  • and snapdrived is starting now succesfully..

Maybe your /etc/redhat-release file is missing or corrupted...

Hope it helps,

Best regards,

Frederic

Re: SDU - Problem to start SnapDrived on RedHat Linux.

Hi Frederic,

You're right. It is exactly the problem. We found the solution as the same time. We did that :

[root@aora11g2 ~]# echo "Red Hat Enterprise Linux Server release 5.5 (Tikanga)" > /etc/issue
You have new mail in /var/spool/mail/root
[root@aora11g2 ~]# echo "Red Hat Enterprise Linux Server release 5.5 (Tikanga)" > /etc/redhat-release
[root@aora11g2 ~]# service snapdrived start
Starting snapdrive daemon: Successfully started daemon

Thanks a lot for your help.

Mathias

Re: SDU - Problem to start SnapDrived on RedHat Linux.

I'm on SL 6.5 and I had to change:

    Scientific Linux release 6.5 (Carbon)

to

    Red Hat Scientific Linux release 6.5 (Carbon)

to get past this problem.

Faye

(not Bob, his colleague, using his creds :-) )

Re: SDU - Problem to start SnapDrived on RedHat Linux.

Your solution helped but now i have this error when i check status of snapdrived:

 

9000-015 SOAP ERROR : 28 : A connection error occured. Please check if snapdrived is running

Re: SDU - Problem to start SnapDrived on RedHat Linux.

do you fixed it ? I have the same question!