Having a hard time with localhost:4440

[Jeremy Ackman]

Hello community
I will start off with saying that Rundeck, is new to me, as the project landed in my lap, in it's very early stages, when a former employee left the company. So you can assume I know nothing. 

I have Ansible up and working. 
Rundeck is install with a Mariadb and all services are up and running. 

I am strugging getting to the Rundeck dashboard using localhost:4440 
I have found that even though I have the port open both in amazon and on the server, the service is still not listening on that port when I run netstat -tuln

I have reviewed all of the config files, 
Tried another port 

etc 

all with no luck. 

Any suggestions? 

[rac...@rundeck.com]

Hi Jeremy,

What kind of installation are you using? (war, rpm, deb, docker). Probably the instance is configured to listen using the DNS name (and not the localhost). To check that, look at the rundeck-config.properties file (usually located in the /etc/rundeck directory), and check the grails.serverURL parameter, there is where the host and port are configured, take a look at this.

Regards.

​

[Jeremy Ackman]

I am running on debian, and my serverURL line looks correct. 
grails.serverURL=http://localhost:4440

[rac...@rundeck.com]

That might work if you're running Rundeck locally, but if you're running the instance on a remote server, that needs to be configured using the server hostname. is that Rundeck running behind a proxy server? That could be the reason for that config.

Regards.

[Jeremy Ackman]

everything is running locally. 

[rac...@rundeck.com]

Then I assume that Rundeck is running in your localhost (that’s valid if Rundeck is running on your computer, not on a remote server). Could you verify the service.log at the moment of launching the rundeckd service? That log is the central place to see what is happening in Rundeck.

You can see the behavior in real-time doing: tail -f /va/log/rundeck/service.log (you can restart the service to see the starting messages).

Another thing: what do you see in your browser at the moment of accessing the localhost:4440?

Greetings.

​

[Jeremy Ackman]

In the browser I get "Unable to connect" 
In the service.log file there is zero activity at the time of launch. 

This seems to align with the fact that I am not seeing 127.0.0.1:4440 when I run netstat -tuln.

 

--
You received this message because you are subscribed to a topic in the Google Groups "rundeck-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rundeck-discuss/gEfv1fZW4xc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/63b09c38-757a-47da-a424-73b4d50a791bn%40googlegroups.com.

--

Blessed are those who wash their robes, that they may have the right to the tree of life and may go through the gates into the city.

[rac...@rundeck.com]

Weird, can you confirm if the rundeck service is up? ps aux | grep "rundeck". Also, you can check it via systemd: systemctl is-active --quiet rundeckd && echo Service is running.

If you don’t see anything on the service.log at the moment of launching rundeck, please check the system requirements (probably that service.log behavior is due to an unsupported Java version) and ensure to have followed this.

​

[Jeremy Ackman]

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/7ada0612-9f91-41d5-89e6-43109203a933n%40googlegroups.com.

[rac...@rundeck.com]

The service is down (your command only printed the grep call). Try launch rundeck: systemctl start rundeckd and see what service.log prints. Please take a look a this guide.

​

[Jeremy Ackman]

The rundeckd service is dying a few minutes after it starts. 

Found a boatload of appender errors in services.log as it's trying to start, which seem to be tied back to the log4j2.properties file. 

2023-11-03 18:26:03,116 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,116 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,116 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,116 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,117 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,117 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,117 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,117 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,117 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,118 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,118 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,118 main ERROR Null object returned for RollingFile in Appenders.
2023-11-03 18:26:03,118 main ERROR Unable to locate appender "rundeck" for logger config "root"
2023-11-03 18:26:03,119 main ERROR Unable to locate appender "storage" for logger config "org.rundeck.storage.events"
2023-11-03 18:26:03,119 main ERROR Unable to locate appender "webhooks" for logger config "org.rundeck.webhook.events"
2023-11-03 18:26:03,119 main ERROR Unable to locate appender "execevents" for logger config "org.rundeck.execution.status"
2023-11-03 18:26:03,119 main ERROR Unable to locate appender "access" for logger config "org.rundeck.web.requests"
2023-11-03 18:26:03,120 main ERROR Unable to locate appender "apirequests" for logger config "org.rundeck.api.requests"
2023-11-03 18:26:03,120 main ERROR Unable to locate appender "audit" for logger config "com.dtolabs.rundeck.core.authorization"
2023-11-03 18:26:03,120 main ERROR Unable to locate appender "project" for logger config "org.rundeck.project.events"
2023-11-03 18:26:03,120 main ERROR Unable to locate appender "audit_events" for logger config "org.rundeck.plugin.audit.AuditLoggerPlugin"
2023-11-03 18:26:03,121 main ERROR Unable to locate appender "jobchanges" for logger config "com.dtolabs.rundeck.data.jobs.changes"
2023-11-03 18:26:03,121 main ERROR Unable to locate appender "webhooks" for logger config "org.rundeck.plugin.webhook"
2023-11-03 18:26:03,121 main ERROR Unable to locate appender "options" for logger config "com.dtolabs.rundeck.remoteservice.http.options"
2023-11-03 18:26:03,121 main ERROR Unable to locate appender "cleanup" for logger config "rundeck.quartzjobs.ExecutionsCleanUp"

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/ce478b3f-7ab0-490f-99a2-14567f32809en%40googlegroups.com.

[rac...@rundeck.com]

It seems that you're facing this. Could you try the fix suggested in the first post? (or re-generate the log4j2 config file from a test instance).

[Jeremy Ackman]

Since rundeck has never worked for me, I went ahead and blew it away. 
Reinstalled and worked through a few config errors. 
Everything is running as expected now. 

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/7da3fc7d-aa3b-469c-96be-5991cdae9d2an%40googlegroups.com.