As far as I know, those br-lines are benign.
What does the Mealie log show in the apps section? Is it starting up?
Stuck on deploying
Mealie logs - empty
Postgres logs
2025-08-28 18:27:57.791819+00:002025-08-28T18:27:57.791819017Z
2025-08-28 18:27:57.791913+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:27:57.791926+00:002025-08-28T18:27:57.791926666Z
2025-08-28 18:27:57.828947+00:002025-08-28 18:27:57.828 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:27:57.829078+00:002025-08-28 18:27:57.828 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:27:57.829175+00:002025-08-28 18:27:57.828 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:27:59.192689+00:002025-08-28T18:27:59.192689216Z
2025-08-28 18:27:59.192763+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:27:59.192797+00:002025-08-28T18:27:59.192797698Z
2025-08-28 18:27:59.212587+00:002025-08-28 18:27:59.212 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:27:59.212666+00:002025-08-28 18:27:59.212 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:27:59.212678+00:002025-08-28 18:27:59.212 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:00.883269+00:002025-08-28T18:28:00.883269818Z
2025-08-28 18:28:00.883345+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:00.883359+00:002025-08-28T18:28:00.883359245Z
2025-08-28 18:28:00.902340+00:002025-08-28 18:28:00.902 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:00.902517+00:002025-08-28 18:28:00.902 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:00.902554+00:002025-08-28 18:28:00.902 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:02.670550+00:002025-08-28T18:28:02.670550734Z
2025-08-28 18:28:02.670595+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:02.670623+00:002025-08-28T18:28:02.670623001Z
2025-08-28 18:28:02.689561+00:002025-08-28 18:28:02.689 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:02.689618+00:002025-08-28 18:28:02.689 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:02.689852+00:002025-08-28 18:28:02.689 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:04.443837+00:002025-08-28T18:28:04.443837065Z
2025-08-28 18:28:04.443916+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:04.443929+00:002025-08-28T18:28:04.443929327Z
2025-08-28 18:28:04.464141+00:002025-08-28 18:28:04.463 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:04.464241+00:002025-08-28 18:28:04.463 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:04.464255+00:002025-08-28 18:28:04.463 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:07.159539+00:002025-08-28T18:28:07.159539329Z
2025-08-28 18:28:07.159823+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:07.159862+00:002025-08-28T18:28:07.159862592Z
2025-08-28 18:28:07.189323+00:002025-08-28 18:28:07.186 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:07.189410+00:002025-08-28 18:28:07.186 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:07.189446+00:002025-08-28 18:28:07.186 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:11.814972+00:002025-08-28T18:28:11.814972029Z
2025-08-28 18:28:11.815132+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:11.815167+00:002025-08-28T18:28:11.815167991Z
2025-08-28 18:28:11.834481+00:002025-08-28 18:28:11.834 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:11.834538+00:002025-08-28 18:28:11.834 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:11.834551+00:002025-08-28 18:28:11.834 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
2025-08-28 18:28:19.156218+00:002025-08-28T18:28:19.156218135Z
2025-08-28 18:28:19.156359+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-08-28 18:28:19.156373+00:002025-08-28T18:28:19.156373056Z
2025-08-28 18:28:19.175385+00:002025-08-28 18:28:19.175 GMT [1] LOG: invalid value for parameter "log_timezone": "GB"
2025-08-28 18:28:19.175478+00:002025-08-28 18:28:19.175 GMT [1] LOG: invalid value for parameter "TimeZone": "GB"
2025-08-28 18:28:19.175587+00:002025-08-28 18:28:19.175 GMT [1] FATAL: configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors
Postgres update logs:
2025-08-28 18:27:56.187444+00:00[ix-postgres-upgrade] - [2025-08-28 19:27:56] - Current version: 15
2025-08-28 18:27:56.189253+00:00[ix-postgres-upgrade] - [2025-08-28 19:27:56] - Target version: 15
2025-08-28 18:27:56.191382+00:00[ix-postgres-upgrade] - [2025-08-28 19:27:56] - Already at target version 15
permissions logs:
2025-08-28 18:27:54.318118+00:00=== Applying configuration on volume with identifier [postgres_postgres_data] ===
2025-08-28 18:27:54.318362+00:00Path [/mnt/permission/postgres_postgres_data] is not empty, skipping...
2025-08-28 18:27:54.318423+00:00=== Applying configuration on volume with identifier [nltk-data] ===
2025-08-28 18:27:54.318460+00:00Path [/mnt/permission/nltk-data] is a temporary directory, ensuring it is empty...
2025-08-28 18:27:54.318534+00:00Current Ownership and Permissions on [/mnt/permission/nltk-data]:
2025-08-28 18:27:54.318591+00:00Ownership: wanted [568:568], got [0:0].
2025-08-28 18:27:54.318626+00:00Permissions: wanted [None], got [0755].
2025-08-28 18:27:54.318679+00:00---
2025-08-28 18:27:54.318713+00:00Ownership is incorrect. Fixing...
2025-08-28 18:27:54.318783+00:00Changing ownership recursively to 568:568 on: [/mnt/permission/nltk-data]
2025-08-28 18:27:54.318817+00:00Ownership after changes:
2025-08-28 18:27:54.318875+00:00Ownership: [568:568]
2025-08-28 18:27:54.318905+00:00Skipping permissions check, chmod is falsy
2025-08-28 18:27:54.318979+00:00Time taken: 2.20ms
2025-08-28 18:27:54.319036+00:00=== Finished applying configuration on volume with identifier [nltk-data] ==
2025-08-28 18:27:54.319069+00:002025-08-28T18:27:54.319069120Z
2025-08-28 18:27:54.319124+00:00Total time taken: 2.70ms
Somethings gone all squiffy 
Wait looking at this… is it because of a bad timezone setting? 
Holy moly it was a bad timezone setting within Postgres - probably due to the system being set to GB
SOLUTION FOR ANYONE WITH THE SAME PROBLEM:
If Mealie is running/Deploying/Stuck - stop the app
Hop into shell and do the following:
Open your Postgres database config
nano /mnt/*INSERT MACHINE NAME HERE*/Mealie/Database/postgresql.conf
Find the following lines:
log_timezone = 'GB'
TimeZone = 'GB'
Change them to the following/your local timezone
log_timezone = 'Europe/London'
TimeZone = 'Europe/London'
Restart Mealie and it SHOULD come back up!
Special thanks to @neofusion for helping - they got it to a point where Mealie would start and I could dig into the errors to find the problem!
1 Like
I don’t know what to make of the postgres log unfortunately. But I see you did, hurray! 
The other two look okay, the permissions log points out some things are owned by root, and appears to fix them. Not sure if that is related to the issue with Mealie and Mealie/Data being owned by root (for some reason).
2 Likes