Menu

#4 ClientTomout of NC_Net segmentation fault check_nt

v3.x
open
tony
None
8
2008-08-15
2008-03-20
ph_lachi
No

Hi,

when starting check_nc_nt with the following options:
./check_nc_nt -p 12489 -H [hostname] -s [password] -v EVENTLOG -t 30 -l "Application,Error,15,0,1,Fatal Error,0"

it dies (sometimes) with a segmentation violation. This behavior doesn't seem to correlate with the timeout values, but that's only a suggestion.

I did execute an strace before with standard options (output is attached). If any other information is required, please let me know.

Discussion

  • ph_lachi

    ph_lachi - 2008-03-20

    strace ./check_nc_nt

     
  • tony

    tony - 2008-08-15

    Logged In: YES
    user_id=1453420
    Originator: NO

    Thanks for the Stacktrace, It pinpointed the error.
    a couple of other reports of this same issue were also reported recently.

    I found the error was induced in the upgrade process to NC_Net 4.0
    The error is due to Check_nt recieving an erro Message of
    "<error value=\"NC_Net TImeout\"/>
    instead of "ERROR:
    Error handling of Check_nt is done with checking the start of the output for the ERROR:
    I will pathch this shortly

    TOny

     
  • tony

    tony - 2008-08-15
    • priority: 5 --> 8
    • assigned_to: nobody --> montitech
    • summary: EVENTLOG dies with segmentation fault --> ClientTomout of NC_Net segmentation fault check_nt
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.