Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development instance throwing dot_parser error #34

Closed
netman2048 opened this issue Jun 27, 2016 · 4 comments
Closed

Development instance throwing dot_parser error #34

netman2048 opened this issue Jun 27, 2016 · 4 comments

Comments

@netman2048
Copy link

I'm trying to install Netbox on a minimal Centos 7 system and having some issues when I go to launch the development instance. It launches and says no issues were identified however it throws a 'Couldn't import dot_parser, loading of dot files will not be possible.' error. When I browse to the website, I get a Bad Request (400) error.

sudo ./manage.py runserver 0.0.0.0:8000 --insecure
Performing system checks...

Couldn't import dot_parser, loading of dot files will not be possible.
System check identified no issues (0 silenced).
June 27, 2016 - 19:07:50
Django version 1.9.7, using settings 'netbox.settings'
Starting development server at http://0.0.0.0:8000/
Quit the server with CONTROL-C.
[27/Jun/2016 19:07:51] "GET / HTTP/1.1" 400 26
[27/Jun/2016 19:07:52] "GET /favicon.ico HTTP/1.1" 400 26
[27/Jun/2016 19:07:53] "GET / HTTP/1.1" 400 26
[27/Jun/2016 19:07:53] "GET /favicon.ico HTTP/1.1" 400 26

In order to get to this point, I had to install additional dependencies such as gcc, openssl-devel, and postgresql-devel at which point I got past pip install section. Not sure what to troubleshoot at this point.

@jeremystretch
Copy link
Member

You can safely ignore the Couldn't import dot_parser errors.

Make sure you're connecting to http://localhost:8000/ to access the development server. You can try adding DEBUG = True to the top of configuration.py to get more information.

@netman2048
Copy link
Author

I resolved the dot_parser errors by uninstalling pyparsing and reinstalling with pyparsing 1.5.7 but since you said I can ignore it, I will likely upgrade it again.

Now here is the interesting part....if I add the debug statement, the web interface loads correct. When I take it off, I get the Bad Request (400) error.

@jeremystretch
Copy link
Member

Could be your ALLOWED_HOSTS setting in configuration.py. What do you have it set to?

See if it works in non-debug mode with ALLOWED_HOSTS = ['*'].

@netman2048
Copy link
Author

netman2048 commented Jun 28, 2016

That seems to have worked.  I tried doing '0.0.0.0' not knowing it was looking for an asterik as the wildcard (is that in the docs somewhere?).  I think I also read that section too quickly thinking that was a list of IPs allowed to access the web interface.  That is probably more of a function of nginx though.  Now i have to troubleshoot gettingg nginx to display the page :)
Thanks for the help.  

@lock lock bot locked as resolved and limited conversation to collaborators Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants