New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fpm-alpine fails with `Command "maintenance:install" is not defined.` after upgrade #489

Open
TLATER opened this Issue Oct 6, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@TLATER
Copy link

TLATER commented Oct 6, 2018

Hi, I just upgraded from 13.0 to 14.0.1 with the fpm-alpine image. When starting with the new image I end up with the following repeating message in my logs:

<snip>
retrying install...
Nextcloud or one of the apps require upgrade - only >
You may use your browser or the occ upgrade command >

  Command "maintenance:install" is not defined.

Did you mean one of these?
      app:install
      maintenance:data-fingerprint
      maintenance:mimetype:update-db
      maintenance:mimetype:update-js
      maintenance:mode
      maintenance:repair
      maintenance:theme:update
      maintenance:update:htaccess

installing of nextcloud failed!

Any ideas? I didn't catch on to stable-fpm-alpine in time, I suppose.

@TLATER

This comment has been minimized.

Copy link

TLATER commented Oct 6, 2018

I'm assuming the relevant part of the script is here:

https://github.com/nextcloud/docker/blob/master/docker-entrypoint.sh#L96

The documentation does say that this is a valid command in 14:

https://docs.nextcloud.com/server/14/admin_manual/configuration_server/occ_command.html#command-line-installation

Now just to wonder why mainenance:install doesn't exist :)

@MiGoller

This comment has been minimized.

Copy link

MiGoller commented Nov 3, 2018

I have encountered the same error. Nextcloud will start but the Docker's entrypoint tries to install a few times; later on Nextcloud will be up and running.

If I do not provide environment variables for database setup, as I've done all the time up to 13.0.4, Nextcloud starts without any error messages.

Can anybody confirm that? It looks like the Nextcloud Docker container does not recognize that Nextcloud is already installed.

@weikinhuang

This comment has been minimized.

Copy link

weikinhuang commented Nov 6, 2018

I am also seeing this upgrading from 14.0.0 to 14.0.3

@SnowMB

This comment has been minimized.

Copy link
Contributor

SnowMB commented Nov 7, 2018

I can't really reproduce the issue. If you start the container, does it give you an installed version number?
Should start with something like this:

docker-compose logs -tf app
app_1  | 2018-11-07T18:36:13.906629237Z Initializing nextcloud 14.0.3.0 ...
app_1  | 2018-11-07T18:36:13.906661268Z Upgrading nextcloud from 13.0.7.2 ...

@SnowMB SnowMB added the help wanted label Nov 7, 2018

@weikinhuang

This comment has been minimized.

Copy link

weikinhuang commented Nov 7, 2018

It thinks it's a new instance:

Initializing nextcloud 14.0.3.0 ...
Initializing finished
New nextcloud instance
Installing with MySQL database
starting nexcloud installation
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade


  Command "maintenance:install" is not defined.

  Did you mean one of these?
      app:install
      maintenance:data-fingerprint
      maintenance:mimetype:update-db
      maintenance:mimetype:update-js
      maintenance:mode
      maintenance:repair
      maintenance:theme:update
      maintenance:update:htaccess

My setup is using this container with kubernetes, so volume isn't persisted, only the data, plugins, and db

@MiGoller

This comment has been minimized.

Copy link

MiGoller commented Nov 7, 2018

If I provide the environment variables MYSQL_* when running docker-compose I receive the same log entries as @weikinhuang does. But without these environment variables my nextcloud container will start with such log entries.

$ docker logs 1........
Initializing nextcloud 13.0.7.2 ...
Initializing finished
New nextcloud instance
running web-based installer on first connect!
...
[Sun Nov 04 00:35:43.912141 2018] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.25 (Debian) PHP/7.2.11 configured -- resuming normal operations
[Sun Nov 04 00:35:43.912170 2018] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

I do not persist /var/www/html as well; I just mount /var/www/html/data, /var/www/html/config and /var/www/html/custom_apps like I did in the past. The database is hold by a shared MariaDB server outside of the nextcloud stack.

Looks like the docker-entrypoint.sh script does not recognize that the upgrade from 13.0.4 to 13.0.7 already succeeded. So the issue is related to the apache images as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment