OpenVZ Forum


Home » Mailing lists » Users » Is apt-get really such a hog or am I doing something wrong? Debian issue
Is apt-get really such a hog or am I doing something wrong? Debian issue [message #11410] Thu, 22 March 2007 20:04
jarcher is currently offline  jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island
Member
Hi All...

I' trying to run a Debian x86_64 VPS from a prebuilt template I DLed from
systs, but it seems that apt-get is a major resource hog. It seems that
the more resources I give it, the more it wants. Currently, I am running
on the sample 'B' configuration from the wiki and still see apt-get failing
because it can not allocate RAM and tcp buffers. From user_beancounters:

uid resource held maxheld
barrier limit failcnt
1001: kmemsize 1082179 2521031
2457600 2621400 133
tcprcvbuf 0 349072
319488 524288 244


Is there a way around this, or do I just have to allocate huge amounts or
resources to the VPS? I really don't want to do that if I can avoid it,
because I'm hoping to get more than 16 or so VPSs going.

Am I just doing something wrong? Here are the errors I see:

Do you want to continue? [Y/n]
Setting up makedev (2.3.1-83) ...
/sbin/MAKEDEV: warning: can't read /proc/devices
/sbin/MAKEDEV: line 160: /bin/rm: Cannot allocate memory
/sbin/MAKEDEV: line 138: /bin/rm: Cannot allocate memory
/sbin/MAKEDEV: fork: Cannot allocate memory
/sbin/MAKEDEV: /sbin/MAKEDEV: Too many open files in system
/var/lib/dpkg/info/makedev.postinst: fork: Cannot allocate memory
dpkg: error processing makedev (--configure):
subprocess post-installation script returned error exit status 254
Errors were encountered while processing:
makedev




Thanks...
Previous Topic: 1/2 OT: installing vz images remotely
Next Topic: Virtual Memory Problems
Goto Forum:
  


Current Time: Sat Nov 09 03:58:26 GMT 2024

Total time taken to generate the page: 0.03146 seconds