Link to home
Start Free TrialLog in
Avatar of jparker81
jparker81

asked on

RSYNC Errors 30 and 5

I am having some major issues with rsync. The IT person before me set this up, I am not really familiar with how this works. I do know that the machine that is taking the backups is an Ubuntu Linux server. One of the drives it is trying to backup is on a 2003 Windows Server. Here are some snippets from the rsync log file.

Sep 26 14:10:48 brown rsyncd[888]: inflate returned -3 (679 bytes)
Sep 26 14:10:48 brown rsyncd[888]: rsync error: error in rsync protocol data stream (code 12) at token.c(546) [receiver=3.0.7]
Sep 26 14:10:48 brown rsyncd[888]: rsync: connection unexpectedly closed (79577 bytes received so far) [generator]
Sep 26 14:10:48 brown rsyncd[888]: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]
Sep 26 14:10:51 brown rsyncd[932]: Unknown Parameter encountered: "patht"
Sep 26 14:10:51 brown rsyncd[932]: IGNORING unknown parameter "patht"
Sep 26 14:10:51 brown rsyncd[932]: name lookup failed for 10.0.0.22: Name or service not known
Sep 26 14:10:51 brown rsyncd[932]: connect from UNKNOWN (10.0.0.22)
Sep 26 14:10:51 brown rsyncd[932]: rsync to redMon/Shares/ from UNKNOWN (10.0.0.22)
Sep 26 14:10:51 brown rsyncd[932]: receiving file list
Sep 26 14:10:52 brown rsyncd[932]: rsync: readlink_stat("/Shares/Temp" (in redMon)) failed: Input/output error (5)
Sep 26 14:10:52 brown rsyncd[932]: IO error encountered -- skipping file deletion
Sep 26 14:10:52 brown rsyncd[932]: rsync: failed to set times on "/Shares/." (in redMon): Read-only file system (30)
Sep 26 14:10:52 brown rsyncd[932]: rsync: failed to set times on "/Shares/ACH" (in redMon): Read-only file system (30)
Sep 26 14:10:52 brown rsyncd[932]: rsync: recv_generator: failed to stat "/Shares/ACH/ALAMON0074" (in redMon): Input/output error (5)

This one is popping up repeatedly in the rsync log file

Sep 26 14:10:53 brown rsyncd[932]: rsync: mkstemp "/Shares/.0405.PVKnPM" (in redMon) failed: Read-only file system (30)

Any help would be greatly appreciated!!
Avatar of noci
noci

Did anything happen to the /Shares filesystem?
is it still in tact?

Appearantly the filesystem is write protected, that can be fixed question is how did it become Read/Only
there is a mechanism that allows you to keep a disk online but  read-only after errors.
In that case you need to verify the filesystem first.

Please do an readonly check of the file system.
for ext2,3,4:    fsck.extX -n /dev/...         # use 2,3 or 4 on X
for xfs:           xfs_check /dev/...

(xfs has a separate repair utility).
If all is well you can try:
mount -o remount,rw /dev/... /Shares

(Assuming the mount FS is /Shares, and not a symbolic link to the real fs.)
I rather think the Windows server is not reachable over the LAN, or its IP address has changed or its drive is no longer shared correctly.
What are the IP addresses of the Windows 2003 and the Ubuntu systems?
Avatar of jparker81

ASKER

The IP address for the Linux server is 10.0.0.14 the WIndows server is 10.0.0.22
The /Shares file system is on the Windows 2003 server.
So on 10.0.0.14/brown? you get an rsync request (from 10.0.0.22) to write to the /Shares path?

Does the user that logs on have write access to the share?
Obviously there is no write access on the /Shares path.

can you supply the output of:
mount
Output of mount. User generated image
BTW the backups are be written to stor/md1 and stor/md2

Thanks!
Does a /Shares exist somehow on that system?

Is the rsyncd using the right directory (/stor/md1 & /stor/md2)?  It looks lik it tries /Shares maybe ./Shares was meant?
Plase verify the rsync command on the other system...?
/Shares is on the windows server.
I understand, but it looks like there is a symlink (or other directory /Shares) on the Ubuntu, the the error is that Content of /Shares can not be written...

Sep 26 14:10:52 brown rsyncd[932]: rsync: readlink_stat("/Shares/Temp" (in redMon)) failed: Input/output error (5)
Sep 26 14:10:52 brown rsyncd[932]: rsync: failed to set times on "/Shares/." (in redMon): Read-only file system (30)
Sep 26 14:10:52 brown rsyncd[932]: rsync: failed to set times on "/Shares/ACH" (in redMon): Read-only file system (30)
Sep 26 14:10:52 brown rsyncd[932]: rsync: recv_generator: failed to stat "/Shares/ACH/ALAMON0074" (in redMon): Input/output error (5)

So there is some directory, which is unwriteable (ownership...)
if the rsynd runs in a chroot environment then /Shares is relative to that root).

the only filesystem that can becom read-only is your / filesystem after there are errors.
But the information doesn't add up.
Can you give the command line for the rsyncd  (ubuntu) and the rsync command (Windows)?
Okay on the windows server rsync is running via DeltaCopy. The target server is brown. Don't know it this helps but it seems to be able to connect to the brown server.
Here is the command used to invoke rsync from the windows server as well as the output.  OutputFromWindowsSideRsync.txt
The problem is at the Windows side: the process on the Windows server executing rsync.exe has no (more) write access rights on the "d:\Shares" directory. Check the permissions on the Windows side.
SOLUTION
Avatar of noci
noci

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
@noci: you are right. Sorry. I was confused by the fact I didn't see any "/Share" directory in the output of the mounted systems of the Ubuntu side. After reading better the logs, I see the problem is at the other side.
@noci: Since you speak about certificates, I suppose rsync in this case uses ssh for connecting to the remote machine.

I see that the Windows machine has Cygwin installed. I would like to know the output of the command, issued from the bash command line on Windows:

ssh brown@10.0.0.14 cat /etc/rsyncd.conf

Open in new window

Certificates might not be necessary when using modules. It depends on the module definition...
I rather forgot to remove that detail before stating my question.
Modules also do chroot to the file system that is mentioned in the profile of that module.
So all references are local to that module.
No user spec?,==> so no authentication needed.

Did only that rsync fail, or are the other weekdays failing too?
does the rsync to redThu still fail?

what does ls -la /stor/md1/redThu
tell?
Note there are several questions below..

AFAICT, the /stor/md1 was readonly at the moment this went wrong.
The error message are reliable in that respect.

I can reproduce the exact messages when mounting a readonly disk and use that as target
(esp when this is not the first update).

Timestamp updates fail with IO error, file write fail with Filesystem Readonly.
The stor/md1 stor/md2 do they get exchanged / remounted ?
Did only that rsync fail, or are the other weekdays failing too?
does the rsync to redThu still fail?
I rebooted the machine and recieved an error: "Ureadahead error main process terminated stat 4 (1194 & 1208)

Then I pressed alt + F2 continued with boot. Attempted to run rysnc again and voila it worked? Do you think this was related to the Ureadahead error?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial