http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions Software, Support, and Training for Apache Cassandra en-US Fri, 24 May 2013 16:39:04 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions/page/2#post-1268 Thu, 01 Mar 2012 22:44:30 +0000 kireet 1268@http://www.datastax.com/support-forums/ <p>i tried it out, it's working! Thanks for the prompt responses. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions/page/2#post-1262 Wed, 29 Feb 2012 23:49:46 +0000 nickmbailey 1262@http://www.datastax.com/support-forums/ <p>All,</p> <p>The latest release of OpsCenter (1.4.1) was just released this afternoon. It should resolve this issue. Please let us know if you see any other problems. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions/page/2#post-1229 Fri, 24 Feb 2012 17:50:22 +0000 thobbs 1229@http://www.datastax.com/support-forums/ <p>If you have your commitlog directory or saved caches directory on a device mapper (like LVM, for example), that will trigger this. (A few other random device types could also trigger this.) If you see the same stracktrace in your logs when running OpsCenter 1.4, you have the same issue.</p> <p>The only workaround is to move your commitlog and saved caches directories onto a different type of device, like a normal scsi drive, for example.</p> <p>A fix for this will be included in 1.4.1, which we expect to release in a week or two. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1226 Fri, 24 Feb 2012 15:59:24 +0000 kireet 1226@http://www.datastax.com/support-forums/ <p>I am facing this error message as well. Is there a way to confirm that it is the same underlying issue? Is there a workaround until the next release is available or is there a timeline for the next release? </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1163 Thu, 16 Feb 2012 16:13:01 +0000 thobbs 1163@http://www.datastax.com/support-forums/ <p>Great, that should be enough to fix the issue in an upcoming release. Thanks again. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1159 Thu, 16 Feb 2012 00:52:06 +0000 Anonymous 1159@http://www.datastax.com/support-forums/ <p>ls -ltr /sys/block/ccis!c0d0</p> <p>drwxr-xr-x 2 root root 0 Feb 12 04:07 slaves/<br /> drwxr-xr-x 2 root root 0 Feb 12 04:07 holders/<br /> drwxr-xr-x 3 root root 0 Feb 12 04:08 queue/<br /> --w------- 1 root root 4.0K Feb 12 04:08 uevent<br /> lrwxrwxrwx 1 root root 0 Feb 12 04:08 subsystem -&gt; ../../block/<br /> -r--r--r-- 1 root root 4.0K Feb 12 04:08 stat<br /> -r--r--r-- 1 root root 4.0K Feb 12 04:08 size<br /> -r--r--r-- 1 root root 4.0K Feb 12 04:08 removable<br /> -r--r--r-- 1 root root 4.0K Feb 12 04:08 range<br /> -r--r--r-- 1 root root 4.0K Feb 12 04:08 dev<br /> lrwxrwxrwx 1 root root 0 Feb 12 04:08 device -&gt; ../../devices/pci0000:00/0000:00:03.0/0000:0a:00.0/0000:0b:08.0/<br /> drwxr-xr-x 3 root root 0 Feb 12 04:08 cciss!c0d0p2/<br /> drwxr-xr-x 3 root root 0 Feb 12 04:08 cciss!c0d0p1/</p> <p>rpm -qa | grep sysfs</p> <p>sysfsutils-2.0.0-6<br /> libsysfs-2.0.0-6<br /> libsysfs-2.0.0-6 </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1158 Wed, 15 Feb 2012 23:38:01 +0000 thobbs 1158@http://www.datastax.com/support-forums/ <p>Heskech, the output of <code>rpm -qa | grep sysfs</code> might also be worthwhile. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1157 Wed, 15 Feb 2012 23:29:45 +0000 thobbs 1157@http://www.datastax.com/support-forums/ <p>Heskech and Naseerm, thank you both, this has been extremely useful.</p> <p>Heskech, it's very unusual that you don't have the normal sysfs directory structure. Is this RHEL instance setup in an unusual way? In a particular VM, or as a cloud instance somewhere?</p> <p>The output of <code>ls /sys/block/cciss!c0d0</code> would also be useful. </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1155 Wed, 15 Feb 2012 22:03:27 +0000 Anonymous 1155@http://www.datastax.com/support-forums/ <p>thobbs:</p> <p>[root@lfs03 logs]# cat /proc/partitions</p> <p>major minor #blocks name</p> <p> 252 0 104857600 vda<br /> 252 1 131072 vda1<br /> 252 2 1048576 vda2<br /> 252 3 1048576 vda3<br /> 252 4 102628352 vda4<br /> 253 0 2097152 dm-0<br /> 253 1 75497472 dm-1<br /> 253 2 1048576 dm-2<br /> 253 3 2097152 dm-3<br /> [root@lfs03x-dxc1 logs]# iostat -x</p> <p>Linux 2.6.32-71.el6.x86_64 (lfs03x-dxc1.cimops.net) 02/15/12 _x86_64_ (1 CPU)</p> <p>avg-cpu: %user %nice %system %iowait %steal %idle<br /> 10.63 0.00 2.55 2.86 0.00 83.96</p> <p>Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util<br /> vda 0.01 2.84 0.05 42.78 1.83 151.65 3.58 0.13 3.09 0.98 4.20<br /> dm-0 0.00 0.00 0.04 0.44 1.23 3.50 9.93 0.23 478.34 0.55 0.03<br /> dm-1 0.00 0.00 0.01 31.40 0.32 142.07 4.53 0.23 7.47 1.26 3.97<br /> dm-2 0.00 0.00 0.00 0.00 0.00 0.02 7.98 0.00 97.35 10.71 0.00<br /> dm-3 0.00 0.00 0.00 0.69 0.02 5.52 8.01 0.01 19.71 3.52 0.24</p> <p>[root@lfs03x logs]# readlink /sys/dev/block/253:0<br /> ../../devices/virtual/block/dm-0<br /> [root@lfs03x logs]# readlink /sys/dev/block/252:0<br /> ../../devices/virtio-pci/virtio1/block/vda</p> <p>thanks </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1153 Wed, 15 Feb 2012 21:44:13 +0000 Anonymous 1153@http://www.datastax.com/support-forums/ <p>2.6.18-194.11.4.el5:RHEL5:5.5-1:x86_64:ib-dev </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1152 Wed, 15 Feb 2012 21:39:04 +0000 thobbs 1152@http://www.datastax.com/support-forums/ <p>Heskech,</p> <p>Thanks very much. No, that's not what I was expecting. What Linux distro and release are you running? </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1151 Wed, 15 Feb 2012 21:28:45 +0000 Anonymous 1151@http://www.datastax.com/support-forums/ <p>Hi, apologies for not responding earlier. The results of the readlinks are empty. I'm not sure if this was the results you were expecting.</p> <p>ls of /sys -&gt;</p> <p>drwxr-xr-x 3 root root 0 Feb 12 04:07 firmware/<br /> drwxr-xr-x 7 root root 0 Feb 12 04:07 devices/<br /> drwxr-xr-x 2 root root 0 Feb 12 04:08 power/<br /> drwxr-xr-x 35 root root 0 Feb 12 04:08 block/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 kernel/<br /> drwxr-xr-x 14 root root 0 Feb 12 04:08 bus/<br /> drwxr-xr-x 30 root root 0 Feb 12 04:09 class/<br /> drwxr-xr-x 3 root root 0 Feb 12 04:09 fs/<br /> drwxr-xr-x 70 root root 0 Feb 12 04:09 module/</p> <p>ls /sys/block -&gt;</p> <p>drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-6/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-5/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-4/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-3/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-2/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram9/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram8/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram7/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram6/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram5/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram4/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram3/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram2/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram15/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram14/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram13/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram12/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram11/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram10/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram1/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 ram0/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-1/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:08 dm-0/<br /> drwxr-xr-x 7 root root 0 Feb 12 04:08 cciss!c0d0/<br /> drwxr-xr-x 5 root root 0 Feb 12 04:09 md0/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop7/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop6/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop5/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop4/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop3/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop2/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop1/<br /> drwxr-xr-x 4 root root 0 Feb 12 04:09 loop0/ </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1146 Wed, 15 Feb 2012 17:05:05 +0000 nickmbailey 1146@http://www.datastax.com/support-forums/ <p>Naseerm,</p> <p>This is caused by a bug in the agent code when handling certain device types. Hopefully there will be a fix for this bug in the next release of OpsCenter.</p> <p>You could help us make sure we fix the bug correctly by giving the output of the following commands on one of your cassandra nodes:</p> <p>cat /proc/partitions<br /> df &lt;data dir&gt; (&lt;data dir&gt; being the location of data_file_directories configured in cassandra.yaml)<br /> df &lt;commitlog dir&gt; (commitlog dir&gt; being the location of commitlog_directory in cassandra.yaml)<br /> iostat -x<br /> readlink /sys/dev/block/253:0<br /> readlink /sys/dev/block/104:0<br /> readlink /sys/dev/block/104:1</p> <p>Thanks for the help if you are able,<br /> Nick </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1145 Wed, 15 Feb 2012 16:45:56 +0000 Anonymous 1145@http://www.datastax.com/support-forums/ <p>was this issue resolved - i have the same issue, unfortunately and any help would be appreciated</p> <p>TIA </p> http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions#post-1131 Fri, 10 Feb 2012 22:09:45 +0000 thobbs 1131@http://www.datastax.com/support-forums/ <p>Thanks for the output. Would you mind also pasting the results of the following?</p> <p>* <code>readlink /sys/dev/block/253:0</code><br /> * <code>readlink /sys/dev/block/104:0</code><br /> * <code>readlink /sys/dev/block/104:1</code> </p>