Bug 16676

Summary:	Cannot reinstate rsync for my server
Product:	Websites	Reporter:	james Whitby <jim>
Component:	mirrors.mageia.org	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	ftg, sysadmin-bugs, thierry.vignaud
Version:	trunk
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://mirrors.mageia.org/new
Whiteboard:
Source RPM:		CVE:
Status comment:

Description james Whitby 2015-08-31 21:35:19 CEST

Having been down for several hours, upgrading, I cannot get my rsync to register again.

Additionally, my listing shows either i586 or x86_64 as broken depending on when it gets checked. Never both, just one or the other.


Http and ftp seem to be ok.

Attempting to add:


rsync://mageia.jameswhitby.net/mageia/


After some seconds I get the following error:

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.


Anything I can do to repair this?



Reproducible: 

Steps to Reproduce:

Comment 1 Thierry Vignaud 2015-09-02 12:52:12 CEST

It looks like you're trying a broken mirror

CC: (none) => thierry.vignaud

Comment 2 james Whitby 2015-09-02 17:44:16 CEST

Nothing was changed here... no reboot, etc.

Rsync now works properly.

It still shows missing i586 files, which are still there.

Comment 3 Frank Griffin 2015-09-02 17:54:29 CEST

Does "ps ax | grep rsync" on mageia.jameswhitby.net show that the rsync daemon is running ?  If so, did your /etc/rsyncd.conf get deleted or damaged ?

CC: (none) => ftg

Comment 4 james Whitby 2015-09-02 18:01:24 CEST

Yes, rsyncd was running, firewall was/is open.

Rsync added today, properly.

Still showing broken i586 dir on all.

Comment 5 Frank Griffin 2015-09-02 20:38:40 CEST

You have a gift for being terse :-)

What does "properly" mean ?  What does "Still showing broken i586 dir on all" mean ?

What is the output of "rsync mageia.jameswhitby.net::" ?

Comment 6 james Whitby 2015-09-03 02:38:13 CEST

$ rsync mageia.jameswhitby.net::

mageia          rsync mageia area
mirror          rsync mageia area

Now the "broken" dir has moved to x86_64.

Comment 7 james Whitby 2015-09-03 03:01:51 CEST

Sorry for the terseness., too many man pages in my head...

onhttps://mirrors.mageia.org/status
Lists the status of (now ) x86_64 as X.for all versions,
 Earlier today it was X for i586.

Rsysnc is now listed as working under http://mirrors.mageia.org/

FWIW Rsync was unlisted because I was off-line. I upgraded to mga5, took longer than expected, so was off-line for several hours. When I finally had the system up and running properly, rsynce was listed as not working on 
http://mirrors.mageia.org/

Attempts to reinstate it meet with internal errors form http://mirrors.mageia.org/new

That was yesterday. Today it works.

Comment 8 Thierry Vignaud 2015-09-03 10:43:21 CEST

Let's close it then.
I picked "old" as resolution as it wasn't really a Mageia bug.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 9 james Whitby 2015-09-03 15:11:08 CEST

I would disagree, however the rsync did start working the next day, even thought nothing changed here.

I'll open a separate bug re: the "status" page.