Bug #1573488 “Openstack Mitaka: can not access dashboard(interna...” : Bugs : OpenStack Dashboard (Horizon)

Revision history for this message

Itxaka Serrano (itxaka) wrote on 2016-04-25:

#1

What is your apache config for horizon? Can you paste it to be sure that its ok?

Changed in horizon:
status:	New → Incomplete

Revision history for this message

dico (bohli-dhekra) wrote on 2016-04-27:

#2

HI did you resolve this problem !!!!! can you help i have a similar situation

Revision history for this message

Rock (zrockf) wrote on 2016-04-28:

#3

Download full text (8.6 KiB)

Hi Itxaka,
Thanks for your reply.
I don't have specific apache config for horizon in /etc/apache2/sites-enabled/ as the installation guide suggests.
But here is the default setting:
root@controller:~# cat /etc/apache2/sites-enabled/000-default.conf
<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

root@controller:~# cat /etc/apache2/apache2.conf
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration sn...

Hi Itxaka,
Thanks for your reply. 
I don't have specific apache config for horizon in /etc/apache2/sites-enabled/ as the installation guide suggests.
But here is the default setting:
root@controller:~# cat /etc/apache2/sites-enabled/000-default.conf 
<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com

ServerAdmin webmaster@localhost
	DocumentRoot /var/www/html

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

root@controller:~# cat /etc/apache2/apache2.conf 
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.

# Global configuration
#
ServerName controller

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf

# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>

# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>

#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
root@controller:~#

Revision history for this message

Rock (zrockf) wrote on 2016-04-28:

#4

Hi Dico,
I haven't solved the problem yet. I decided to back to Liberty release. It works fine.

Revision history for this message

Freerider (seanjohnmcgrath) wrote on 2016-05-09:

#5

This seems to be a legitimate bug, if you try and follow the ubuntu mitaka install. Is this being looked at? Are there any pointers? I've run into the EXACT same issue. ubuntu 14.04.4 LTS.

Revision history for this message

Freerider (seanjohnmcgrath) wrote on 2016-05-12:

#6

Hmm. Fixed. (at least in my environment).

root@mitakamaster:/etc/apache2/conf-enabled# cat openstack-dashboard.conf
WSGIScriptAlias /horizon /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi
WSGIDaemonProcess horizon user=horizon group=horizon processes=3 threads=10
WSGIProcessGroup horizon
WSGIApplicationGroup %{GLOBAL} <------ ADDED THIS
Alias /static /usr/share/openstack-dashboard/openstack_dashboard/static/
Alias /horizon/static /usr/share/openstack-dashboard/openstack_dashboard/static/
<Directory /usr/share/openstack-dashboard/openstack_dashboard/wsgi>
Order allow,deny
Allow from all
</Directory>

Restarted apache, and bingo. Dashboard access on ubuntu 14.04 / mitaka.

Revision history for this message

Aashish (aash-43) wrote on 2016-05-13:

#7

Hi,
I'm facing the same issue after following mitaka openstack installation guide on Ubuntu 14.04.4 LTS,

Please find the apache2 logs below,
[Fri May 13 11:31:04.573431 2016] [:info] [pid 1066:tid 139768017549184] mod_wsgi (pid=1066): Attach interpreter ''.
[Fri May 13 11:31:12.477906 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of Require all granted: granted
[Fri May 13 11:31:12.477967 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of <RequireAny>: granted
[Fri May 13 11:31:12.478073 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of Require all granted: granted
[Fri May 13 11:31:12.478083 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of <RequireAny>: granted
[Fri May 13 11:31:12.492575 2016] [:info] [pid 1067:tid 139767914018560] mod_wsgi (pid=1067): Create interpreter 'controller|/horizon'.
[Fri May 13 11:31:12.494695 2016] [:info] [pid 1067:tid 139767914018560] [remote 192.168.1.140:1863] mod_wsgi (pid=1067, process='horizon', application='controller|/horizon'): Loading WSGI script '/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi'.
[Fri May 13 06:06:14.575389 2016] [:info] [pid 1067:tid 139767930803968] mod_wsgi (pid=1067): Daemon process deadlock timer expired, stopping process 'horizon'.
[Fri May 13 06:06:14.575539 2016] [:info] [pid 1067:tid 139768017549184] mod_wsgi (pid=1067): Shutdown requested 'horizon'.
[Fri May 13 06:06:19.576133 2016] [:info] [pid 1067:tid 139767662200576] mod_wsgi (pid=1067): Aborting process 'horizon'.
[Fri May 13 11:36:19.584275 2016] [core:error] [pid 1083:tid 139767832377088] [client 192.168.1.140:57969] End of script output before headers: django.wsgi
[Fri May 13 11:36:19.813866 2016] [:info] [pid 1063:tid 139768017549184] mod_wsgi (pid=1067): Process 'horizon' has died, restarting.

Hi,
I'm facing the same issue after following mitaka openstack installation guide on Ubuntu 14.04.4 LTS,

Please find the apache2 logs below,
[Fri May 13 11:31:04.573431 2016] [:info] [pid 1066:tid 139768017549184] mod_wsgi (pid=1066): Attach interpreter ''.
[Fri May 13 11:31:12.477906 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of Require all granted: granted
[Fri May 13 11:31:12.477967 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of <RequireAny>: granted
[Fri May 13 11:31:12.478073 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of Require all granted: granted
[Fri May 13 11:31:12.478083 2016] [authz_core:debug] [pid 1083:tid 139767832377088] mod_authz_core.c(802): [client 192.168.1.140:57969] AH01626: authorization result of <RequireAny>: granted
[Fri May 13 11:31:12.492575 2016] [:info] [pid 1067:tid 139767914018560] mod_wsgi (pid=1067): Create interpreter 'controller|/horizon'.
[Fri May 13 11:31:12.494695 2016] [:info] [pid 1067:tid 139767914018560] [remote 192.168.1.140:1863] mod_wsgi (pid=1067, process='horizon', application='controller|/horizon'): Loading WSGI script '/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi'.
[Fri May 13 06:06:14.575389 2016] [:info] [pid 1067:tid 139767930803968] mod_wsgi (pid=1067): Daemon process deadlock timer expired, stopping process 'horizon'.
[Fri May 13 06:06:14.575539 2016] [:info] [pid 1067:tid 139768017549184] mod_wsgi (pid=1067): Shutdown requested 'horizon'.
[Fri May 13 06:06:19.576133 2016] [:info] [pid 1067:tid 139767662200576] mod_wsgi (pid=1067): Aborting process 'horizon'.
[Fri May 13 11:36:19.584275 2016] [core:error] [pid 1083:tid 139767832377088] [client 192.168.1.140:57969] End of script output before headers: django.wsgi
[Fri May 13 11:36:19.813866 2016] [:info] [pid 1063:tid 139768017549184] mod_wsgi (pid=1067): Process 'horizon' has died, restarting.

Revision history for this message

Aashish (aash-43) wrote on 2016-05-13:

#8

I tried solution suggested by Freerider (seanjohnmcgrath), it did not resolve the issue in my environment, I got a new exception with that change in /etc/apache2/conf-enabled# cat openstack-dashboard.conf file as shown below,

[Fri May 13 06:20:47.166292 2016] [:error] [pid 1777:tid 139671292704512] File "/usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py", line 71, in render_offline
[Fri May 13 06:20:47.166393 2016] [:error] [pid 1777:tid 139671292704512] 'You may need to run "python manage.py compress".' % key)
[Fri May 13 06:20:47.166488 2016] [:error] [pid 1777:tid 139671292704512] OfflineGenerationError: You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".

Revision history for this message

xiaoqiyixin (379893594-s) wrote on 2016-05-15:

#9

i have the same problem,and my error.log only have "End of script output before headers: django.wsgi"

my apache2 have no broblem,http://localhost is normal.

I tried solution suggested by #6 ,but it did not resolve the issue.

comandline service apache2 restart with follews:
root@controller:/etc/apache2/conf-enabled# service apache2 restart
* Restarting web server apache2 [fail]
* The apache2 configtest failed.
Output of config test was:
AH00526: Syntax error on line 4 of /etc/apache2/conf-enabled/openstack-dashboard.conf:
Invalid command 'WSGIApplicationGroup%{GLOBAL}', perhaps misspelled or defined by a module not included in the server configuration
Action 'configtest' failed.
The Apache error log may have more information.

error.log
[Sun May 15 07:49:37.296060 2016] [mpm_event:notice] [pid 10704:tid 139920269113216] AH00489: Apache/2.4.7 (Ubuntu) mod_wsgi/3.4 Python/2.7.6 configured -- resuming normal operations
[Sun May 15 07:49:37.296102 2016] [core:notice] [pid 10704:tid 139920269113216] AH00094: Command line: '/usr/sbin/apache2'
[Sun May 15 10:30:51.322057 2016] [mpm_event:notice] [pid 10704:tid 139920269113216] AH00491: caught SIGTERM, shutting down

Revision history for this message

Freerider (seanjohnmcgrath) wrote on 2016-05-18:

#10

aaishish, Are you seeing this error? Trying running it?

[Fri May 13 06:20:47.166488 2016] [:error] [pid 1777:tid 139671292704512] OfflineGenerationError: You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".

xiaoqiyixin, post your entire openstack-dashboard.conf. You sure there is no typo/space?

Revision history for this message

Aashish (aash-43) wrote on 2016-05-19:

#11

Freerider, Yes I see the below mentioned error when I tried the solution mentioned in #6,

[Thu May 19 04:26:58.202768 2016] [:error] [pid 19301:tid 140428522313472] OfflineGenerationError: You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".

When I try to access the dashboard from the browser, I'm getting below error,
OfflineGenerationError at /auth/login/
You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".
Request Method: GET
Request URL: http://192.168.1.167/horizon/auth/login/?next=/horizon/
Django Version: 1.8.7
Exception Type: OfflineGenerationError
Exception Value:
You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".
Exception Location: /usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py in render_offline, line 71
Python Executable: /usr/bin/python
Python Version: 2.7.6
Python Path:
['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
'/usr/lib/python2.7',
'/usr/lib/python2.7/plat-x86_64-linux-gnu',
'/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages/PILcompat',
'/usr/lib/python2.7/dist-packages/gtk-2.0',
'/usr/lib/python2.7/dist-packages/ubuntu-sso-client',
'/usr/share/openstack-dashboard/',
'/usr/share/openstack-dashboard/openstack_dashboard']
Server time: Thu, 19 May 2016 04:26:58 +0000

Revision history for this message

Freerider (seanjohnmcgrath) wrote on 2016-05-19:

#12

Solution in #6 does not address the problem you are having. Trying running the compression?

You have offline compression enabled but key "337c10dadc650d2900f653d9efa97201" is missing from offline manifest. You may need to run "python manage.py compress".

python manage.py compress

Revision history for this message

Aashish (aash-43) wrote on 2016-05-20:

#13

Freerider, I'm not executing compression. After adding "WSGIApplicationGroup %{GLOBAL}" in openstack-dashboard.conf file and apache server restart, I started seeing this error related to offline compression.
When I reverted the changes, I'm getting End of script error as mentioned in #7

Revision history for this message

Aashish (aash-43) wrote on 2016-05-20:

#14

Freerider, I'm able to access the dashboard now. Thanks for your suggestion.

After solution suggested in #6 I executed "python manage.py compress", the issue was resolved

/usr/share/openstack-dashboard$ sudo python manage.py compress
[sudo] password for controller:
Found 'compress' tags in:
        /usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_conf.html
        /usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html
        /usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_scripts.html
Compressing... done
Compressed 4 block(s) from 3 template(s) for 1 context(s).

But is this an additional step for installation in mitaka release, please confirm the same?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-07-20:

#15

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]

Changed in horizon:
status:	Incomplete → Expired

Revision history for this message

Praveen N (praveenn) wrote on 2016-08-24:

#16

Still the issue persists, and after following #6 and #14 resolved for me.

Revision history for this message

maburycn (maburycn) wrote on 2017-03-22:

#17

I got same situation, even with that 2 resolution, no luck.

Any more suggestions? thanks

Revision history for this message

Maciej Kucia (maciejkucia) wrote on 2017-09-20:

#18

For anyone with similar issue.

Fix with
WSGIApplicationGroup %{GLOBAL}
in
openstack-dashboard.conf
should work.

Please remember to restart httpd (CentOS/Fedora/RHEL).
systemctl restart httpd

In Ubuntu/Debian
systemctl start apache2.service

Revision history for this message

Adil Lebbat (adil-lebbat) wrote on 2017-10-08:

#19

For anyone using Kolla and Kolla-ansible for an allinone or multinode deployment :

- Edit the file /etc/kolla/horizon/horizon.conf on the node/nodes that contain the horizon docker container

After -------> WSGIProcessGroup horizon-http
ADDED THIS -------> WSGIApplicationGroup %{GLOBAL}

- docker stop/start ALL_HORIZON_CONTAINERS_ON_EACH_NODE

This should fix the issue (Kolla 5.0.0 / CentOS 7.4)

Revision history for this message

LIU Yulong (dragon889) wrote on 2018-05-30:

#20

Queens still has such issue.

Env:
CentOS 7.2
kernel: 3.10.0-514.el7.x86_64
rpm -qa|grep dashboard
openstack-dashboard-13.0.1-1.el7.noarch

Install doc:
https://docs.openstack.org/horizon/queens/install/install-rdo.html

And yes, add the fix to /etc/httpd/conf.d/openstack-dashboard.conf
WSGIApplicationGroup %{GLOBAL}
then restart the httpd service:
systemctl restart httpd.service

Revision history for this message

Akihiro Motoki (amotoki) wrote on 2018-05-30:

#21

Apart from the documention bug, this is a packaging bug in CentOS package. The horizon upstream development team does not maintain individual package, so a packaging bug needs to be filed to CentOS package.

Note that documentation bug is handled as bug 1741354 and a backport to queens documentation has been proposed.

OpenStack Dashboard (Horizon)

Openstack Mitaka: can not access dashboard(internal server 500)

Bug Description

Other bug subscribers

Remote bug watches