Error 503 - Service Unavailable

[Patrick S]

Hi,

I'm trying to install RunDeck on a Vagrant box, and while I've managed to install it and start the service, when accessing RunDeck in my browser, I get the following error message:

HTTP ERROR: 503

Problem accessing /user/login. Reason:

    Service Unavailable

---

Powered by Jetty://

 

Having looked round on the line, I can't seem to find any documentation or fixed in relation to this. The closest I got was this GitHub page: https://github.com/rundeck/rundeck/wiki/FAQ#i-get-an-error-logging-in-http-error-403--reason-role

Any suggestions?

Many thanks,

Patrick

[Alex Honor]

Hi Patrick,

How are you installing it (JAR, RPM)? Can you include output from the service.log?

Thanks

--
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.
For more options, visit https://groups.google.com/d/optout.

--

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

Be sure to comment and vote on Rundeck Feature Development!

[Patrick S]

Hi,

Thanks for your fast reply. I installed it using the deb package using openjdk-7-jdk.

As per your request, I have uploaded its contents to Pastebin: http://pastebin.com/sJgZ4fQk

Thank you

Alex Honor

[SimplifyOps, Inc | a....@simplifyops.com ]

[Alex Honor]

Errors seem to be due to a permission error (eg, 

/tmp/rundeck/org.hibernate.cache.UpdateTimestampsCache.data (Permission denied)). 

How did you start rundeck? Also, it's possible that there is a conflict between two java processes trying to run it. Can you make sure it's really down and then try starting the service?

Thanks

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

[Patrick S]

I started it as one would start most other processes; using sudo service rundeckd start

Having used sudo, I wouldn't expect Rundeckd to run into any permission issues? That's why I'm rather confused about this all.

Once again, thank you for your help.

[Alex Honor]

The service start script will attempt to start the java process as the rundeck user. Once the process starts up (as rundeck), it will begin updating the runtime files like logs or the database. I notice the paths begin with /tmp/rundeck. Normally, the deb/rpm install puts rundeck in /usr/lib/rundeck.

--

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.
For more options, visit https://groups.google.com/d/optout.

[Patrick S]

And here are the exact steps I took re: making sure it's really down:

vagrant@localhost:~$ sudo service rundeckd stop

rundeckd stop/waiting

vagrant@localhost:~$ ps aux | grep rundeck

vagrant  10919  0.0  0.1  10464   924 pts/0    S+   16:03   0:00 grep --color=auto rundeck 

vagrant@localhost:~$ sudo service rundeckd start

rundeckd start/running, process 10931

vagrant@localhost:~$ ps aux | grep rundeck

rundeck  10931 97.2 22.1 1864180 110992 ?      Ssl  16:04   0:03 /usr/bin/java -Djava.security.auth.login.config=/etc/rundeck/jaas-loginmodule.conf -Dloginmodule.name=RDpropertyfilelogin -Drdeck.config=/etc/rundeck -Drdeck.base=/var/lib/rundeck -Drundeck.server.configDir=/etc/rundeck -Dserver.datastore.path=/var/lib/rundeck/data -Drundeck.server.serverDir=/var/lib/rundeck -Drdeck.projects=/var/rundeck/projects -Drdeck.runlogs=/var/lib/rundeck/logs -Drundeck.config.location=/etc/rundeck/rundeck-config.properties -Djava.io.tmpdir=/tmp/rundeck -Xmx1024m -Xms256m -server -cp /var/lib/rundeck/bootstrap/not-yet-commons-ssl-0.3.11.jar:/var/lib/rundeck/bootstrap/libpam4j-1.5.jar:/var/lib/rundeck/bootstrap/jna-3.2.2.jar:/var/lib/rundeck/bootstrap/rundeck-jetty-server-2.1.2.jar:/var/lib/rundeck/bootstrap/jetty-all-7.6.0.v20120127.jar:/var/lib/rundeck/bootstrap/servlet-api-2.5.jar:/var/lib/rundeck/bootstrap/log4j-1.2.16.jar: com.dtolabs.rundeck.RunServer /var/lib/rundeck 4440

vagrant  10946  0.0  0.1  10464   920 pts/0    S+   16:04   0:00 grep --color=auto rundeck

vagrant@localhost:~$

[Patrick S]

Right- that explains a bit. Do you have any idea how I could rectify the problem?

Thanks again :)

Alex Honor

[SimplifyOps, Inc | a....@simplifyops.com ]

[Alex Honor]

Possibly the RDECK_BASE environment variable is set to /tmp/rundeck. 

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

[Patrick S]

Okay, I'll give that a look. It could also very well be that my Ansible script is messing things around. I'll give it another look and see if I can spot anything wrong.

Will report back with findings.

[Mike Johnson]

Hi

id rundeck

chgrp rundeck /tmp/rundeck

chmod g+rwx /tmp/rundeck

Those commands will help.  I'm still installing it so I don't know if it's a complete fix.  A step forward at least.

Mike

[Patrick S]

Mike, your suggestion has worked! I have just updated my Ansible playbook and it seems to be working when I boot up a new vagrant instance.

Obviously running in /tmp is a poor choice, but that's something I need to figure out ansible end. Thank you for your suggestion, sir :-)

[Mike Johnson]

Happy to help!  Really whatever creates that directory, be it the installer or the daemon/webapp itself when it starts, should be doing a check to see what the effective UID is and setting ownership/perms of that directory accordingly.  It's a simple fix though, I've put it into puppet.

Mike

--
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/A6Wu2VnoquA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.

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

--

Mike Johnson | Systems Administrator | mik...@google.com | 07920576168