How to log log failures?



  • How are you doing this in your code? If logging fails, what do you log to?



  • I hard fail.



  • @frits said:

    I hard ❤ fail.

    FTFY



  • @frits said:

    I hard fail.

    FOYSW!



  • Report log failures in the database and report database issues in the log. Simple really.



  • @Nagesh said:

    FOYSW!

    I'm sorry, your acronym doesn't show up in urban dictionary.  Can you please spell it out?



  • @frits said:

    I'm sorry, your acronym doesn't show up in urban dictionary. Can you please spell it out?
    Well, he did give you the last three words in the tags. I'm sure you can make an educated guess at the first two.



  • @Scarlet Manuka said:

    @frits said:
    I'm sorry, your acronym doesn't show up in urban dictionary. Can you please spell it out?
    Well, he did give you the last three words in the tags. I'm sure you can make an educated guess at the first two.

    French Onion?

    Fissilingual Oration?

    Fulge On?

    I find it ironic that anyone posting as Nagesh call someone else "silly" or "wanker".



  • @Scarlet Manuka said:

    Report log failures in the database and report database issues in the log. Simple really.
     

     

    What I experienced with logging log failure is infinite recursive function that finally blow the stack and grind all application to sudden halt.

    Not sure if anyone else here also experience same thing. We are using log4j over here just if your midley curious.



  • @Nagesh said:

    What I experienced with logging log failure is infinite recursive function that finally blow the stack and grind all application to sudden halt.


    Try doubling the stack size.



  • @pjt33 said:

    @Nagesh said:

    What I experienced with logging log failure is infinite recursive function that finally blow the stack and grind all application to sudden halt.


    Try doubling the stack size.

    And build in a sleep, say, 3 seconds will do.



  • @Weps said:

    @pjt33 said:
    @Nagesh said:

    What I experienced with logging log failure is infinite recursive function that finally blow the stack and grind all application to sudden halt.


    Try doubling the stack size.

    And build in a sleep, say, 3 seconds will do.

    Are you making post from experience or just atempt to lead me down garden path? Please let me know!

    TIA,
    Nagesh



  • @Nagesh said:

    Are you making post from experience or just atempt to lead me down garden path?

    Oh, it's definitely experience.



  • Console.Beep() and morse code.



  • @bgodot said:

    Console.Beep() and morse code.
    I'm a big fan of MessageBox.Show(), though Console.Beep() doesn't block.  Interesting...



  • @bgodot said:

    Console.Beep() and morse code.
     

    While this is an excellent method of outputing error messages it does not actually log them.

    What I would do is connect a microphone to a second PC to record the error beeps.  The only way to get the time that the beeps were emitted is to have a speakerphone permanently connected to the speaking clock and record this too.



  • @RTapeLoadingError said:

    @bgodot said:

    Console.Beep() and morse code.
     

    While this is an excellent method of outputing error messages it does not actually log them.

    What I would do is connect a microphone to a second PC to record the error beeps.  The only way to get the time that the beeps were emitted is to have a speakerphone permanently connected to the speaking clock and record this too.

     

     

    Alternatively, instead of just a simple recorder on the other PC - have the software listen for a certain series of beeps (the start of the output) and then record the beeps, along with the date / time stamp

     



  • @RTapeLoadingError said:

    @bgodot said:

    Console.Beep() and morse code.
     

    While this is an excellent method of outputing error messages it does not actually log them.

    What I would do is connect a microphone to a second PC to record the error beeps.  The only way to get the time that the beeps were emitted is to have a speakerphone permanently connected to the speaking clock and record this too.

    Due to this sugestion, my project manager is now dead. He dead from laffing too much. Our company lawyer is going to issue court summons for RTapeLoading and bgodot. Get ready for trip to India.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.