Home » General » Support » More vzyum problems
| More vzyum problems [message #3810] |
Mon, 19 June 2006 15:55  |
rollinw
Messages: 25
Registered: June 2006
Location: Santa Barbara, California
|
Junior Member |
|
|
I'm new to the Forum--this is my first post.
I have seen posts on vzyum rpm problems dating back to late 2005.
None of these indicates that a final solution has been found.
I am running CentOS4.3 x86_64 on an Opteron as hardware processor
with vmlinuz-2.6.8-022stab077.1-smp. Think the CentOS kernel is
actually 2.6.9-34-EL.
I get the error message when trying to install vzyum.rpm.
It complains that cElementTree.so is missing. Those who have
said there is Python path problem may be right, because the
shared library is there in /usr/lib64.
There is a record of rpms installed:
[root@hwnode1 SPECS]# rpm -qa | grep sqlite
sqlite-3.2.2-1
python-sqlite-1.1.6-1
[root@hwnode1 SPECS]# rpm -qa | grep yum
yum-2.4.2-2.centos4
centos-yumconf-4-4.5
[root@hwnode1 SPECS]# rpm -qa | grep python
python-elementtree-1.2.6-4
rpm-python-4.3.3-13_nonptl
gnome-python2-bonobo-2.6.0-3
python-2.3.4-14.1
libxml2-python-2.6.16-6
gnome-python2-gtkhtml2-2.6.0-3
python-ldap-2.0.1-2
python-sqlite-1.1.6-1
gnome-python2-2.6.0-3
dbus-python-0.22-12.EL.5
python-devel-2.3.4-14.1
vzrpm43-python-4.3.3-7_nonptl.6
python-urlgrabber-2.9.6-2
gnome-python2-canvas-2.6.0-3
vzrpm44-python-4.4.1-22.5
Notice that I installed both vzrpm43 and vzrpm44, since
instructions did not say how to choose between them.
Another question: I haven't installed the kernel patch,
because the install instructions did not say to do it.
Thanks for help for these problems.
Rollin Weeks
|
|
|
|
|
|
| Re: More vzyum problems [message #3972 is a reply to message #3810] |
Mon, 26 June 2006 12:54  |
Preatorian
Messages: 2
Registered: June 2006
Location: Netherlands
|
Junior Member |
|
|
I'm having almost the same problem with this one.
after the change of the cacheos script i'm getting the following message
I'm Using CentOS 4.3 86_64
Linux openvz 2.6.8-022stab078.10-smp #1 SMP Wed Jun 21 14:01:02 MSD 2006 x86_64 x86_64 x86_64 GNU/Linux
Getting the following error,
Creating cache for centos-4-i386-default OS template
rpmdb: Program version 4.2 doesn't match environment version
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /vz/root/100001/var/lib/rpm
Traceback (most recent call last):
File "/usr/share/vzyum/bin/yum", line 28, in ?
yummain.main(sys.argv[1:])
File "/usr/share/vzyum/yum-cli/yummain.py", line 75, in main
base.getOptionsConfig(args)
File "/usr/share/vzyum/yum-cli/cli.py", line 172, in getOptionsConfig
self.doConfigSetup(fn=opts.conffile, root=root, vps=opts.vps)
File "/usr/share/vzyum/lib/yum/__init__.py", line 82, in doConfigSetup
self.conf = config.yumconf(configfile=fn, root=root, vps=vps)
File "/usr/share/vzyum/lib/yum/config.py", line 271, in __init__
self.yumvar['releasever'] = self._getsysver()
File "/usr/share/vzyum/lib/yum/config.py", line 384, in _getsysver
idx = ts.dbMatch('provides', self.getConfigOption('distroverpkg'))
TypeError: rpmdb open failed
ERROR: yum failed with 1 exit code
Creating cache for centos-4-i386-minimal OS template
rpmdb: Program version 4.2 doesn't match environment version
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /vz/root/100001/var/lib/rpm
Traceback (most recent call last):
File "/usr/share/vzyum/bin/yum", line 28, in ?
yummain.main(sys.argv[1:])
File "/usr/share/vzyum/yum-cli/yummain.py", line 75, in main
base.getOptionsConfig(args)
File "/usr/share/vzyum/yum-cli/cli.py", line 172, in getOptionsConfig
self.doConfigSetup(fn=opts.conffile, root=root, vps=opts.vps)
File "/usr/share/vzyum/lib/yum/__init__.py", line 82, in doConfigSetup
self.conf = config.yumconf(configfile=fn, root=root, vps=vps)
File "/usr/share/vzyum/lib/yum/config.py", line 271, in __init__
self.yumvar['releasever'] = self._getsysver()
File "/usr/share/vzyum/lib/yum/config.py", line 384, in _getsysver
idx = ts.dbMatch('provides', self.getConfigOption('distroverpkg'))
TypeError: rpmdb open failed
ERROR: yum failed with 1 exit code
|
|
|
|
| Re: More vzyum problems [message #3979 is a reply to message #3810] |
Mon, 26 June 2006 14:06 |
rollinw
Messages: 25
Registered: June 2006
Location: Santa Barbara, California
|
Junior Member |
|
|
Thanks to those who have responded to my post of several days ago. I have not worked on this problem for a while. There was a post at some point--maybe in April--that indicated there is a problem with a path in the vzyum rpm spec, which causes vzyum to look in the wrong place for python packages, etc. I have not checked Bugzilla to see if this has been entered as a bug. Seemingly, the problem exists only for x86_64 kernels, which have both a /usr/lib and a /usr/lib64. At least one person seems to have solved the problem by installing 32-bit yum rpms. To me, this is a hack, not a solution (nothing personal). I would like a complete package in which everything works as advertised (maybe this is a lot to ask for a new, evolving software collection).
In the meantime, I bypassed the problem by installing yum inside a VE and using it to bring in needed software. Now I have two CentOS and one SuSE9.3 VEs running. The brute-force approach, i.e., copying VPS kernels into the cache area and running vzctl create did the trick OK. Last week I did a split for 5 VEs, because the default basic resource allocation did not provide enough resources for a small number of VEs (I had been getting a malloc error while running CPAN to install mysql/Perl packages).
It would be nice if we had an "official" answer to our problem. If I can help anyone privately, let me know.
rollinw
|
|
|
|
|
|
| Re: More vzyum problems [message #4685 is a reply to message #4678] |
Fri, 21 July 2006 16:30 |
rollinw
Messages: 25
Registered: June 2006
Location: Santa Barbara, California
|
Junior Member |
|
|
By the time of my 2nd post, I had a VE based on centos-4-x86_64-default.tar.gz and the CentOS4.3 x86_64 smp version.
The bottom line is that I still do NOT have vzyum working on the hardware node for my VEs, which are all 64-bit systems. Rather I gave up on metadata processing and built my VEs from existing templated systems. Besides the CentOS VE, I also have Suse and Debian VEs. I just put the xxx.tar.gz version into /vz/template/cache/ and ran the vzctl create routine. I am using mostly the Suse 9.3 VEs.
When you genereate a VE from a basic default template, what you get is a system that tends to be pretty lean (i.e., a lot of handy things missing). That's one reason vzyum is very useful. In my case, it was difficult even to edit files, since vim was missing. So I proceeded as follows:
1. Made sure the network in the VE was working.
2. Started the sshd in the VE.
3. Found a good repository for Suse RPMs.
4. Downloaded vim and wget rpms to my PC.
5. Uploaded the 2 rpms from my PC to the VE using ssh relative,
scp.
A while back I discovered that wget is a really good friend. After I installed vim and wget, I used wget from the VE to bring in rpms for bzip2, mm, and python. From then on, anything that was missing, I could pull in with wget. On the CentOS VE, I also brought in all the rpms needed for yum. This allowed me to completely bypass vzyum. Though, as you say, I don't have the capability of processing metadata for templates. So far I have managed to get by without it.
Hopefully vzyum for 64-bit systems will be fixed. In the meantime, maybe you can proceed somewhat like I did to get your virtualizations working OK without it.
Regards,
rollinw
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Thu Jul 18 22:33:02 GMT 2024
Total time taken to generate the page: 0.02792 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
