I know few things on it, if you can add few more.
1. Set up you domain at new server / host.
2. Upload files at new server.
3. Change domain name servers.
4. Keep site at old as well as new server during domain propagation.
I have PSM and i just found out that even though they initiated my server they dont support GD on the initially installed apache 2.
I really need a simple solution like GD to create simple thumbnails about 4-5 times per day.
So PSM offered to downgrade the server to apache 1.X, i'm not sure this is right and needed to be done just to get simple GD functions.
I'm with fairly limited server management skills, thats why i have psm.
So i googled this topic and found out i can use Cpanel's builtin apache builder to rebuild the same web server with GD,
I got this error:
file /etc/fonts/conf.d/30-aliases-fedora.conf from install of fontconfig-2.4.1-7.el5 conflicts with file from package fontconfig-2.4.1-6.el5
Error Summary
-------------
Could not ensure pkglist 'zlib1-devel, expat-devel, gettext, automake19, libstdc++.x86_64, libpng-devel, libopenssl0-dev, expat, openssl, gcc-c++, glibc-devel, libpng-dev, zlib-devel, zlib, bison, autoconf261, gmake, libXpm, libjpeg-devel, openssl-devel, automake, coreutils, libtool-libltdl-devel, libopenssl0, openssl-dev, libtool, patch, libz-devel, libltdl3-devel, libltdl, libjpeg-dev, libopenssl0.9.7-static-devel, pam-dev, libtool-ltdl-devel, libopenssl0.9.7-devel, libltdl-devel, fileutils, libXpm-devel, sed, libXpm-dev, lsof, krb5-dev, flex, glibc-dev, expat-dev, krb5-devel, libstdc++-devel.x64_64, make, libstdc++-dev.x86_64, libX11-devel, xorg-x11-devel, libtool-ltdl, libssl-dev, gd, pam-devel, cpp, xorg-x11-dev, gcc, libopenssl0-devel, ssl-dev, lex, autoconf'
Please visit [url]for help with this error.!
Restoring original working apache!
my heart went down to my pants, but the original web server was restored and working as usual...
I simply don't know what to do now, since this seems like a too complicated issue for a server newbie to fix, into getting GD to work with the current server would be great!
I've been working in this industry for 5 years now. Over the years, I've come to realize the little things that customers do that REALLY piss tech support off. This is a guide for customers for 10 things NOT do when contacting their host's technical support team.
This is a repost of what I already posted before the big catastrophe.
Please forgive the brutal honesty. It's for your own good.
1. One ticket per issue.
Emailing your issue to Support, Sales, Billing, Abuse, the owner, each individual tech, and the mayor of your town is not going to get your ticket answered any quicker. Additionally, opening 2, 3, 4, or 10 tickets isn't going to get things done any faster. Seriously - all it will do is irritate the support guy
2. Contact the proper department
If your account is suspended due to non-payment, or your account hasn't yet been setup, or you want to upgrade your account - please don't bother contacting support hoping it'll get done faster. All it will do is slow down their response time to customers that have actual support issues. Billing issues goto Billing. Sales issues goto Sales. Abuse issues goto abuse. Get the picture?
3. Contact support via ONE medium
If you put in a support ticket, don't get on live chat and call too. Trust me - you'll get the same answer on live chat and the phone as you will in the ticket . Same goes for requesting "updates" on your ticket - if your ticket is in queue, wait patiently for a response. If you don't get a timely response, contact the management to complain.
4. Everyone thinks their ticket is CRITICAL
Tech support reps realize that you think your issue is CRITICAL and must be dealt with IMMEDIATELY. But, guess what, so does everyone else that submitted their ticket before you. Your CRITICAL ticket will be answered in the order received after everyone else's CRITICAL ticket has been answered.
5. Do not try to "bump" your ticket
Making continuous replies to your ticket in an event to get a faster response won't work. In fact, in most common helpdesk applications, each reply made rotates the ticket to the bottom of the queue. So really, by bumping your ticket, you're just making yourself wait longer. Not getting service fast enough? Contact the manager of the company!
6. Include all relevant information, but only relevant information
Seriously - we don't care to hear your life story. Submit your ticket with your client ID, domain name, username, password, error messages, steps to reproduce, and other information directly pertinent to your issue. If your website is inaccessible, check http://www.downforeveryoneorjustme.com/ and include your local IP address (from www.whatismyip.com) and a traceroute. That will save you a reply.
7. Just because YOU can't see the website does NOT mean the server is down
So please - don't come shouting at us claiming we're fraudsters and have horrible uptime and demand a credit. Most of the time you will find there is either a firewall issue or a routing issue - or scheduled maintenance. Check http://www.downforeveryoneorjustme.com/ and your host's forums before screaming at them.
8. Avoid live chat & phone support
Unless you have a quick question, live chat and phone support are probably not going to be good avenues. Chances are, if your issue requires someone to login to the server to investigate, you're just going to be escalated to a support ticket. Instead of whining about how long the support ticket will take to get answered - just get it in queue. Figure if you spend 5-10 minutes on the phone only for them to tell you that you need to submit a ticket - that's 5-10 minutes that your ticket could have been looked into. Think about it. If you do call or chat - be brief - and keep in mind we have other customers to help.
9. We don't make the rules
If you don't like a company's policies or procedures, don't complain to your support tech about it. They don't make the rules, they just follow them. If you want a change, contact the management of the company.
10. Do NOT disrespect or mistreat support people
If you curse at us, disrespect us, or mistreat us in any way - you can almost be guaranteed that we won't be going out of our way to help you beyond the minimum. By polite, cordial, and courteous to your support tech and it will get you a LOT farther. We don't get paid enough to deal with people's abuse.
11 (Free bonus ). The amount of money you pay does not matter to us
Seriously - the fact that you pay us $9.95/month does not matter to us. We're going to provide you with the same support that we provide somebody that's paying $3.95/month or $99.95/month. Don't expect better treatment based on the amount of money you pay.
I've been working in this industry for 5 years now. Over the years, I've come to realize the little things that customers do that REALLY piss tech support off. This is a guide for customers for 10 things NOT do when contacting their host's technical support team.
Please forgive the brutal honesty. It's for your own good.1. One ticket per issue.
Emailing your issue to Support, Sales, Billing, Abuse, the owner, each individual tech, and the mayor of your town is not going to get your ticket answered any quicker.
Additionally, opening 2, 3, 4, or 10 tickets isn't going to get things done any faster.
Seriously - all it will do is irritate the support guy 2. Contact the proper department
If your account is suspended due to non-payment, or your account hasn't yet been setup, or you want to upgrade your account - please don't bother contacting support hoping it'll get done faster. All it will do is slow down their response time to customers that have actual support issues. Billing issues goto Billing. Sales issues goto Sales. Abuse issues goto abuse. Get the picture?3. Contact support via ONE medium
If you put in a support ticket, don't get on live chat and call too. Trust me - you'll get the same answer on live chat and the phone as you will in the ticket . Same goes for requesting "updates" on your ticket - if your ticket is in queue, wait patiently for a response. If you don't get a timely response, contact the management to complain.4. Everyone thinks their ticket is CRITICAL
Tech support reps realize that you think your issue is CRITICAL and must be dealt with IMMEDIATELY. But, guess what, so does everyone else that submitted their ticket before you. Your CRITICAL ticket will be answered in the order received after everyone else's CRITICAL ticket has been answered.5. Do not try to "bump" your ticket
Making continuous replies to your ticket in an event to get a faster response won't work. In fact, in most common helpdesk applications, each reply made rotates the ticket to the bottom of the queue. So really, by bumping your ticket, you're just making yourself wait longer. Not getting service fast enough? Contact the manager of the company!6. Include all relevant information, but only relevant information
Seriously - we don't care to hear your life story. Submit your ticket with your client ID, domain name, username, password, error messages, steps to reproduce, and other information directly pertinent to your issue. If your website is inaccessible, check [url] and include your local IP address (from www.whatismyip.com) and a traceroute. That will save you a reply.7. Just because YOU can't see the website does NOT mean the server is down
So please - don't come shouting at us claiming we're fraudsters and have horrible uptime and demand a credit. Most of the time you will find there is either a firewall issue or a routing issue - or scheduled maintenance. Check [url]and your host's forums before screaming at them.8. Avoid live chat
There has been a recent rash of Windows 2003 customers being hacked and having "UTorrent" installed, as well as having their Administrator password changed, rendering the server inaccessible.
At the moment, we have yet to determine the vulnerability in Windows allowing the hackers to breach the systems however we believe it is related to RDP.
We highly suggest you are complying with the following, to lessen your risk of having your server compromised:
1) Run RDP on a non-standard port
[url]
2) Run a software firewall on your machine, blocking ALL unnecessary ports on your server. You should only have the bare minimum open.
3) Limit any non-public access to your IP and trusted IP's only. This will prevent any other outside networks or servers from reaching your machine through ports which are not meant to be public (http for example)
4) Ensure you have FULL updates for your Windows O/S, immediately.
5) Ensure any 3rd party software you are running, has also been fully updated to the latest version including any patches.
Please make sure these suggestions are implemented immediately to lessen you risk of being hacked by the current wave of exploits.
Apache error log for a subdomain
[Thu Apr 17 00:02:24 2008] [crit] [client 69.113.17.156] (13)Permission denied: /home/user/public_html/subdir/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
However, there is no htaccess file in that directory anyway
/home/user/public_html/subdir
Server is Centos 5 / Cpanel
I am shopping around for a new dedicated server and am running into sites that offer 100% Uptime guarantees.
Is 100% uptime possible? Wouldn't that mean that they never reboot their server, or never perform specific maintenance/updates on the server?
I guess when I see 100% uptime, I would expect perfection. I thought I'd ask here if this is possible because I'd hate to invest dollars on something false.
A web will be down due to many problems, like disk failure, web services dead etc. even ISP offers 100% network uptime SLA. So, my question is how to keep a web 100% uptime?
for instance, when any server(either db server or web server, either hardware or software failure)dies, the redundant server may immediately and automatically take over the dead one.
Is this possible I can get 100% uptime on my VPS. I think if I buy another VPS and use it for secondary VPS and If my first gone down that VPS start working after that.
View 14 Replies View Relatedhow come every web host says they have 99.9% uptime? I just saw a new webhost that started last week and they said they had 99.9% uptime. They've only been around for a week, they should have 100%. Why does every web host advertise that fact?
Next, how is that .1% lost? Do their servers crash for a second?
I currently have two VPS 1 at modvps.com and i'm having some serious problems with downtime.
Could someone recommend a vps service where i can have something near 99,999% of uptime?
i think in dedicated servers you can put second server and if first server gone down second server autometically start working.
is this possible in VPS too. I have four VPS
is it possible to have 100% uptime i mean is it possible to have 2 servers(2 different data centers) with the same hosting information
ns1 (first data center)
ns2 (second data center)
has anyone here had a server with wholesaleinternet.com for a while? Preferably someone that can post some uptime statistics? A publicly available uptime report for at least the last six months would be perfect...
View 2 Replies View RelatedIt's my first post, but I thought it would be useful to create a list with links to public statistics of uptime of VPS's of different hosting.
Hyper-v windows 2003 vps at webspacedepot.com
serviceuptime.com/users/uptimemonitoring.php?S=8621c2c30f85e3fadc3d6f056170db65&Id=14678
(I don't have 5 post yet so I can't link it)
what is the meaning of uptime?
View 11 Replies View RelatedI am getting increasing frustrated each day as I went from shared server to shared server and now I'm on a VPS and my server is typically down 2-5% per day. Is this normal? Is it to much to expect 99% uptime?
View 14 Replies View RelatedI'd be interested to hear from anyone who can point to independently documented evidence of uptime of 99.99% or better for at least 12 months for a specific site hosted on a commercial hosting company. (Less than 53 mins of downtime.) I'm looking for something like a link to a report on an independent monitor site (e.g. hyperspin, alertra, host-tracker) that has checked at least every 10 mins over that period.
We get a lot of requests for "reliable" hosting here, and I'm hoping this will be useful information - even if there are no responses!
I'm not interested in anecdotal reports or "near misses" - feel free to post them in a different thread, but not here, please.
If you respond, could you please indicate whether the monitored site used scripting (e.g. PHP) and/or database access (e.g. MySQL) during the entire 12 months and whether you used this host for email, and the price you actually paid for this hosting package?
I have a client who wants to have 100% uptime for his emails only. Is it possible to have 2 hostings with same domain and have the emails goes to any server.
View 18 Replies View RelatedFor a Web Host What Do you consider an acceptable uptime level?
View 23 Replies View RelatedI see a lot of web hosts that link to webhostingstuff.com which tracks the uptime of their main page. i would like to offer a similar service, where i track and list the uptime of hosts. can anyone point me in the proper direction for this? is there a particular script that I can purchase? how is this done?
View 9 Replies View RelatedAs I've mentioned in other threads, I work in the hosting industry at the support end of things. I can't go more than 10 minutes into my shift each day without seeing a ticket where someone is complaining about or contesting the "99% uptime guarantee". One day a couple weeks ago, I had someone complaining about an Alertra report with 98.7% uptime, and how it was unsatisfactory for their site to be down for 10 minutes every month. What's more, it was just a stupid World of Warcraft forum that probably saw 5 visitors per day.
My co-workers and I have been debating this, though. What worth is there in 99% uptime? Is it something that can be achieved? If so, would people pay more for it? Would it be able to be marketed to the shared hosting community? Would people be willing to pay more for 100% uptime? Would the same answers apply?
Recurring maintenace can be down the uptime %?
View 5 Replies View RelatedI have a VPS and am looking for a way to show existing and potential clients the uptime levels of the server. I have a basic uptime page provided by WHMCS, but I want to go a little beyond that.
If I were to choose an uptime reporting service such as siteuptime.com, hyperspin.com or site24x7.com, what would you recommend that I monitor? Obviously HTTP, FTP, POP3 and MySQL, but anything else? Do these services monitor the server load also?
Also, is it a good idea to display these stats publicly?
Is there any tool that I can use to check my site uptime?
I am pissed-off with my host...my site is on/off and I want to show them result that I cannot work on it.. I feel really bad..
100% Uptime or Never Down shared hosting.
100% Uptime or Never Down shared hosting.
if your site is up ALL the time in the past 6-12 months, monitored by server uptime service,
please mention your host on this thread....
Just looking for opinions on uptime guarantees. Does anyone actually look at those guarantees anymore? Or is it just assumed that every host now a days is up 99.9% of the time.
The reason I ask is that it appears that every host has one, but I haven't really ever experienced one myself.
Who would you suggest to hire for simple uptime and service monitoring?
View 14 Replies View Relateduptime monitor service for my shared hosting account to:
Monitor http and if possible https
Sent text message to UK Mobile
Send email to me
Send email to hosting company
thinking about it's to find some solution for offer 100% uptime for my customers.
Actually I have 4 servers running cpanel, my idea it's to setup another server where I put 4 VPS with a copy of the servers, and in case them fails, I up the VPS.
Real dedicated server will be ns1.
And the VPS will be ns2.
What I don't know how to manage it's the cpanel license, because if I want to have a copy of the servers in VPS I have to pay that licenses sure?
Also, today I see the DNS ONLY cpanel, could be better option? I'm also testing some cloud systems like mosso cloud servers and gogrid, but this don't allow me to be 100% and free of hardware failures.
And yes, not 100% because it's impossible, but 99,9999999%
I currently have a VPS host that, for the past 45 days or so, has delivered an average of 66% uptime. The best results are 75% and the worst are 50%. I'm still waiting for an official response from the company so I'm not including any names. But I do have sites at Dreamhost and Hostgator and they're reporting 99% and 100% respectively.
Is it normal for VPS hosts to have lower uptime? Or is this just the result of a bad server or cluster?
Note: I have about 10 sites on the VPS host and all report the same results. Dreamhost has about 3 sites and Hostgator has 1.