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

Create almalinux.jetserver.co.il.yml #1003

Merged
merged 5 commits into from
Apr 16, 2024
Merged

Conversation

JetServerCloud
Copy link
Contributor

AlmaLinux mirror from Jetserver Cloud

@codyro
Copy link
Member

codyro commented Mar 31, 2024

Hello,

Thank you for the mirror! It looks like it's not syncing properly. Would you mind investigating before we merge this in?

Thanks!

Sun Mar 24 07:38:08 UTC 2024

@JetServerCloud
Copy link
Contributor Author

Hello,

Thank you for the mirror! It looks like it's not syncing properly. Would you mind investigating before we merge this in?

Thanks!

Sun Mar 24 07:38:08 UTC 2024

Hello,

It turned out that 1TB isn't enough. I've increased the disk to 1.5TB. looks like it's working as it should.
Can you validate it please?

Thank you!

@codyro
Copy link
Member

codyro commented Apr 2, 2024

We'll be moving the vaults off the main repos soon, which should free up a lot of space.

It looks like this is still reporting as out-of-date: Sun Mar 24 07:38:08 UTC 2024

If you're curious, I'm pulling this from https://almalinux.jetserver.co.il/timestamp.txt, which the mirror service uses to help determine if a mirror is up-to-date and should be listed. As-is, your mirror wouldn't show up even if it were merged.

@JetServerCloud
Copy link
Contributor Author

We'll be moving the vaults off the main repos soon, which should free up a lot of space.

It looks like this is still reporting as out-of-date: Sun Mar 24 07:38:08 UTC 2024

If you're curious, I'm pulling this from https://almalinux.jetserver.co.il/timestamp.txt, which the mirror service uses to help determine if a mirror is up-to-date and should be listed. As-is, your mirror wouldn't show up even if it were merged.

Unfortunately I'm getting an error that I don't understand the reason behind it.
The initial sync was a success, we've managed to get the full 973G of data. but the cron we've set isn't working for some reason.

This is the cron:

0 */3 * * * sleep $(((RANDOM\%3500)+1)) && /usr/bin/flock -n /var/run/almalinux_rsync.lock -c "/usr/bin/rsync -avSH --exclude='.~tmp~' --delete-delay --delay-updates rsync://[rsync.repo.almalinux.org/almalinux/](http://rsync.repo.almalinux.org/almalinux/) /Files-Path/"

When I try to run the command manually, this is what I get:

-bash: (RANDOM\%3500)+1: syntax error: invalid arithmetic operator (error token is "\%3500)+1")

And when I try to run it this way:

/usr/bin/flock -n /var/run/almalinux_rsync.lock -c "/usr/bin/rsync -avSH --exclude='.~tmp~' --delete-delay --delay-updates rsync://[rsync.repo.almalinux.org/almalinux/](http://rsync.repo.almalinux.org/almalinux/) /Files-Path/"

This is what I get:

rsync: [Receiver] failed to connect to [rsync.repo.almalinux.org](http://rsync.repo.almalinux.org/) (162.43.206.5): Connection refused (111)
rsync: [Receiver] failed to connect to [rsync.repo.almalinux.org](http://rsync.repo.almalinux.org/) (2605:21c0:1000:4e::5): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

I appreciate the help!

@jonathanspw
Copy link
Member

It looks like the URL(s) you copied have markdown in them. How exactly did you copy them?

@JetServerCloud
Copy link
Contributor Author

Hello,

We found a firewall problem, but it's fixed now. Please check.

@codyro
Copy link
Member

codyro commented Apr 15, 2024

It looks like the https URL is throwing a 403:

root@c ~# curl -I https://almalinux.jetserver.co.il
HTTP/1.1 403 Forbidden
Server: nginx/1.14.1
Date: Mon, 15 Apr 2024 10:42:59 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive

@JetServerCloud
Copy link
Contributor Author

It looks like the https URL is throwing a 403:

root@c ~# curl -I https://almalinux.jetserver.co.il
HTTP/1.1 403 Forbidden
Server: nginx/1.14.1
Date: Mon, 15 Apr 2024 10:42:59 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive

Hello,

Directory listing was off over https. I've enabled it and it looks like it's working just fine now.

@codyro
Copy link
Member

codyro commented Apr 16, 2024

Looks good! Thanks for the mirror @JetServerCloud & @Noam-Alum

@codyro codyro merged commit 0789c77 into AlmaLinux:master Apr 16, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants