-
Notifications
You must be signed in to change notification settings - Fork 141
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
CentOS 7 using incorrect Image #71
Comments
I just checked with an AWS CentOS7 Ami. |
Same problem here, more informations about my CentOS 7 below:
|
To be honest, the script doesn't work on CentOS 7 at all for me, even correcting this error, the installed later fails at Let's Encrypt saying the SSL directories don't exist.Works on Ubuntu 16 fine though...
-------- Original message --------From: WaZaK <[email protected]> Date: 21/04/2020 13:44 (GMT+00:00) To: ReinerNippes/nextcloud <[email protected]> Cc: Hybrice <[email protected]>, Author <[email protected]> Subject: Re: [ReinerNippes/nextcloud] CentOS 7 using incorrect Image (#71)
Same problem here, more informations about my CentOS 7 below:
[ansible@nextcloud ~]$ cat /etc/*elease
CentOS Linux release 7.7.1908 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
CentOS Linux release 7.7.1908 (Core)
CentOS Linux release 7.7.1908 (Core)
[ansible@nextcloud ~]$ uname -r
3.10.0-1062.el7.x86_64
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#71 (comment)",
"url": "#71 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
I changed the path /etc/ImageMagick-6 to with commit f8efb46. |
Next try. @Hybrice @WaZaK There is a newer version of ImageMagick in the remi php repos. During the installation of the php modules ImageMagick become updated as well and this changed silently the config folder to /etc/ImageMagick-6. I moved the installation to the prep_php role. So ImageMagick will be installed from the remi repo at once. For testing I pushed it to: https://github.com/ReinerNippes/nextcloud/tree/ImageMagick |
I've tried building with the ImageMagick branch using cloud-init and ami-0affd4508a5d2481b (CentOS 7 with updates) and it fails to build. I tried building again with the Ansible output redirected to a log file and it always gets stuck on applying SElinux tasks. I then tried running it again with the script running as "centos" with already tested inventory file set and "sudo -u centos ./nextcloud.yml" from UserData and it managed to apply SELinux bit but got stuck again when getting the UUID for web-server user. Thanks for the wonderful script never seen such attention to small customization details. I've just decided to move from the Ubuntu version to CentOS version overnight at a bad time.
|
@daleosm Do you have the output of the playbook run? Maybe you have to add a |
Here is my Ansible log:
|
This is my execution:
Edit: I'm now getting this error when launching the install from a CloudFormation script but with the same execution method. I'm so confused as the reason for it not working keeps changing but my code is 99% the same.
I can pull Nextcloud on the instance with wget fine. |
I have seen problems downloading the nextcloud tgz. Nevertheless rather seldom. I just tried with the ami you mentioned. In the inventory I only changed the fqdn. And it worked.
|
CentOS 7 now installs ImageMagick-6 during setup script, meaning nextcloud.yml breaks during running as files are locked at /etc/ImageMagick-6/ not /etc/ImageMagick/, editing the ansible role for this corrects the problem.
The text was updated successfully, but these errors were encountered: