Server: irc.freenode.net , Channel: #rundeck
I don’t see any stacktrace being generated, and here are last couple lines from the rundeck.log: 2013-04-16 08:40:06,374 [1870277025@qtp-2099901365-0] WARN grails.app.service.rundeck.services.FrameworkService - rdeck.base is: /etc/rundeck
2013-04-16 08:40:43,316 [1870277025@qtp-2099901365-0] INFO grails.app.service.rundeck.services.ScheduledExecutionService - scheduling immediate job run: TEMP:admin:1:28
2013-04-16 08:40:43,690 [quartzScheduler_Worker-1] ERROR grails.app.service.rundeck.services.ExecutionService - Execution failed: 28: [Workflow , Node failures: {krkenv05saapp1=[]}]
2013-04-16 08:40:43,770 [quartzScheduler_Worker-1] INFO grails.app.service.rundeck.services.ExecutionService - updated scheduled Execution
2013-04-16 08:41:02,017 [1870277025@qtp-2099901365-0] INFO grails.app.service.rundeck.services.ScheduledExecutionService - scheduling immediate job run: TEMP:admin:1:29
2013-04-16 08:41:02,103 [quartzScheduler_Worker-2] ERROR grails.app.service.rundeck.services.ExecutionService - Execution failed: 29: [Workflow , Node failures: {krkenv05saapp1=[]}]
is “krkenv05saapp1” an example windows node?
yes
I use winrs windows command to test that node, and it works just fine
ok, so that’s related
relates to?
oh the error in the stack trace is related to the winrm problem
i’m not sure if configuring run deck log4j to DEBUG level will expose more info from the plugin
is this caused by incorrect version or configuration?
i’m not sure. just trying to get more info
the previous paste I put on is already have debug turn on
debug already set for log4j?
but it didn’t give more information
I set dropdown to debug when I ran the job
log level set to debug
oh, that’s just the log level for the job. there is a global flag which turns on more debug in the service.log
how do I set it?
need to set from project.properteis file?
or framework.properties?
no, it’s in RDECK_BASE/etc/log4j.properties
is this a Launcher or RPM type install?
it is deb
ok, similar to rpm then
yep
how do I turn on debug from log4j?
take a look for /etc/rundeck/log4j.properties
I am on it
ok. set: log4j.rootCategory=DEBUG, file
so need to add this key?
right
the current value will say INFO
ok
after changing it to DEBUG, go ahead and restart
I just did
I will run the job again
ok, you should see a lot more messages in the service.log
this is what I got after DEBUG is set, 2013-04-16 08:52:02.667:/:INFO: Destroying Spring FrameworkServlet ‘gsp’
2013-04-16 08:52:02.691:/:INFO: Destroying Spring FrameworkServlet ‘grails’
2013-04-16 08:52:02.741:/:INFO: Closing Spring root WebApplicationContext
2013-04-16 08:52:02.845::INFO: Shutdown hook complete
…terminated.
WARNING: HTTPS is not enabled, specify -Drundeck.ssl.config=/etc/rundeck/server/config/ssl.properties to enable.
2013-04-16 08:52:04.018::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
2013-04-16 08:52:04.041::INFO: jetty-6.1.21
2013-04-16 08:52:04.140::INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
2013-04-16 08:52:04.964:/:INFO: Initializing Spring root WebApplicationContext
INFO BeanBuilder: [RuntimeConfiguration] Configuring data source for environment: PRODUCTION
WARN BootStrap: using rdeck.base system property: /etc/rundeck
INFO BootStrap: config: rdeck.base = /etc/rundeck
INFO BootStrap: loaded configuration: /etc/rundeck/framework.properties
looks like normal startup messages, so far
yes, not much information there
did you already run a job to the windows node?
yes
ok. so yah it didn’t produce any extra error context
no
ckm, did you post as “wildxy49”?
(post to the google group)
yes
ok. just wanted to be sure
I post it there but no reply, that why I came over here
i wonder if there is a problem with 1.5 with respect to that plugin.
i know there are a couple people working on upgrading the plugin but i am not sure about their status
so this mean I may have to fallback to 1.4 for winrm
or I have to use ssh until the problem gets resolved
they upgraded the plugin to use a newer version of the underlying library (overthere). I’ll reply to your post
ok
hi Diranged what is the problem?
hey
http://pastie.org/7612219
so thast my default.aclpolicy file… i have other policies that give specific groups access to specific projects.
but what i have found is that this policy doesn’t work — i have to change the ‘.*’ to a specific group name to let people log into rundeck at all..
I’m just confused about how to do a group wildcard..
groups/users can’t use a wildcard
really .. that should be documented .:)
so how can i say “all groups” can log in.. or rather, all users can log in
you would have to put all users in a default group, e.g. “users”, then add aclpolicy for that group
for some reason
can’t say there’s still a good reason for it. you should file an enhancement request to change that
ok
for now i have a workaround.. but ill file a request
ok. you can also list multiple groups instead, if you have a static list of them
so i can just do 2 group lines?
one right after the other?
as shown here: http://rundeck.org/docs/manpages/man5/aclpolicy-v10.html#by
using a yaml sequence
ah thanks
[travis-ci] dtolabs/rundeck#186 (development - c8ee337 : Greg Schueler): The build passed.
[travis-ci] Change view : https://github.com/dtolabs/rundeck/compare/a8bf46b16e19…c8ee33782b38
[travis-ci] Build details : http://travis-ci.org/dtolabs/rundeck/builds/6396771