NextCloudPi PHP7.2 NC14.0.1 a call for testing

NEW RELEASE

testing the upgrade (backup first)

Hi everyone,

The release is ready to go to the testing channel. I have tested it and it seems to works fine. It brings

  • NC14.0.1
  • PHP7.2

It would be great to have some brave testers to run sudo ncp-update devel and verify that all is good before I roll it out to the rest of the users. If you haven’t got nc-autoupdate-nc activated you will have to run nc-update-nextcloud manually, otherwise in less than a day your instance should upgrade to NC14.0.1

testing the images

The generated images have been uploaded to ownyourbits.com/downloads/testing.

Please, everyone with a board willing to test it speak out, or add yourself to the list in

Following the protocol, I will call out to the following testers: please, one tester per board give us an ACK (meaning they will test that board), and another one if the testing goes well. See details in the link above

Thanks!

I already tested briefly docker x86, regular rpi, and rock64, but more thorough testing would be welcome

Thanks for your work, nachoparker

ACK, I test the ODROID-Image (still downloading…)

1 Like

Booting with the ODROID-Image works, also Activating NCP.
But while I want to restore my data I get this error:


Have the problem while restoring the data and cleanup-processes are starting I have the message “Something went wrong”. Anybody else with this error?

1 Like

I´ll test Berryboot

1 Like

After installing the new image I still have NextCloud 13.0.6. So I did the update via NCP-Webpage. Then the same problem with Cleanup:

After this I did a reboot and now I have this error in NextCloud:

The details are:

Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

  • news
    • EXCEPTION
      • OC\IntegrityCheck\Exceptions\InvalidSignatureException
      • Signature data not found.

Raw output

Array
(
[news] => Array
(
[EXCEPTION] => Array
(
[class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
[message] => Signature data not found.
)

    )

)

1 Like

Testing curl installer, initially getting following error output, on a clean debian 9 install (VM):

root@ncpvm:~# curl -sSL https://github.com/nextcloud/nextcloudpi/blob/devel/install.sh | bash
bash: line 9: syntax error near unexpected token newline' bash: line 9:
curl: (23) Failed writing body (899 != 1370)

But when copy content from install.sh and making executable it seems to run fine. So will report when done !

It seems to want to install 13.0.6 and ends with:

> Installing nc-backup
> Installing nc-restore
> Nextcloud is not installed - only a limited number of commands are available
> 
>                                                                   
>   [Symfony\Component\Console\Exception\CommandNotFoundException]  
>   Command "app:install" is not defined.                           
>   Did you mean one of these?                                      
>       app:check-code                                              
>       maintenance:install                                         
>                                                                   
> 
> Nextcloud is not installed - only a limited number of commands are available
> 
>                                                                   
>   [Symfony\Component\Console\Exception\CommandNotFoundException]  
>   Command "app:enable" is not defined.                            
>   Did you mean this?                                              
>       app:check-code                                              
>                                                                   
> 
> NextCloudPi updated to version v0.60.8
> Activating nc-init
> Setting up a clean Nextcloud instance... wait until message 'NC init done'
> Setting up database...
> Setting up Nextcloud...
> Nextcloud is not installed - only a limited number of commands are available
> Nextcloud was successfully installed
> Set mode for background jobs to 'cron'
> System config value mysql.utf8mb4 set to boolean true
> System config value trusted_domains => 1 set to string 192.168.2.9
> System config value trusted_domains => 5 set to string nextcloudpi.local
> 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
> calendar installed
> contacts installed
> notes installed
> tasks installed
> news installed
> admin_notifications installed
> calendar enabled
> contacts enabled
> notes enabled
> tasks enabled
> news enabled
> admin_notifications enabled
> System config value overwriteprotocol set to string https
> NC init done
> ~
> Done.
> Type 'sudo ncp-config' to configure NCP, or access ncp-web on https://<this_ip>:4443
> 
> root@ncpvm:~# 

When visiting local IP I get redirected to activation after which I can log in to NC with activation credentials. But NC it is still version 13.0.6
NextCloudPi configuration ver. v0.60.8

1 Like

Tried updating from ncp-config after updating ncp to ver 62.0 with ncp-update devel

Launching nc-update-nextcloud
Current   Nextcloud version 13.0.6.1
Available Nextcloud version 14.0.1
Download Nextcloud 14.0.1...
Back up current instance...
check free space...
Maintenance mode enabled
backup database...
backup base files...
compressing backup file...
backup /var/www//nextcloud-bkp_20180929_1538222681.tar.gz generated
Nextcloud is in maintenance mode - no apps have been loaded

Maintenance mode disabled
Install Nextcloud 14.0.1...
Restore apps...
 * admin_notifications
 * apporder
 * bookmarks
 * calendar
 * checksum
 * circles
 * contacts
 * dashboard
 * external
 * flowupload
 * notes
 * ocsms
 * previewgenerator
 * richdocuments
 * socialsharing_email
 * tasks
Fix permissions...
Upgrade...
Nextcloud is not installed - only a limited number of commands are available

                                     
  Command "upgrade" is not defined.  
                                     

Abort
Clean up...
Rolling back to backup /var/www/nextcloud-bkp_20180929_1538222681-13.0.6.1.tar.gz...
decompressing backup file /var/www/nextcloud-bkp_20180929_1538222681-13.0.6.1.tar.gz...
extracting backup file /var/www/ncp-restore.BoTuj5/nextcloud-bkp_20180929_1538222681.tar...
restore files...
restore database...
no datadir found in backup
Nextcloud is in maintenance mode - no apps have been loaded

Maintenance mode disabled

Scanning files for 18 users
Starting scan for user 1 out of 18 (***)
Starting scan for user 2 out of 18 (***)
Starting scan for user 3 out of 18 (***)
Starting scan for user 4 out of 18 (***)
Starting scan for user 5 out of 18 (***)
Starting scan for user 6 out of 18 (***)
Starting scan for user 7 out of 18 (***)
Starting scan for user 8 out of 18 (***)
Starting scan for user 9 out of 18 (***)
Starting scan for user 10 out of 18 (***)
Starting scan for user 11 out of 18 (***)
Starting scan for user 12 out of 18 (***)
Starting scan for user 13 out of 18 (***)
Starting scan for user 14 out of 18 (***)
Starting scan for user 15 out of 18 (***)
Starting scan for user 16 out of 18 (***)
Starting scan for user 17 out of 18 (***)
Starting scan for user 18 out of 18 (***)

+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 6745    | 38135 | 00:03:35     |
+---------+-------+--------------+
System config value trusted_domains => 1 set to string 192.168.2.214
Cleanup...
Rollback successful. Nothing was updated
Done. Press any key...
1 Like

@Kunibert, did you install the testing image?

https://ownyourbits.com/downloads/testing/NextCloudPi_OdroidHC2_09-27-18/

I haven’t seen this, but will look into it. It is a harmless thing though, at that point the restore process is complete

Seems yet another problem with the news app update. What version of the app are you at? I already worked around the .htaccess problem.

Many thanks!

@OliverV,

I think that you haven’t installed from devel, but from master

  • Download install.sh
  • Make it executable
  • Change this line to BRANCH=devel

Many thanks

@Pantelis

Are you on a rpi? did the upgrade to PHP7.2 go well? Did your NC instance roll back ok to the previous version?

Thanks!

Used https://github.com/nextcloud/nextcloudpi/blob/devel/install.sh
without changing it to BRANCH=devel, which explains why I end up with 13 still, I will give it another run later tho, just to make sure.

Just did re-run on clean install VM Debian 9, works like a charme!
install14success-Screenshot%20at%202018-09-29%2016-18-16
ncp-web:

php --version
PHP 7.2.9-1 (cli) (built: Aug 19 2018 06:56:13) ( NTS )
Copyright © 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright © 1998-2018 Zend Technologies
with Zend OPcache v7.2.9-1, Copyright © 1999-2018, by Zend Technologies
root@ncpvm14:~# pstree
systemd─┬─agetty
├─apache2───2*[apache2───63*[{apache2}]]
├─cron
├─dbus-daemon
├─dhclient
├─dnsmasq
├─fail2ban-server───2*[{fail2ban-server}]
├─lvmetad
├─master─┬─pickup
│ └─qmgr
├─mysqld───29*[{mysqld}]
├─php-fpm7.2───3*[php-fpm7.2]
├─redis-server───2*[{redis-server}]
├─rpc.idmapd
├─rpc.mountd
├─rpcbind
├─rsyslogd─┬─{in:imklog}
│ ├─{in:imuxsock}
│ └─{rs:main Q:Reg}
├─sshd───sshd───sshd───bash───su───bash───pstree
├─systemd───(sd-pam)
├─systemd-journal
├─systemd-logind
├─systemd-timesyn───{sd-resolve}
├─systemd-udevd
└─wicd───wicd-monitor

1 Like

Hi, i am seeing a similar problem with news, so i just uninstalled it, but there is another issue, a wrong hash for user.ini

Results
=======
- core
	- INVALID_HASH
		- .user.ini

can you help me fix this? Maybe i made the mistake and first updated nextcloud to 14.0.1 via nextcloud before reading this thread and thinking i could give this a try… php 7.2 did install perfectly on my rpi2 btw

@FadeFx use the NCP updater, that’s a bug in the NC updater

https://github.com/nextcloud/nextcloudpi/issues/656#issuecomment-425599786

the NCP installer also takes care of the News problem

awesome, thanks @OliverV!!

Tested berryboot 09-27-18 img:
boot is fine.
when visit local ip get redirected to activation after which can
log in to NC 14.0.1
log in ncp v0.60.8
No errors encountered, seems to be working fine :slight_smile:
Nice job!

awesome @OliverV, many thanks!!

@nachoparker, any way to fix these issues manually, or am i forced to restore a backup and start from 13.0.6?

Hi @nachoparker,

yes, I took the image from https://ownyourbits.com/downloads/testing/. But I see there is a new image (I took the one from 2018-27-09, now there is a version 201829-09. Should I test this, too?

The news-app was version 12.0.4. upgraded it now to 13.x. but I already have this error:
Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

  • core
    • INVALID_HASH
      • .user.ini
  • news
    • FILE_MISSING
      • vendor/ezyang/htmlpurifier/maintenance/.htaccess

Raw output

Array
(
[core] => Array
(
[INVALID_HASH] => Array
(
[.user.ini] => Array
(
[expected] => 467d4f028c447895716a2b7859ed6e569f8ee34b87b51d73dab2e6a9ca4fbe63172c7be3e365ae864a60408286afcce852dd38ee544b61685ed4ee5e021fecb0
[current] => 90a880b341698d33de15d0a07ac1fdc12f06fae40fffab5edd5f60dbef8344c1715c12aedcd1c520cc065418456979b8db5e5be870d32bc64c78fb4cb229bf21
)

            )

    )

[news] => Array
    (
        [FILE_MISSING] => Array
            (
                [vendor/ezyang/htmlpurifier/maintenance/.htaccess] => Array
                    (
                        [expected] => 4d51270ac56b1600199cd52c4f0fc34171bb306db59761863c87978049b771a053ebb80c8dda03b4d98bf5e43361ec0e1e1d2ad4b01fc315fb809b40acd23843
                        [current] => 
                    )

            )

    )

)

this worked for me,

found in older topics,

Hi,

Here is a trick (do it only if you are sure of your “.htaccess” file integrity)

Put that in your “config.php” :

‘integrity.check.disabled’ => true,

Now reload the page and when you see the yellow banner click on rescan
Log-out and next time you log-in as admin you will not see the banner.
You can now delete the line you put in your config.php to re-enable the integrity check, and you will not see anymore the banner.