• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • log-parser-plugin
    • None
    • jenkins Version 2.462.1
      logparser plugin Version 2.3.5

      We have a logparser step in our pipeline.

      99% of the time the step takes under 1sec. but sometimes the logparser does not exit.

      and then the whole pipeline times out.

      No timeout. 

      14:50:32 No translation files to commit - exit
      [Pipeline] }
      [Pipeline] // script
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] stage
      [Pipeline] { (Declarative: Post Actions)
      [Pipeline] logParser
      [Pipeline] script
      [Pipeline] {

       

      Stage Logs (Declarative: Post Actions)  
          Console output (build log) parsing  (self time 484ms)    

       
      Time out: Logparser is not completed after 20min. 

      21:58:26 No translation files to commit - exit
      [Pipeline] }
      [Pipeline] // script
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] stage
      [Pipeline] { (Declarative: Post Actions)
      [Pipeline] logParser
      22:20:10 Cancelling nested steps due to timeout
      Stage Logs (Declarative: Post Actions) 
            Console output (build log) parsing (self time 21min 44s)

      Pipeline:
       

      post {       
      always {       
         step([$class: 'LogParserPublisher',
                   failBuildOnError: false, 
                   unstableOnWarning: false,     
                   parsingRulesPath: env.WORKSPACE + '\\Tools\\Jenkins\\logParsingRegex.txt',  
                 useProjectRule: false])

       

          [JENKINS-73671] Logparser pipeline step hangs .

          Jens added a comment -

          some jenkins log

          Start reading log part 0 in thread #0
          Aug 22, 2024 9:55:23 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionA thread (pool-29-thread-1/4947) died unexpectedly due to an uncaught exception. This may leave your server corrupted and usually indicates a software bug.
          java.lang.NullPointerException: Cannot invoke "hudson.plugins.logparser.LogParserLogPart.getLines()" because "this.logPart" is null
          	at PluginClassLoader for log-parser//hudson.plugins.logparser.LogParserThread.run(LogParserThread.java:37)
          	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
          	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
          	at java.base/java.lang.Thread.run(Unknown Source)
          
          Aug 22, 2024 9:55:23 AM INFO hudson.plugins.logparser.LogParserReader readLogPart

          Jens added a comment - some jenkins log Start reading log part 0 in thread #0 Aug 22, 2024 9:55:23 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionA thread (pool-29-thread-1/4947) died unexpectedly due to an uncaught exception. This may leave your server corrupted and usually indicates a software bug. java.lang.NullPointerException: Cannot invoke "hudson.plugins.logparser.LogParserLogPart.getLines()" because "this.logPart" is null at PluginClassLoader for log-parser//hudson.plugins.logparser.LogParserThread.run(LogParserThread.java:37) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Aug 22, 2024 9:55:23 AM INFO hudson.plugins.logparser.LogParserReader readLogPart

          Jens added a comment -

          I have determined the cause of the hang.

          The problem is QuickEdit in a windows console

          Our jenkins server runs via a batch script in a console.

          If quickedit is enabled and text is selected in the console. Then the jenkins server is blocked from writing to the console.

          Jenkins can still start builds and will run as normal but apparently logparser does not handle not being able to read/write to console and will hang until enter is pressed in the console. 

          I have disabled QuickEdit and this solves my problem.

          This bug can be closed if needed.

          Jens added a comment - I have determined the cause of the hang. The problem is QuickEdit in a windows console Our jenkins server runs via a batch script in a console. If quickedit is enabled and text is selected in the console. Then the jenkins server is blocked from writing to the console. Jenkins can still start builds and will run as normal but apparently logparser does not handle not being able to read/write to console and will hang until enter is pressed in the console.  I have disabled QuickEdit and this solves my problem. This bug can be closed if needed.

            mreinhardt Martin Reinhardt
            jens_lund_jensen Jens
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: