From rriley at procuri.com Tue Apr 3 03:47:54 2007 From: rriley at procuri.com (Richard Riley) Date: Mon, 2 Apr 2007 23:47:54 -0400 Subject: sshd time in /var/log/secure Message-ID: It appears that since I updated my machines with the new tzdata, ssh logins are logged with two entries in the /var/log/secure file. One appears to be UTC while the other is correct local time. This is consistent with both RHEL ES3 and ES4. I have applied subsequent tzdata and openssh updates and rebooted the machines and still get the double entries. I can find no instances in any other log files. Mar 6 16:11:08 admin4 sshd[16822]: Accepted password for rriley from ::ffff:172.29.1.193 port 1557 ssh2 Mar 6 11:11:08 admin4 sshd[16821]: Accepted password for rriley from ::ffff:172.29.1.193 port 1557 ssh2 Mar 6 17:12:15 admin4 sshd[21665]: Accepted password for rriley from ::ffff:172.29.1.196 port 4418 ssh2 Mar 6 12:12:15 admin4 sshd[21664]: Accepted password for rriley from ::ffff:172.29.1.196 port 4418 ssh2 Apr 3 03:24:42 admin4 sshd[12422]: Accepted password for rriley from 172.30.3.131 port 3502 ssh2 Apr 2 23:24:42 admin4 sshd[12421]: Accepted password for rriley from 172.30.3.131 port 3502 ssh2 Richard Riley IT System Administrator From RichardM at nashuamobile.com Tue Apr 3 14:38:45 2007 From: RichardM at nashuamobile.com (Richard Mayhew) Date: Tue, 3 Apr 2007 16:38:45 +0200 Subject: sshd time in /var/log/secure In-Reply-To: References: Message-ID: <74E2EBF294D9C4448F323258E685C41F0BF532@matrix.nashuamobile.com> _________________________________________________________________ Nashua Mobile (PTY) LTD Electronic Mail Notice: Click Here or send an email to emailnotice at nashuamobile.com _________________________________________________________________ Hi, I can back you up on that, I'm receiving the same double entries in my secure log file on each SSHD login. Regards Richard -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Richard Riley Sent: 03 April 2007 05:48 AM To: redhat-sysadmin-list at redhat.com Subject: sshd time in /var/log/secure It appears that since I updated my machines with the new tzdata, ssh logins are logged with two entries in the /var/log/secure file. One appears to be UTC while the other is correct local time. This is consistent with both RHEL ES3 and ES4. I have applied subsequent tzdata and openssh updates and rebooted the machines and still get the double entries. I can find no instances in any other log files. Mar 6 16:11:08 admin4 sshd[16822]: Accepted password for rriley from ::ffff:172.29.1.193 port 1557 ssh2 Mar 6 11:11:08 admin4 sshd[16821]: Accepted password for rriley from ::ffff:172.29.1.193 port 1557 ssh2 Mar 6 17:12:15 admin4 sshd[21665]: Accepted password for rriley from ::ffff:172.29.1.196 port 4418 ssh2 Mar 6 12:12:15 admin4 sshd[21664]: Accepted password for rriley from ::ffff:172.29.1.196 port 4418 ssh2 Apr 3 03:24:42 admin4 sshd[12422]: Accepted password for rriley from 172.30.3.131 port 3502 ssh2 Apr 2 23:24:42 admin4 sshd[12421]: Accepted password for rriley from 172.30.3.131 port 3502 ssh2 Richard Riley IT System Administrator -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From pool at utilika.org Tue Apr 3 17:44:28 2007 From: pool at utilika.org (Jonathan Pool) Date: Tue, 3 Apr 2007 10:44:28 -0700 (PDT) Subject: sshd time in /var/log/secure In-Reply-To: <74E2EBF294D9C4448F323258E685C41F0BF532@matrix.nashuamobile.com> References: <74E2EBF294D9C4448F323258E685C41F0BF532@matrix.nashuamobile.com> Message-ID: <49185.192.168.1.2.1175622268.squirrel@utilika.org> My system is up to date, but /var/log/secure entries are not exhibiting this duplication problem. From rriley at procuri.com Wed Apr 4 22:40:47 2007 From: rriley at procuri.com (Richard Riley) Date: Wed, 4 Apr 2007 18:40:47 -0400 Subject: tar failure Message-ID: I have a nightly backup process that uses tar writing the output to a file on an NFS mount. It had been working fine for weeks and suddenly on Tuesday started failing with error code of 141. Anyone know where I can find out what the error code means. I have tried a google search and looking at tar source code, both to no avail. I have another machine running the exact same script also writing to NFS mount and is experiencing no problems. The machine that has started failing is RHEL 3. The second machine is running RHEL 4 and the NFS server is running RHEL 4. They are manually kept up to date using up2date command. Here is the script. day=`date +%a` if [ "$day" == "Sun" ] then STAMP="Wk`date +%U`-$day`date +%m%d%H%M`" else STAMP="$day`date +%m%d%H%M`" fi logfile=/var/log/db-bkup/bkuplog-$STAMP db_bkup_file=$bkup_hold_dir/`hostname`-db_bkup-$STAMP.tar.gz # Stop mysql process to start backup, force flush to disk /sbin/service mysql stop echo "backup started at `date`" >$logfile cd /home/ # backup /var/lib/mysql to $db-bkup-file directory tar -czv --ignore-failed-read --totals mysql >$db_bkup_file 2>>$logfile CODE=$? if [ $CODE == 0 ] then echo "backup completed at `date`" >>$logfile else echo "Backup failed at `date` with error code ($CODE)" >>$logfile fi # Start mysql service again, will resync with master at this point /sbin/service mysql start The tar command is failing in the exact same place every time, regardless of when run from cron or kicked off manually. I know this by the logfile which shows a list of all the files written. It appears to be part way through a directory. If I run tar on that directory alone, it completes fine. I can find no other error indicators. Richard Riley System Administrator Procuri Inc. www.procuri.com \ From redhat at ryansimpkins.com Thu Apr 5 01:56:31 2007 From: redhat at ryansimpkins.com (Ryan Simpkins) Date: Wed, 4 Apr 2007 19:56:31 -0600 (MDT) Subject: tar failure In-Reply-To: References: Message-ID: <2984.67.172.244.9.1175738191.squirrel@io.ryansimpkins.com> On Wed, April 4, 2007 16:40, Richard Riley wrote: > I have a nightly backup process that uses tar writing the output to a > file on an NFS mount. It had been working fine for weeks and suddenly > on Tuesday started failing with error code of 141. Anyone know where I > can find out what the error code means. I have tried a google search > and looking at tar source code, both to no avail. SIGPIPE 13 Write on a pipe with no reader, Broken pipe (POSIX) -Ryan From rriley at procuri.com Thu Apr 5 03:40:44 2007 From: rriley at procuri.com (Richard Riley) Date: Wed, 4 Apr 2007 23:40:44 -0400 Subject: tar failure In-Reply-To: <2984.67.172.244.9.1175738191.squirrel@io.ryansimpkins.com> References: <2984.67.172.244.9.1175738191.squirrel@io.ryansimpkins.com> Message-ID: OK. I have finally found an error message I understand, but still don't understand why or how to fix. When I ran the tar command manually (as root) insuring an output file size larger than 2GB, I actually got an error message of "File size limit exceeded". My confusion is when I run "ulimit -a" it shows file size "unlimited". When I run this command on the NFS server I am writing the file to it also shows "unlimited". I checked the ulimit.conf file in /etc/security and it also shows file size is set to "unlimited". What is more confusing is this had been working fine for multiple weeks creating a file over 4.5GB in size. The only thing that has caused any changes on either machine is running "up2date -u", but I did not notice anything that I thought could relate to a file size restriction. Also, I still have another machine writing files to the NFS server of over 7.5GB. Again, DB machine with problem - RHEL 4 - kernel 2.6.9 release 34.0.1 NFS machine - RHEL 4 - kernel 2.6.9 release 42.0.8 Other DB machine - RHEL 4 - kernel 2.6.9 release 34.0.2 Richard ------------------------------------------------------------------------ ---- Any chance your output file is hitting 2Gb or some other magical file size? Bill Watson bill at magicdigits.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ryan Simpkins Sent: Wednesday, April 04, 2007 9:57 PM To: redhat-sysadmin-list at redhat.com Subject: Re: tar failure On Wed, April 4, 2007 16:40, Richard Riley wrote: > I have a nightly backup process that uses tar writing the output to a > file on an NFS mount. It had been working fine for weeks and suddenly > on Tuesday started failing with error code of 141. Anyone know where I > can find out what the error code means. I have tried a google search > and looking at tar source code, both to no avail. SIGPIPE 13 Write on a pipe with no reader, Broken pipe (POSIX) -Ryan -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From Neill.Flynn at itg.com Thu Apr 5 09:00:34 2007 From: Neill.Flynn at itg.com (Flynn, Neill) Date: Thu, 5 Apr 2007 10:00:34 +0100 Subject: tar failure In-Reply-To: Message-ID: Hi Bill, In your script you call the tar command as follows: tar -czv --ignore-failed-read --totals mysql >$db_bkup_file 2>>$logfile CODE=$? Maybe you should specify the absolute path to tar, that way you can be sure which version of tar is being used. Neill -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Richard Riley Sent: 05 April 2007 04:41 To: bill at magicdigits.com; redhat-sysadmin-list at redhat.com Subject: RE: tar failure OK. I have finally found an error message I understand, but still don't understand why or how to fix. When I ran the tar command manually (as root) insuring an output file size larger than 2GB, I actually got an error message of "File size limit exceeded". My confusion is when I run "ulimit -a" it shows file size "unlimited". When I run this command on the NFS server I am writing the file to it also shows "unlimited". I checked the ulimit.conf file in /etc/security and it also shows file size is set to "unlimited". What is more confusing is this had been working fine for multiple weeks creating a file over 4.5GB in size. The only thing that has caused any changes on either machine is running "up2date -u", but I did not notice anything that I thought could relate to a file size restriction. Also, I still have another machine writing files to the NFS server of over 7.5GB. Again, DB machine with problem - RHEL 4 - kernel 2.6.9 release 34.0.1 NFS machine - RHEL 4 - kernel 2.6.9 release 42.0.8 Other DB machine - RHEL 4 - kernel 2.6.9 release 34.0.2 Richard ------------------------------------------------------------------------ ---- Any chance your output file is hitting 2Gb or some other magical file size? Bill Watson bill at magicdigits.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ryan Simpkins Sent: Wednesday, April 04, 2007 9:57 PM To: redhat-sysadmin-list at redhat.com Subject: Re: tar failure On Wed, April 4, 2007 16:40, Richard Riley wrote: > I have a nightly backup process that uses tar writing the output to a > file on an NFS mount. It had been working fine for weeks and suddenly > on Tuesday started failing with error code of 141. Anyone know where I > can find out what the error code means. I have tried a google search > and looking at tar source code, both to no avail. SIGPIPE 13 Write on a pipe with no reader, Broken pipe (POSIX) -Ryan -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- This message is for the named person's use only. This communication is for informational purposes only and has been obtained from sources believed to be reliable, but it is not necessarily complete and its accuracy cannot be guaranteed. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. Moreover, this material should not be construed to contain any recommendation regarding, or opinion concerning, any security. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Securities products and services provided to Canadian investors are offered by ITG Canada Corp. (member CIPF and IDA), an affiliate of Investment Technology Group, Inc. ITG Inc. and/or its affiliates reserves the right to monitor and archive all electronic communications through its network. ITG Inc. Member NASD, SIPC -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- From stellr at cns.vt.edu Thu Apr 5 12:37:28 2007 From: stellr at cns.vt.edu (Ray Stell) Date: Thu, 5 Apr 2007 08:37:28 -0400 Subject: tar failure In-Reply-To: References: <2984.67.172.244.9.1175738191.squirrel@io.ryansimpkins.com> Message-ID: <20070405123728.GC12167@cns.vt.edu> On Wed, Apr 04, 2007 at 11:40:44PM -0400, Richard Riley wrote: > OK. I have finally found an error message I understand, but still don't > understand why or how to fix. > > When I ran the tar command manually (as root) insuring an output file > size larger than 2GB, I actually got an error message of "File size > limit exceeded". use gtar http://www.gnu.org/software/tar/ From dave.cunningham at lmco.com Tue Apr 10 16:10:04 2007 From: dave.cunningham at lmco.com (Cunningham, Dave) Date: Tue, 10 Apr 2007 09:10:04 -0700 Subject: nis cacheing problem ? Message-ID: <3D92CA467E530B4E8295214868F840FE0A31855E@emss01m12.us.lmco.com> Had a situation today on a RHEL ES 4 U3 system that is running as a NIS master. A user defined in NIS, and not in the local passwd file, changed password. The change was reflected the the passwd map as seen with "ypcat passwd | grep username", but login to the system still required his "old" password. To my surprise, "ypmatch username passwd" returned a record with the old password hash... ie, it was different that what was returned by ypcat. This situation persisted overnight. A ypserv restart corrected the problem. My first though was nscd, but I notice that it isn't running (not configured to start...). This leads to two questions. 1. Any advice or experience that bears on the mismatch between ypcat and ypmatch ? 2. What are the tradeoffs for running or not running nscd on this release ? Thanks, Dave Dave Cunningham Computing and Network Services (408) 756-1382 Office, (408) 660-7979 Cell dave.cunningham at lmco.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgalgoci at redhat.com Tue Apr 10 16:22:40 2007 From: mgalgoci at redhat.com (Matthew Galgoci) Date: Tue, 10 Apr 2007 12:22:40 -0400 Subject: nis cacheing problem ? In-Reply-To: <3D92CA467E530B4E8295214868F840FE0A31855E@emss01m12.us.lmco.com> References: <3D92CA467E530B4E8295214868F840FE0A31855E@emss01m12.us.lmco.com> Message-ID: > Had a situation today on a RHEL ES 4 U3 system that is running as a NIS > master. A user defined in NIS, and not in the local passwd file, > changed password. The change was reflected the the passwd map as seen > with "ypcat passwd | grep username", but login to the system still > required his "old" password. To my surprise, "ypmatch username passwd" > returned a record with the old password hash... ie, it was different > that what was returned by ypcat. This situation persisted overnight. A > ypserv restart corrected the problem. > > My first though was nscd, but I notice that it isn't running (not > configured to start...). This leads to two questions. > > 1. Any advice or experience that bears on the mismatch between ypcat > and ypmatch ? > 2. What are the tradeoffs for running or not running nscd on this > release ? Depending on your environment you can probably run a couple hundred NIS clients without nscd and your NIS master wouldn't break a sweat. In my experience nscd only becomes critical when using nss_ldap (even with a small number of clients!!). If you must use nscd, take a hard look at tuning the /etc/nscd.conf paramaters that define caching sematics for name lookups. -- Matthew Galgoci GIS Production Operations Red Hat, Inc 919.754.3700 x44155 From susan at cdl.edu Tue Apr 10 17:01:57 2007 From: susan at cdl.edu (Susan Baur) Date: Tue, 10 Apr 2007 10:01:57 -0700 Subject: rhel5 problem creating virtual machine Message-ID: <6D9C39D6-5CED-43E3-B219-5E07C194C1AF@cdl.edu> I've just installed rhel 5 on a test box wit the virtualization kernel. I'd like to start exploring the virtualization that's part of rhel 5 but when I try to create a guest operating system I receive the following error. # xm create wg1 -c Using config file "/etc/xen/wg1". Error: destroyDevice() takes exactly 3 arguments (2 given) here are the non-comment lines from my wg1 config file kernel = "/boot/vmlinuz-2.6.18-8.1.1.el5xen" memory = 64 name = "WebGUI_1" vif = [ '' ] disk = [ 'phy:hda1,hda1,w' ] root = "/dev/hda1 ro" extra = "4" If I run it as a dryrun, i get the following # xm create wg1 -n Using config file "/etc/xen/wg1". (vm (name WebGUI_1) (memory 64) (vcpus 1) (image (linux (kernel /boot/vmlinuz-2.6.18-8.1.1.el5xen) (root '/dev/hda1 ro') (args 4) ) ) (device (vbd (uname phy:hda1) (dev hda1) (mode w))) (device (vif)) ) Any ideas on where to start? This is my first foray into Xen, so any help would be appreciated --Susan From clockwork at sigsys.org Tue Apr 10 19:41:15 2007 From: clockwork at sigsys.org (clockwork at sigsys.org) Date: Tue, 10 Apr 2007 15:41:15 -0400 Subject: rhel5 problem creating virtual machine In-Reply-To: <6D9C39D6-5CED-43E3-B219-5E07C194C1AF@cdl.edu> References: <6D9C39D6-5CED-43E3-B219-5E07C194C1AF@cdl.edu> Message-ID: <5849d9130704101241o6042f5d4yeda738aa96ac54e@mail.gmail.com> You might want to look into using virt-install, its a lot cleaner than using xm directly. Here are some notes to point you in the right direction: http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-f266d304d6d690475bf4ca21e643679700a86c08 On 4/10/07, Susan Baur wrote: > > I've just installed rhel 5 on a test box wit the virtualization > kernel. I'd like to start exploring the virtualization that's part of > rhel 5 but when I try to create a guest operating system I receive > the following error. > > # xm create wg1 -c > Using config file "/etc/xen/wg1". > Error: destroyDevice() takes exactly 3 arguments (2 given) > > here are the non-comment lines from my wg1 config file > kernel = "/boot/vmlinuz-2.6.18-8.1.1.el5xen" > memory = 64 > name = "WebGUI_1" > vif = [ '' ] > disk = [ 'phy:hda1,hda1,w' ] > root = "/dev/hda1 ro" > extra = "4" > > If I run it as a dryrun, i get the following > # xm create wg1 -n > Using config file "/etc/xen/wg1". > (vm > (name WebGUI_1) > (memory 64) > (vcpus 1) > (image > (linux > (kernel /boot/vmlinuz-2.6.18-8.1.1.el5xen) > (root '/dev/hda1 ro') > (args 4) > ) > ) > (device (vbd (uname phy:hda1) (dev hda1) (mode w))) > (device (vif)) > ) > > Any ideas on where to start? This is my first foray into Xen, so any > help would be appreciated > > --Susan > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From susan at cdl.edu Tue Apr 10 23:24:10 2007 From: susan at cdl.edu (Susan Baur) Date: Tue, 10 Apr 2007 16:24:10 -0700 Subject: rhel5 problem creating virtual machine In-Reply-To: <5849d9130704101241o6042f5d4yeda738aa96ac54e@mail.gmail.com> References: <6D9C39D6-5CED-43E3-B219-5E07C194C1AF@cdl.edu> <5849d9130704101241o6042f5d4yeda738aa96ac54e@mail.gmail.com> Message-ID: <4A88A0E4-85C5-48C1-BF53-753369EBBF57@cdl.edu> Thanks for the suggestion. Unfortunately, I was unable to get past the location option in virt-install. I'm fairly certain my xm problems lie in the config file, but I'm not finding a lot information out there. I've made some progress though by changing the kernel line and adding a ramdisk line. --Susan On Apr 10, 2007, at 12:41 PM, clockwork at sigsys.org wrote: > You might want to look into using virt-install, its a lot cleaner > than using xm directly. Here are some notes to point you in the > right direction: > > http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head- > f266d304d6d690475bf4ca21e643679700a86c08 > > > On 4/10/07, Susan Baur < susan at cdl.edu> wrote:I've just installed > rhel 5 on a test box wit the virtualization > kernel. I'd like to start exploring the virtualization that's part of > rhel 5 but when I try to create a guest operating system I receive > the following error. > > # xm create wg1 -c > Using config file "/etc/xen/wg1". > Error: destroyDevice() takes exactly 3 arguments (2 given) > > here are the non-comment lines from my wg1 config file > kernel = "/boot/vmlinuz-2.6.18-8.1.1.el5xen" > memory = 64 > name = "WebGUI_1" > vif = [ '' ] > disk = [ 'phy:hda1,hda1,w' ] > root = "/dev/hda1 ro" > extra = "4" > > If I run it as a dryrun, i get the following > # xm create wg1 -n > Using config file "/etc/xen/wg1". > (vm > (name WebGUI_1) > (memory 64) > (vcpus 1) > (image > (linux > (kernel /boot/vmlinuz-2.6.18-8.1.1.el5xen) > (root '/dev/hda1 ro') > (args 4) > ) > ) > (device (vbd (uname phy:hda1) (dev hda1) (mode w))) > (device (vif)) > ) > > Any ideas on where to start? This is my first foray into Xen, so any > help would be appreciated > > --Susan > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From clockwork at sigsys.org Wed Apr 11 02:34:58 2007 From: clockwork at sigsys.org (clockwork at sigsys.org) Date: Tue, 10 Apr 2007 22:34:58 -0400 Subject: rhel5 problem creating virtual machine In-Reply-To: <4A88A0E4-85C5-48C1-BF53-753369EBBF57@cdl.edu> References: <6D9C39D6-5CED-43E3-B219-5E07C194C1AF@cdl.edu> <5849d9130704101241o6042f5d4yeda738aa96ac54e@mail.gmail.com> <4A88A0E4-85C5-48C1-BF53-753369EBBF57@cdl.edu> Message-ID: <5849d9130704101934l234b7a46u32f6ee844cc2ba13@mail.gmail.com> Well the only real gotcha with virt-install is that the install data has to be accessible via nfs, ftp or http. You could post either the output/problem from virt-install or the xm config file. (or both). On 4/10/07, Susan Baur wrote: > > Thanks for the suggestion. Unfortunately, I was unable to get past > the location option in virt-install. I'm fairly certain my xm > problems lie in the config file, but I'm not finding a lot > information out there. I've made some progress though by changing the > kernel line and adding a ramdisk line. > > --Susan > > > On Apr 10, 2007, at 12:41 PM, clockwork at sigsys.org wrote: > > > You might want to look into using virt-install, its a lot cleaner > > than using xm directly. Here are some notes to point you in the > > right direction: > > > > http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head- > > f266d304d6d690475bf4ca21e643679700a86c08 > > > > > > On 4/10/07, Susan Baur < susan at cdl.edu> wrote:I've just installed > > rhel 5 on a test box wit the virtualization > > kernel. I'd like to start exploring the virtualization that's part of > > rhel 5 but when I try to create a guest operating system I receive > > the following error. > > > > # xm create wg1 -c > > Using config file "/etc/xen/wg1". > > Error: destroyDevice() takes exactly 3 arguments (2 given) > > > > here are the non-comment lines from my wg1 config file > > kernel = "/boot/vmlinuz-2.6.18-8.1.1.el5xen" > > memory = 64 > > name = "WebGUI_1" > > vif = [ '' ] > > disk = [ 'phy:hda1,hda1,w' ] > > root = "/dev/hda1 ro" > > extra = "4" > > > > If I run it as a dryrun, i get the following > > # xm create wg1 -n > > Using config file "/etc/xen/wg1". > > (vm > > (name WebGUI_1) > > (memory 64) > > (vcpus 1) > > (image > > (linux > > (kernel /boot/vmlinuz-2.6.18-8.1.1.el5xen) > > (root '/dev/hda1 ro') > > (args 4) > > ) > > ) > > (device (vbd (uname phy:hda1) (dev hda1) (mode w))) > > (device (vif)) > > ) > > > > Any ideas on where to start? This is my first foray into Xen, so any > > help would be appreciated > > > > --Susan > > > > > > -- > > redhat-sysadmin-list mailing list > > redhat-sysadmin-list at redhat.com > > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > > > -- > > redhat-sysadmin-list mailing list > > redhat-sysadmin-list at redhat.com > > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: