stateless problems

Peter Schobel pschobel at porchlight.ca
Tue Nov 23 17:33:40 UTC 2004


that worked,

it seems to not be getting the rsync path

[root at store-lan1-141 stateless]# ./stateless-bootstrap.py -r
/reserve-root -b /reserve-boot
relabelling /dev/hda3 to "RESERVE_ROOT"
relabelling /dev/hda5 to "RESERVE_BOOT"
Mounting /dev/hda3 at /tmp/tmpc4x1Vg/reserve_root (type ext3)
Could not determine client snapshot information for active root
partition
Could not determine client snapshot information for reserve root
partition
Mounting /dev/hda5 at /tmp/tmpc4x1Vg/reserve_boot (type ext3)
Could not determine client snapshot information for active boot
partition
Could not determine client snapshot information for reserve boot
partition
Provisioning data from server:(config "pinab", protocol "None", snapshot
"pinab-1")
Getting (config "pinab", protocol "None", snapshot "pinab-1") to device
/dev/hda3
rsync url:"rsync://NoneNone/pinab/pinab-1/"
excluding /boot
rsync finished
role finished
                                          (  0%) [Error              ]

i used the stateless-server command to add the server to my ldap tree
with the rsync path /srv/stateless/snapshots

i'm assuming that the server entry in ldap should have the same name as
LDAP_SERVER in /etc/sysconfig/stateless

am i doing this correctly?

Peter Schobel
~

On Tue, 2004-11-23 at 02:57, Mark McLoughlin wrote:
> On Mon, 2004-11-22 at 19:43 -0500, Peter Schobel wrote:
> > i tried changing line 304 in replicator.py to 
> > 
> > devices = ['/dev/hda1', '/dev/hda2', '/dev/hda3', '/dev/hda5'] # FIXME
> > 
> > and now i am just getting 
> > 
> > [root at store-lan1-141 stateless]# ./stateless-bootstrap.py -r
> > /reserve-root -b /reserve-boot
> >                                           (  0%) [Error              ]
> > 
> 
> 	Try changing:
> 
> def debug_print(msg):
>     pass
> 
> 	to
> 
> def debug_print(msg):
>     print msg
> 
> 	in replicator.py and passing --debug to stateless-bootstrap.py and see
> what that tells you.
> 
> Cheers,
> Mark.
> 





More information about the fedora-devel-list mailing list