[RESOLVED via FM] Is there something wrong with the Ibiblio server?

[YouCanToo]

I noticed in my log files that when I tries to sync with the ibiblio server at 10:00pm it failed. I tried to run it manually and this is the results that came back

rsync: failed to connect to distro.ibiblio.org: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]

I tried this on two different machines now with the same results

[Old-Polack]

I noticed in my log files that when I tries to sync with the ibiblio server at 10:00pm it failed. I tried to run it manually and this is the results that came back

rsync: failed to connect to distro.ibiblio.org: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]

I tried this on two different machines now with the same results

I just did my upgrades to the 64 bit test system, from ibiblio, at 1:00 Central Time and had no trouble with connecting. Maybe it was just syncing with what Texstar was uploading when you tried. Try again.

[YouCanToo]

nope same thing at 23:10 PST

[root@findmoore pclosusers]# ./get-files.sh
rsync: failed to connect to distro.ibiblio.org: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.4]

I will try it once more in a couple of hours.

[Just17]

No problem here either ....  updating 64 bit .....  and now the main repo .... as I write this ..

[YouCanToo]

Well I am not sure just what is going on here. I tried connecting two more times last night and it still has not worked. I tried again this morning about 8 am PST and was still not working. I tried again about 11:00 am PST and it finally worked. Yeah    Perhaps it is some sort of a networking issue as a couple of folks said it was working for them. Though I not so sure as the message stated "Connection Refused"  Anyway I am marking the message as "resolved via FM"

[muungwana]

"Connection refused" error message usually means the server at the other end of the connection is up and running and reachable but there is no service running on the port you want to connect to. The error is produces by the kernel when it accepts your connection, look up the port number you ask to connect to and find out there is no application listening on that port. It then just drops the connection with that error.

Those who responding said they were on 64 bit, maybe they werent accessing the same server/server port number?

[Just17]

"Connection refused" error message usually means the server at the other end of the connection is up and running and reachable but there is no service running on the port you want to connect to. The error is produces by the kernel when it accepts your connection, look up the port number you ask to connect to and find out there is no application listening on that port. It then just drops the connection with that error.

Those who responding said they were on 64 bit, maybe they werent accessing the same server/server port number?

Dunno about the ports ......  but I connected to the 64 bit and also to the main repo at the same time period.

[YouCanToo]

"Connection refused" error message usually means the server at the other end of the connection is up and running and reachable but there is no service running on the port you want to connect to. The error is produces by the kernel when it accepts your connection, look up the port number you ask to connect to and find out there is no application listening on that port. It then just drops the connection with that error.

Those who responding said they were on 64 bit, maybe they weren't accessing the same server/server port number?

One would think it should not matter which version (32 or 64bit) was being used, rsync as it defaults should be using port 873. Really guess it does not matter at the time now that it is working.

[muungwana]

what does "FM" mean?

It happened before, to you this time, it probably will happen again, to you or somebody else. If we do not find out what happened this time, we will be exactly where you were on your first post when it happen again.

I do not know how rsync works. It connects to the server on port 873? I think normal access to the repositories is on port 80. Maybe this is why others manage to connect correctly? They were using synaptic and it was connection on port 80 and your were failing because you were connecting on port 873?

[YouCanToo]

what does "FM" mean?

frigging magic

It happened before, to you this time, it probably will happen again, to you or somebody else. If we do not find out what happened this time, we will be exactly where you were on your first post when it happen again.

I do not know how rsync works. It connects to the server on port 873?

I agree it would indeed be nice to know why it happened! At this time I am also happy that it is working as it should be.

yes, rsync connects on port 873

I think normal access to the repositories is on port 80. Maybe this is why others manage to connect correctly? They were using synaptic and it was connection on port 80 and your were failing because you were connecting on port 873?

I sync pclosusers repository using rsync not synaptic using the following command

Code: [Select]

rsync -av -P --stats --delete \distro.ibiblio.org::pclinuxos/pclinuxos/apt/. \/home/members/pclosusers/pclosfiles

rsync does not do the same thing as synaptic which indeed uses port 80

Even if it were the case that still would not explain why it didn't work and than started working about 12 hours later. It wasn't on just one machine either. It was on 2 different machines on different networks.

[muungwana]

rsync does not do the same thing as synaptic which indeed uses port 80

Even if it were the case that still would not explain why it didn't work and than started working about 12 hours later. It wasn't on just one machine either. It was on 2 different machines on different networks.

You tried to connect using rsync and it tried to connect on port 873 but there was no service running on that port number on the server and thats why the server returned a "connection refused" error.

Those who tested the server tested using synaptic and hence on port 80 and thats why things worked for them.

The only explanation remaining is that the rsync server was down and now it is up.

[Texstar]

It must have been down earlier because I just tried it and it went to ibiblio without issue.

[YouCanToo]

rsync does not do the same thing as synaptic which indeed uses port 80

Even if it were the case that still would not explain why it didn't work and than started working about 12 hours later. It wasn't on just one machine either. It was on 2 different machines on different networks.

You tried to connect using rsync and it tried to connect on port 873 but there was no service running on that port number on the server and thats why the server returned a "connection refused" error.

Those who tested the server tested using synaptic and hence on port 80 and thats why things worked for them.

The only explanation remaining is that the rsync server was down and now it is up.

Yes, I think we can all agree on it.

[Just17]

rsync does not do the same thing as synaptic which indeed uses port 80

Even if it were the case that still would not explain why it didn't work and than started working about 12 hours later. It wasn't on just one machine either. It was on 2 different machines on different networks.

You tried to connect using rsync and it tried to connect on port 873 but there was no service running on that port number on the server and thats why the server returned a "connection refused" error.

Those who tested the server tested using synaptic and hence on port 80 and thats why things worked for them.

The only explanation remaining is that the rsync server was down and now it is up.

Yes, I think we can all agree on it.

Well I cannot agree .......  as I was using rsync for both sets of downloads when I posted above.
The downloads were in progress and as I posted, one finished and the other started.

If I could find a service running there then so should everyone else.
Unless the times were out .....  or is it possible there is a limit on connections and it was exceeded when you tried?

To me it seems more like an issue with your provider at the time .....

regards.

[muungwana]

just18,
can you check and confirm your rsync command did point to "distro.ibiblio.org"?