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.

Sign up for GitHub

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

Jump to bottom

Web interface: "Error :(" #95

Closed
stefanheijnen opened this issue Sep 20, 2019 · 6 comments
Closed

Web interface: "Error :(" #95

stefanheijnen opened this issue Sep 20, 2019 · 6 comments

Comments

@stefanheijnen
Copy link

Describe the bug
I just installed photonix on Ubuntu 18.04.3 server, I navigate to the webinterface and I'm greeted with "Error :(". Docker version 19.03.2, build 6a30dfc

Log:

Attaching to photonix-postgres, photonix-redis, photonix
photonix-postgres | The files belonging to this database system will be owned by user "postgres".
photonix-postgres | This user must also own the server process.
photonix-postgres | 
photonix    | DNS fwd/rev mismatch: postgres != photonix-postgres.photonix_default
photonix    | postgres [172.18.0.2] 5432 (postgresql) : Connection refused
photonix    | Postgres is unavailable - sleeping
photonix-redis | 1:C 20 Sep 18:03:59.832 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
photonix-postgres | The database cluster will be initialized with locale "en_US.utf8".
photonix-postgres | The default database encoding has accordingly been set to "UTF8".
photonix-postgres | The default text search configuration will be set to "english".
photonix-postgres | 
photonix-postgres | Data page checksums are disabled.
photonix-redis | 1:M 20 Sep 18:03:59.842 # Not listening to IPv6: unsupproted
photonix-postgres | 
photonix-redis |                 _._                                                  
photonix-redis |            _.-``__ ''-._                                             
photonix-redis |       _.-``    `.  `_.  ''-._           Redis 3.2.8 (00000000/0) 64 bit
photonix-redis |   .-`` .-```.  ```\/    _.,_ ''-._                                   
photonix-redis |  (    '      ,       .-`  | `,    )     Running in standalone mode
photonix-redis |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
photonix-redis |  |    `-._   `._    /     _.-'    |     PID: 1
photonix-redis |   `-._    `-._  `-./  _.-'    _.-'                                   
photonix-redis |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
photonix-redis |  |    `-._`-._        _.-'_.-'    |           http://redis.io        
photonix-redis |   `-._    `-._`-.__.-'_.-'    _.-'                                   
photonix-redis |  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
photonix-redis |  |    `-._`-._        _.-'_.-'    |                                  
photonix-redis |   `-._    `-._`-.__.-'_.-'    _.-'                                   
photonix-redis |       `-._    `-.__.-'    _.-'                                       
photonix-redis |           `-._        _.-'                                           
photonix-redis |               `-.__.-'                                               
photonix-redis | 
photonix-redis | 1:M 20 Sep 18:03:59.843 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
photonix-redis | 1:M 20 Sep 18:03:59.843 # Server started, Redis version 3.2.8
photonix-redis | 1:M 20 Sep 18:03:59.843 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
photonix-redis | 1:M 20 Sep 18:03:59.843 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
photonix-redis | 1:M 20 Sep 18:03:59.843 * DB loaded from disk: 0.000 seconds
photonix-redis | 1:M 20 Sep 18:03:59.843 * The server is now ready to accept connections on port 6379
photonix-postgres | fixing permissions on existing directory /var/lib/postgresql/data ... ok
photonix-postgres | creating subdirectories ... ok
photonix-postgres | selecting default max_connections ... 100
photonix-postgres | selecting default shared_buffers ... 128MB
photonix-postgres | selecting dynamic shared memory implementation ... posix
photonix-postgres | creating configuration files ... ok
photonix-postgres | running bootstrap script ... ok
photonix-postgres | performing post-bootstrap initialization ... sh: locale: not found
photonix-postgres | 2019-09-20 18:04:00.179 UTC [26] WARNING:  no usable system locales were found
photonix-postgres | ok
photonix-postgres | syncing data to disk ... 
photonix-postgres | WARNING: enabling "trust" authentication for local connections
photonix-postgres | You can change this by editing pg_hba.conf or using the option -A, or
photonix-postgres | --auth-local and --auth-host, the next time you run initdb.
photonix-postgres | ok
photonix-postgres | 
photonix-postgres | Success. You can now start the database server using:
photonix-postgres | 
photonix-postgres |     pg_ctl -D /var/lib/postgresql/data -l logfile start
photonix-postgres | 
photonix-postgres | waiting for server to start....2019-09-20 18:04:01.307 UTC [30] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
photonix-postgres | 2019-09-20 18:04:01.319 UTC [31] LOG:  database system was shut down at 2019-09-20 18:04:00 UTC
photonix-postgres | 2019-09-20 18:04:01.321 UTC [30] LOG:  database system is ready to accept connections
photonix-postgres |  done
photonix-postgres | server started
photonix    | DNS fwd/rev mismatch: postgres != photonix-postgres.photonix_default
photonix    | postgres [172.18.0.2] 5432 (postgresql) : Connection refused
photonix    | Postgres is unavailable - sleeping
photonix    | DNS fwd/rev mismatch: postgres != photonix-postgres.photonix_default
photonix    | postgres [172.18.0.2] 5432 (postgresql) : Connection refused
photonix    | Postgres is unavailable - sleeping
photonix    | DNS fwd/rev mismatch: postgres != photonix-postgres.photonix_default
photonix    | postgres [172.18.0.2] 5432 (postgresql) : Connection refused
photonix    | Postgres is unavailable - sleeping
photonix-postgres | CREATE DATABASE
photonix-postgres | 
photonix-postgres | 
photonix-postgres | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
photonix-postgres | 
photonix-postgres | waiting for server to shut down....2019-09-20 18:04:03.679 UTC [30] LOG:  received fast shutdown request
photonix-postgres | 2019-09-20 18:04:03.712 UTC [30] LOG:  aborting any active transactions
photonix-postgres | 2019-09-20 18:04:03.713 UTC [30] LOG:  background worker "logical replication launcher" (PID 37) exited with exit code 1
photonix-postgres | 2019-09-20 18:04:03.714 UTC [32] LOG:  shutting down
photonix-postgres | 2019-09-20 18:04:03.920 UTC [30] LOG:  database system is shut down
photonix-postgres |  done
photonix-postgres | server stopped
photonix-postgres | 
photonix-postgres | PostgreSQL init process complete; ready for start up.
photonix-postgres | 
photonix-postgres | 2019-09-20 18:04:04.025 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
photonix-postgres | 2019-09-20 18:04:04.028 UTC [1] LOG:  could not create IPv6 socket for address "::": Address family not supported by protocol
photonix-postgres | 2019-09-20 18:04:04.063 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
photonix-postgres | 2019-09-20 18:04:04.180 UTC [41] LOG:  database system was shut down at 2019-09-20 18:04:03 UTC
photonix-postgres | 2019-09-20 18:04:04.215 UTC [1] LOG:  database system is ready to accept connections
photonix    | DNS fwd/rev mismatch: postgres != photonix-postgres.photonix_default
photonix    | postgres [172.18.0.2] 5432 (postgresql) open
photonix    | Postgres is up
photonix    | Running migrations
photonix-postgres | 2019-09-20 18:04:04.420 UTC [48] LOG:  incomplete startup packet
photonix    | Operations to perform:
photonix    |   Apply all migrations: admin, auth, contenttypes, photos, sessions
photonix    | Running migrations:
photonix    |   Applying contenttypes.0001_initial... OK
photonix    |   Applying auth.0001_initial... OK
photonix    |   Applying admin.0001_initial... OK
photonix    |   Applying admin.0002_logentry_remove_auto_add... OK
photonix    |   Applying contenttypes.0002_remove_content_type_name... OK
photonix    |   Applying auth.0002_alter_permission_name_max_length... OK
photonix    |   Applying auth.0003_alter_user_email_max_length... OK
photonix    |   Applying auth.0004_alter_user_username_opts... OK
photonix    |   Applying auth.0005_alter_user_last_login_null... OK
photonix    |   Applying auth.0006_require_contenttypes_0002... OK
photonix    |   Applying auth.0007_alter_validators_add_error_messages... OK
photonix    |   Applying auth.0008_alter_user_username_max_length... OK
photonix    |   Applying photos.0001_initial... OK
photonix    |   Applying photos.0002_auto_20190224_2119... OK
photonix    |   Applying photos.0003_auto_20190225_0647... OK
photonix    |   Applying photos.0004_auto_20190225_2147... OK
photonix    |   Applying photos.0005_auto_20190305_1837... OK
photonix    |   Applying photos.0006_auto_20190306_1827... OK
photonix    |   Applying photos.0007_auto_20190507_1655... OK
photonix    |   Applying sessions.0001_initial... OK
photonix    | Resetting Redis lock
photonix    | RESET_ALL_SCRIPT not cached.
photonix    | DELETE_ALL_SIGNAL_KEYS_SCRIPT not cached.
photonix    | Starting supervisor
photonix    | 2019-09-20 18:04:10,450 CRIT Supervisor running as root (no user in config file)
photonix    | Unlinking stale socket /tmp/supervisor.sock
photonix    | 2019-09-20 18:04:10,758 INFO RPC interface 'supervisor' initialized
photonix    | 2019-09-20 18:04:10,758 CRIT Server 'unix_http_server' running without any HTTP authentication checking
photonix    | 2019-09-20 18:04:10,758 INFO supervisord started with pid 20
photonix    | 2019-09-20 18:04:11,763 INFO spawned: 'rescan_photos_periodically' with pid 23
photonix    | 2019-09-20 18:04:11,767 INFO spawned: 'classification_style_processor' with pid 24
photonix    | 2019-09-20 18:04:11,770 INFO spawned: 'raw_processor' with pid 25
photonix    | 2019-09-20 18:04:11,771 INFO spawned: 'nginx' with pid 26
photonix    | 2019-09-20 18:04:11,772 INFO spawned: 'webpack' with pid 27
photonix    | 2019-09-20 18:04:11,773 INFO spawned: 'classification_color_processor' with pid 28
photonix    | 2019-09-20 18:04:11,775 INFO spawned: 'classification_object_processor' with pid 31
photonix    | 2019-09-20 18:04:11,776 INFO spawned: 'classification_scheduler' with pid 32
photonix    | 2019-09-20 18:04:11,777 INFO spawned: 'thumbnail_scheduler' with pid 34
photonix    | 2019-09-20 18:04:11,778 INFO spawned: 'watch_photos' with pid 36
photonix    | 2019-09-20 18:04:11,779 INFO spawned: 'raw_scheduler' with pid 37
photonix    | 2019-09-20 18:04:11,780 INFO spawned: 'classification_location_processor' with pid 38
photonix    | 2019-09-20 18:04:11,788 INFO spawned: 'app_server' with pid 48
photonix    | 2019-09-20 18:04:11,788 INFO exited: webpack (exit status 0; not expected)
photonix    | Starting Nginx in prd mode
photonix    | 2019/09/20 18:04:11 [notice] 33#33: using the "epoll" event method
photonix    | 2019/09/20 18:04:11 [notice] 33#33: nginx/1.10.3
photonix    | 2019/09/20 18:04:11 [notice] 33#33: OS: Linux 5.0.0-25-generic
photonix    | 2019/09/20 18:04:11 [notice] 33#33: getrlimit(RLIMIT_NOFILE): 1048576:1048576
photonix    | 2019/09/20 18:04:11 [notice] 33#33: start worker processes
photonix    | 2019/09/20 18:04:11 [notice] 33#33: start worker process 41
photonix    | 2019/09/20 18:04:11 [notice] 33#33: start worker process 42
photonix    | 2019/09/20 18:04:11 [notice] 33#33: start worker process 43
photonix    | 2019/09/20 18:04:11 [notice] 33#33: start worker process 44
photonix    | Starting Gunicorn server as in prd mode
photonix    | [2019-09-20 18:04:11 +0000] [50] [INFO] Starting gunicorn 19.9.0
photonix    | [2019-09-20 18:04:11 +0000] [50] [INFO] Listening at: http://0.0.0.0:8000 (50)
photonix    | [2019-09-20 18:04:11 +0000] [50] [INFO] Using worker: sync
photonix    | [2019-09-20 18:04:11 +0000] [55] [INFO] Booting worker with pid: 55
photonix    | 2019-09-20 18:04:13,004 INFO spawned: 'webpack' with pid 58
photonix    | 2019-09-20 18:04:13,012 INFO exited: webpack (exit status 0; not expected)
photonix    | 2019-09-20 18:04:15,016 INFO spawned: 'webpack' with pid 59
photonix    | 2019-09-20 18:04:15,021 INFO exited: webpack (exit status 0; not expected)
photonix    | 2019-09-20 18:04:17,024 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
photonix    | 2019-09-20 18:04:18,026 INFO spawned: 'webpack' with pid 62
photonix    | 2019-09-20 18:04:18,029 INFO exited: webpack (exit status 0; not expected)
photonix    | 2019-09-20 18:04:19,031 INFO gave up: webpack entered FATAL state, too many start retries too quickly
photonix    | 2019-09-20 18:04:22,034 INFO success: watch_photos entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
photonix    | UNLOCK_SCRIPT not cached.
photonix    | 2019-09-20 18:04:27,753 INFO success: raw_processor entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
photonix    | 2019-09-20 18:04:27,753 INFO success: raw_scheduler entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
photonix    | 2019-09-20 18:04:28,754 INFO success: thumbnail_scheduler entered RUNNING state, process has stayed up for > than 16 seconds (startsecs)
photonix    | 2019-09-20 18:04:29,756 INFO success: classification_scheduler entered RUNNING state, process has stayed up for > than 17 seconds (startsecs)
photonix    | 2019-09-20 18:04:30,757 INFO success: classification_color_processor entered RUNNING state, process has stayed up for > than 18 seconds (startsecs)
photonix    | 2019-09-20 18:04:31,758 INFO success: classification_location_processor entered RUNNING state, process has stayed up for > than 19 seconds (startsecs)
photonix    | 2019-09-20 18:04:32,760 INFO success: classification_style_processor entered RUNNING state, process has stayed up for > than 20 seconds (startsecs)
photonix    | 2019-09-20 18:04:33,761 INFO success: classification_object_processor entered RUNNING state, process has stayed up for > than 21 seconds (startsecs)
photonix    | 2019-09-20 18:04:42,773 INFO success: app_server entered RUNNING state, process has stayed up for > than 30 seconds (startsecs)
photonix    | 10.0.1.1 - - [20/Sep/2019:18:04:49 +0000] "POST /graphql HTTP/1.1" 400 37 "http://control.hijnn.net:8888/" "Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0"
photonix    | 10.0.1.1 - - [20/Sep/2019:18:04:49 +0000] "POST /graphql HTTP/1.1" 400 37 "http://control.hijnn.net:8888/" "Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0"
photonix    | 2019-09-20 18:05:13.631243: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
photonix    | 10.0.1.1 - - [20/Sep/2019:18:14:03 +0000] "POST /graphql HTTP/1.1" 400 37 "http://control.hijnn.net:8888/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36"
photonix    | 10.0.1.1 - - [20/Sep/2019:18:14:04 +0000] "POST /graphql HTTP/1.1" 400 37 "http://control.hijnn.net:8888/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36"

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: Manjaro Linux Juhraya 18.1.0
  • Browser: Firefox 69 and Chromium 74

If you need more info, please let me know.
@damianmoore
Copy link
Collaborator

Hi @stefanheijnen. Thanks for reporting this. I've not been able to reproduce this issue yet. Would you be able to try again and use your browser's inspector to look at the network traffic, please? I'm wondering if there are error messages returned from the server when the POST to /graphql returns status code 400. Thanks.

@bobobo1618
Copy link
Contributor

I have the same issue, there are no error messages, just a blob of HTML: <h1>Bad Request (400)</h1>

@bobobo1618
Copy link
Contributor

On a hunch, I used an SSH port forward so that I could access the container with the localhost hostname and everything works fine.

It looks like this is a result of Django's ALLOWED_HOSTS setting. I'd recommend disabling these checks (by changing it to *), I always find them more trouble than they're worth.

@stefanheijnen
Copy link
Author

@damianmoore You mean this?

image

@bobobo1618
Copy link
Contributor

By the way @stefanheijnen I resolved this by changing the ALLOWED_HOSTS line in the docker-compose.yml to “*” (with quotes).

damianmoore added a commit that referenced this issue Nov 18, 2019
@damianmoore
#95 Makes compose files less likely to cause ALLOWED_HOSTS HTTP 400 e…
9da23fc 
…rrors. Docs will need to make it clear to the user why they should change it if running in production.
@damianmoore
Copy link
Collaborator

damianmoore commented Nov 18, 2019 •
edited

Thanks @stefanheijnen for reporting and sending screenshots. Thanks @bobobo1618 for identifying the problem. For these quick set-up docker compose files I've decided to set ALLOWED_HOSTS to '*' so people aren't put off when trying it out. The fact that it's still there in the compose files rather than a default at a lower level will hopefully bring it to people's attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bobobo1618 @damianmoore @stefanheijnen