Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
Description
Hi,
The graphs for DRBD are not working (no values) however I can see data via telnet:
- telnet 192.168.1.10 36602 | sed -n '/<<<drbd>>>/,/<<<.*>>>/p'
<<<drbd>>>
version: 8.4.2 (api:1/proto:86-101)
GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by dag@Build64R6, 2012-09-06 08:16:10
0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:70185244 nr:0 dw:65118492 dr:5896129 al:2248 bm:579 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
<<<postfix_mailq>>>
Connection closed by foreign host.
Attachments
Activity
it seems for me that it doesn't detect it at all after a deletion. I have just tried with another host and that doesn't have a DRBD section now either, so it's not just one broken on here it seems.
Just to clarify, i have updated nothing at all on the client side at all, is that correct? i have a feeling i'm missing something!
Well, the old DRBD application and mechanisms are now gone, replaced with a bit of code to fake the application using the <<<drbd>>> section.
You should see it readded during polling now, it's working for me (albeit the data graphs are 1024 off at the moment due to drbd returning KB not B 
)
That's interesting because my issue appears to be with it not detecting the DRDB element at all now. So for a new host added there is now simply no longer a tab under agents for DRBD at all.
So it only finds NTPD in my example (which is the only other active agent plugin on there) - the DRBD was in there before I deleted and re-added the host though (albeit with blank graphs).
I'm not sure if this is 'the' issue you are looking at, as it sounds like you are maybe dealing with graphs that don't update, rather than it totally not showing up as having DRBD installed at all? Hope that makes some remote sense...
You can remove the old drbd file, I'm now using the <<<drbd>>> section built in to the agent.
Parsing it is proving to be a bit of a pain, but I think I have that sorted now. I thought it was all working, but it seems like there are still some issues, as it' snot actually dropping data to the RRDs successfully. I need to check that.
FWIW - I had tested by removing and re-adding an existing DRBD host, after the re-add it now no longer detects the host as having the DRBD agent at all.
Also, I see the drbd file in agent-local is still from October 2013 in my pull, so i have nothing new to 'push' to the clients - This may or may not be remotely relevant information 
Excellent - does it require the client side agent script to be replaced or modified? Ours are still not showing results for anything, or is there some other corrective action required when hosts with DRBD already existed but were already broken?
I'm looking at rewriting the whole thing at the moment to do all of the parsing on the Observium side, switching to the <<<drbd>>> output.
It's taken the whole day so far. I was hoping to clear up another couple of hundred ancient tickets too, oh well!
Ok good, i guess! At least you can see it also. Let me know if there is any information I can provide, we have a number (about 8-10) of instances of DRBD here on a mixture of Debian and Ubuntu, fwiw, so can test any potential fixes. Cheers!
This is working pretty much fine for me now. Just dumped the agent on a new system with drbd, and it worked fine there too.