Warning regarding need Bigint after 17.01 to 17.02 upgrade

why can’t there be an update without having to do some extra stuff :frowning:
i run my NC’s at shared hosting, there is no change of running those commands.
is there any other way of fixing it?

1 Like

I’m seeing the same warning on my instance. I’m running nextcloudpi on raspberrypi. When I enter ‘sudo -u www-data php occ db:convert-filecache-bigint’ I get ‘could not open inout file: occ’
What is the right command for nextcloudpi? And is it enough to put the instance in maintenance mode ?

And how am I going to run this command in CentOS 7? Can someone please help me on having compatible command for CentOS 7 ?

Thanks!

I have the same question do you have a solution?

See JanDragon’s post above. That works on Centos 7.

As I had the same problem - no SSH access - I used the possibility to create a cron job in the backend of my hoster and called the script from there, in my case:
/usr/bin/php /usr/www/users/xxx/cloud.xxx.com/occ db:convert-filecache-bigint --no-interaction

The “–no-interaction is necessary” - otherwise the script would “ask” to continue.

It’s probably also possible to create a temporary php script to execute “occ” from a system() call, maybe like this:

<?php
  $cmd = "/usr/bin/php /usr/www/users/xxx/cloud.xxx.com/occ db:convert-filecache-bigint --no-interaction";
  system($cmd,$return_value);
  ($return_value == 0) or die("returned an error: $cmd");
?>