SOLVED: After upgrade to Bluefin Nextcloud unreachable

[teg]

I upgraded my Truenas Scale to Bluefin and after that I'm unable to reach Nextcloud. It seems to be running and there are no error messages, but Nextcloud is unreachable. Looks like it isn't listening its port. What could cause this?

 

[sretalla]

Are you sure it's not just stuck in deploying state complaining about the SMB share path conflict?

Are you sharing out any of the paths published into the container via SMB?

See the SMB section here:

Bluefin Recommended Settings and Optimizations

My Bluefin 22.12.0 upgrade from Angelfish 22.02.4 was flawless. I'm going to post all steps I took during my TrueNAS Scale Build upgrade, as well other improvements and optimizations I implemented, as reference for other users. For related inquiries or questions involving formatted code, please...

www.truenas.com

 

[teg]

No, I'm not sharing any of the paths and Nextcloud isn't complaining about any conflicts.

 

[sretalla]

OK, well we've had a try at me guessing what may be wrong and you telling me no.

Now it's time for you to look at some logs and actually figure it out.

On the app, from the 3 dots in the top right, select logs, then select the nextcloud container and have a look at what's there.

 

[teg]

I didn't found any suspicious events from logs.

Nextcloud:

2023-01-18 19:10:45.387678+00:00Conf remoteip disabled.
2023-01-18 19:10:45.387748+00:00To activate the new configuration, you need to run:
2023-01-18 19:10:45.387765+00:00service apache2 reload
2023-01-18 19:10:45.438044+00:00Initializing nextcloud 25.0.3.2 ...
2023-01-18 19:10:45.438098+00:00Upgrading nextcloud from 25.0.2.3 ...
2023-01-18 19:10:53.970633+00:00Nextcloud or one of the apps require upgrade - only a limited number of commands are available
2023-01-18 19:10:53.970721+00:00You may use your browser or the occ upgrade command to do the upgrade
2023-01-18 19:10:53.985642+00:00Setting log level to debug
2023-01-18 19:10:53.986409+00:00Turned on maintenance mode
2023-01-18 19:10:54.587571+00:00Updating database schema
2023-01-18 19:10:54.612396+00:00Updated database
2023-01-18 19:10:58.385392+00:00Starting code integrity check...
2023-01-18 19:11:05.554156+00:00Finished code integrity check
2023-01-18 19:11:05.554977+00:00Update successful
2023-01-18 19:11:05.555132+00:00Turned off maintenance mode
2023-01-18 19:11:05.555207+00:00Resetting log level
2023-01-18 19:11:05.872048+00:00The following apps have been disabled:
2023-01-18 19:11:05.877706+00:00Initializing finished
2023-01-18 19:11:05.946086+00:00AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.13.25. Set the 'ServerName' directive globally to suppress this message
2023-01-18 19:11:05.975834+00:00AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.13.25. Set the 'ServerName' directive globally to suppress this message
2023-01-18 19:11:05.994197+00:00[Wed Jan 18 19:11:05.994046 2023] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.54 (Debian) PHP/8.1.14 configured -- resuming normal operations
2023-01-18 19:11:05.994262+00:00[Wed Jan 18 19:11:05.994074 2023] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

And for postgres:

2023-01-18 19:10:29.331826+00:002023-01-18T19:10:29.331826549Z
2023-01-18 19:10:29.331870+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-01-18 19:10:29.331878+00:002023-01-18T19:10:29.331878740Z
2023-01-18 19:10:29.352605+00:002023-01-18 19:10:29.352 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2023-01-18 19:10:29.352708+00:002023-01-18 19:10:29.352 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-01-18 19:10:29.352749+00:002023-01-18 19:10:29.352 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-01-18 19:10:29.360166+00:002023-01-18 19:10:29.360 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-01-18 19:10:29.370366+00:002023-01-18 19:10:29.370 UTC [26] LOG: database system was interrupted; last known up at 2023-01-18 19:10:14 UTC
2023-01-18 19:10:29.404049+00:002023-01-18 19:10:29.403 UTC [26] LOG: database system was not properly shut down; automatic recovery in progress
2023-01-18 19:10:29.411402+00:002023-01-18 19:10:29.411 UTC [26] LOG: redo starts at 2/E07D2970
2023-01-18 19:10:29.419419+00:002023-01-18 19:10:29.419 UTC [26] LOG: redo done at 2/E09F15E8
2023-01-18 19:10:29.516426+00:002023-01-18 19:10:29.516 UTC [1] LOG: database system is ready to accept connections

Everything seems to be ok, but nexcloud doesn't seem to be bind on any external network interface?

 

[teg]

At the same time when I was posting the reply, I found solution. Another app is binding on the same port. Usually Nextcloud does start before the other one but now the order has been changed. Interesting that there is no error or warning from an app if it isn't able to bind to a port

 

[sretalla]

At the same time when I was posting the reply, I found solution. Another app is binding on the same port. Usually Nextcloud does start before the other one but now the order has been changed. Interesting that there is no error or warning from an app if it isn't able to bind to a port

That may have been visible from the "Application Events" list (click on the app card and see it at the bottom of that panel)

 

[teg]

Maybe it should but at least there is no events there in my setup