Skip to content
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

Integrity check false alert on fresh installation #5578

Closed
MarcinOrlowski opened this issue Jun 30, 2017 · 7 comments
Closed

Integrity check false alert on fresh installation #5578

MarcinOrlowski opened this issue Jun 30, 2017 · 7 comments
Labels
papercut Annoying recurring issue with possibly simple fix.

Comments

@MarcinOrlowski
Copy link

I am doing fresh automated install of NextCloud and each time it reports integrity check issue:

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
	- EXTRA_FILE
		- lib/private/oc_tmp_zJAacJ-.tar.gz

Raw output
==========
Array
(
    [core] => Array
        (
            [EXTRA_FILE] => Array
                (
                    [lib/private/oc_tmp_zJAacJ-.tar.gz] => Array
                        (
                            [expected] => 
                            [current] => .....
                        )
                )
        )
)

The trick is that the file does not exists and as name suggests it is probably something that existed during installation, so the bug is most likely in the order of operations as integrity should checked after all temp files are removed.

Rescan solves the issue

@jospoortvliet
Copy link
Member

A timing issue then - as a rescan happens automatically after some time anyway, I'm not sure we have to do anything here.

@MarcinOrlowski
Copy link
Author

MarcinOrlowski commented Jul 5, 2017

While this is not the highest priority, I think it should be addressed as this may give false impression the installation is i.e. "doctored"

@jospoortvliet
Copy link
Member

@LukasReschke anything we can/should do here?

@jospoortvliet jospoortvliet added the papercut Annoying recurring issue with possibly simple fix. label Jul 15, 2017
@LukasReschke
Copy link
Member

How did you do that automated installation? The file there is not generated by us as neither our web installer nor our regular updater uses the TAR file.

@MarcinOrlowski
Copy link
Author

I wrote Ansible playbook for that. The location of this temp file made me think that it is part your installer process, yet I will check now to ensure this is correct assumption

@florian-s-code
Copy link

florian-s-code commented Jun 16, 2019

This is still an issue on Nextcloud 16.0.1.

The instance was installed manually using the tar.gz file downloaded on the official website. The server is a Synology box running Apache 2.4 with PHP 7.2.

@kesselb
Copy link
Contributor

kesselb commented Jun 16, 2019

This is still an issue on Nextcloud 16.0.1.

The instance was installed manually using the tar.gz file downloaded on the official website. The server is a Synology box running Apache 2.4 with PHP 7.2.

Please don't respond to closed and stale issues. This issue is closed since 2017. There is a similar issue for newer versions #15681 or create a new issue.

@nextcloud nextcloud locked as resolved and limited conversation to collaborators Jun 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
papercut Annoying recurring issue with possibly simple fix.
Projects
None yet
Development

No branches or pull requests

5 participants