Can't access scalr-ser

179 views
Skip to first unread message

Karima Kaddouri

unread,
Mar 11, 2015, 7:38:19 AM3/11/15
to scalr-...@googlegroups.com
Hello,

This is the first time I am trying Scalr. I am following the steps for the open source version. After installing scalr-server and finishing its setup, I can't access scalr to login as admin.

When I run "nestat -nlp" port 80 is not listening on 0.0.0.0. How can I solve this.

Also, what is my.scalr.com and how do we get credentials to have access to it ?

Thank you!


Thomas Orozco

unread,
Mar 11, 2015, 7:45:49 AM3/11/15
to scalr-...@googlegroups.com
Did you run "scalr-server-ctl reconfigur"? If you did, did you see any errors? If you're unsure, re-run it. 

my.scalr.com is a hosted version of Scalr. You can learn more and / or sign up for a trial here: http://www.scalr.com/pricing/hosted

Cheers,

Karima Kaddouri

unread,
Mar 11, 2015, 8:32:16 AM3/11/15
to scalr-...@googlegroups.com
Hi, 

I ran  "scalr-server-ctl reconfigure" and I got an error "Error executing action 'start' on resource 'supervisor_service[httpd]', followed by the error trace.

Best,

Karima

karl.qu...@ticketfly.com

unread,
Mar 11, 2015, 1:15:07 PM3/11/15
to scalr-...@googlegroups.com
Please post the trace; that's the helpful bit that'll clue somebody into what's going wrong :).

Sebastian Stadil

unread,
Mar 11, 2015, 2:28:15 PM3/11/15
to scalr-...@googlegroups.com
Thanks for pitching in, Karl!

--
You received this message because you are subscribed to the Google Groups "scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--


Follow us: Twitter - Facebook - Blog

Thomas Orozco

unread,
Mar 11, 2015, 3:05:51 PM3/11/15
to scalr-...@googlegroups.com

This means Apache was unable to start (and therefore explains why nothing is listening on port 80).

You should review the logs under /opt/scalr-server/var/log/httpd and /opt/scalr-server/var/log/supervisor/httpd.err, and look for errors there.

Feel free to post the logs here if you can't find the root cause yourself.

Cheers,

Karima Kaddouri

unread,
Mar 12, 2015, 7:15:30 AM3/12/15
to scalr-...@googlegroups.com
Thank you so much for your input guys !

I tried to find the root of the error from the trace but I couldn't, so I am posting it here hoping someone could.

RuntimeError
    ------------
    Supervisor service httpd was unable to be started
   
    Cookbook Trace:
    ---------------
    /opt/scalr-server/embedded/cookbooks/supervisor/providers/service.rb:49:in `block (2 levels) in class_from_file'
    /opt/scalr-server/embedded/cookbooks/supervisor/providers/service.rb:47:in `block in class_from_file'
   
    Resource Declaration:
    ---------------------
    # In /opt/scalr-server/embedded/cookbooks/scalr-server/recipes/group_httpd_enabled.rb
   
     42: supervisor_service 'httpd' do
     43:   command         "#{node[:scalr_server][:install_root]}/embedded/bin/httpd" \
     44:                   " -f #{etc_dir_for node, 'httpd'}/httpd.conf" \
     45:                   ' -DFOREGROUND'
     46:   stdout_logfile  "#{log_dir_for node, 'supervisor'}/httpd.log"
     47:   stderr_logfile  "#{log_dir_for node, 'supervisor'}/httpd.err"
     48:   action          [:enable, :start]
     49:   autostart       true
     50:   startsecs       5
     51:   subscribes      :restart, 'user[scalr_user]' if service_is_up?(node, 'httpd')
     52:   subscribes      :restart, 'template[php_ini]' if service_is_up?(node, 'httpd')
     53: end
   
    Compiled Resource:
    ------------------
    # Declared in /opt/scalr-server/embedded/cookbooks/scalr-server/recipes/group_httpd_enabled.rb:42:in `from_file'
   
    supervisor_service("httpd") do
      action [:enable, :start]
      updated true
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      declared_type :supervisor_service
      cookbook_name :"scalr-server"
      recipe_name "group_httpd_enabled"
      command "/opt/scalr-server/embedded/bin/httpd -f /opt/scalr-server/etc/httpd/httpd.conf -DFOREGROUND"
      stdout_logfile "/opt/scalr-server/var/log/supervisor/httpd.log"
      stderr_logfile "/opt/scalr-server/var/log/supervisor/httpd.err"
      autostart true
      startsecs 5
      service_name "httpd"
      process_name "%(program_name)s"
      numprocs 1
      numprocs_start 0
      priority 999
      autorestart :unexpected
      startretries 3
      exitcodes [0, 2]
      stopsignal :TERM
      stopwaitsecs 10
      stdout_logfile_maxbytes "50MB"
      stdout_logfile_backups 10
      stdout_capture_maxbytes "0"
      stderr_logfile_maxbytes "50MB"
      stderr_logfile_backups 10
      stderr_capture_maxbytes "0"
      serverurl "AUTO"
    end
   

Running handlers:
[2015-03-12T11:13:23+00:00] ERROR: Running exception handlers
  - Raven::Chef::SentryHandler
Running handlers complete
[2015-03-12T11:13:24+00:00] ERROR: Exception handlers complete
[2015-03-12T11:13:24+00:00] FATAL: Stacktrace dumped to /opt/scalr-server/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 22 resources updated in 21.162231414 seconds
[2015-03-12T11:13:24+00:00] ERROR: supervisor_service[httpd] (scalr-server::group_httpd_enabled line 42) had an error: RuntimeError: Supervisor service httpd was unable to be started
[2015-03-12T11:13:24+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)




Thomas Orozco

unread,
Mar 12, 2015, 8:38:25 AM3/12/15
to scalr-...@googlegroups.com

Hi,

Like I asked a bit earlier, please include the Apache log files.

The trace only indicate Apache couldn't start. The log files will indicate why.

Cheers,

Karima Kaddouri

unread,
Mar 12, 2015, 11:06:37 AM3/12/15
to scalr-...@googlegroups.com
Hi!

I managed to fix the issue after some research :) ! thank you for your help and your time everyone !

Cheers,

Karima

Daniele Testa

unread,
Mar 16, 2015, 7:53:23 AM3/16/15
to scalr-...@googlegroups.com
What OS are you running this on? Is it a clean server or do you run other things as well?

It might be that you have something else blocking port 80. When you did the "netstat -nlp", did you see port 80 being used at all? Maybe listening on 127.0.0.1?

Regards,
Daniele

Thomas Orozco

unread,
Mar 16, 2015, 7:54:33 AM3/16/15
to scalr-...@googlegroups.com
Hey there,

Please disregard the last message here from Daniele, it was stuck in moderation and I just let it through (and therefore it's a bit outdated). 

Sorry about the inconvenience,

Cheers, 

-- Thomas | Product Manager @ Scalr | tho...@scalr.com | www.scalr.com | blog.scalr.com
Reply all
Reply to author
Forward
0 new messages