Error 1 Sending The Modular Data For Machine_type
Sign in Pricing Blog Support Search GitHub This repository Watch 64 Star 326 Fork 194 ganglia/monitor-core Code Issues 51 Pull requests 7 Projects 0 Wiki Pulse Graphs New issue syslog fills with "Error 1 sending the modular data", gmond keeps using socket after EINVAL #65 Open dpocock opened this Issue Oct 28, 2012 · 2 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 3 participants Ganglia Development Team member dpocock commented Oct 28, 2012 Suggested action/solution: if write returns EINVAL, gmond should try to recreate or re-bind the sending socket, rather than continuing to send on a bad socket (and filling logs with errors) Google reveals this has been discussed several times in the past, and none of the discussions ended with a solution, so I'm presenting some analysis below. Here is what I did and what I found: I discovered my gmond PID = 21015 and I checked it with strace: strace -p 21015 -o /tmp/gmond.errs -v After about a minute, I had a look inside /tmp/gmond.errs, lots of this: write(7, "\0\0\0\205\0\0\0\4srv1\0\0\0\fmachine_type\0\0\0\0"..., 52) = 52 write(8, "\0\0\0\205\0\0\0\4srv1\0\0\0\fmachine_type\0\0\0\0"..., 52) = -1 EINVAL (Invalid argument) write(7, "\0\0\0\200\0\0\0\4srv1\0\0\0\7os_name\0\0\0\0\0\0\0\0\6"..., 164) = 164 write(8, "\0\0\0\200\0\0\0\4srv1\0\0\0\7os_name\0\0\0\0\0\0\0\0\6"..., 164) = -1 EINVAL (Invalid argument) time([1351418592]) = 1351418592 sendto(9, "<30>Oct 28 11:03:12 /usr/sbin/gm"..., 90, MSG_NOSIGNAL, NULL, 0) = 90 Notice the `sendto' is actually sending the error to syslog, not sending a metric packet Ok, the `write' calls show me two file descriptors, 7 and 8. writes to FD 8 are failing with EINVAL: write(8, .... ) = -1 EINVAL (Invalid argument) The file descriptors correspond to two different udp_send_channels in gmond.conf - but which is which? Fortunately, lsof tells me: lsof -p 21015 -n gmond 21015 ganglia 7u IPv4 2747622 0t0 UDP 192.168.1.2:44778->239.2.11.71:8649 gmond 21015 ganglia 8u IPv4 2747628 0t0 UDP (VPN address):53976->(remote server address):8649 Notice that FD 7 corresponds to a very standard multicast channel, while FD 8 corresponds to a UDP unicast channel. I have deleted the IP addresses, but this immediately revealed the problem (in my case anyway): the local address (VPN address) exis
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a https://github.com/ganglia/monitor-core/issues/65 file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Ganglia Mailing Lists Ganglia Scalable, distributed monitoring system for high-performance computing Brought to you by: bernardli, bnicholes, carenas, knobi1, and 2 others Summary Files Reviews Support Wiki Mailing Lists Code Blog ganglia-announce ganglia-bugzilla ganglia-developers ganglia-general https://sourceforge.net/p/ganglia/mailman/ganglia-general/thread/502BA541.5070301@gmail.com/ ganglia-svn ganglia-general [Ganglia-general] Error 1 sending the modular data From: Iban Cabrillo
for the unit diskStable Newton-Cotes FormulasOverlapped Newton-Cotes QuadraturesStable Newton-Cotes Formulas (Open Type)Noise-robust smoothing filterQuickLaTeXImage ProcessingNoise Robust Gradient OperatorsAbout« Digital Filters by Richard HammingHow To: QextSerialPort for Visual Studio 2010 »How To Compile Qt with Visual StudioFebruary 1, 2011This post is a step-by-step guide on how to compile Qt http://www.holoborodko.com/pavel/2011/02/01/how-to-compile-qt-4-7-with-visual-studio-2010/ 4.x.x with MSVC 2010.Although we use Qt 4.7.1 as an example (for historical reasons), you can also find suggestions on building newer versions of Qt by MSVC 2012 and even by Intel Compiler for both platforms x86 and x64. All kudos go to numerous contributors, who spend their time to do all the tweaking and testing (see updates below).In particular there are instructions on error 1 how to build Qt 5 for x64 platform contributed by Vincenzo Mercuri.Updates December 21, 2012. Vincenzo Mercuri shared instructions for building Qt 5.0.0 in x64 configuration.
December 19, 2012. Vincenzo Mercuri informed that he have compiled Qt 4.8.4-x64 by the guide. Also he shared his instructions for building Qt with Intel C++ Compiler into static library.November 4, 2012: As reported by Mike Pelton, whatnick and error 1 sending Borislav Stanimirov, 32 & 64bit versions of Qt 4.8.3 have been successfully compiled by this guide, by both Visual Studio 2010 & 2012. Be aware that Qt might not be adjusted yet for Windows 8 (as reported here).June 4, 2012: As reported by Wenqing, Qt 4.8.2 has been successfully compiled by this guide.April 5, 2012: As reported by Snouty, 32bit version of Qt 4.8.1 has been successfully compiled by this guide.December 20, 2011: As reported by Evon, 64bit version of Qt 4.8.0 has been successfully compiled by this guide. To do 64bit compilation, please use Visual Studio x64 Win64 Command Prompt (2010) in step 8. Also please use jom 1.06 and don't forget to install Service Pack 1 for Visual Studio.September 16, 2011: Qt 4.7.4 has been successfully compiled by this guide.August 14, 2011: In order to build Qt for 64 bits just use Visual Studio x64 Win64 Command Prompt (2010) in step 8. Also install Service Pack 1 for Visual Studio 2010 beforehand - it fixes few bugs related to x64 compilation.July 18 2011: Qt 4.7.3 and Qt 4.8 (beta) has been successfully compiled by this guide. Just replace