ERROR: permission denied to create role

[zulip]

ERROR: permission denied to create role

[galexrt]

@decker502 You can currently ignore these "errors", because when you look at the end of the logs you posted you'll see that everything starting without any problems. (Please retry with repulled images, thanks).

database_1 | 2015-10-22 04:10:42 UTC [88-2] zulip@zulip STATEMENT:  CREATE USER zulip;
database_1 | 2015-10-22 04:10:42 UTC [88-3] zulip@zulip ERROR:  database "zulip" already exists
database_1 | 2015-10-22 04:10:42 UTC [88-4] zulip@zulip STATEMENT:  CREATE DATABASE zulip OWNER=zulip;
database_1 | 2015-10-22 04:10:42 UTC [89-1] zulip@zulip ERROR:  permission denied to create extension "tsearch_extras"
database_1 | 2015-10-22 04:10:42 UTC [89-2] zulip@zulip HINT:  Must be superuser to create this extension.
database_1 | 2015-10-22 04:10:42 UTC [89-3] zulip@zulip STATEMENT:  CREATE EXTENSION tsearch_extras SCHEMA zulip;

They just mean that while setting up the database (on every start), we just try recreate the database user, database and the extension.
But yes you are right, this below is half of an error. When you use an image like mine quay.io/galexrt/zulip-postgresql-tsearchextras or quay.io/repository/sameersbn/postgresql, you will get an user that is not the postgres/root user, so will "fail" to create the EXTENSION tsearch_extras for the zulip scheme. A fail in this case isn't that worse (at least I haven't tested it with different postgresql server images ;) ).
This is no problem when using the default database server from the docker-compose (quay.io/galexrt/zulip-postgresql-tsearchextras:latest).

database_1 | 2015-10-22 04:10:42 UTC [89-1] zulip@zulip ERROR:  permission denied to create extension "tsearch_extras"
database_1 | 2015-10-22 04:10:42 UTC [89-2] zulip@zulip HINT:  Must be superuser to create this extension.
database_1 | 2015-10-22 04:10:42 UTC [89-3] zulip@zulip STATEMENT:  CREATE EXTENSION tsearch_extras SCHEMA zulip;

I'll create an ticket for the "error", so we do something about it.

[galexrt]

BTW your zulip should be running perfectly, because everything needed was started by supervisor.
Can you start it up and check if it is reachable? Looking at the logs it should be reachable 😄

---

Related to #22

[decker502]

I have tried to run zulip client.
"You look familiar." is shown. I can't see login and password input. I'm not sure if this is cause of server

[galexrt]

@decker502 Okay. So at least Zulip starts up correctly.
Could you provide me the new log from the zulip container?

[decker502]

zulip seems not to produce the new log:(

[galexrt]

Have you tried docker logs ZULIP_CONTAINER_NAME?

[decker502]

docker-compose logs and docker logs all were both tried

[galexrt]

That's weird. There should be log output.
Could you repull the quay.io/galexrt/zulip image, start it again and post the log output here?

[decker502]

Because Internet speed of china is very slow, it would be done until tomorrow:(
I'll try it, and post the log output here at tomorrow, thank you very much!

[galexrt]

@decker502 If you have any other questions regarding the configuration of zulip or have other problems, you can ask me on the irc channel #docker-zulip.

[decker502]

@galexrt OK :)

[galexrt]

Fixed in the latest version.