Web Hosting Talk : Web Hosting Main Forums : VPS Hosting : Help me pls!!!!!!

[lightstarm2k]

I have a VPS at Ramhost, now my sites are offline and when I reboot my VPS from VPS panel it shows this message: and my sites are still offline

Result: Starting VE ...
VE is mounted
Adding IP address(es): 204.12.214.104
bash: line 291: 6 Segmentation fault grep -qE '191.255.255.[0-1]' $file
bash: line 406: 7 Segmentation fault grep -q "${FAKEGATEWAYNET}/24 dev ${VENET_DEV}" ${ROUTE} 2> /dev/null
bash: line 61: 9 Segmentation fault grep -E "^$name=.*" $file > /dev/null 2>&1
bash: line 61: 10 Segmentation fault grep -E "^$name=.*" $file > /dev/null 2>&1
bash: line 390: 11 Segmentation fault grep -q 'if \[ "\${DEVICE}" = "lo" \]; then' ${file} 2> /dev/null
bash: line 492: 22 Done echo "${IFNUMLIST}"
23 Segmentation fault | grep -q -E "^${IFNUM}$" 2> /dev/null
bash: line 519: 25 Segmentation fault mv -f bak/* ${IFCFG_DIR}/ > /dev/null 2>&1
Setting CPU limit: 100
Setting CPU units: 1000
Setting CPUs: 1
Setting devices
Configure meminfo: 262144
Set hostname: vps6.vz9.ramhost.us
bash: line 304: 32 Segmentation fault mv -f ${cfg}.$$ ${cfg}
bash: line 61: 33 Segmentation fault grep -E "^$name=.*" $file > /dev/null 2>&1
ERROR: Can't change file /etc/resolv.conf
bash: line 376: 37 Segmentation fault mv -f ${cfgfile}.$$ ${cfgfile}
File resolv.conf was modified
VE start in progress...
VE is already running

Help pls

[lightstarm2k]

when I start lighttpd service it shows this message:

(network.c.300) can't bind to port: xxx.xxx.xxx.xxx 443 Cannot assign requested address

[VIPoint]

Check if any service is running on the port 443 and 80 or not. You can check that using the command

ps aux |grep :80
ps aux |grep :443

If any service is running then kill the service and they try restarting httpd.

[lightstarm2k]

Originally Posted by VIPoint

Check if any service is running on the port 443 and 80 or not. You can check that using the command

ps aux |grep :80
ps aux |grep :443

If any service is running then kill the service and they try restarting httpd.

[root@vps6 /]# ps aux |grep :443
Segmentation fault

[gigatux]

Sounds like you've got some very corrupt binaries there.

Maybe it's worth running file `which ps` to see what the binary is detected as, and then see if that matches your VPS's architecture. However, a reinstall (or at least a copy of known, working binaries) might be in order.

[lightstarm2k]

Well, the problem is that I don't know linux..
I have to wait for their live support online


Thanks

[gigatux]

Ah, I see. Unfortunately, this does not look like a simple issue to fix so you are probably best off waiting for the live support.

[xtrac568]

maybe a host node is out of memory.

[lightstarm2k]

Originally Posted by xtrac568

maybe a host node is out of memory.

I think so, my VPS has 1024MB of Memory and I have around 10K visitors per day
I wonder why it show errors when I start VPS

[gigatux]

Originally Posted by lightstarm2k

I think so, my VPS has 1024MB of Memory and I have around 10K visitors per day

But according to your initial post, you get Segmentation Faults as soon as you boot up. Surely you can't be out of memory straight away? It's also pretty weird to not even be able to run a simple command such as 'ps'.

[lightstarm2k]

The VPS is not connected to the internet

[root@vps6 ~]# wget google.com
--2010-01-07 07:39:49-- http://google.com/
Resolving google.com... failed: Temporary failure in name resolution.
wget: unable to resolve host address `google.com'

[Up2vps]

check /etc/resolv.conf

[lightstarm2k]

they said network configuration files got deleted or corrupted

[gigatux]

Originally Posted by lightstarm2k

they said network configuration files got deleted or corrupted

Tell them you can't even run 'ps' as above. That's not network related, so I think there's also another issue (e.g. some binaries got corrupted).

[lightstarm2k]

Originally Posted by cocodude

Tell them you can't even run 'ps' as above. That's not network related, so I think there's also another issue (e.g. some binaries got corrupted).

Thanks people now the server is back online, I don't know what was the issue.

Thanks to Ramhost support, now my sites are even faster