OpenVZ Forum


Home » Mailing lists » Users » VPS don't start correctly, just 4 proc
Re: VPS don't start correctly, just 4 proc [message #13141 is a reply to message #13137] Mon, 21 May 2007 13:42 Go to previous messageGo to previous message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member

anything in dmesg, /var/log/messages?
Looks like only grep fails on your machine.

can you execute a simple command in host system plz like:
# echo yyy | grep y
does it fail with Segmentation fault?

What has changed on your node? What host OS do you use?
I remember some one was reporting the same problem when wrong gcc options were
used for compilation. Please search forum/mailling lists, maybe it helps.

Thanks,
Kirill


José David Bravo Álvarez wrote:
> [root@genesis ~]# vzctl start 102
> Starting VPS ...
> VPS is mounted
> bash: line 266: 16312 Segmentation fault grep -q
> "${FAKEGATEWAYNET}/24 dev ${VENET_DEV}" ${routefile} 2>/dev/null
> bash: line 56: 16316 Segmentation fault grep -E "^$name=.*" $file
> >/dev/null 2>&1
> bash: line 56: 16318 Segmentation fault grep -E "^$name=.*" $file
> >/dev/null 2>&1
> bash: line 250: 16319 Segmentation fault grep -q 'if \[
> "\${DEVICE}" = "lo" \]; then' ${file} 2>/dev/null
> Setting CPU units: 1000
> Set hostname: exodo.colombiahosting.com.co
> bash: line 235: 16331 Segmentation fault grep -q -E
> "[[:space:]]${val}" ${cfgfile} 2>/dev/null
> bash: line 235: 16332 Done echo "${val}"
> 16333 Segmentation fault | grep "\." >/dev/null 2>&1
> bash: line 88: 16334 Segmentation fault grep -E "^\<$name\>" $file
> >/dev/null 2>&1
> bash: line 56: 16335 Segmentation fault grep -E "^$name=.*" $file
> >/dev/null 2>&1
> VPS start in progress...
> [root@genesis ~]#
>
 
Read Message
Read Message
Read Message
Previous Topic: Filesystem size limit in the vzquota system ?
Next Topic: Another Error
Goto Forum:
  


Current Time: Thu Jun 06 22:40:45 GMT 2024

Total time taken to generate the page: 0.05287 seconds