Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

send_multi: message improvements #15

Merged
merged 2 commits into from
Jul 28, 2011
Merged

send_multi: message improvements #15

merged 2 commits into from
Jul 28, 2011

Conversation

flackem
Copy link
Contributor

@flackem flackem commented Jul 28, 2011

Hi Sven,

send_multi is too silent when the feeding check_multi has a problem, it only states:
WARNING: 0 check_multi child checks submitted

I now look for a ASCIIZ message in STDIN stream and provide this message instead,
if there were no successful child checks parsed.

The only thing to get this working is to add a '2>&1' to the check_multi cmdline.

Cheers,
-Matthias

flackem added 2 commits July 28, 2011 07:04
Errors in the feeding check_multi are hard to find if there is no
output. And 'WARNING: 0 check_multi child checks submitted' sounds
like 'something went wrong' ;).
When no chunks could be read, send_multi now looks for a valid
ASCIIZ messages in the STDIN input and prints them out. The only
thing you have to do is to redirect STDERR to STDOUT in your
command line: check_multi ... 2>&1 | send_multi ...
@sni
Copy link
Owner

sni commented Jul 28, 2011

Hi Matthias,

instead of warning, i would prefer Unknown. Should we change the return code too?

Thanks,
Sven

@flackem
Copy link
Contributor Author

flackem commented Jul 28, 2011

You're pretty right with UNKNOWN, go for it...

-Matthias

sni added a commit that referenced this pull request Jul 28, 2011
send_multi: message improvements
@sni sni merged commit 1e3eacf into sni:master Jul 28, 2011
sni added a commit that referenced this pull request Nov 19, 2024
this leads to crashes sometimes:

    #0  0x00007ffff6f56387 in raise () from /lib64/libc.so.6
    #1  0x00007ffff6f57a78 in abort () from /lib64/libc.so.6
    #2  0x00007ffff43bca95 in __gnu_cxx::__verbose_terminate_handler() () from /lib64/libstdc++.so.6
    #3  0x00007ffff43baa06 in ?? () from /lib64/libstdc++.so.6
    #4  0x00007ffff43baa33 in std::terminate() () from /lib64/libstdc++.so.6
    #5  0x00007ffff43ba631 in __gxx_personality_v0 () from /lib64/libstdc++.so.6
    #6  0x00007ffff41559f4 in ?? () from /lib64/libgcc_s.so.1
    #7  0x00007ffff4155d44 in _Unwind_ForcedUnwind () from /lib64/libgcc_s.so.1
    #8  0x00007ffff6ab0362 in __pthread_unwind () from /lib64/libpthread.so.0
    #9  0x00007ffff6aa88e5 in sigcancel_handler () from /lib64/libpthread.so.0
    #10 <signal handler called>
    #11 0x00007ffff701020d in close () from /lib64/libc.so.6
    #12 0x00007ffff55846ab in ?? () from /omd/sites/mon/lib/libgearman.so.8
    #13 0x00007ffff558476e in ?? () from /omd/sites/mon/lib/libgearman.so.8
    #14 0x00007ffff558d02d in ?? () from /omd/sites/mon/lib/libgearman.so.8
    #15 0x00007ffff558d05e in ?? () from /omd/sites/mon/lib/libgearman.so.8
    #16 0x00007ffff558fe78 in gearman_worker_free () from /omd/sites/mon/lib/libgearman.so.8
    #17 0x00007ffff5e7e319 in gm_free_worker (worker=worker@entry=0x7ffff0386ee8) at common/gearman_utils.c:274
    #18 0x00007ffff5e83f88 in result_worker (data=<optimized out>) at neb_module_naemon/result_thread.c:115
    #19 0x00007ffff6aa9ea5 in start_thread () from /lib64/libpthread.so.0
    #20 0x00007ffff701eb0d in clone () from /lib64/libc.so.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants