HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   HOWTO-Related Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=2)
-   -   Systemimager (rsync) doesn't copy all (http://www.howtoforge.com/forums/showthread.php?t=6456)

comedit 26th August 2006 01:55

Systemimager (rsync) doesn't copy all
 
I have generated a systemimage just before i tested something.

I need to restore the old situation and discovered that my /proc/ files were not put in the image.

Not to worry i thought just rsync that part and you should be ok

But no rsync gives errors on /poc/ files (see below).

So I thought gunzip (through winscp) the lot and transfer to the image

wrong again same problem


any suggetions ?


output from:

rsync -avz -e ssh user@192.168.100.20:/proc/ /proc/

Quote:

rsync: recv_generator: mkdir "/proc/1084" failed: No such file or directory (2)
rsync: stat "/proc/1084" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1084/fd" failed: No such file or directory (2)
rsync: stat "/proc/1084/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1094" failed: No such file or directory (2)
rsync: stat "/proc/1094" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1094/fd" failed: No such file or directory (2)
rsync: stat "/proc/1094/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1098" failed: No such file or directory (2)
rsync: stat "/proc/1098" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1098/fd" failed: No such file or directory (2)
rsync: stat "/proc/1098/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1103" failed: No such file or directory (2)
rsync: stat "/proc/1103" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1103/fd" failed: No such file or directory (2)
rsync: stat "/proc/1103/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1107" failed: No such file or directory (2)
rsync: stat "/proc/1107" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1107/fd" failed: No such file or directory (2)
rsync: stat "/proc/1107/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1117" failed: No such file or directory (2)
rsync: stat "/proc/1117" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1117/fd" failed: No such file or directory (2)
..

...


rsync: stat "/proc/1679/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1680" failed: No such file or directory (2)
rsync: stat "/proc/1680" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1680/fd" failed: No such file or directory (2)
rsync: stat "/proc/1680/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1684" failed: No such file or directory (2)
rsync: stat "/proc/1684" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1684/fd" failed: No such file or directory (2)
rsync: stat "/proc/1684/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1692" failed: No such file or directory (2)
rsync: stat "/proc/1692" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1692/fd" failed: No such file or directory (2)
rsync: stat "/proc/1692/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1700" failed: No such file or directory (2)
rsync: stat "/proc/1700" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1700/fd" failed: No such file or directory (2)
rsync: stat "/proc/1700/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1701" failed: No such file or directory (2)
rsync: stat "/proc/1701" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1701/fd" failed: No such file or directory (2)
rsync: stat "/proc/1701/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1702" failed: No such file or directory (2)
rsync: stat "/proc/1702" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1702/fd" failed: No such file or directory (2)
rsync: stat "/proc/1702/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1703" failed: No such file or directory (2)
rsync: stat "/proc/1703" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1703/fd" failed: No such file or directory (2)
rsync: stat "/proc/1703/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1704" failed: No such file or directory (2)
rsync: stat "/proc/1704" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1704/fd" failed: No such file or directory (2)
rsync: stat "/proc/1704/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1705" failed: No such file or directory (2)
rsync: stat "/proc/1705" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1705/fd" failed: No such file or directory (2)
rsync: stat "/proc/1705/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1706" failed: No such file or directory (2)
rsync: stat "/proc/1706" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1706/fd" failed: No such file or directory (2)
rsync: stat "/proc/1706/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1798" failed: No such file or directory (2)
rsync: stat "/proc/1798" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1798/fd" failed: No such file or directory (2)
rsync: stat "/proc/1798/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1800" failed: No such file or directory (2)
rsync: stat "/proc/1800" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1800/fd" failed: No such file or directory (2)
rsync: stat "/proc/1800/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1804" failed: No such file or directory (2)
rsync: stat "/proc/1804" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1804/fd" failed: No such file or directory (2)
rsync: stat "/proc/1804/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1814" failed: No such file or directory (2)
rsync: stat "/proc/1814" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1814/fd" failed: No such file or directory (2)
rsync: stat "/proc/1814/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1815" failed: No such file or directory (2)
rsync: stat "/proc/1815" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1815/fd" failed: No such file or directory (2)
rsync: stat "/proc/1815/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1817" failed: No such file or directory (2)
rsync: stat "/proc/1817" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1817/fd" failed: No such file or directory (2)
rsync: stat "/proc/1817/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1819" failed: No such file or directory (2)
rsync: stat "/proc/1819" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1819/fd" failed: No such file or directory (2)
rsync: stat "/proc/1819/fd" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1820" failed: No such file or directory (2)
rsync: stat "/proc/1820" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/1820/fd" failed: No such file or directory (2)
rsync: stat "/proc/1820/fd" failed: No such file or directory (2)
rsync: failed to set times on "/proc/2": Operation not permitted (1)
rsync: failed to set times on "/proc/3": Operation not permitted (1)
rsync: failed to set times on "/proc/4": Operation not permitted (1)
rsync: recv_generator: mkdir "/proc/467" failed: No such file or directory (2)
rsync: stat "/proc/467" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/467/fd" failed: No such file or directory (2)
rsync: stat "/proc/467/fd" failed: No such file or directory (2)
rsync: failed to set times on "/proc/5": Operation not permitted (1)
rsync: failed to set times on "/proc/6": Operation not permitted (1)
rsync: failed to set times on "/proc/99": Operation not permitted (1)
rsync: recv_generator: mkdir "/proc/driver/emu10k1" failed: No such file or directory (2)
rsync: stat "/proc/driver/emu10k1" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/driver/emu10k1/00:0a.0" failed: No such file or directory (2)
rsync: stat "/proc/driver/emu10k1/00:0a.0" failed: No such file or directory (2)
rsync: recv_generator: mkdir "/proc/ide/ide0/hdb" failed: No such file or directory (2)
rsync: stat "/proc/ide/ide0/hdb" failed: No such file or directory (2)

sent 129720 bytes received 80979 bytes 28093.20 bytes/sec
total size is 134212469 speedup is 636.99
rsync error: some files could not be transferred (code 23) at main.c(1166)

falko 27th August 2006 16:35

You don't need to back up the /proc files. They are created by the system on the fly. So when you restore your system from your image, everything should be fine even without the /proc files. :)

comedit 27th August 2006 21:35

thanks
 
Thanks Falco,

That explains a lot ..

The thing is that once the masterscript it loaded these problems come up.

So the system does not restore itself because the script "hangs".

I wil have a look in the restore masterscript which belongs to this image to see if I can detect what could be altererd (in this scipt or the image).

comedit 28th August 2006 09:30

This is what happens
 
..... (up till hear it all works fine it finds the masterscript on the imageserver and gets it)
....

I will now run the autoinstallscript : /scripts/backupserver.master

get arch
DisKorder=sd,cciss,ida,rd,hd
Logmsg: no such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory

logmsg: No such file or directory
logmsg: No such file or directory
Error: Could not stat device /dev/hda/ - No such file or directory.
logmsg: No such file or directory
Error: Could not stat device /dev/hda/ - No such file or directory.
logmsg: No such file or directory
Killing off all running processes.
killall: udp-receiver: no process killed

Write_variables

... Then a message follows that it did not succeed bla bla


FYI: this backupserver is software wise allmost similar to my webserver. It is debian sarge with ispconfig 2.2.6.

I first made an image before I installed Mysql 5.0.24 ( a package which I wanted to test needed mysql 4.2 or above). Mysql 5 is installed but not working because of dependencies.

So the machine still starts up but mysql is just not working ( and maybe there are some other problems I am not aware of)
I will install the dependencies to see what happens then.

Or somebody might have other sugggetions.

Allthough I do wan't Systemimager to work since I think that's just Ideal !! (if it works)

comedit 28th August 2006 14:26

Ooops what a web of problems
 
One dependency leads to antother etcetera,

I am entangled in multiple problems here;

I just need to get my old system back ! :(


Anybody any suggestions how I can still restore my system. (all is still accessable though. Replacing only the var usr an etc directories with the old ones is not enough i experienced myself ) I identified these directories in the tar of msql-server 5)

For your info: I used the downloadable image from falko's site (see the how to create an image ... with systemimager) for the diskette and added the local.cfg

Thanks in advance

falko 29th August 2006 19:03

Quote:

Originally Posted by comedit
I will now run the autoinstallscript : /scripts/backupserver.master

Why do you want to run the master script? All you have to do is to insert the autoinstall diskette into the system that you want to restore...

comedit 29th August 2006 23:55

That' s what I have done
 
Quote:

Why do you want to run the master script? All you have to do is to insert the autoinstall diskette into the system that you want to restore...
Falko that is what I have done:

I reboot with the auto installdiskette

The message
Quote:

I will now run the autoinstallscript : /scripts/backupserver.master
Is a message during the install (from the autoinstalldiskette)

so the auto install starts the script and the comes up with:
Quote:

get arch
DisKorder=sd,cciss,ida,rd,hd
Logmsg: no such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
cat: /proc/diskstats: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory
logmsg: No such file or directory

logmsg: No such file or directory
logmsg: No such file or directory
Error: Could not stat device /dev/hda/ - No such file or directory.
logmsg: No such file or directory
Error: Could not stat device /dev/hda/ - No such file or directory.
logmsg: No such file or directory
Killing off all running processes.
killall: udp-receiver: no process killed

Write_variables

... Then a message follows that it did not succeed bla bla


I might misunderstand you but it is exactly what I have done:

reboot with the autoinstalldiskette: and that gives the errors

falko 30th August 2006 16:39

Hm... Did you follow the SystemImager tutorial as close as possible?
Which distribution do you use?

comedit 31st August 2006 14:10

Yes i did
 
Falko

If I remember well I followed it to the letter.

The only thing I did have a problem with is that it would not work in the beginning.

I read the forums,and found out that somebody solved it (also on debian sarge 3.1) by installing both the server and the client software on both the machines.

I did the same and it solved the problem.

The preparation of the client seemed to go fluenlty, allthough i think rsync did give a problem on some files.

I am sorry I dont know it accurately because all is about one month ago

Is there a certain logfile you know off I could still check in ?

falko 1st September 2006 16:52

Quote:

Originally Posted by comedit
Is there a certain logfile you know off I could still check in ?

I'm not sure. I'd check all logs in /var/log.


All times are GMT +2. The time now is 22:00.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.