Attribute absolute='true' specified but no grails.serverURL set in Config ??

[Barry Kaplan]

I'm getting this error:

ERROR ExecutionJob: Failed execution 1 : Attribute absolute='true' specified but no grails.serverURL set in Config

I definitely do not have grails.serverURL set because it will be accessed via both a vpn and bastion node which will have different urls. Do I have to have a fixed url for rundeck to work? Can't all the resources be relative?

[Barry Kaplan]

If I set grails.serverURL to a valid value all works. But that is not going to work for us, as, like I said, some access will be via the vpn, some via port forwarding over the bastion node. 

Any solution that does not require hard coding the url would be very appreciated.

[Barry Kaplan]

Hmm, I set 

  grails.serverURL = http://localhost:4440

and this seems work just fine. But I don't understand why? (No experience with grails since pre 1.0).

[Barry Kaplan]

So it is the case that rundeck cannot work unless the process knows explicitly the concret uri? Is this is a grails limitation?

[Greg Schueler]

We expect the grailsUrl to be set, so we can generate URLs to refer back to Rundeck, e.g. links within notification emails and hrefs in API responses. Grails also uses that URL when issuing HTTP redirects to client browsers.

We could change some of those URL generation that use absolute=‘true’ to make it optional via a config flag, for special cases such as yours.  Can you file an issue about it?

On Jul 21, 2015, at 7:53 PM, Barry Kaplan <mem...@gmail.com> wrote:

So it is the case that rundeck cannot work unless the process knows explicitly the concret uri? Is this is a grails limitation?

--
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 rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/4179a281-b8e7-4c1f-8bfd-d1ad7d3fcc72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Niko Smeds]

Running into same issue (we want Rundeck accessible both directly and through a load balancer, thus via multiple DNS records). Removing `grails.serverURL` parameter allows this, but then jobs fail to run.

No progress eh?

On Wednesday, July 22, 2015 at 11:25:47 AM UTC-7, greg wrote:

We expect the grailsUrl to be set, so we can generate URLs to refer back to Rundeck, e.g. links within notification emails and hrefs in API responses. Grails also uses that URL when issuing HTTP redirects to client browsers.

We could change some of those URL generation that use absolute=‘true’ to make it optional via a config flag, for special cases such as yours.  Can you file an issue about it?

On Jul 21, 2015, at 7:53 PM, Barry Kaplan <mem...@gmail.com> wrote:

So it is the case that rundeck cannot work unless the process knows explicitly the concret uri? Is this is a grails limitation?

--
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 rundeck...@googlegroups.com.

[Niko Smeds]

I've opened https://github.com/rundeck/rundeck/issues/5795 for this issue.