HostMySite VPS Constantly Crashing Or Slow

Feb 5, 2009

I give HMS VPS hosting two thumbs down. <--- flip those over

This VPS I am working with is constantly crashing or slow.

Seeing as pricing wise how they are a "premium" VPS provider, the service is anything.

(By service I mean the VPS service provided, their tech support is quick to respond, the problem remains, but they are quick to respond, usually it seems they just reboot the vps)

Does anyone know how many VPS's the put on one server?

Is there anyway from the command line to view my virtuozzo stats to see if their were any blocks? Ex. oomgarpages, numothersock, kmemsize, etc.

View 14 Replies


ADVERTISEMENT

Hostmysite.com

May 27, 2008

Very unhappy with current provider and they are a very attractive company.

View 6 Replies View Related

HostMySite / LiquidWeb

Jan 4, 2009

We need to move couple of sites from their current platform. If you had to pick either HostMySite or LiquidWeb, which one would you choose for shared hosting?

It will be nice to have Pros and Cons

View 14 Replies View Related

HostMySite VPS 1 Year Review

Aug 15, 2008

One year has gone by since we bought our hosting plan at HostMySite (HMS) and I thought I'd post another review. You can read my previous review here (http://www.webhostingtalk.com/showthread.php?t=659594)

The Short Of It
We have 2 IIS Coldfusion VPS (CF VPS+ plan). The first one we had was originally just a CF VPS (for developing) but we later changed it over to a CF VPS+ (more ram, more space, etc). This VPS is 1 year and 1 month old. Our production VPS which currently hosts our website is a healthy 1 year old. The reliability has been great and we never had any speed or performance issues.

We are very happy at HMS. We have had very little issues with the our VPSes and those issues are usually resolved very quickly. Anytime we needed support, it was overall always quick and helpful. We recommend HMS to anyone who needs a Windows VPS.

Security and Friends
The SSL certificate we purchased from our previous host expired so we bought a new one via HMS. At first the order we placed was apparently processed by them but wasn't sent to the issuer for processing. We didn't find out until we sent a ticket in wondering about the status. They immediately processed it for us. Except for the fact that they processed it for 1 year when we bought it for 3. So another ticket flew across the internet and flew back to us just as quickly resolving the problem.

They asked if they wanted them to install it and we emphatically said yes. They installed the certificate and we were set. Or so we thought. We began having issues with our merchant account not being able to verify our SSL certificate. They forgot to add in the intermediate certificate so that third party processors can see verify it's legitimacy. This was resolved very quickly (faster than we expected) and we have not had issues with it since.

The One Thing
The only thing we'd like to mention was an incident that occurred several months ago. One day, out of the apparently gray clouds, for some reason our site could not be connected to. After shaking our fists futilely at the weather gods, we sat down and tried to figure out what was wrong. By doing the basic diagnostics to make sure it wasn't us or our ISP we cursed the Lunar Goddess and contacted HMS to see what was up. They fixed it but didn't tell us what the issue was. Apologies in the form of cup cakes to the Moon was issued.

The next day, the same problem occurred or at least we thought and was told it was the same problem. We could not access our site. This time we did both live chat and started a ticket (for documentation, last time we just called). In the live chat they stated it was an issue with the node and not specific to our VPS and they were working on it. They said it was the same issue as yesterday.

This is where it starts getting dicey.

They also responded via the ticket that the firewall was blocking the ports and not the same issue as yesterday. Now considering only one person has access to the VPS (via RDC) to make changes and he did not log in to make any changes to the firewall (why would we?) that explanation didn't even seem plausible. And the ports blocked (pretty much everything except FTP) didn't make any sense. We went back and forth, with me explaining that after several months of not touching the firewall after setup, why would we inexplicable block ourselves out? Why would we even touch the firewall? Also that it can't be a coincidence with the node issues yesterday and they had already stated it was the same issue.

After a bit of going back and forth, they finally came to the conclusion that the patch they applied to fix the node issue made changes to the firewall which caused the subsequent issue. While this explanation didn't exactly seem completely kosher, we weren't going waste more time asking for a better explanation.

Now given that the total "downtime" of both issues was about 5 hours we thought we'd see how much of a resistance they will put up for the uptime guarantee. The first issue we pretty much knew wasn't going to get any attention because according to their TOS, they will only refund for time it was down when you posted a support ticket. Since we did this over the phone, there was no documentation to speak of when it went down and when it got fixed.

As for the second issue (which did have a ticket) they stated that since the VPS was technically up, the uptime guarantee did not apply even if the problem was caused by them (they didn't specifically say that but it was implied). While we didn't expect anything from it and didn't bother to pursue it, that response raised some eyebrows. While within their rights, it did seem a bit "whoa". They did apologize and were very polite and respectful. It was pretty much what we expected in terms of responses.

The Train Ride
While the above issue may seem bad, it was a one-time event. These things can happen. We haven't had any uptime, access or server issues since that problem. Support is quick and helpful.

The site has been running fine for months with no downtime.

We are overall very happy with HMS and would recommend them to anyone who needs a Windows VPS.

Overall Rating: 9.5/10
Support: 9/10
Reliability: 9/10
Speed and Bandwidth: 10/10

View 4 Replies View Related

HostMySite.com Unreliable Web Host

Mar 20, 2009

Unbelievable how bad HostMySite.com has become. At one time they were pretty much at the top but there has been enough mistakes, bad service and lack of support on HostMySite.com's part to warn others. The most recent situation could have come out of a modern day Three Stooges skit. When I asked to have a host set up three were generated instead by billing.

When I contacted support about the web not showing he stated that he could see the files I had upload just fine. I looked in the HostMySite.com control panel and found the duplicate entries for the domain. When I contact support again, another technician said that he could see the HostMySite "under construction" page just fine - two different IPs. After finding the duplicate errors I requested that HostMySite.com remove the other entries so that the domain was using only one IP.

I received an email stating the reason for the conflict was due to duplicate entries and that the support ticket was forwarded to billing to remove the duplicates (no kidding). Long story short was nothing happened so I contacted them again and was informed that the support request was stuck in the billing queue - no one had looked at it. My deadline had already pasted (marketing).

More to that story but I sure would like to hear from others that may have had bad encounters from HostMySite.com.

Being one that has been around the block with internet marketing I can say that the original mistake could have been forgiven. The inability on their part to correct the mistake cause for concern. HostMySite.com's lack of concern for their mistake unforgivable.

View 3 Replies View Related

VPS Constantly Rebooting

Jun 29, 2009

I have a vps and I was having memory issues so I reboot my server. Upon doing that it seems to have put itself into a loop and is constantly rebooting itself every 5mins.

I checked the logs at /var/log/messages and found this:

Code:
(?@127.0.0.1) [INFO] Logout.
Jun 29 11:55:49 evercuben xinetd[24525]: EXIT: ftp status=255
pid=24296 duration=0(sec)
Jun 29 11:55:49 evercuben xinetd[24525]: EXIT: smtp status=1 pid=24292
duration=0(sec)
Jun 29 12:00:49 evercuben xinetd[24525]: START: smtp pid=1628 from=127.0.0.1
Jun 29 12:00:49 evercuben xinetd[24525]: START: ftp pid=1630 from=127.0.0.1
Jun 29 12:00:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] New
connection from 127.0.0.1
Jun 29 12:00:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Jun 29 12:00:49 evercuben xinetd[24525]: EXIT: ftp status=255 pid=1630
duration=0(sec)
Jun 29 12:00:49 evercuben xinetd[24525]: EXIT: smtp status=1 pid=1628
duration=0(sec)
Jun 29 12:05:49 evercuben xinetd[24525]: START: smtp pid=11347 from=127.0.0.1
Jun 29 12:05:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] New
connection from 127.0.0.1
Jun 29 12:05:49 evercuben xinetd[24525]: START: ftp pid=11349 from=127.0.0.1
Jun 29 12:05:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Jun 29 12:05:49 evercuben xinetd[24525]: EXIT: ftp status=255
pid=11349 duration=0(sec)
Jun 29 12:05:51 evercuben xinetd[24525]: EXIT: smtp status=1 pid=11347
duration=2(sec)
Jun 29 12:10:49 evercuben xinetd[24525]: START: smtp pid=20210 from=127.0.0.1
Jun 29 12:10:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] New
connection from 127.0.0.1
Jun 29 12:10:49 evercuben xinetd[24525]: START: ftp pid=20212 from=127.0.0.1
Jun 29 12:10:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Jun 29 12:10:49 evercuben xinetd[24525]: EXIT: ftp status=255
pid=20212 duration=0(sec)
Jun 29 12:10:49 evercuben xinetd[24525]: EXIT: smtp status=1 pid=20210
duration=0(sec)
Jun 29 12:15:49 evercuben xinetd[24525]: START: smtp pid=30100 from=127.0.0.1
Jun 29 12:15:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] New
connection from 127.0.0.1
Jun 29 12:15:49 evercuben xinetd[24525]: START: ftp pid=30102 from=127.0.0.1
Jun 29 12:15:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Jun 29 12:15:49 evercuben xinetd[24525]: EXIT: ftp status=255
pid=30102 duration=0(sec)
Jun 29 12:15:49 evercuben xinetd[24525]: EXIT: smtp status=1 pid=30100
duration=0(sec)
Jun 29 12:20:49 evercuben xinetd[24525]: START: smtp pid=7525 from=127.0.0.1
Jun 29 12:20:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] New
connection from 127.0.0.1
Jun 29 12:20:49 evercuben xinetd[24525]: START: ftp pid=7527 from=127.0.0.1
Jun 29 12:20:49 evercuben pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Jun 29 12:20:49 evercuben xinetd[24525]: EXIT: ftp status=255 pid=7527
duration=0(sec)

View 6 Replies View Related

SLHOST Constantly Down

Jun 30, 2007

I moved to SLHost some time around January. The first couple of months were okay. However, the last two months have been hellish. This month alone the server was down June 1, 3, 4, 16 (for 13 hours) and, again, today.

anyone else having the same experience with SLHost?

View 14 Replies View Related

Constantly Blocked On Pop3

Sep 14, 2007

I just setup a new pop account in Outlook 2007 and provided all the proper details as I have on other pop accounts I have setup. I am constantly getting blocked by the firewall on the server (CSF + LFD) and I am 100% positive I am using the right password. This happens every time I setup a new pop account and I don't know why.

Using cpanel / exim

Firewall shows this

tcp:in:d=110=xxxxxx # lfd: 3 (pop3d) login failures from xxxxxx - Fri Sep 14 16:42:16 2007
tcp:in:d=995=xxxxxx 2 # lfd: 3 (pop3d) login failures from xxxxxx - Fri Sep 14 16:42:16 2007

Outlook constantly pops up the login dialog box even though I set that up already with "remember password" checked as well.

I closed / restarted Outlook, pop, exim and still getting the login box + firewall blocking me again.

If that isn't enough, I even put my IP in the allow list (CSF) and restarted it while made sure it was not in the disallow list.

STILL getting blocked!

View 3 Replies View Related

Spamd Is Constantly Failing

Aug 5, 2008

I have been using my Server for a decent while, All of a sudden of the last month it has decided that it wants to play a game.

"Spamd" keeps failing and automagically restarts.

It restarts and works, But then Fails once again a few hours later. One morning I woke up to 7 error messages with the same service.
By Restarting Exim it resolves the issue but it happens hours later.
I have tried mostly of what I can think of.

Does anyone have any other thoughts on this issue and how it can be resolved?

View 4 Replies View Related

Perl Install Constantly Fails With Out Of Memory, But Nothing's Running

Aug 12, 2008

an inexpensive VPS host and based on reviews on this forum, went with Web Wide Hosting.

I had a smooth signup and thanks to Jon at WWH, managed to get a payment snafu with Paypal resolved smoothly.

However, I've been struggling a lot with getting most recommended steps to actually work in my VPS and I'm getting increasingly frustrated.

The latest problem I have is that trying to install Perl modules fails with a "cannot allocate memory" error. First google hits suggest increasing memory, which really isn't an option for me right now. More puzzling is the fact that both HyperVM and user_beancounters suggest I have enough headroom atleast to install perl modules!

Output from session:

cpan> install Authen::PAM
CPAN: Storable loaded ok
Going to read /root/.cpan/sources/authors/01mailrc.txt.gz
Going to read /root/.cpan/sources/modules/02packages.details.txt.gz
Database was generated on Mon, 11 Aug 2008 07:02:52 GMT
HTTP::Date not available

There's a new CPAN.pm version (v1.9205) available!
[Current version is v1.7602]
You might want to try
install Bundle::CPAN
reload cpan
without quitting the current session. It should be a seamless upgrade
while we are running...

Going to read /root/.cpan/sources/modules/03modlist.data.gz
Could not pipe[/bin/gzip --decompress --stdout /root/.cpan/sources/modules/03modlist.data.gz |]: Cannot allocate memory at /usr/lib/perl5/5.8.8/CPAN.pm line 5726.

# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
6050: kmemsize 2383965 4269136 2147483646 2147483646 0
lockedpages 0 0 99 99 0
privvmpages 6418 26175 25600 25600 38
shmpages 685 1981 25600 25600 0
dummy 0 0 0 0 0
numproc 22 38 99 99 0
physpages 3147 22279 0 2147483647 0
vmguarpages 0 0 25600 2147483647 0
oomguarpages 3147 22279 25600 2147483647 0
numtcpsock 5 42 792 792 0
numflock 3 9 99 99 0
numpty 1 3 50 50 0
numsiginfo 0 3 99 99 0
tcpsndbuf 55900 411424 20971520 24215552 0
tcprcvbuf 81920 4136784 20971520 24215552 0
othersockbuf 2236 11744 20971520 24215552 0
dgramrcvbuf 0 8380 20971520 24215552 0
numothersock 9 20 792 792 0
dcachesize 113634 194947 912384 912384 0
numfile 495 856 2376 2376 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 14 14 99 99 0

Not even getting started on the problems I'm having trying to mount /tmp as a noexec,nosuid partition

View 13 Replies View Related

Plesk 11.x / Linux :: Pmmcli-daemon Running Constantly?

May 23, 2014

For some reason pmmcli-daemon has started to run constantly at 90-100% CPU even when it's not backing up.

No error message emails are generated.

I can stop it, but then I find it running after it has completed the domain backups.

View 13 Replies View Related

VPS Incredibly Slow, Huge Numbers Of Slow MySQL Queries For Plesk/Watchdog

Nov 11, 2008

I've got 25 domains on a Virtuozzo/Plesk8.6/CentOS5 VPS. Each domain has one up-to-date install of WordPress, most have very little traffic (average 200mb per month), maybe 2 domains get 5-7gb traffic per month.

I monitor port 80 connections and rarely see more than 10 at a time.
That should in my opinion be no problem at all for a VPS with 768mb guaranteed ram and 2.4ghz cpu. I've got 30gb hard drive spare too.

But.... about 8 or 10 times a day it grinds to a complete halt: server load at 500-1000%, sites timing out, plesk takes 3mins to load, often I can't even connect with SSH, and the plesk web server, apache

INSERT INTO module_watchdog_sys_stat (time, type, value, service_id) VALUES(FROM_UNIXTIME(1226404705), 'MAINMEM_USAGE', 17472, 11);

80 seconds sounds like a huge amount of time for a MySQL insert to me! Does anyone know if this is likely to be the cause of my trouble? Some problem with Plesk and the database? Or could it be something else?

View 3 Replies View Related

Apache Procs Constantly Rise, Until Apache Is Restarted

Jul 23, 2007

I've had this problem a long time now with my hosting network and decided to ask here hoping I get some good solutions, or if someone is willing to looking at this (I'll pay if they want).

Here's what I mean:
[url]

Problem is as you can see apache processes constantly rise infinitely, at least until I restart apache (/etc/init.d/httpd restart). The point of restart is shown in red lines.

And after restart, it goes down again for X amount of hours then eventually rises again infinitely until it's restarted again.

But the fact that after restart it remains down, it means it had the potential to be down all along.

So my question is: what could be causing this and does anyone have solution to keep them low at all times (as per graphs)?

View 14 Replies View Related

Mysql Keeps Crashing ...

Nov 2, 2009

Today on a server of mine mysql keeps crashing and I need to manually restart it over and over, the load as well keeps spiking quite high until I stop mysql for a few minutes. There isn't a extra load of traffic or anything as I have the same amount of users on several other servers doing more then this one.

How do I tell exactly whats happening from then how would I go about fixing it?

Basically it mysql crashes and needs to just be manually restarted via ssh.

View 13 Replies View Related

Site Keeps Crashing

Jun 25, 2009

My web site keeps crashing for some reason like every 10 minutes. The site will be up for 10 minutes and then down for 10 minutes. Up for anotehr 10 minutes and then down for another 10 minutes.

The odd thing is that the server does not crash, the site itself does. I can access WHM during these periods of downtime and WHM says everything is perfect. All green check marks, low server load, low memory usage. Everything looks perfect.

On top of being able to access WHM during these periods of downtime, I can even access that green page from the IP, 123.456.789 (exampe ip) that says "Great success, Apache is working on your WHM/Cpanel server"

(this one: img34.imageshack.us/img34/749/greatsuccessw.jpg)

But as soon as I put in my account name after the IP (like 123.456.789/~account), the site crashes. And by crash I mean it goes super slow and then times out.

I don't understand what the problem is and the managed solutions support that I have is usually really good at this, but is also having trouble with this problem.

I'm not sure if this is relevant, but incase it helps I have vBulletin forums and a mySQL database backend. Also, the dedicated server is a linux server with Centos 5.3.

View 14 Replies View Related

Apache Keeps Crashing

Feb 25, 2008

I've been having problems for the past two weeks. Apache and MySQL kept crashing. I tweaked MySQL, and MySQL stopped crashing. But Apache still crashes, sometimes twice a day, sometimes once every few days. It's driving me crazy. It started around the same time I acquired a new customer, so it's possible the customer has some sort of script or something that is causing problems, but I'm not quite sure how to determine whether the problem is the server itself, or if it's the customer.

So here am I, asking you experts for whatever assistance you feel willing to render. Even if you only merely read it, I thank you for at the very least taking the time to read it. Thanks in advance for any and all assistance given. That being said, here's the information the "How To: Request help from the experts" sticky recommended giving. I also took the liberty of including httpd.conf and my.cnf. I apologize if that resulted in being too much information, and humbly ask a moderator to "white out", or so to speak, (or at least point out) the information that shouldn't be shown.

Linux OS: CentOS release 4.6 (Final)
Kernel Version: 2.6.9-023stab044.4-enterprise
Control Panel: Plesk 8.2.1
Hardware information: 20 GB storage, 256MB RAM, 1 TB bandwidth

Results of "php -v":

PHP 5.2.5 (cli) (built: Jan 19 2008 10:08:24)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
with the ionCube PHP Loader v3.1.32, Copyright (c) 2002-2007, by ionCube Ltd., and
with Xdebug v2.0.2-dev, Copyright (c) 2002-2007, by Derick Rethans
Results of "SELECT VERSION;" in MySQL:

Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 1134
Server version: 5.0.54 Source distribution

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> SELECT VERSION();
+-----------+
| VERSION() |
+-----------+
| 5.0.54 |
+-----------+
1 row in set (0.00 sec)
Results of "ps auxf"

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1628 608 ? Ss 12:41 0:00 init [3] ....

View 11 Replies View Related

Lighttpd Crashing

Nov 12, 2008

I keep getting a segmentation fault after a few hours when I leave lighttpd on. It doesn't seem like much resources are being used and its serving about 60mbit/s. There's nothing in the error or log file.

I'm using CentOS 2.6.18-92.1.13.el5
and
lighttpd-1.5.0-r1992
Here's the config:
server.modules = (
"mod_access",
"mod_trigger_b4_dl",
"mod_status",
"mod_proxy_core",
"mod_proxy_backend_fastcgi",
"mod_uploadprogress"
)
upload-progress.progress-url = "/progress"
server.network-backend = "gthread-aio"
server.max-fds = 15000
server.max-connections = 10000
server.event-handler = "linux-sysepoll"
I've actually been having this issue since I've moved to lighttpd 1.5, 1.4 was working fine but I need the features in 1.5. I've tried changing the event handler and network backend to no avail.

How can I at least find out what's causing the error?

View 1 Replies View Related

CPanel Crashing

Oct 19, 2008

I've experienced two episodes of cPanel/WHM not loading or working twice within the past 2 weeks.

Suddenly cPanel/WHM fails to load, but web service, provided by Litespeed (only installed today) continues to serve and mysql is unaffected, just cPanel/WHM.

View 8 Replies View Related

Server Keeps Crashing ..

Jul 19, 2008

System specs:

Intel Celeron Proccesor
256 RAM (yeah I know...)
Debian Etch
Joomla! 1.5

Okay... so, here goes.

Recently, I have switched from Siteground hosting services and everything was fine. Now I have changed over to a dedicated server that resides at my house. I'm routing DNS through FreeDNS (freedns.afraid.org).


For a week or two, the server was fine. Recently, we started working on the website on the new server (posting new articles, changing the theme, adding some plugins, etc.) and it's steadily gotten worse and worse about, when we save changes to something, or post an article, the website will go offline. Eventually, the website will come back.

My question is: What is causing this? The actual server isn't shutting off, so It has to be something between my modem and the user. Is my modem just shutting off because it's overloaded? (that seems sort of improbable) Or, is it a DNS issue? (I have a Dynamic DNS system set up that is working fine)

View 7 Replies View Related

Server Keeps Crashing ...

Feb 27, 2008

My server keeps crashing and this is the last log. Can you help me to find out whats the problem here.

Feb 27 11:41:55 Xxxxxxxx kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 27 11:41:55 Xxxxxxxx kernel: ata1.00: (BMDMA stat 0x25)
Feb 27 11:41:55 Xxxxxxxx kernel: ata1.00: cmd 25/00:00:bf:eb:0f/00:04:04:00:00/e0 tag 0 cdb 0x0 data 524288 in
Feb 27 11:41:55 Xxxxxxxx kernel: res 51/40:f6:c9:ec:0f/40:02:04:00:00/e0 Emask 0x9 (media error)
Feb 27 11:41:55 Xxxxxxxx kernel: ata1.00: configured for UDMA/133
Feb 27 11:41:55 Xxxxxxxx kernel: ata1: EH complete
Feb 27 11:41:56 Xxxxxxxx kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Feb 27 11:41:56 Xxxxxxxx kernel: sda: Write Protect is off
Feb 27 11:41:57 Xxxxxxxx kernel: SCSI device sda: drive cache: write back
Feb 27 12:11:26 Xxxxxxxx kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 27 12:11:26 Xxxxxxxx kernel: ata1.00: (BMDMA stat 0x24)
Feb 27 12:11:28 Xxxxxxxx kernel: ata1.00: cmd 25/00:08:47:83:a6/00:00:1f:00:00/e0 tag 0 cdb 0x0 data 4096 in
Feb 27 12:11:28 Xxxxxxxx kernel: res 51/40:00:4e:83:a6/40:00:1f:00:00/e0 Emask 0x9 (media error)
Feb 27 12:11:28 Xxxxxxxx kernel: ata1.00: configured for UDMA/133
Feb 27 12:11:28 Xxxxxxxx kernel: ata1: EH complete
Feb 27 12:11:28 Xxxxxxxx kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Feb 27 12:11:28 Xxxxxxxx kernel: sda: Write Protect is off
Feb 27 12:11:28 Xxxxxxxx kernel: SCSI device sda: drive cache: write back
Feb 27 12:11:51 Xxxxxxxx kernel: ** RABHIT ** IN=eth0 OUT= MAC=00:30:48:90:ea:50:00:17:cb:4b:9a:00:08:00 SRC=83.143.15.168 DST=xx.xx.xx.xx LEN=40 TOS=0x00 PREC=0x00 TTL=45 ID=3304 PROTO=TCP SPT=113 DPT=57956 WINDOW=0 RES=0x00 ACK RST FIN URGP=0
Feb 27 12:14:07 Xxxxxxxx smartd[6368]: Device: /dev/sda, 95 Currently unreadable (pending) sectors
Feb 27 12:14:07 Xxxxxxxx smartd[6368]: Device: /dev/sda, 21 Offline uncorrectable sectors
Feb 27 12:31:44 Xxxxxxxx named[2355]: lame server resolving '245.236.229.195.in-addr.arpa' (in '236.229.195.in-addr.arpa'?): 194.170.1.6#53
Feb 27 12:31:44 Xxxxxxxx pure-ftpd: (?@204.13.168.174) [INFO] Logout.
Feb 27 12:31:58 Xxxxxxxx named[2355]: lame server resolving '217.236.229.195.in-addr.arpa' (in '236.229.195.in-addr.arpa'?): 194.170.1.99#53
Feb 27 12:33:15 Xxxxxxxx kernel: ** RABHIT ** IN=eth0 OUT= MAC=00:30:48:90:ea:50:00:17:cb:4b:9a:00:08:00 SRC=78.172.82.50 DST=xx.xx.xx.xx LEN=40 TOS=0x00 PREC=0x00 TTL=46 ID=39216 PROTO=TCP SPT=113 DPT=43432 WINDOW=0 RES=0x00 ACK RST FIN URGP=0
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41549
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Received SNMP packet(s) from UDP: [204.13.168.174]:41549
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41549
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41549
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41551
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Received SNMP packet(s) from UDP: [204.13.168.174]:41551
Feb 27 12:34:38 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41551
Feb 27 12:34:40 Xxxxxxxx last message repeated 10 times
Feb 27 12:35:16 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41880
Feb 27 12:35:16 Xxxxxxxx snmpd[27298]: Received SNMP packet(s) from UDP: [204.13.168.174]:41880
Feb 27 12:35:16 Xxxxxxxx snmpd[27298]: Connection from UDP: [204.13.168.174]:41880

View 3 Replies View Related

Server Crashing

Feb 19, 2007

I cannot figure out why my server is always dead when i wake up most mornings.

I am trying to figure out why my server is crashing nearly every night between 12am and 9am eastern time. When it crashes it is down all night until i wake up and have to reboot the damn server. I am wondering if cron jobs are taking up alot of the cpu or something because the server load isn't that much. here is my specs:

Server:
Softlayer
2 CPUS - dual core xenon 3.0mhz
500gb hd
2 gb DDR memory

Softare:
WHM/Control Panel with Ipanel back admin

Sites:
I am currently hosting 4,500 sites on the server.

The server load usually stays below 1 and is blazing fast. I just cannot figure out why it crashes when i sleep. I dont know if there is a virus or what. PHP mail is disabled so there would be no spamming crashing it. Here is my cron jobs:

17 2 * * * /scripts/upcp
0 1 * * * /scripts/cpbackup
*/15 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
2,58 * * * * /usr/local/bandmin/bandmin
0 0 * * * /usr/local/bandmin/ipaddrmap
31 5 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify
56 18 * * * cd /usr/local/cpanel/whostmgr/docroot/cgi/fantastico/scripts/ ; /usr/local/cpanel/3rdparty/bin/php cron.php > /d$
0 8 * * * /root/homedb_update.sh > /dev/null 2>&1
0 6 * * * /scripts/exim_tidydb > /dev/null 2>&1
*/5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1

I dont know much about cron jobs as I am new to this server hosting thing and just bought an established company. Maybe one of the cron jobs is causing it to crash in the middle of the night?

View 13 Replies View Related

Eaccelerator Crashing

Feb 22, 2007

After upgrading to php 4.4.5 from 4.4.4 I am getting this error in modern bill

[23126] EACCELERATOR: PHP crashed on opline 245 of session_register() at /home/user/public_html/modernbill/include/functions.inc.php:99

Anyone face this issue before? I've always used both EA and MB.

[eAccelerator]
zend_extension="/usr/lib/php/eaccelerator/eaccelerator.so"
eaccelerator.shm_size="4096"
eaccelerator.cache_dir="/tmp/eaccelerator"
eaccelerator.enable="1"
eaccelerator.optimizer="3"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="1"
eaccelerator.keys="shm_and_disk"
eaccelerator.sessions="shm_and_disk"
eaccelerator.content="shm_and_disk"

[Zend]
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.2.2
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.2.2
zend_optimizer.version=3.2.2

zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so

.htaccess file:

<Files .htaccess>
order allow,deny
deny from all
</Files>

DirectoryIndex index.php
Options -Indexes

php_value "magic_quotes_gpc" "1"
php_value "register_globals" "1"
php_value "error_reporting" "2039"

View 6 Replies View Related

My Kernel Keeps Crashing

Nov 18, 2007

new server, cent os 5

the damn kernal keeps dying every other day.

I've disabled everything from xcache to monitoring software, etc, and it's still doing it.

here's the output from my ssh session i had open when it died.

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8c61b15>] cifs_writepages+0x2c9/0x56c [cifs]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0453c09>] get_page_from_freelist+0x96/0x310

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0453eda>] __alloc_pages+0x57/0x27e

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f88959ea>] ext3_readpages+0x0/0x15 [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f88959ea>] ext3_readpages+0x0/0x15 [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c045532d>] __do_page_cache_readahead+0x126/0x1c6

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8896546>] ext3_get_block+0x0/0xbd [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04547ab>] do_writepages+0x20/0x32

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0450536>] __filemap_fdatawrite_range+0x65/0x70

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c045072f>] filemap_fdatawrite+0x12/0x16

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8c5ffb3>] cifs_flush+0x16/0x42 [cifs]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04690f0>] filp_close+0x2f/0x54

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c042512c>] put_files_struct+0x65/0xa7

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04260da>] do_exit+0x229/0x746

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c042666d>] sys_exit_group+0x0/0xd

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0403eff>] syscall_call+0x7/0xb

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: Oops: 0003 [#2]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: SMP

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: CPU: 1

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: EIP is at print_trace_stack+0x0/0x3

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: eax: c0613ddf ebx: eba5f000 ecx: c066231c edx: c063c336

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: esi: 00000000 edi: eba5e000 ebp: c0613ddf esp: eba5eb24

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: ds: 007b es: 007b ss: 0068

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: Process gzip (pid: 22837, ti=eba5e000 task=eefbc550 task.ti=eba5e000)

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: Stack: c040502c 00000000 c0613ddf 00000018 00000000 c0613ddf c0405046 c066231c

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: c0613ddf eba5ec9b c04050e2 c0613ddf c0613ca4 c0613ddf eba5ec04 eba5ec38

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: 00000002 00210016 eba5ec04 eba5ec38 c040520f c0613ddf c0613dd3 00000001

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: Call Trace:

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c040502c>] dump_trace+0x8c/0x96

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0405046>] show_trace_log_lvl+0x10/0x20

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04050e2>] show_stack_log_lvl+0x8c/0x94

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c040520f>] show_registers+0x125/0x191

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0404c44>] print_trace_stack+0x0/0x3

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0405411>] die+0x196/0x296

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c05fd66f>] do_page_fault+0x3ea/0x4b8

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c05fd285>] do_page_fault+0x0/0x4b8

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0404a71>] error_code+0x39/0x40

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0404c44>] print_trace_stack+0x0/0x3

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c040502c>] dump_trace+0x8c/0x96

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415a96>] do_flush_tlb_all+0x0/0x5a

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0405046>] show_trace_log_lvl+0x10/0x20

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0405540>] show_trace+0xa/0xc

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c040563d>] dump_stack+0x15/0x17

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415a96>] do_flush_tlb_all+0x0/0x5a

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c044a0b7>] softlockup_tick+0x98/0xa6

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c042cc98>] update_process_times+0x39/0x5c

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04176ec>] smp_apic_timer_interrupt+0x5c/0x64

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04049bf>] apic_timer_interrupt+0x1f/0x24

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415a96>] do_flush_tlb_all+0x0/0x5a

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415921>] smp_call_function+0x99/0xc3

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415a96>] do_flush_tlb_all+0x0/0x5a

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0415a96>] do_flush_tlb_all+0x0/0x5a

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0427b46>] on_each_cpu+0x10/0x1f

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04159d7>] flush_tlb_all+0x13/0x15

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0459195>] kmap_high+0x90/0x18f

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0454dfe>] test_clear_page_dirty+0xc4/0xe6

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8c61b15>] cifs_writepages+0x2c9/0x56c [cifs]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0453c09>] get_page_from_freelist+0x96/0x310

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0453eda>] __alloc_pages+0x57/0x27e

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f88959ea>] ext3_readpages+0x0/0x15 [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f88959ea>] ext3_readpages+0x0/0x15 [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c045532d>] __do_page_cache_readahead+0x126/0x1c6

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8896546>] ext3_get_block+0x0/0xbd [ext3]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04547ab>] do_writepages+0x20/0x32

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0450536>] __filemap_fdatawrite_range+0x65/0x70

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c045072f>] filemap_fdatawrite+0x12/0x16

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<f8c5ffb3>] cifs_flush+0x16/0x42 [cifs]

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04690f0>] filp_close+0x2f/0x54

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c042512c>] put_files_struct+0x65/0xa7

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c04260da>] do_exit+0x229/0x746

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c042666d>] sys_exit_group+0x0/0xd

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: [<c0403eff>] syscall_call+0x7/0xb

Message from syslogd@sv03 at Sun Nov 18 09:00:55 2007 ...
sv03 kernel: Recursive die() failure, output suppressed

View 4 Replies View Related

Server Keeps Crashing

May 2, 2007

I have a FreeBSD server with Cpanel. It keeps crashing every few hours. Data centre swapped RAM, Chassie but no luck. Hard Drive was scanned and no errors found. I can't find anything in the logs (/var/logs/messages). Which direction should I be looking into?

View 10 Replies View Related

VPS Crashing Due To Running Out Of Memory

Jun 19, 2009

I run a drupal site on a VPS running Lighttpd with 128MB ram and 15GB disk space. Every so often the server crashes and I have no access to even reboot via the shell, I have to get my host to reboot the VPS. They say its most likely due to the server running out of memory. I would have no more than 5 users plus 5 guests online at the same time. So my question is this...

How can I find out exactly what is consuming the memory and causing the server to crash? I have looked at drupal logs and the server logs, but I'm no wiser as to whats causing it. What should I be looking for and what can I do to try and solve this?

View 14 Replies View Related

Server Keeps Crashing Every Few Days

Apr 20, 2008

One of my servers at FDC Servers is crashing (= kernel panic) every few days since we got it.

The specs of the machine are:
C2D E6550, 2 GB

Linux .. 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:15:49 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

I opened several tickets with FDC, after running memtest and clocking down memory they say it's not a hardware issue but software related.

Quote:

I see that according to this ticket, memtest has been run without error and the memory was even slightly clocked down to avoid problems. It appears that the errors you are reporting are software related...

I already tried several kernels and different application versions.

The server is only running lighttpd.

View 12 Replies View Related

Xen: DomU Crashing Frequently

Oct 3, 2008

I've been running 3 Xen servers for the last few months in a production environment, and facing a strange problem with one of them.

Server 1 and 2 run a couple of DomU's and are running just fine.

Server 3 runs one DomU and takes care of all the backups for the DomU's of Server 1 and 2
The DomU on Server 3 is crashing every night, right when the backups are being made.
DomU becomes inaccessible, but keeps appearing at xm list with state ------

When I try to connect to the console it wont let me connect. The only way to get the DomU back up is by using xm destroy and xm create again.

For the back-up I use NFS where the DomU on Server 3 is the host, and the other DomU's of Server 1 and 2 connect to it through an internal bridge.

Below you'll find some information about Server 3:

Hardware:
HP ProLiant DL380 G5
10Gb Memory
( 8 x 146G SAS10k in RAID 5 )

Dom0:
CentOS 5 kernel 2.6.18-92.1.10.el5xen
Booting params: dom0_mem=1024M

DomU:
CentOS 5 kernel 2.6.18-92.1.10.el5
Booting params: acpi=off clock=pit

The last qemu-dm log on Dom0:
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 4000
shared page at pfn bffff
buffered io page at pfn bfffd
xs_read(/vm/a8af3ec4-19d4-774e-af65-0902374dc616/rtc/timeoffset): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_write(/vm/a8af3ec4-19d4-774e-af65-0902374dc616/rtc/timeoffset, rtc/timeoffset): write error

View 3 Replies View Related

Server Crashing Frequently

May 1, 2008

this is getting out of control. I have a dedicated server that is "unmanaged" meaning, I manage it

I typically can make my way around a server and do most things - but in this case I'm stuck. I host a number of websites on this box and have went over a year with little problems. The past month or so it seems as though the server crashes daily or every other day. It will be running just fine, then all of a sudden the processes and loads will go out of control until the server is just unusable.

What do I need to provide here for you to be of any help to me? I watch the processes using "top -ci" and it's typically small output - but when it's getting ready to crash it's like a ton of processes get backed up and continue running.

View 14 Replies View Related

Server Don't Stop Crashing

Jan 10, 2007

as many of you know, FreeBSD is a stable system... I have many other FreeBSD servers (with the same kernel as this one) that doesn't have problems but this server keeps rebooting once or twice a day (EVERY DAY)

it's just a reboot... something very very similar to someone pushing the reset button

1) messages, security, auth or dmesg has no entries just before the reset, so the kernel is not getting aware the server is rebooting

2) the server comes back after around 10 minutes (reboot time + fsck)

this is happening for long time, so I compiled a new kernel... and the problem didn't stop

I request the datacenter techs to replace hardwares and they told me everything was replaced: motherboard, CPU, memories... and yesterday also the power suply
so I have no other idea on what to do

in fact I have one... setting a nobreak in this server power suply for 2 or 3 days to see if the problem stops, but the datacenter didn't like this idea

View 10 Replies View Related

Server Crashing, Cgi And Grsec

Feb 20, 2007

this server is crashing after a few hours... it just got frozen... and after rebooted the server, i was looking at the /var/log/message logs and saw this ( you will see when system restart after the crash ):

Code:
Feb 20 17:35:04 server kernel: grsec: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:13280]
uid/euid:48/48 gid/egid:48/48, parent /us
r/sbin/httpd[httpd:6180] uid/euid:48/48 gid/egid:48/48
Feb 20 17:41:40 server kernel: grsec: From 190.73.138.68: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:27459]
uid/euid:48/48 gid/eg
id:48/48, parent /usr/sbin/httpd[httpd:20166] uid/euid:48/48 gid/egid:48/48
Feb 20 17:45:03 server kernel: grsec: signal 7 sent to /usr/bin/php[php:31710]
uid/euid:0/0 gid/egid:0/0, parent /bin/bash[sh:8963] uid/euid:0/0
gid/egid:0/0
Feb 20 17:48:41 server kernel: grsec: From 87.219.205.218: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:11897]
uid/euid:48/48 gid/e
gid:48/48, parent /usr/sbin/httpd[httpd:8152] uid/euid:48/48 gid/egid:48/48
Feb 20 17:51:04 server kernel: grsec: From 85.58.139.135: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:28508]
uid/euid:48/48 gid/eg
id:48/48, parent /usr/sbin/httpd[httpd:19918] uid/euid:48/48 gid/egid:48/48
Feb 20 17:51:58 server kernel: grsec: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:15615]
uid/euid:48/48 gid/egid:48/48, parent /us
r/sbin/httpd[httpd:2482] uid/euid:48/48 gid/egid:48/48
Feb 20 17:52:08 server kernel: grsec: From 166.114.104.42: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:4662]
uid/euid:48/48 gid/eg
id:48/48, parent /usr/sbin/httpd[httpd:24468] uid/euid:48/48 gid/egid:48/48
Feb 20 17:52:38 server kernel: grsec: From 189.175.50.103: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:12497]
uid/euid:48/48 gid/e
gid:48/48, parent /usr/sbin/httpd[httpd:32213] uid/euid:48/48 gid/egid:48/48
Feb 20 17:54:32 server kernel: grsec: From 83.53.142.7: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:18556]
uid/euid:48/48 gid/egid
:48/48, parent /usr/sbin/httpd[httpd:22809] uid/euid:48/48 gid/egid:48/48
Feb 20 17:55:04 server kernel: grsec: signal 7 sent to /usr/bin/php[php:29694]
uid/euid:502/502 gid/egid:502/502, parent /bin/bash[sh:30003]
uid/euid:502/502 gid
/egid:502/502
Feb 20 18:00:54 server kernel: grsec: From 189.141.26.82: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:10817]
uid/euid:48/48 gid/eg
id:48/48, parent /usr/sbin/httpd[httpd:13549] uid/euid:48/48 gid/egid:48/48
Feb 20 18:01:07 server kernel: grsec: signal 7 sent to /usr/bin/php[php:20901]
uid/euid:0/0 gid/egid:0/0, parent /bin/bash[sh:12242] uid/euid:0/0
gid/egid:0/0
Feb 20 18:03:06 server kernel: grsec: signal 7 sent to /usr/bin/php[php:9696]
uid/euid:502/502 gid/egid:502/502, parent /bin/bash[sh:23721]
uid/euid:502/502 gid/
egid:502/502
Feb 20 18:03:29 server kernel: grsec: From 68.26.197.159: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:917]
uid/euid:48/48 gid/egid
:48/48, parent /usr/sbin/httpd[httpd:20771] uid/euid:48/48 gid/egid:48/48
Feb 20 18:04:43 server kernel: grsec: From 87.219.88.132: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:10750]
uid/euid:48/48 gid/eg
id:48/48, parent /usr/sbin/httpd[httpd:4130] uid/euid:48/48 gid/egid:48/48
Feb 20 18:05:04 server kernel: grsec: From 189.167.128.26: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:14515]
uid/euid:48/48 gid/e
gid:48/48, parent /usr/sbin/httpd[httpd:2598] uid/euid:48/48 gid/egid:48/48
Feb 20 18:07:05 server kernel: grsec: signal 7 sent to /usr/bin/php[php:29589]
uid/euid:0/0 gid/egid:0/0, parent /bin/bash[sh:7958] uid/euid:0/0
gid/egid:0/0
Feb 20 18:08:31 server kernel: grsec: From 88.64.181.89: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:15335]
uid/euid:48/48 gid/egi
d:48/48, parent /usr/sbin/httpd[httpd:27788] uid/euid:48/48 gid/egid:48/48
Feb 20 18:08:43 server kernel: grsec: From 201.244.116.46: signal 11 sent
to /usr/www/htdocs/mywebsite.com_cgi/script/out.cgi[out.cgi:15217]
uid/euid:48/48 gid/e
gid:48/48, parent /usr/sbin/httpd[httpd:29545] uid/euid:48/48 gid/egid:48/48
Feb 20 18:17:34 server syslogd x.x.x: restart.
Feb 20 18:17:34 server syslog: Iniciaci&#65533; de syslogd succeeded
Feb 20 18:17:34 server kernel: klogd x.x.x, log source = /proc/kmsg started.
Feb 20 18:17:34 server kernel: Linux version 2.x.xxgrs-bipiv-ipv4
(root@kernel.myserver.net) (gcc version xxxx) #1 SMP Tue Jan 31 17:34:40 CET 2006
Feb 20 18:17:34 server kernel: BIOS-provided physical RAM map:
Feb 20 18:17:34 server kernel: BIOS-e820: 0000000000000000 - 000000000009c400
(usable)
Feb 20 18:17:34 server kernel: BIOS-e820: 000000000009c400 - 00000000000a0000
(reserved)
Feb 20 18:17:34 server kernel: BIOS-e820: 00000000000ea070 - 0000000000100000
(reserved)
Feb 20 18:17:34 server kernel: BIOS-e820: 0000000000100000 - 000000007
Bold date are ( I think ) the crash, and the system booting...
Any ideas about what can be causing the crash.. ? Is this kernel compiled with GRSecurity ? may that affect cgis ?

This is a fedora core server, xeon 3.2 GHZ x 4 procs using about 25 MBits per day.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved