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

Failed request: runJobInline . Result: Internal Server Error #534

Closed
jerome83136 opened this issue Sep 5, 2013 · 2 comments
Closed

Failed request: runJobInline . Result: Internal Server Error #534

jerome83136 opened this issue Sep 5, 2013 · 2 comments
Assignees
Labels
Milestone

Comments

@jerome83136
Copy link

Hello,
As it was suggested, I open an issue for my problem with rundeck.

Full Story follows:

Hello,

I'm testing RUNDESK which I want to use to run tasks on multiple nodes, remotely.

I've created a job, associated to my localhost node (where rundesk is installed).

When I try to run that job (remote command: "uname -a"), I get an error "Failed request: runJobInline . Result: Internal Server Error"

The detailled log found in $RDEC_BASE//var/log/service.log follows:

2013-09-02 18:51:10,324 ERROR GrailsExceptionResolver - Exception occurred when processing request: [POST] /job/runJobInline
Stacktrace follows:
java.lang.NullPointerException: Cannot get property 'argString' on null object
at rundeck.services.ExecutionService.selectSecureOptionInput(ExecutionService.groovy:1188)
at rundeck.services.ExecutionService.selectSecureOptionInput(ExecutionService.groovy)
at rundeck.services.ExecutionService$selectSecureOptionInput.callCurrent(Unknown Source)
at rundeck.services.ExecutionService$selectSecureOptionInput.callCurrent(Unknown Source)
at rundeck.services.ExecutionService.executeScheduledExecution(ExecutionService.groovy:1078)
at rundeck.services.ExecutionService$$FastClassByCGLIB$$ffb73873.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at rundeck.services.ExecutionService$$EnhancerByCGLIB$$e636f2d0.executeScheduledExecution()
at rundeck.services.ExecutionService$executeScheduledExecution.call(Unknown Source)
at rundeck.controllers.ScheduledExecutionController.runJob(ScheduledExecutionController.groovy:1633)
at rundeck.controllers.ScheduledExecutionController.this$2$runJob(ScheduledExecutionController.groovy)
at rundeck.controllers.ScheduledExecutionController$_closure28.doCall(ScheduledExecutionController.groovy:1570)
at rundeck.controllers.ScheduledExecutionController$_closure28.doCall(ScheduledExecutionController.groovy)

Please note that, when I try to run a command (not a JOB), by using the form in the "Nodes" tab, it just works fine.
The output shows: "Linux localhost.localdomain 2.6.32-358.18.1.el6.i686 #1 SMP Wed Aug 28 14:27:42 UTC 2013 i686 i686 i386 GNU/Linux"

Some useful information (I hope):

  • tried a .jar / RPM install
  • now running the 1.6.0.1 version.
  • also tried the 1.6.1 version

These actions did not help me.

could you give me some help ?

Thanks by advance

Best regards

Jérôme

Alex Honor  

4 sept.
Hi Jerome,

That looks like a bug. As a work around, you might try mlei's suggestion to specify the command using bash -c 'uname -a'. Would you mind logging this as an issue? No matter what, a NullPointerException should not be thrown.

Thanks

  • afficher le texte des messages précédents -

    • afficher le texte des messages précédents -

    You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

    For more options, visit https://groups.google.com/groups/opt_out.

Alex Honor

[SimplifyOps, Inc | [email protected] ]

Hi Alex,
Thanks for the reply.

I've just tried that:

Edited the job and changed the command for:

  • /bin/bash -c 'uname -a'
  • bash -c 'uname -a'

The same error still occurs :-(

I don't know I it can help: I'm using a Virtualbox VM with a Centos 6.4 x86

May I ask you how I can log it as an issue ?

Thanks by advance
Regards
Jérôme

@jerome83136
Copy link
Author

Hello,
The issue is fixed.
It seems that if we create a job with a single command without any option, it just throw the error: "java.lang.NullPointerException: Cannot get property 'argString' on null object"

After adding an option in the same job, it just runs fine.

Thanks
Jérôme

@gschueler
Copy link
Member

hi @jerome83136 I reopened this as it should not have a problem when running a job without an option

@ghost ghost assigned gschueler Sep 11, 2013
gschueler added a commit that referenced this issue Sep 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants