NCP - updateing to 22.2.2 did not work because of preview generator app

Hi, i had issues with preview generator app earlier, but this time it looks like there is more substance to what causes my issue, after update from 21.0.4 to 22.2.2 i got a message that the webupdater can not update one app, prebiew generator exactly. Following error message came up:

InvalidArgumentException: Column "oc_preview_generation"."locked" is type Bool and also NotNull, so it can not store "false".

So i disabled and removed PG app before the next attempt, now i wanted to reinstall PG from appstore, but i could not, same message, but the ap was only disabled, not removed, so i removed it again, and tried to install again, now the error changed to

Exception: App "previewgenerator" cannot be installed because appinfo file cannot be read.

Any idea what can be done?

What does your nc-info look like?

No matter, i fixed it by deleting the leftover empty appfolder /var/www/nextcloud/apps/previewgenerator and tried to install again, that then worked
I guess a permission issue on that one

This also happens using @nachoparker cURL instalation script:

Instalation script fails with: Column “oc_preview_generation”.“locked” is type Bool and also NotNull, so it can not store “false”. #1391

You mean you had installed ncp via curl installer? I did that as well back then, but afterwards restored a nc backup from an older ncp instance. However, i doubt it has something to do with the curl installer

Hi @FadeFx

I mean that the same error happens when someone tried to do a clean install NextCloudPi via the cURL script. Here is what happens:

Script shell output log
Preparing to unpack .../avahi-daemon_0.7-4+deb10u1_amd64.deb ...
Unpacking avahi-daemon (0.7-4+deb10u1) ...
Setting up libdaemon0:amd64 (0.14-7) ...
Setting up libavahi-core7:amd64 (0.7-4+deb10u1) ...
Setting up avahi-daemon (0.7-4+deb10u1) ...
Created symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/avahi-daemon.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/sockets.target.wants/avahi-daemon.socket → /lib/systemd/system/avahi-daemon.socket.
Processing triggers for systemd (241-7~deb10u8) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for libc-bin (2.28-10) ...
Running nc-init
Setting up a clean Nextcloud instance... wait until message 'NC init done'
Setting up database...
Setting up Nextcloud...
Nextcloud was successfully installed
Set mode for background jobs to 'cron'
System config value tempdirectory set to string /var/www/nextcloud/data/tmp
System config value mysql.utf8mb4 set to boolean true
System config value trusted_domains => 22 set to string nextcloudpi
System config value trusted_domains => 22 set to string nextcloudpi.local
System config value trusted_domains => 22 set to string nextcloudpi.lan
System config value trusted_domains => 22 set to string nextcloudpi.lan
System config value mail_smtpmode set to string sendmail
System config value mail_smtpauthtype set to string LOGIN
System config value mail_from_address set to string admin
System config value mail_domain set to string ownyourbits.com
nextcloudpi 0.0.1 enabled
calendar 2.3.4 installed
calendar enabled
calendar already enabled
contacts 4.0.6 installed
contacts enabled
contacts already enabled
notes 4.2.0 installed
notes enabled
notes already enabled
tasks 0.14.2 installed
tasks enabled
tasks already enabled
updatenotification 1.12.0 disabled
news 16.2.1 installed
news enabled
news already enabled
notify_push 0.3.0 installed
notify_push enabled
notify_push already enabled
Column "oc_preview_generation"."locked" is type Bool and also NotNull, so it can not store "false".

I have been using the script for a long time and just love how easy it makes for the likes of me to get NextCloud up and running in a LAN with WAN access to files and with also good security (SSL, etc…).

I have helped friends get it running in HW like RPi, Odroid HC2 to “recycling” old laptops which just work great as NCP “server” :slight_smile:

In that case @nachoparker may need to take a look at the issue…

1 Like

should be fixed now. Thanks

1 Like

Just tested, seems OK but the version number is strange?

previewgenerator 99.99.99 enabled

news already enabled
notify_push 0.3.0 installed
notify_push enabled
notify_push already enabled
previewgenerator 99.99.99 enabled
Config value squareSizes for app previewgenerator set to 32 256
Config value widthSizes for app previewgenerator set to 256 384
Config value heightSizes for app previewgenerator set to 256
System config value preview_max_x set to string 2048
System config value preview_max_y set to string 2048
System config value jpeg_quality set to string 60
Config value jpeg_quality for app preview set to 60
System config value overwriteprotocol set to string https
System config value overwrite.cli.url set to string https://nextcloudpi/
Hit:1 http://ftp.rnl.tecnico.ulisboa.pt/pub/debian buster InRelease
Hit:2 http://ftp.rnl.tecnico.ulisboa.pt/pub/debian buster-updates InRelease
Hit:3 http://security.debian.org/debian-security buster/updates InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
bash-completion is already the newest version (1:2.8-6).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
All tables already up to date!
Check indices of the share table.
Check indices of the filecache table.
Check indices of the twofactor_providers table.
Check indices of the login_flow_v2 table.
Check indices of the whats_new table.
Check indices of the cards table.
Check indices of the cards_properties table.
Check indices of the calendarobjects_props table.
Check indices of the schedulingobjects table.
Check indices of the oc_properties table.
Done.
NC init done
/root
Done.

First: Visit https://192.168.200.88/  https://nextcloudpi.local/ (also https://nextcloudpi.lan/ or https://nextcloudpi/ on windows and mac)
to activate your instance of NC, and save the auto generated passwords. You may review or reset them
anytime by using nc-admin and nc-passwd.
Second: Type 'sudo ncp-config' to further configure NCP, or access ncp-web on https://192.168.200.88:4443/
Note: You will have to add an exception, to bypass your browser warning when you
first load the activation and :4443 pages. You can run letsencrypt to get rid of
the warning if you have a (sub)domain available.

This is also something that happens to me all the time… since a long time ago :slight_smile:

Every time I finish the installation script, I cannot open the activator page, I always get:

image

after a restart apache2 I get:

I don’t see people complaining so I don’t know if I should open a issue in github :frowning:

The trusted domain stuff is obvious, you have to add the ip address and the url you use to trusted domains in nextcloud/config.php, this can be done via ncp pannel as well.

The rest seems to be about activation of nextcloud and ncp and is a final step to do. If you still have questions, please open a new thread, one thread one subject please.

Not sure I follow…

As I mentioned, I just restart apache2 and I don’t get the “trusted domain” message. Plus, I think that the /var/www/nextcloud/config/config.php is “automatically” filled in properly. I just double checked it… The only thing I do is restart apache so if this was a issue with the config file, restarting should not change any content.