Re: [sisuite-users] Imaging issues with RH ES 4
Yes I have removed the /selinux/* from the image however I'm waiting for some new machines to try again. I agree that adding the patterns would be the fast solution.Of course the best solution would be to have mount/mtab show all mounts ... I could open a ticket with RH however I'm not sure I would get too far. Andrea Righi <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 2007/02/22 04:17 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To [EMAIL PROTECTED] cc sisuite-dev , sisuite-users@lists.sourceforge.net Subject Re: [sisuite-users] Imaging issues with RH ES 4 [EMAIL PROTECTED] wrote: > > Andrea, > > Find below the autoinstallscript.conf. > > What appears to have happended is that /selinux was imaged and then > propagated to the > new machine. By removing /selinux files, creating /.autorelabel and > rebooting /selinux was > properly mounted and 'fixfiles relabel' was run. Hi all, I think that we should add some common unwanted patters to the exclusions automatically made by systemimager during image retrieval by si_getimage. In some recent distributions some pseudo-filesystem are not reported with mount. On the other looking in /proc/mounts doesn't resolve, because there are also the filesystems mounted *under* others (usually rootfs, initramfs, etc). Here is a list of patterns that we could always exclude: # selinux stuff /selinux/* # eventfs in SuSE /lib/klibc/events/* # mounted media devices not reported by mount /media/* # NFS stuff /var/lib/nfs/* # LVM caches and backups (automatically re-created at the first boot) /etc/lvm/.cache /etc/lvm/backup/* /etc/lvm/archive/* What do you think? Do you know other patterns that should be automatically excluded? Regards, -Andrea PS for David: have you tried to remove /selinux/* from your image and try to repeat the installation? this is equivalent to run si_getimage with --exclude '/selinux/*'. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging issues with RH ES 4
[EMAIL PROTECTED] wrote: > > Andrea, > > Find below the autoinstallscript.conf. > > What appears to have happended is that /selinux was imaged and then > propagated to the > new machine. By removing /selinux files, creating /.autorelabel and > rebooting /selinux was > properly mounted and 'fixfiles relabel' was run. Hi all, I think that we should add some common unwanted patters to the exclusions automatically made by systemimager during image retrieval by si_getimage. In some recent distributions some pseudo-filesystem are not reported with mount. On the other looking in /proc/mounts doesn't resolve, because there are also the filesystems mounted *under* others (usually rootfs, initramfs, etc). Here is a list of patterns that we could always exclude: # selinux stuff /selinux/* # eventfs in SuSE /lib/klibc/events/* # mounted media devices not reported by mount /media/* # NFS stuff /var/lib/nfs/* # LVM caches and backups (automatically re-created at the first boot) /etc/lvm/.cache /etc/lvm/backup/* /etc/lvm/archive/* What do you think? Do you know other patterns that should be automatically excluded? Regards, -Andrea PS for David: have you tried to remove /selinux/* from your image and try to repeat the installation? this is equivalent to run si_getimage with --exclude '/selinux/*'. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging issues with RH ES 4
Andrea,
Find below the autoinstallscript.conf.
What appears to have happended is that /selinux was imaged and then
propagated to the
new machine. By removing /selinux files, creating /.autorelabel and
rebooting /selinux was
properly mounted and 'fixfiles relabel' was run.
As you can see below /selinux(selinuxfs) is not shown. The mount command
RHEL4 does
not show selinux however /proc/mounts does. rc.sysinit determines if
selinuxfs is mounted
as : selinuxfs=`awk '/ selinuxfs / { print $2 }' /proc/mounts` . I
checked si_prepareclient and
mount is used and not /proc/mounts. What is the best solution ?
- mount returns :
[EMAIL PROTECTED] etc]# which mount
/bin/mount
[EMAIL PROTECTED] etc]# /bin/mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/cciss/c0d0p1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[EMAIL PROTECTED] etc]#
- cat /proc/mounts returns :
[EMAIL PROTECTED] etc]# cat /proc/mounts
rootfs / rootfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
none /dev tmpfs rw 0 0
/dev/root / ext3 rw 0 0
none /dev tmpfs rw 0 0
none /selinux selinuxfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
/sys /sys sysfs rw 0 0
none /dev/pts devpts rw 0 0
/dev/cciss/c0d0p1 /boot ext3 rw 0 0
none /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED]
Andrea Righi <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2007/02/19 14:48
Please respond to
[EMAIL PROTECTED]; Please respond to
sisuite-users@lists.sourceforge.net
To
sisuite-users@lists.sourceforge.net
cc
Subject
Re: [sisuite-users] Imaging issues with RH ES 4
[EMAIL PROTECTED] wrote:
>
> Using UYOK and 3.7.6 I successfully imaged and loaded a RHES 4
> machine(DL380G4) without any major
> issues. I did however run into pronlems when subsequently attemping to
> install an rpm(see below for
> error). I tracked the error to a getxattr call for security.selinux.
> Disabling selinux avoids the problem
> but doesn't correct it. I'm now guessing but does the fact that I imaged
> and loaded the system
> from a systemimager server running on RHES 3 without user_xattr on the
> filesystem have
> something to do with it ? Anyone else run into this ? Can I "fix" my
> imaged system somehow ?
Are your filesystems mounted with user_xattr (or xattr) after the
imaging? what's the output of a simple "mount"? could you post also your
autoinstallscript.conf?
Regards,
-Andrea
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging issues with RH ES 4
[EMAIL PROTECTED] wrote: > > Using UYOK and 3.7.6 I successfully imaged and loaded a RHES 4 > machine(DL380G4) without any major > issues. I did however run into pronlems when subsequently attemping to > install an rpm(see below for > error). I tracked the error to a getxattr call for security.selinux. > Disabling selinux avoids the problem > but doesn't correct it. I'm now guessing but does the fact that I imaged > and loaded the system > from a systemimager server running on RHES 3 without user_xattr on the > filesystem have > something to do with it ? Anyone else run into this ? Can I "fix" my > imaged system somehow ? Are your filesystems mounted with user_xattr (or xattr) after the imaging? what's the output of a simple "mount"? could you post also your autoinstallscript.conf? Regards, -Andrea - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Imaging issues with RH ES 4
Using UYOK and 3.7.6 I successfully imaged and loaded a RHES 4 machine(DL380G4) without any major issues. I did however run into pronlems when subsequently attemping to install an rpm(see below for error). I tracked the error to a getxattr call for security.selinux. Disabling selinux avoids the problem but doesn't correct it. I'm now guessing but does the fact that I imaged and loaded the system from a systemimager server running on RHES 3 without user_xattr on the filesystem have something to do with it ? Anyone else run into this ? Can I "fix" my imaged system somehow ? [EMAIL PROTECTED] nx]# rpm -ivh nxclient-2.1.0-11.i386.rpm Preparing...### [100%] error: %pre(nxclient-2.1.0-11.i386) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping nxclient-2.1.0-11 [EMAIL PROTECTED] nx]# David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
