<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SDU - Problem to start SnapDrived on RedHat Linux. in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26157#M4214</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm on SL 6.5 and I had to change:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Scientific Linux release 6.5 (Carbon)&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Red Hat Scientific Linux release 6.5 (Carbon)&lt;/P&gt;&lt;P&gt;to get past this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Faye&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(not Bob, his colleague, using his creds &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Mar 2014 13:48:40 GMT</pubDate>
    <dc:creator>wolfsonmicro</dc:creator>
    <dc:date>2014-03-26T13:48:40Z</dc:date>
    <item>
      <title>SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26138#M4211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Folk,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to start snapdrive on RedHat 5.5 and I have the following problem :&lt;BR /&gt;&amp;gt;&amp;gt; snapdrived start&lt;BR /&gt;Fatal error: Assertion detected in production code: ../sbl/Operation.cpp:173: Test 'osAssistants.size() == 1' failed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried a lot of things without success (with and without HTTPS, I checked 4094 and 4095 ports…)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My conf is RHEL 5 update 5 x64. SnapDrive 4.2. HUK 5.3 with qlogic FC HBA.&lt;BR /&gt;An Oracle RAC is installed on this system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hints ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Mathias&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find the sd-trace.log below :&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'autosupport-enabled=off'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'default-transport=fcp'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'multipathing-type=NativeMPIO'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'fstype=ext3'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'vmtype=none'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-filer=off'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-dfm=off'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-viadmin=off'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'use-https-to-sdu-daemon=off'&lt;BR /&gt;12:26:43 04/26/11 [f7f746c0]v,2,2,Config Refresh found 'enable-alua=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'autosupport-enabled=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'default-transport=fcp'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'multipathing-type=NativeMPIO'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'fstype=ext3'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'vmtype=none'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-filer=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-dfm=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-viadmin=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'use-https-to-sdu-daemon=off'&lt;BR /&gt;12:26:47 04/26/11 [f7f0e6c0]v,2,2,Config Refresh found 'enable-alua=off'&lt;BR /&gt;12:26:49 04/26/11 [f7f0e6c0]i,2,40,getVirtualInstance: Virtual Interface == NULL.&lt;BR /&gt;12:26:49 04/26/11 [f7f0e6c0]i,2,6,"-Initializing VM Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.154419): /sbin/lvm version &lt;BR /&gt;12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.208817): Output:&lt;BR /&gt;File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;&amp;nbsp; LVM version:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.02.56(1)-RHEL5 (2010-02-08)&lt;BR /&gt;&amp;nbsp; Library version: 1.02.39-RHEL5 (2009-11-11)&lt;BR /&gt;&amp;nbsp; Driver version:&amp;nbsp; 4.11.5&lt;BR /&gt;12:26:49 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.209763): /sbin/lvm version &lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.263112): Output:&lt;BR /&gt;File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;&amp;nbsp; LVM version:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.02.56(1)-RHEL5 (2010-02-08)&lt;BR /&gt;&amp;nbsp; Library version: 1.02.39-RHEL5 (2009-11-11)&lt;BR /&gt;&amp;nbsp; Driver version:&amp;nbsp; 4.11.5&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.263399): lvm help --driverloaded y&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.317535): Output:&lt;BR /&gt;File descriptor 3 (/var/log/sd-daemon-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 4 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 5 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 6 (/opt/NetApp/snapdrive/.snapdrived.pid) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;File descriptor 8 (/var/log/sd-trace.log) leaked on lvm invocation. Parent PID 5986: snapdrived&lt;BR /&gt;&amp;nbsp; Available lvm commands:&lt;BR /&gt;&amp;nbsp; Use 'lvm help &amp;lt;command&amp;gt;' for more information&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; dumpconfig&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Dump active configuration&lt;BR /&gt;&amp;nbsp; formats&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List available metadata formats&lt;BR /&gt;&amp;nbsp; help&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display help for commands&lt;BR /&gt;&amp;nbsp; lvchange&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change the attributes of logical volume(s)&lt;BR /&gt;&amp;nbsp; lvconvert&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change logical volume layout&lt;BR /&gt;&amp;nbsp; lvcreate&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Create a logical volume&lt;BR /&gt;&amp;nbsp; lvdisplay&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display information about a logical volume&lt;BR /&gt;&amp;nbsp; lvextend&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Add space to a logical volume&lt;BR /&gt;&amp;nbsp; lvmchange&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; With the device mapper, this is obsolete and does nothing.&lt;BR /&gt;&amp;nbsp; lvmdiskscan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List devices that may be used as physical volumes&lt;BR /&gt;&amp;nbsp; lvmsadc&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Collect activity data&lt;BR /&gt;&amp;nbsp; lvmsar&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Create activity report&lt;BR /&gt;&amp;nbsp; lvreduce&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Reduce the size of a logical volume&lt;BR /&gt;&amp;nbsp; lvremove&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remove logical volume(s) from the system&lt;BR /&gt;&amp;nbsp; lvrename&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Rename a logical volume&lt;BR /&gt;&amp;nbsp; lvresize&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Resize a logical volume&lt;BR /&gt;&amp;nbsp; lvs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display information about logical volumes&lt;BR /&gt;&amp;nbsp; lvscan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List all logical volumes in all volume groups&lt;BR /&gt;&amp;nbsp; pvchange&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change attributes of physical volume(s)&lt;BR /&gt;&amp;nbsp; pvresize&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Resize physical volume(s)&lt;BR /&gt;&amp;nbsp; pvck&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Check the consistency of physical volume(s)&lt;BR /&gt;&amp;nbsp; pvcreate&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Initialize physical volume(s) for use by LVM&lt;BR /&gt;&amp;nbsp; pvdata&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display the on-disk metadata for physical volume(s)&lt;BR /&gt;&amp;nbsp; pvdisplay&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display various attributes of physical volume(s)&lt;BR /&gt;&amp;nbsp; pvmove&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Move extents from one physical volume to another&lt;BR /&gt;&amp;nbsp; pvremove&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remove LVM label(s) from physical volume(s)&lt;BR /&gt;&amp;nbsp; pvs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display information about physical volumes&lt;BR /&gt;&amp;nbsp; pvscan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List all physical volumes&lt;BR /&gt;&amp;nbsp; segtypes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List available segment types&lt;BR /&gt;&amp;nbsp; vgcfgbackup&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Backup volume group configuration(s)&lt;BR /&gt;&amp;nbsp; vgcfgrestore&amp;nbsp;&amp;nbsp;&amp;nbsp; Restore volume group configuration&lt;BR /&gt;&amp;nbsp; vgchange&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change volume group attributes&lt;BR /&gt;&amp;nbsp; vgck&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Check the consistency of volume group(s)&lt;BR /&gt;&amp;nbsp; vgconvert&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change volume group metadata format&lt;BR /&gt;&amp;nbsp; vgcreate&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Create a volume group&lt;BR /&gt;&amp;nbsp; vgdisplay&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display volume group information&lt;BR /&gt;&amp;nbsp; vgexport&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Unregister volume group(s) from the system&lt;BR /&gt;&amp;nbsp; vgextend&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Add physical volumes to a volume group&lt;BR /&gt;&amp;nbsp; vgimport&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Register exported volume group with system&lt;BR /&gt;&amp;nbsp; vgmerge&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Merge volume groups&lt;BR /&gt;&amp;nbsp; vgmknodes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Create the special files for volume group devices in /dev&lt;BR /&gt;&amp;nbsp; vgreduce&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remove physical volume(s) from a volume group&lt;BR /&gt;&amp;nbsp; vgremove&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remove volume group(s)&lt;BR /&gt;&amp;nbsp; vgrename&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Rename a volume group&lt;BR /&gt;&amp;nbsp; vgs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display information about volume groups&lt;BR /&gt;&amp;nbsp; vgscan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Search for all volume groups&lt;BR /&gt;&amp;nbsp; vgsplit&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Move physical volumes into a new or existing volume group&lt;BR /&gt;&amp;nbsp; version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Display software and driver version information&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,2,sbl_init:VmAssistant::initAssistants 0&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing File System Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing SCSI Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing OS Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.321052): cat /etc/SuSE-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.322931): Output:&lt;BR /&gt;cat: /etc/SuSE-release: No such file or directory&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.323119): cat /etc/SuSE-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.325381): Output:&lt;BR /&gt;cat: /etc/SuSE-release: No such file or directory&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,26,OsAssistant::initAssistants: Couldn't init assistant.&amp;nbsp; Error: &lt;BR /&gt;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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.325777): cat /etc/redhat-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.328010): Output:&lt;BR /&gt;redhat release 5&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.332753): cat /etc/SuSE-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.334570): Output:&lt;BR /&gt;cat: /etc/SuSE-release: No such file or directory&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.334643): cat /etc/redhat-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.336891): Output:&lt;BR /&gt;redhat release 5&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.336958): cat /etc/redhat-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.339244): Output:&lt;BR /&gt;redhat release 5&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 1 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing Host Cluster Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing Multipathing Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.340094): /etc/init.d/multipathd status&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.350678): Output:&lt;BR /&gt;multipathd (pid&amp;nbsp; 3083) is running...&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,26,MpAssistant::initAssistants: Couldn't init assistant.&amp;nbsp; Error: &lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,Operation::addErrorReport: (1) MpAssistant:MpAssistant 6 1082:Initialization of MpAssistant failed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.351092): cat /etc/SuSE-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.353351): Output:&lt;BR /&gt;cat: /etc/SuSE-release: No such file or directory&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.353420): cat /etc/redhat-release&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.355656): Output:&lt;BR /&gt;redhat release 5&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.355855): /etc/init.d/multipathd status&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.366346): Output:&lt;BR /&gt;multipathd (pid&amp;nbsp; 3083) is running...&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.366416): lsmod | grep multipath&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.370722): Output:&lt;BR /&gt;dm_multipath&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 56921&amp;nbsp; 2 dm_round_robin&lt;BR /&gt;scsi_dh&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 42177&amp;nbsp; 1 dm_multipath&lt;BR /&gt;dm_mod&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 101649&amp;nbsp; 51 dm_multipath,dm_raid45,dm_zero,dm_log&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 1 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing HBA Assistants&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,Initialized vmwarefcp&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.371277): /sbin/lsmod | grep iscsi&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.375246): Output:&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,26,HbaAssistant::initAssistants: Couldn't init assistant.&amp;nbsp; Error: &lt;BR /&gt;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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.375675): /sbin/lsmod | grep iscsi&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,9,0,ASSISTANT EXECUTION (at 0.379480): Output:&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,26,HbaAssistant::initAssistants: Couldn't init assistant.&amp;nbsp; Error: &lt;BR /&gt;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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 2 Error Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,6,ErrorReport::cleanErrorReportList: 0 Warning Report objects&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying VM Assistant versions&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying File System Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying Multipathing Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying Host Cluster Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying OS Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying SCSI Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Verifying HBA Assistant version&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]i,2,6,"-Initializing ONTAPI&lt;BR /&gt;"&lt;BR /&gt;12:26:50 04/26/11 [f7f0e6c0]v,2,18,FilerZephyr::startup: done =&amp;gt; 0&lt;BR /&gt;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&lt;BR /&gt;[root@aora11g1 netapp_linux_host_utilities_5_2]#&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2011 10:36:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26138#M4211</guid>
      <dc:creator>Mathias_Robichon</dc:creator>
      <dc:date>2011-04-26T10:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26144#M4212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathias,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Funny, I got the same issue today.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My configuration is a little bit different with CentOS 5.6 but error message is the same:&lt;/P&gt;&lt;P&gt;"Fatal error: Assertion detected in production code: ../sbl/Operation.cpp:173: Test 'osAssistants.size() == 1' failed"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way I fixed it:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;edit /etc/redhat-release file&lt;/LI&gt;&lt;LI&gt;replace string "CentOS release 5.6 (Final)"&lt;/LI&gt;&lt;LI&gt;by "Red Hat Enterprise Linux Server release 5.6 (Tikanga)"&lt;/LI&gt;&lt;LI&gt;and snapdrived is starting now succesfully..&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe your /etc/redhat-release file is missing or corrupted...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps,&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Frederic&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2011 20:09:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26144#M4212</guid>
      <dc:creator>FREDERICS51</dc:creator>
      <dc:date>2011-04-26T20:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26152#M4213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frederic,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You're right. It is exactly the problem. We found the solution as the same time. We did that :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;[root@aora11g2 ~]# echo "Red Hat Enterprise Linux Server release 5.5 (Tikanga)" &amp;gt; /etc/issue&lt;BR /&gt;You have new mail in /var/spool/mail/root&lt;BR /&gt;[root@aora11g2 ~]# echo "Red Hat Enterprise Linux Server release 5.5 (Tikanga)" &amp;gt; /etc/redhat-release&lt;BR /&gt;[root@aora11g2 ~]# service snapdrived start&lt;BR /&gt;Starting snapdrive daemon: Successfully started daemon&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mathias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2011 07:34:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26152#M4213</guid>
      <dc:creator>Mathias_Robichon</dc:creator>
      <dc:date>2011-04-27T07:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26157#M4214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm on SL 6.5 and I had to change:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Scientific Linux release 6.5 (Carbon)&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Red Hat Scientific Linux release 6.5 (Carbon)&lt;/P&gt;&lt;P&gt;to get past this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Faye&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(not Bob, his colleague, using his creds &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 13:48:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/26157#M4214</guid>
      <dc:creator>wolfsonmicro</dc:creator>
      <dc:date>2014-03-26T13:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/101681#M4215</link>
      <description>&lt;P&gt;Your solution helped but now i have this error when i check status of snapdrived:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;9000-015 SOAP ERROR : 28 : A connection error occured. Please check if snapdrived is running&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2015 16:12:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/101681#M4215</guid>
      <dc:creator>Kangethe</dc:creator>
      <dc:date>2015-03-11T16:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: SDU - Problem to start SnapDrived on RedHat Linux.</title>
      <link>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/110052#M4216</link>
      <description>&lt;P&gt;do you fixed it ? I have the same question!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2015 14:41:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SDU-Problem-to-start-SnapDrived-on-RedHat-Linux/m-p/110052#M4216</guid>
      <dc:creator>PUKKA_XUJIE</dc:creator>
      <dc:date>2015-09-22T14:41:48Z</dc:date>
    </item>
  </channel>
</rss>

