This post is more than 5 years old
15 Posts
0
1692
July 13th, 2016 09:00
Getting error - "value of type=6 is not representable" for platform API '/platform/1/statistics/current?key=node.memory'
We are building a splunk plugin for Isilon and fetching data through Platform APIs.
For memory monitoring we are executing API call - /platform/1/statistics/current?key=node.memory' on Isilon Simulator versions 7.2 and 8.0
However, We are getting below given output for this call :
{
"stats" :
[
{
"devid" : 1,
"error" : "value of type=6 is not representable",
"error_code" : null,
"key" : "node.memory",
"time" : 1468426270,
"value" : null
}
]
}
We couldn't find reason for this error in documents. Any idea when we get this error?
Thanks,
Pankaj
No Events found!
kipcranford
125 Posts
1
July 19th, 2016 09:00
x4102-1# isi version osrelease
v7.2.1.3
x4102-1# isi statistics query -s node.memory
NodeID node.memory
1 0x00304f4600ff4aff00000000
x4101-1# isi version | awk '{print $3}'
v8.0.0.1
x4101-1# isi_classic statistics query -s node.memory
NodeID node.memory
1 0x00805c5d330000000090e3d80a0000000000000000000000
In OneFS 8.0 and later releases, the 'node.memory' key is no longer present as was pointed out by Peter_Sero:
x4101-1# isi version | awk '{print $3}'
v8.0.0.1
x4101-1# isi statistics list keys | grep node | grep memory
node.memory.used
node.memory.free
node.memory.cache
The fact that the 'node.memory' key (in OneFS 8.0+) still seems to be in the code somewhere (i.e. you don't get an "invalid key" return when it's queried) looks to me like a bug. I'll file it as such and update this thread with what I find out.
Peter_Sero
6 Operator
•
1.2K Posts
1
July 14th, 2016 05:00
I've seen this error with some newer keys that, when used on the CLI with "isi statistics",
return seemingly meaningless strings -- probably encoding arrays in some packed form
which hasn't been documented yet.
In your case, "node.memory" isn't even advertised by /platform/1/statistics/keys,
at least not on OneFS 7.2.0.
But these keys work:
node.memory.free
node.memory.used
node.memory.cache
hth
-- Peter
Isilon123
15 Posts
0
July 14th, 2016 23:00
Thanks for the reply Peter.
I agree that this API call is not advertised but my assumption is that if you are not getting 404 - Not found error that meand that API all is valid and should give statistical value. I tried isi statisctics cli but it is also giving '--' in output.
For now I have no choice but to use 'node.memory.free' and 'node.memory.used' and add them to get node memory.
Thanks,
Pankaj
kipcranford
125 Posts
0
July 15th, 2016 08:00
>
> I tried isi statisctics cli but it is also giving '--' in output.
>
Can you post the exact 'isi statistics' syntax you used, and the output you received?
Isilon123
15 Posts
0
July 18th, 2016 06:00
Following is the command and output screenshot for node.memory:
Thanks,
Pankaj
Peter_Sero
6 Operator
•
1.2K Posts
1
July 19th, 2016 02:00
OneFS 7.2.0.4 CLI:
# isi statistics query -s node.memory
NodeID node.memory
1 0x00ff1bff00105f4100000000
"Encoded" data, but undocumented....
Isilon123
15 Posts
0
July 19th, 2016 02:00
kipcranford @Peter_sero
Thanks for all the help. I am struggling with one more issue and it is kind of a blocker for me. Can you have a look at this question? - Is there a Platform API to get mapping of device id and internal-ip?
Thanks,
Pankaj
Isilon123
15 Posts
0
July 19th, 2016 02:00
OneFS 7.2.0.1 CLI :
Thanks,
Pankaj
Isilon123
15 Posts
0
July 19th, 2016 10:00
Thanks a lot Kip. I really appreciate all the help you have been doing since last few days.
Thanks,
Pankaj