--
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/48f60e6f-a9e6-4988-b5b8-b04fe8798bc2n%40googlegroups.com.
Hi Jabraj,
Checking your service.log you can see the following line:
java.net.BindException: Address already in use
This means that Rundeck can’t launch because can’t listen on the default TCP port (4440 by default) perhaps another service is using it, you’re using some security software which blocks that port or you need to reconfigure Rundeck to listen on another TCP port, you can identify the process with lsof -i :4440.
Hope it helps!
Hi Jabraj,
Can you share the service.log content at the moment of accessing to Rundeck (usually at /var/log/rundeck/ path) to take a look?
Regards!
Hi Jabraj,
Checking the logs I can see this: Error requesting URL Resource Model Source: http://127.0.0.1:9980//gamma_continuous_patching: com.dtolabs.rundeck.core.common.FileUpdaterException: java.net.ConnectException: Connection refused (Connection refused) which means that some URL Resource Model Source is unreachable by Rundeck, check your Resource Models, and make sure that’s Rudneck can reach them (for example testing your remote Resource Model providers from Rundeck server).
Hope it helps!
PD: Post typo fixed :-)