Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
Mirrorbits?
#1
when did you guys cut over to mirrorbits?

sneaky ;o
Reply
#2
this week Wink
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#3
Image
Image
Image

Just a day ago Smile
Reply
#4
By the way, i am not able to rsync-read from z.os6.org from our server, could you take a look at that ? It effectively disables that mirror.
Reply
#5
I like Mirrorbits way better than mirrorbrain. Mirrorbits is so simple to setup.

I was wondering why both of the mirrors were balanced and noticed someone upgraded to mirrorbits. It load balances rather than relying on geoip. I just setup a second nic on z to cope with the bursts and now i doubt it will max gbit TonguePP


Kib,

I saw that yesterday.

i think someone fat fingered the url and added it as "zee.os6.org".

I made a cname from zee.os6.org > z.os6.org and its working now :p

Do you have a cpu graph while it was mirrorbrain? I'm curious how the load has changed.

Are you going to go down the mirrorbrain cluster route once mirrorbits releases it? seems interesting : ]

keep up the good work Rofl
Reply
#6
stats stats stats : ]

http://mirrors.xbmc.org/releases/win32/k...irrorstats


leaseweb is stealing all my traffic!
Reply
#7
it was a quick import from an outdated spreadsheet which wasn't kept up to date with mirrorbrain. Still lots of tweaking needed.

Mirrorbrain was good while it lasted but we simple outgrew the vast amount of data/connections
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#8
Image
Reply
#9
Huh, interesting. It was not fat fingered at all.
I manually set it up as zee.os6.org in description only, the url is set up as z.os6.org.
The reason for this was I couldn't put it back when it was set as z.os6.org because it complained it was already in the database that way.
(which is a seperate issue I need to discuss with etix, the creator if mirrorbits).

It should not connect to zee.os6.org at all, this would mean we discovered a bug where it connects to the descriptive name instead of the rsync url set up.
Code:
Mirror: zee.os6.org
HttpURL: http://z.os6.org/xbmc/
RsyncURL: rsync://z.os6.org/xbmc/
FtpURL: ""
SponsorName: OS6
SponsorURL: ""
SponsorLogoURL: ""
AdminName: <redacted>
AdminEmail: <redacted>
CustomData: ""
ContinentOnly: false
CountryOnly: false
ASOnly: false
Score: 20
Latitude: 34.0438
Longitude: -118.2512
ContinentCode: NA
CountryCodes: US
ASNum: 8100
Enabled: true

Wrote a ticket about the editing / removing bit of mirrorbits here: https://github.com/etix/mirrorbits/issues/19

I've managed to get the flakey key out of the database and readded the mirror as z.os6.org Smile
Reply
#10
Etix already fixed the issue:
https://github.com/etix/mirrorbits/commi...80c1c31251
Reply
#11
wow Etix is a beast!
Reply
#12
I'm waiting for someone to make a opensource mirrorbits mirror network. So many projects that would benefit from it.
Reply

Logout Mark Read Team Forum Stats Members Help
Mirrorbits?0