Conversation

Notices

1. Embed this notice
   zeitverschreib (zeitverschreib@freundica.de)'s status on Sunday, 15-Dec-2024 05:40:14 JST zeitverschreib

   • Friendica Admins

   Is there any #Friendica admin out there reading this who's running their instance on a #Synology NAS using the setup instructions by Marius?

   mariushosting.com/how-to-insta…

   I seem to have a problem. Or two, I don't know.

   The install finishes without errors and the instance is up and running. But: the global timeline is always empty, even though I can follow and also DM outside accounts.

   Checking the logs of the cron and db containers, I see this:

   Cron:
   

   Waiting for MySQL friendica-db initialization...

   DB:
   

   ...
   2024-12-14 21:11:02 9 [Warning] Aborted connection 9 to db: 'unconnected' user: 'unauthenticated' host: '172.22.0.5' (This connection closed normally without authentication)
   2024-12-14 21:10:00 0 [Note] Plugin 'wsrep-provider' is disabled.
   Version: '11.4.4-MariaDB-ubu2404' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
   2024-12-14 21:10:04 0 [Note] Server socket created on IP: '::'.
   2024-12-14 21:10:05 0 [Note] mariadbd: ready for connections.
   2024-12-14 21:10:05 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
   2024-12-14 21:10:04 0 [Note] Server socket created on IP: '0.0.0.0'.
   2024-12-14 21:10:02 0 [Note] InnoDB: Buffer pool(s) load completed at 241214 21:10:02

   I guess the timelines are empty because cron is waiting for the db to initialize.

   What am I missing?

   Thanks in advance.

   @admins @mariush

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Sunday, 15-Dec-2024 05:40:12 JST silverwizard

     in reply to
     @zeitverschreib Aborted connection 9 to db: 'unconnected' user: 'unauthenticated' host: '172.22.0.5' (This connection closed normally without authentication)
     that line looks like you are trying to connect to a remote database rather than one on the same server, without a user? So the DB isn't initializing because the credentials/location are wrong? Probably some passwords don't match in step 13?
   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Sunday, 15-Dec-2024 06:10:10 JST silverwizard

     in reply to
     @zeitverschreib I wonder if the passwords were persisted to the volume? It might be you need to destroy the volume and restart?
   • Embed this notice
     zeitverschreib (zeitverschreib@freundica.de)'s status on Sunday, 15-Dec-2024 06:10:11 JST zeitverschreib

     in reply to

     • silverwizard

     @silverwizard The database is in a different container on the same docker installation. I copied the script from Marius' page and only changed the instance URL and admin mail address.

     On my first try, I issued new passwords for redis, db, etc. Same problem. I then used the script verbatim, to make sure that I didn't introduce and password issues.

     All containers created by the script have separate IPs.

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Sunday, 15-Dec-2024 06:26:45 JST silverwizard

     in reply to

     @zeitverschreib dang!

     Well, I can tell you that it seems to not be authing to the DB but dunno

   • Embed this notice
     zeitverschreib (zeitverschreib@freundica.de)'s status on Sunday, 15-Dec-2024 06:26:46 JST zeitverschreib

     in reply to

     • silverwizard
     @silverwizard Also tried that, I deleted everything and started from scratch. But I will try again. 😄
   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Sunday, 15-Dec-2024 06:27:28 JST silverwizard

     in reply to
     sometimes volumes stick around and get reused, but I'll assume you got it