Is there any #Friendica admin out there reading this who's running their instance on a #Synology NAS using the setup instructions by Marius?
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
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.
@Friendica Admins @mariush
How to Install Friendica on Your Synology NAS
Trustworthy expert guide to your Synology NAS.Marius Hosting
Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.
Michael 🇺🇦
in reply to zeitverschreib [friendica] • • •silverwizard
in reply to zeitverschreib [friendica] • • •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?
zeitverschreib [friendica]
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.
silverwizard
in reply to zeitverschreib [friendica] • • •zeitverschreib [friendica]
in reply to silverwizard • • •silverwizard
in reply to zeitverschreib [friendica] • • •@zeitverschreib [friendica] dang!
Well, I can tell you that it seems to not be authing to the DB but dunno
silverwizard
in reply to silverwizard • • •zeitverschreib [friendica]
in reply to silverwizard • • •@silverwizard After a re-install I still see problems with the db connect:
172.23.0.4 is the Friendica container
172.23.0.5 is the CRON container
Something's very wrong.
zeitverschreib [friendica]
in reply to zeitverschreib [friendica] • • •I just tried to run the same setup on a Pi 4 and get the very same messages:
JB Carroll
in reply to zeitverschreib [friendica] • • •zeitverschreib [friendica]
in reply to JB Carroll • • •@JB Carroll
Yes, that works, but every attempt by the Cron container fails.
@silverwizard
JB Carroll
in reply to zeitverschreib [friendica] • • •