| 26 Sep 2022 |
|  wivodaim joined the room. | 07:55:35 |
| wivodaim set a profile picture. | 08:00:13 |
| 30 Sep 2022 |
|  @dominion:cdom.de joined the room. | 09:47:57 |
| @dominion:cdom.de | Hi, since 2 days I got an error in my docker setup:
| 09:56:15 |
| @dominion:cdom.de | * Hi, since 2 days I got an error in my docker setup:
mobilizon-mobilizon-1 | Crash dump is being written to: erl_crash.dump...-- Waiting for database...
mobilizon-mobilizon-1 | db:5432 - accepting connections
mobilizon-mobilizon-1 | NOTICE: extension "pg_trgm" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | NOTICE: extension "unaccent" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | -- Running migrations...
mobilizon-mobilizon-1 | ERROR! the application :mobilizon has a different value set for key :instance during runtime compared to compile time. Since this application environment entry was marked as compile time, this difference can lead to different behaviour than expected:
mobilizon-mobilizon-1 |
| 09:56:35 |
 tcit | In reply to @dominion:cdom.de
Hi, since 2 days I got an error in my docker setup:
mobilizon-mobilizon-1 | Crash dump is being written to: erl_crash.dump...-- Waiting for database...
mobilizon-mobilizon-1 | db:5432 - accepting connections
mobilizon-mobilizon-1 | NOTICE: extension "pg_trgm" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | NOTICE: extension "unaccent" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | -- Running migrations...
mobilizon-mobilizon-1 | ERROR! the application :mobilizon has a different value set for key :instance during runtime compared to compile time. Since this application environment entry was marked as compile time, this difference can lead to different behaviour than expected:
mobilizon-mobilizon-1 |
Sorry for the trouble. CI seems to be misconfigured and accidently pushed a beta tag to latest. I pushed back 2.1.0 to latest, but you can use 2.1.0 as well. | 11:38:43 |
| tcit | In reply to @dominion:cdom.de
Hi, since 2 days I got an error in my docker setup:
mobilizon-mobilizon-1 | Crash dump is being written to: erl_crash.dump...-- Waiting for database...
mobilizon-mobilizon-1 | db:5432 - accepting connections
mobilizon-mobilizon-1 | NOTICE: extension "pg_trgm" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | NOTICE: extension "unaccent" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | -- Running migrations...
mobilizon-mobilizon-1 | ERROR! the application :mobilizon has a different value set for key :instance during runtime compared to compile time. Since this application environment entry was marked as compile time, this difference can lead to different behaviour than expected:
mobilizon-mobilizon-1 |
also if you have just a few more log lines, please post them, as it will be helpful identifing what's the issue | 11:39:26 |
| @dominion:cdom.de | Thanks so much | 11:39:39 |
| @dominion:cdom.de | I'm offsite now, I do it later | 11:40:18 |
 Jakob | In reply to @killy-ann:systemli.org
Hetzner does not have any swap Did it work with the swapfile? | 11:40:37 |
 cos | For some reason i'm getting TypeError: this.config is undefined when I open a event page on first time. Second time reload works. The page in question is https://jarkkaa.fi/events/33898139-1350-45b4-be8c-20850219a61e | 14:02:51 |
|  malinois joined the room. | 19:22:52 |
| 1 Oct 2022 |
| @dominion:cdom.de | tcit:
mobilizon-mobilizon-1 | Crash dump is being written to: erl_crash.dump...-- Waiting for database...
mobilizon-mobilizon-1 | db:5432 - accepting connections
mobilizon-mobilizon-1 | NOTICE: extension "pg_trgm" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | NOTICE: extension "unaccent" already exists, skipping
mobilizon-mobilizon-1 | CREATE EXTENSION
mobilizon-mobilizon-1 | -- Running migrations...
mobilizon-mobilizon-1 | ERROR! the application :mobilizon has a different value set for key :instance during runtime compared to compile time. Since this application environment entry was marked as compile time, this difference can lead to different behaviour than expected:
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | * Compile time value was set to: [name: "My Mobilizon Instance", description: "Change this to a proper description of your instance", hostname: "localhost", registrations_open: false, registration_email_allowlist: [], registration_email_denylist: [], languages: [], default_language: "en", demo: false, repository: "https://framagit.org/framasoft/mobilizon", allow_relay: true, federating: true, remote_limit: 100000, upload_limit: 10485760, avatar_upload_limit: 2097152, banner_upload_limit: 4194304, remove_orphan_uploads: true, orphan_upload_grace_period_hours: 48, remove_unconfirmed_users: true, unconfirmed_user_grace_period_hours: 48, activity_expire_days: 365, activity_keep_number: 100, enable_instance_feeds: false, email_from: "noreply@localhost", email_reply_to: "noreply@localhost"]
mobilizon-mobilizon-1 | * Runtime value was set to: [registration_email_allowlist: [], registration_email_denylist: [], languages: [], default_language: "en", repository: "https://framagit.org/framasoft/mobilizon", remote_limit: 100000, upload_limit: 10485760, avatar_upload_limit: 2097152, banner_upload_limit: 4194304, remove_orphan_uploads: true, orphan_upload_grace_period_hours: 48, remove_unconfirmed_users: true, unconfirmed_user_grace_period_hours: 48, activity_expire_days: 365, activity_keep_number: 100, enable_instance_feeds: false, name: "XXXXXXXXXXXXXXX", description: "Change this to a proper description of your instance", hostname: "mobilize.xxxxxxxx.de", registrations_open: true, demo: false, allow_relay: true, federating: true, email_from: "noreply@xxxxxxxx.de", email_reply_to: "kontakt@xxxxxxx.de"]
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | To fix this error, you might:
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | * Make the runtime value match the compile time one
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | * Recompile your project. If the misconfigured application is a dependency, you may need to run "mix deps.compile mobilizon --force"
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | * Alternatively, you can disable this check. If you are using releases, you can set :validate_compile_env to false in your release configuration. If you are using Mix to start your system, you can pass the --no-validate-compile-env flag
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 |
mobilizon-mobilizon-1 | {"init terminating in do_boot",{<<"aborting boot">>,[{'Elixir.Config.Provider',boot,2,[]}]}}
mobilizon-mobilizon-1 | init terminating in do_boot ({,[{Elixir.Config.Provider,boot,2,[]}]})
mobilizon-mobilizon-1 |
| 06:43:08 |
| @dominion:cdom.de | this was the error from yesterday (the docker latest problem) | 06:43:34 |
| @dominion:cdom.de | thanks for your fast help | 06:43:40 |
|  opensourceror2 joined the room. | 14:51:08 |
| @dominion:cdom.de left the room. | 21:20:23 |
 moanos [he/him] | I try to build the docker image locally for development and get this when running make setup
Generating responsive versions of the pictures…
Done!
Done in 0.06s.
21:55:01.144 [error] GenServer #PID<0.532.0> terminating
** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
(db_connection 2.4.2) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 4.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
21:55:01.162 [error] GenServer #PID<0.538.0> terminating
** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
(db_connection 2.4.2) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 4.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
** (Mix) The database for Mobilizon.Storage.Repo couldn't be created: killed
21:55:02.102 [error] Postgrex.Protocol (#PID<0.533.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:02.102 [error] Postgrex.Protocol (#PID<0.532.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:04.096 [error] Postgrex.Protocol (#PID<0.533.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:04.659 [error] Postgrex.Protocol (#PID<0.532.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:05.074 [error] Could not create schema migrations table. This error usually happens due to the following:
* The database does not exist
* The "schema_migrations" table, which Ecto uses for managing
migrations, was defined by another library
* There is a deadlock while migrating (such as using concurrent
indexes with a migration_lock)
To fix the first issue, run "mix ecto.create".
To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:
config :mobilizon, Mobilizon.Storage.Repo,
migration_source: "some_other_table_for_schema_migrations",
migration_repo: AnotherRepoForSchemaMigrations
The full error report is shown below.
** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2981ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
I know that there is an issue connecting to the database, but the logs show the database up and running. Any idea?
| 21:57:23 |
| 2 Oct 2022 |
|  maximus222 joined the room. | 09:06:15 |
 setop | In reply to @moanos:hyteck.de
I try to build the docker image locally for development and get this when running make setup
Generating responsive versions of the pictures…
Done!
Done in 0.06s.
21:55:01.144 [error] GenServer #PID<0.532.0> terminating
** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
(db_connection 2.4.2) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 4.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
21:55:01.162 [error] GenServer #PID<0.538.0> terminating
** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
(db_connection 2.4.2) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 4.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
** (Mix) The database for Mobilizon.Storage.Repo couldn't be created: killed
21:55:02.102 [error] Postgrex.Protocol (#PID<0.533.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:02.102 [error] Postgrex.Protocol (#PID<0.532.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:04.096 [error] Postgrex.Protocol (#PID<0.533.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:04.659 [error] Postgrex.Protocol (#PID<0.532.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
21:55:05.074 [error] Could not create schema migrations table. This error usually happens due to the following:
* The database does not exist
* The "schema_migrations" table, which Ecto uses for managing
migrations, was defined by another library
* There is a deadlock while migrating (such as using concurrent
indexes with a migration_lock)
To fix the first issue, run "mix ecto.create".
To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:
config :mobilizon, Mobilizon.Storage.Repo,
migration_source: "some_other_table_for_schema_migrations",
migration_repo: AnotherRepoForSchemaMigrations
The full error report is shown below.
** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2981ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
I know that there is an issue connecting to the database, but the logs show the database up and running. Any idea?
I run Mobilizon in prod using docker and docker-compose.
I baked my own docker-compose.yml and had to add this section within the "api" service section:
services:
db:
...
api:
environment:
MOBILIZON_DATABASE_HOST: db
...
links:
- db:db ## <= here !
To make the api know where to connect.
| 14:13:20 |
| 3 Oct 2022 |
|  @muekoeff:matrix.org left the room. | 21:16:28 |
| 5 Oct 2022 |
|  sillyconcarne joined the room. | 16:43:31 |
| 6 Oct 2022 |
 categulario | are ye able to see images in development? I have a container setup of mobilizon and I'm able to upload images (like event and group banners) but I'm not able to see them because they are requested from https://localhost (notice the https). Am I missing something? | 05:18:08 |
| categulario | In reply to @categulario:matrix.cuates.net
are ye able to see images in development? I have a container setup of mobilizon and I'm able to upload images (like event and group banners) but I'm not able to see them because they are requested from https://localhost (notice the https). Am I missing something? ok I managed to do it by modifying the config file... this should be more obvious... | 06:03:36 |
| moanos [he/him] | Will try :) | 09:07:45 |
| moanos [he/him] | Another question. I get Mails that instances do want to follow me but I can'd find them wehen cklining the link in the mail (e.g. https://climatejustice.events/settings/admin/instances/mobilize-hannover.de
`
In the logs I found this
08:59:53.969 [error] #PID<0.23038.11> running Mobilizon.Web.Endpoint (connection #PID<0.23039.11>, stream id 1) terminated
Server: climatejustice.events:80 (http)
Request: POST /api
** (exit) an exception was raised:
** (BadMapError) expected a map, got: nil
(stdlib 3.17.2) :maps.merge(nil, %{followed_status: :pending, follower_status: :pending, has_relay: true, relay_address: "relay@mobilize-hannover.de"})
(mobilizon 2.1.0) lib/graphql/resolvers/admin.ex:485: Mobilizon.GraphQL.Resolvers.Admin.get_instance/3
(absinthe 1.7.0) lib/absinthe/resolution.ex:209: Absinthe.Resolution.call/2
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:230: Absinthe.Phase.Document.Execution.Resolution.reduce_resolution/1
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:185: Absinthe.Phase.Document.Execution.Resolution.do_resolve_field/3
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:170: Absinthe.Phase.Document.Execution.Resolution.do_resolve_fields/6
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:88: Absinthe.Phase.Document.Execution.Resolution.walk_result/5
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:67: Absinthe.Phase.Document.Execution.Resolution.perform_resolution/3
| 09:09:00 |
|  rakoo joined the room. | 11:59:26 |
| rakoo | 12:00:26 |
 To Setto Setto (UTC+2) | In reply to @moanos:hyteck.de
Another question. I get Mails that instances do want to follow me but I can'd find them wehen cklining the link in the mail (e.g. https://climatejustice.events/settings/admin/instances/mobilize-hannover.de
`
In the logs I found this
08:59:53.969 [error] #PID<0.23038.11> running Mobilizon.Web.Endpoint (connection #PID<0.23039.11>, stream id 1) terminated
Server: climatejustice.events:80 (http)
Request: POST /api
** (exit) an exception was raised:
** (BadMapError) expected a map, got: nil
(stdlib 3.17.2) :maps.merge(nil, %{followed_status: :pending, follower_status: :pending, has_relay: true, relay_address: "relay@mobilize-hannover.de"})
(mobilizon 2.1.0) lib/graphql/resolvers/admin.ex:485: Mobilizon.GraphQL.Resolvers.Admin.get_instance/3
(absinthe 1.7.0) lib/absinthe/resolution.ex:209: Absinthe.Resolution.call/2
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:230: Absinthe.Phase.Document.Execution.Resolution.reduce_resolution/1
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:185: Absinthe.Phase.Document.Execution.Resolution.do_resolve_field/3
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:170: Absinthe.Phase.Document.Execution.Resolution.do_resolve_fields/6
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:88: Absinthe.Phase.Document.Execution.Resolution.walk_result/5
(absinthe 1.7.0) lib/absinthe/phase/document/execution/resolution.ex:67: Absinthe.Phase.Document.Execution.Resolution.perform_resolution/3
i have a similar issue in that some instances have accepted my federation request, and their events are beeing agregated, but they show up nowhere. not even if i use the link you posted (but adapted to my instance and ending with their instance?) | 16:40:09 |
| To Setto Setto (UTC+2) | * i have a similar issue in that some instances have accepted my federation request, and their events are beeing agregated, but they show up nowhere. not even if i use the link you posted (but adapted to my instance and ending with their instance.) | 16:40:30 |
