How long is a reboot issued through DirectAdmin supposed to take?
My server specs:
CPU: Celeron D 2.66 Ghz
RAM: 512 MB
HD: 80 GB IDE. Swap: 2 GB
OS: CentOS 4.4
Control Panel: DirectAdmin newest version
It has already taken over 21 minutes and the server is still not up or at least not able to serve any pages or anything.
I've got two websites on my server.
As soon as I turn on site #2, apache starts eating up the ram.
After 30 minutes server goes into swap, and the sleeping processes starts increasing.
Reason why I know it's apache, is if I stop apache, the amount of free ram immediately starts increasing.
Is this a misconfiguration of Apache?
Code:
[Sat Jul 28 21:40:09 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations
[Sat Jul 28 21:45:08 2007] [notice] caught SIGTERM, shutting down
[Sat Jul 28 21:45:18 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] Digest: generating secret for digest authentication ...
[Sat Jul 28 21:45:19 2007] [notice] Digest: done
[Sat Jul 28 21:45:19 2007] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Sat Jul 28 21:45:19 2007] [notice] LDAP: SSL support unavailable
[Sat Jul 28 21:45:19 2007] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations
[Sat Jul 28 21:50:08 2007] [notice] caught SIGTERM, shutting down
[Sat Jul 28 21:50:08 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
........
This just started a few hours ago. This is in my inbox:
06:54:01 PM cpanel@server.mydomain mysql on server.mydomain failed
06:45:11 PM cpanel@server.mydomain mysql on server.mydomain failed
06:36:25 PM cpanel@server.mydomain mysql on server.mydomain failed
06:27:34 PM cpanel@server.mydomain mysql on server.mydomain failed
06:18:46 PM cpanel@server.mydomain mysql on server.mydomain failed
06:09:57 PM cpanel@server.mydomain mysql on server.mydomain failed
06:01:05 PM cpanel@server.mydomain mysql on server.mydomain failed
05:51:46 PM cpanel@server.mydomain mysql on server.mydomain failed
05:42:58 PM cpanel@server.mydomain mysql on server.mydomain failed
05:34:08 PM cpanel@server.mydomain mysql on server.mydomain failed
05:25:19 PM cpanel@server.mydomain mysql on server.mydomain failed
05:16:31 PM cpanel@server.mydomain mysql on server.mydomain failed
05:07:43 PM cpanel@server.mydomain mysql on server.mydomain failed
04:58:53 PM cpanel@server.mydomain mysql on server.mydomain failed
04:50:05 PM cpanel@server.mydomain mysql on server.mydomain failed
04:41:09 PM cpanel@server.mydomain mysql on server.mydomain failed
04:32:15 PM cpanel@server.mydomain mysql on server.mydomain failed
04:23:28 PM cpanel@server.mydomain mysql on server.mydomain failed
04:14:36 PM cpanel@server.mydomain mysql on server.mydomain failed
04:05:48 PM cpanel@server.mydomain mysql on server.mydomain failed
03:56:57 PM cpanel@server.mydomain mysql on server.mydomain failed
03:48:09 PM cpanel@server.mydomain mysql on server.mydomain failed
And they're still arriving to my inbox. When you look at the time stamps, it's failing every 9 minutes. I looked in the crontab and there is nothing running every 9 minutes. Not even close. But there's something happening every 9 minutes. Where do I look?
Even though I have set notification_interval from 120 to 120m. It might take the changed interval_limit from nagios.cfg.
I am receiving far too many e-mails and text messages in case of downtime at the moment. We're testing our monitoring servers at the moment, but we don't need a new notification every 25 minutes...
I recently signed up (just yesterday) with this company on the grounds of pricing and reviews. I especially noted the fact that they respond "in minutes" well. I have opened 2 tickets thusfar:
first:
Created On: 15 Jul 2007 04:54 PM Last Update: 15 Jul 2007 06:06 PM
second:
reated On: 16 Jul 2007 02:25 AM
I am new to the VPS hosting game. Are support times generally longer than with shared hosting? Or am I just encountering some bad luck? To me, you should want to be impressing newly registered customers. Especially concerning support and when the client has stated VPS is new to him.
I am currently on this plan:
Managed
cPanel - Platinum
450GB 512MB 1.5GB 30GB 2 IPs cPanel: $44.95
Any others out there with quick support times (livechat?) and a comparable package/price? (price is important)
Our new server crashes about every 30',causing high high load(80!)
After mysql restart,everything its ok.
System:
Dual Core @ 3Ghz
1GB Ram
Sata Drives
Centos 5
---
My.Cnf config:
--
Code:
[mysqld]
socket = /var/lib/mysql/mysql.sock
safe-show-database
old-password=1
max_connections=500
interactive_timeout=100
wait_timeout=30
connect_timeout=30
thread_cache_size=8
key_buffer=32M
join_buffer=8M
max_allowed_packet=32M
table_cache=1024
sort_buffer=32M
record_buffer=8M
thread_cache_size=128
max_user_connections=30
thread_concurrency=4
myisam_sort_buffer_size=64M
query_cache_limit=2M
query_cache_size=32M
query_cache_type=1
old-passwords = 1
[safe_mysqld]
err-log=/var/log/mysqld.log
open_files_limit=8192
[mysqldump]
quick
max_allowed_packet=32M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_bufer=16M
[myisamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M
[mysqlhotcopy]
interactive-timeout
----
Top Process,showing in whm and status2k:
--
/usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/server3.zaxihosting.com.pid --skip-external-locking --socket=/var/lib/mysql/mysql.sock
One of my servers keep overloading due to a SQL process.
The process is:
/usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/zeus1.forcium.net.pid --skip-external-locking --socket=/var/lib/mysql/mysql.sock
It takes up pretty much 90-95% of the cpu and memory at times if I do not kill the process. But even after I kill the process it comes back and immediately hogs up cpu load again causing it to go into loads of 8.00 or higher ( I have 8cpus ).
I installed Direct Admin on my 192mb RAM vps and right now my VPS is at 270mb (I'm going into burst). I found that if I stopped named, it goes down to less than 70. Why is Bind taking up so much RAM?
View 11 Replies View RelatedI don't have a problem with Bluehost, but after getting this email tonight I would have thought that it's not that hard to have enough fuel and a big enough generator to last more than five minutes after a power outage. It seems like pretty poor redundancy planning if a major host can't last more then five minutes with no power. Hospitals and other places don't have any problem doing it with similar or bigger power demands.
Dear Bluehost Customer,
This evening (July 14th) from about 5:25pm-6:55pm many of our servers
were offline causing significant downtime for many of our users. The
outage was due to a severe power outage in the north end of Orem, Utah
where our servers are located. We do have UPS backup as well as diesel
generators, but at about 5:30 they finally gave out. The power outage
was for much longer than that period of time, but the reserve power
was eventually consumed in its entirety. When it rains it pours.
For users on box65-box145 there have been periodic problems with the
Redhat linux kernel that we were using that was causing problems with
the filesystem that your data is stored on. This issue has been causing
periodic problems for users on those boxes. In the last few days we have
resolved that issue which also caused those boxes to require a reboot.
The downtime is extremely regretable. We apologize profusely for the
inconvenience to our customers and in turn to those who were trying to visit
your sites during the outage. With the fixes we have put in place in the
last few days coupled with other upgrades you should experience MUCH
better uptime in the future.
Thanks for you patience,
Matt Heaton / President Bluehost.com
My entire experience with Gigenet has been very bad. I will post a 30 day review once I have completed my first and only billing cycle with them. This topic will be solely focused on the way Gigenet handled my server being down for 17 hours and 50 minutes. I have paid Gigenet for 30 days of service, one billing cycle. My account is set to be terminated on the 7th of June.
I pay Gigenet to actively monitor my server. These services are called "NOC Response from Monitoring" and "Host Ping (ICMP) and TCP Service Monitoring". The extra "service" cost $10/mo.
I realized that my server was down after 7 hours of downtime. I sent in a "critical" support ticket at about 3 AM.
Here is a timeline of my support ticket with Gigenet
Quote:
Originally Posted by ME - 05 Jun 2009 03:11 AM
My Server is down. Any reason for the down time?
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:24 AM
Can I at least get a confirmation that this issue is being worked? It's 3:32 AM...I have to work tomorrow morning and would prefer to get some sleep.
Thanks...
* Note: I am not exactly clear why the time stamp and the time mentioned by me in the ticket don't line up.
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:24 AM
I'm looking into your issue now, all updates will be posted here.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:29 AM
I have server monitoring. Can you also explain to me how SEVEN HOURS of down time was over looked by your "server monitoring"?
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:37 AM
This server has been marked for cancellation.
I see that the date set was for June 7th and today is the 5th, I will need to speak to a Billing representative before I can re-enable this device. The Billing Department will not be in until 10am, I will leave this ticket open and I will speak to them first chance I get.
* Note my server is still down at this point.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:44 AM
Yes, because canceling my service two days earlier makes a lot of sense. I paid Gigenet for 30 days, I should get all 30 days. Maybe I'm misunderstanding something?
Please respond so I can get to bed...
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:55 AM
I understand your concern, but your server port was administratively shutdown and I was able to find the cancellation ticket. I need to speak with someone from Billing concerning this issue. This looks to be a mistake on our end, but I don't have all the details in front of me. I will attempt to contact my manager and get this straightened out. All further updates will be posted here.
It was nearly 4:00 AM at this point. I had to be at work by 6:30 AM. My server was still down, so I went to bed.
The next day I received this response:
Quote:
Originally Posted by Gigenet Posted On: 05 Jun 2009 01:43 PM
Hello,
Your server should be back online until the 7th. We're very sorry for the inconvenience. I've confirmed the server's availability via ping from my workstation. Please let us know if you have problems accessing it and we'll take another look.
At this point in time my server was restored. The total downtime was 17 hours and 50 minutes. I monitor my server with a third-party service called "HyperSpin".
Seeking an answer to explain nearly 18 hours of downtime; I sent this response.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 04:14 PM
What is the reason for the downtime? Is 17 hours and 50 minutes of unexplainable downtime something that I should expect from Gigenet?
Quote:
Originally Posted by Gigenet -Posted On: 05 Jun 2009 04:22 PM
Hello,
Unfortunately I' not exactly sure what happened. I think the server may have been prematurely canceled, but I'm not totally certain. The server should be back up and I've put in the necessary ticket to make sure it stays on until the 7th, as you requested. We're very sorry for this inconvenience.
So, the best I can get out of Gigenet is that my server may have been shutdown prematurely. I don't understand why Gigenet can not fully explain nearly 18 hours of downtime. No one seems to know exactly what happened...
Do you trust in 10 minutes response time guarantee?
Sharkspace.com guarantee that for their clients.
How do I get a cron job to run every
1 hour 10 mintues, so basicly 10 mins past the hour
Also
1 hour 15 mintues, so basicly 15 mins past the hour
Is it ?
10 * * * * and 15 * * * *
I'm currently considering a host change, so I'm putting out feelers to potential candidates. As always, I'm putting on my difficult customer mask (turning down my rationality and patience module) to find out if the host can actually handle real-life customers (one of the things I find most important and that I don't want to find out once the server is already on fire). Most companies pass the test very well. Here's how LiquidWeb handles new customers:
Quote:
Originally Posted by yosmc
Hi guys,
I'm looking to switch hosts in the next couple of months. I'd probably wait until January, but since the recent experience has been a bit bumpy with our current host, I'd like to get some basic info now so we can move more quickly if circumstances force us to do so.
MY SITUATION: I'm a do-it-yourself webmaster who has been managing his own server for years. It's become a curse though because managing your own server means you have to be online virtually every day. I'm looking for a solution that will allow me to be offline for several weeks (a REAL vacation, something I haven't had in a decade), knowing that whatever major issue there is with my sites, someone will take action and make sure the service stays available.
- Last year, I've switched to my first managed solution, but as it turns out, they're not doing what I need. Yesterday, for example, I came home to find my sites offline. The site was unavailable for over 40 minutes, and after asking about it I learned that they didn't take action because the server wasn't quite dead yet, only really, really, really slow. To me, this is hairsplitting, the only thing that matters is whether or not my site is available to visitors. - And once the service has been restored, I would also expect a managed host to figure out what caused the issue, and to propose a solution (or just implement one, e.g. change the mysql configuration) so that a similar issue won't happen anymore under the same circumstances.
- If my sites are unavailable due to a fatal error (e.g. a table needing repairs, or max users reached, "can't connect" or whatever else) I would also expect my managed host to catch it on their own, restore things to normality, and possibly think of ways to keep similar issues from happening in the future.
- If my site suffers a DOS attack, I would expect a managed host to think about how my site can be protected.
And so on.
- My largest database tables are 2.5 GIGs in size, but the /tmp disk my host configured has only 600 MB available, so everytime I perform a major operation (even if it's about slimming it down and running an OPTIMIZE afterwards) everything goes down the crapper (/tmp 100% full and load average shooting up to 200). Seems like the fact that /tmp is 100% full doesn't even trigger any alarms with my host, they send the alert to me, and expect me to contact them and ask for a fix. - When I needed to run a business-critical script that keept failing due to the small /tmp, it was me who reconfigured mysql so that it would temporarily use another partition for /tmp - no suggested solution from the host whatsoever. Not good at all.
- I would also like to see a host being able to learn from past incidents. This would require the host admitting though when they made a mistake, or gave the wrong advice. A host not admitting mistakes means that they will not learn, and will therefore keep making the same mistakes all over again (for the client that's a horrible outlook).
- I also think it's embarrassing if a host tells the client that fixing a certain issue is beyond the scope of their support, if it turns out afterwards that the issue happened because of some update done by the host. If in doubt, the host should always provide assistance.
- And if an issue does go beyond what can be expected from managed hosting, it would be the icing on the cake if the host could offer to fix it anyway, possibly against a fee. Such a situation could occur if a major site error is due to a broken script that was provided by the client. ("Looks like your script blah.php is causing the fatal error, we can look into it but this will likely take X hours and cost you Y USD.") Again, the ultimate goal for me is to be able to be offline for several weeks at a time, knowing that any major interruptions to my sites can be resolved without me.
- I would also appreciate a system that will allow trusted site members to report issues - i.e. one where I can give users the ability to report problems without at the same time giving them the privilege to push any red buttons that may damage my site.
So in a nutshell I'm trying to figure out if Liquid Web is the right hosting solution for me. Please let me know if your hosting philosophy meets me needs (and don't hesitate to let me know if it doesn't ).
Thanks!
Quote:
Greetings,
Thank you for contacting us. Liquid Web offers Heroic Support which covers the
hardware, OS, and installed components. We will also monitor your server, and
if a service fails one of our reps will log into your box and restart the
service. We do not provide support for your content (including backups). If
you are having a problem we will help you to troubleshoot the problem, however
if the fault is in your content or scripts we will not be able to assist you
with that.
For more information on what your support covers please see our website at:
[url]
If you have any further questions please let us know.
Quote:
Originally Posted by yosmc
Hi,
I hadn't written such a long email because I'm bored, but because I wanted to know where Liquid Web stands on the issues mentioned ("what would have happened in these situations if I was hosting with Liquid Web"). You have basically answered the question about fixing script problems, and for the rest sent me to a page with unspecific promotional teasers. If that's all I can get as a reply I guess that also answers my questions (I'm already Googling for alternatives) but then again maybe you just want to give it another try?
Thank you.
Quote:
Originally Posted by LiquidWeb
Greetings,
We will take care of server administration issues, we do not take care of any
content issues. From the email you sent it sounds as if you are looking for a
web developer that can watch over your site, and make corrections and
adjustments as needed. This is beyond the scope of what we offer.
If you have further questions please let us know.
Quote:
Originally Posted by yosmc
XY, right now I am just looking for someone to answer my questions. For what it's worth, I didn't draw the name "Liquid Web" out of a hat, and I had already been to your website prior to sending you my mail. Anyway, here's what I read from your responses:
THE BAD NEWS:
- Even if it's a one-time emergency, you are paid extra and not providing help would ruin the client's business because the client is currently in a thunderstorm in the middle of the Atlantic, it is not possible to convince Liquid Web support to fix a fatal error that may have been triggered by a programming error in one of the client's scripts.
- Although Liquid Web's server monitoring is called "Sonar" it is - in practice - just as slow as the one I've described in my intitial mail (because if it was any better, you would have told me by now how LW would have handled the given example differently).
- Even if all my sites are down because your staff has misconfigured mysql to break under heavier traffic, or because one of the tables crashed, Liquid Web's staff will do nothing until notified because as long as the mysql service itself is up, you don't see any reason to intervene (if this is something you'd care about and fix, I'm sure you would have let me in on it by now). - EDIT: Or wait - you guys are installing mySQL but you're not configuring/tweaking it so it actually works for the client? Not sure, seems like I actually have to *guess* on that one.
- Liquid Web's ticket system cannot provide sub-accounts with lesser privileges (because if it could, you would have advertised it to me).
- When Liquid Web sets up new servers, /tmp is below 1 gigabyte as well, and when this causes issues, it is definitely not Liquid Web's fault (because if you would be handling this any differently, you would have pointed it out).
- Liquid Web has too many customers already, which is why even customers who know what they want aren't told what they can get, but instead receive links to canned information that doesn't answer their questions, along with the info that Liquid Web probably isn't for them anyway.
- Generally you're in a hurry and can't spend more than 5 minutes on the average ticket.
THE GOOD NEWS:
- LiquidWeb offers DoS protection (I had missed that, but see it clearly now).
Hope there was nothing I missed. So - thanks for all the extensive information you gave me (and sorry for using up so much of your precious time), I will make sure to honor it when I reach my decision.
No further replies.
Anyone know what's wrong with these people? Are they full, or do they only take on easy customers who need nothing?
My server has been crashing quite alot lately, it does have some high traffic sites on there but it has never really been this bad before. Today i noticed these in cpanel, what are they and is there anyway I can control them?
View 13 Replies View RelatedCode:
2.1 2:06.99 cpanellogd - sleeping for logs
Why does cpanellogd take a lot of memory, 2.1% of memory for just idling.
I have a VPS where i have cpanel installed. I have noticed quite a number of times through my WHM Cpu/Memory usage that there are 3 instances of MRTG and they seem to be taking up a lot of resources.
I did not install mrtg and i don't even know how do i go ahead and view them
Can someone tell me how do i remove them and is it just me or are there actually 3 instances of MRTG running for everyone?
Here's a screenshot of the same:
[url]
We've had a VPS for just over a month now. I am not going to mention the host by name (yet) but they advertise here and other people here reported liking them.
Sadly it's not my experience and I regret my purchase.
Every morning for the past few weeks, we get load spikes every 30 minutes that make our site unusable for a minute (on our VPS, any load over 1.0 is sluggish, over 2.0 is virtually unusable, over 3 is unresponsive)
Here's a series of days as an example:
[url]
The worst part about this is the host insists 1. either it's not happening or 2. they can't find it
I know it's happening because when I try to load a page on the half-hour, it takes over 13 seconds (less than 1 second normally). And it's fairly obvious it's someone doing a cron job with some nasty downloading, uploading, or maybe a massive mysql update.
Someone tell me what to tell them because this is driving me out of my mind. The load is NOT being caused by ourselves, I've made sure all our cron jobs don't happen on the exact half hour and we get lots of traffic later in the day without loads.
Recently we have launched our new cpanel server, We have some problems on that.
When we restart httpd, all things will be good before 15 min, but after that, speed goes down to 1/10 and after some hours that will get as low as nobody can view pages on the server.
We are using cPanel latest release and CSF on CentOS4.5.
Apache 1.3.7 and PHP4.4.7 is running on the server with Zend.
I just logged into my VPS and was astonished by how much space I have in use.
8.09GB... but I can't figure out what's using up so much space!?
How can I find out were large files are located ? Since it's increasing daily
I use LXAdmin with HyperVM Control Panel
I was on a 100mbps shared port with a dedicated server from FDC and I use it only for downloads. The downloads took a little long to start but once they did, were as fast as they could be.
Thinking this was definitely a shared bandwidth problem, I ordered a dedicated port of 25mbps from FDC to fix it but it seems to have gotten worse.
The website uses around 10/15mbps but it takes forever for the server to respond. Even logging into cPanel takes around 40/50 seconds for the dialog box to appear but everything is fast once I log into my cPanel.
I also hired a sys admin to look into the server and He says everything is fine. I don't know what to do. I could increase my port bandwidth higher but it'll be disappointing if I do and it's just a waste of bandwidth (and money!)
I just noticed something weird on my FreeBSD server
FreeBSD Disklabel Editor shows:
twed0s1e /home 108GB *
df -h shows:
/dev/twed0s1d 105G 4.0K 96G 0% /home
so... 108 GBs become 105 GB that become 96 GBs usable?
that's 11,11% loss
pretty big IMO
(this has nothing to do with "real space"... it's really GBs (1024^3, not 1000^3)
Look this:
root@empresarios [~]# free -m
total used free shared buffers cached
Mem: 2017 1966 50 0 20 1054
-/+ buffers/cache: 892 1125
Swap: 2000 1378 621
U know more than me, but why my dedicated server is taking Swap if as u cann se still have 50 Mb free of RAM?
FreeBSD 7.0
Apache 2.2
PHP5
Mysql 5.1
I have been battling this for a while. A user will setup a CMS like joomla, e107, etc and every time the CMS changes files either with user interaction on the website or the admin changing things in their cms admin web page, apache takes ownership of the files.
I have tried installing suPHP, FastCGI, and most recently suexec. I am not having any luck with this. I really don't know what I am doing with these recent additions but meanly going on suggestions. Does anyone know of a walk through to fix this permission problem? Anyone with some good advise? Surely not everyone is having to write a script to chown each user's dir and run a cronjob every 5 minutes.
suddendly some of my sites in my server is taking sessions errors...then after a while all its going ok and then again the same problem...the problem still continues.from what might be the problem?a php update?mysql update?any exprerience?
i havent made any change.my server is linux has centos 4.7
HostGator is the only one I know of taking your 404 traffic by default. I have never experienced this with any other host I have used.
Personally it does not bother me much because I know how to change it simple. I'm a big fan of HostGator otherwise. They do provide a great service. I just find it weird your 404 page is a HostGator ad with a coupon code.
Is this a popular thing I have just never run into? I know it is the norm with free hosting providers.
what is the linux command to check, how much space is a directory taking?
and
what is the linux command to check, how much space are directories taking in increasing or decreasing order of there sizes?
