Project

General

Profile

Bug #15011

Updated by Nicolas CHARLES over 5 years ago

I got the following error after doing a clear cache with 2500 nodes 
 <pre> 
 [2019-06-01 12:59:22] WARN    explain_compliance.a04d8f89-27f4-4428-ad89-6ab4e45798a4a04d8f89-27f4-4428-ad89-6ab4e45798a4 - Received a run at 2019 
 -06-01T12:57:11.000Z for node 'a04d8f89-27f4-4428-ad89-6ab4e45798a4a04d8f89-27f4-4428-ad89-6ab4e45798a4' with configId '20190529-153902-d76426ef 
 ' but that node should be sending reports for configId 20190531-224745-355b5fdd 
 Jun 01, 2019 12:59:22 PM com.zaxxer.nuprocess.linux.LinuxProcess start 
 WARNING: Failed to start process 
 java.io.IOException: error=7, Argument list too long 
         at com.zaxxer.nuprocess.internal.LibJava8.Java_java_lang_UNIXProcess_forkAndExec(Native Method) 
         at com.zaxxer.nuprocess.linux.LinuxProcess.start(LinuxProcess.java:109) 
         at com.zaxxer.nuprocess.linux.LinProcessFactory.createProcess(LinProcessFactory.java:40) 
         at com.zaxxer.nuprocess.NuProcessBuilder.start(NuProcessBuilder.java:266) 
         at com.normation.rudder.hooks.RunNuCommand$.run(RunNuCommand.scala:153) 
         at com.normation.rudder.hooks.RunHooks$.$anonfun$asyncRun$3(RunHooks.scala:186) 
         at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:303) 
         at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37) 
         at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60) 
         at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402) 
         at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) 
         at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) 
         at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) 
         at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) 

 [2019-06-01 12:59:22] INFO    policy.generation - Policy generation completed in:      2921610 ms 
 [2019-06-01 12:59:22] ERROR policy.generation - Error when updating policy, reason was: Exit code=-2147483648 for hook: '/opt/rudder/etc/hooks.d/policy-generation-finished/50-reload-policy-file-server'. 
  stdout:  
  stderr: '' 
 [2019-06-01 12:59:22] INFO    policy.generation - Flag file '/opt/rudder/etc/policy-update-running' successfully removed 
 [2019-06-01 12:59:22] ERROR policy.generation - Policy update error for process '111' at 2019-06-01 12:59:22: Exit code=-2147483648 for hook: '/opt/rudder/etc/hooks.d/policy-generation-finished/50-reload-policy-file-server'. 
 </pre> 

 This is a template, please edit and remove what is not relevant. 

 I found this bug in Rudder version [Your Version here], on [Distribution here] 

 This bug happens: 

 * During installation of Rudder agent / Rudder server 
 * While running rudder agent on a Node 
 * When using Rudder web interface 
 * When looking at compliance of a Node 
 * When configurations are generated on Rudder Server 
 * When a Nodes applies a configuration 

 Description: 


 You can reproduce it with the following steps: 

 * ... 
 * ... 

 You can workaround this issue by doing likewise: 

Back