Friday, December 28, 2007

टिकेट हिस्टरी ऑफ़ थे लास्ट वीक

Dec 28 2007 - 08:51 GMT RUBY ON RAILS PROBLEMS (Redmine)
Dec 28 2007 - 08:48 GMT YOUR RATING SYSTEM IS AGAIN NOT WORKING
Dec 28 2007 - 08:32 GMT Please inform the owner - YOUR BOSS! about the Problems here in
Dec 28 2007 - 07:33 GMT RUBY ON RAILS CHAOS AT SERVAG HOSTING
Dec 28 2007 - 06:47 GMT RATING OF SUPPORT NO MORE WORKING
Dec 28 2007 - 05:40 GMT RUBY ON RAILS CAN'T FIND DATABASE RAKE ABORTED
Dec 28 2007 - 03:58 GMT DOES SERVAGE HOSTING HAS VALUABLE SUPPORT?
Dec 28 2007 - 02:45 GMT RUBY ON RAILS APPLICATION NOT WORKING ON SERVAGE HOSTING
Dec 27 2007 - 21:56 GMT REDMINE NOT WORKING on SERVAGE HOSTING
Dec 27 2007 - 19:23 GMT AGAIN CANNOT DELETE SYMLINKS at SERVAGE HOSTING
Dec 27 2007 - 16:14 GMT MAGENTO - REDMINE - RUBY ON RAILS NOT WORKING ON SERVAGE HOSTING
Dec 27 2007 - 10:12 GMT MAGENTO on SERVAGE HOSTING
Dec 27 2007 - 08:51 GMT CANNOT DELETE SYMLINKS at SERVAGE HOSTING
Dec 27 2007 - 05:58 GMT TYPO3 can't update extensions
Dec 27 2007 - 05:27 GMT 24/7 Service
Dec 27 2007 - 04:25 GMT RUBY ON RAILS REDMINE on SERVAGE HOSTING - Application error
Dec 27 2007 - 03:35 GMT AUTOINSTALLER on SERVAGE HOSTING NOT WORKING
Dec 27 2007 - 02:55 GMT LEGAL INFORMATION about SERVAGE HOSTING
Dec 27 2007 - 01:46 GMT RUBY ON RAILS on SERVAGE HOSTING
Dec 27 2007 - 01:37 GMT COMPRESSING FILES ON SERVAGE
Dec 26 2007 - 18:17 GMT CANNOT DELETE or RENAME SYMLINKS
Dec 26 2007 - 13:07 GMT MYSQL PHPMYADMIN ERRORS
Dec 26 2007 - 12:58 GMT REDMINE on SERVAGE HOSTING 3rd
Dec 26 2007 - 10:43 GMT File not deletable
Dec 26 2007 - 09:24 GMT Not connecting to its ROOT Folder
Dec 26 2007 - 07:56 GMT MYSQL DATABASE - PHPMYADMIN PROBLEMS
Dec 25 2007 - 16:59 GMT vTiger can\'t find created database
Dec 25 2007 - 05:20 GMT MYSQL CONNECTION PROBLEM
Dec 25 2007 - 04:10 GMT Not starting from application folder and showing index.html
Dec 25 2007 - 01:27 GMT REDMINE RUBY ON RAILS at SERVAGE HOSTING 2nd
Dec 22 2007 - 05:40 GMT REDMINE on SERVAGE
Dec 22 2007 - 02:03 GMT MYSQL UTF8 Settings
Dec 22 2007 - 01:11 GMT NOT ABLE TO DELETE FILES/FOLDERS
Dec 21 2007 - 12:02 GMT NAMESERVERS???
Posted by at No comments:
Labels:

DOES SERVAGE HOSTING SUPPORT RUBY ON RAILS

Dec 28 - 15:07 GMT
Customer

 If yes then please tell the Servage Hosting Support the HOWTO as they seem to have no idea at all.

Trying to get a Ruby on Rails Application running on Servage Clustered Hosting is a nightmare as there is absolutly NO SUPPORT who will be able to assist you. Perhaps you should Ask Steffan the German Owner of this company why he is advertising RoR Support when it isn't possible to get even one simple RoR Application like Redmine running on Servage Hosting

We should try also some other RUBY Applications - let's see how we can get them running on Servage.

WE ARE WAITING FOR SUPPORT SINCE DEC 21st and until NOW - 8 days later there isn't any Support visible on the horizon from servage who will be willing to help and assist customers who wanna install a RoR on Servage Hosting. WHY?

So another Question:
HOW LONG DO WE NEED TO WAIT FOR AN ANSWER?

Dec 28 - 15:08 GMT
Servage - Julie

 Hello Andreas,

Thank you for submitting a ticket. We do support ROR, here are the details:

ROR - Ruby on Rails. Here are the paths: /usr/bin/ruby /usr/lib/ruby


Thank you :)


Kind regards,
Julie, Support Team Member
Servage Hosting

Dec 28 - 15:52 GMT
Customer

 Hi Julie nice to hear that you are back. I posted already the links to the manual of redmine and also the server requirements and so on. but since then nothing happend at all and no support.

How can you get Ruby on Rails Application Redmine running one Servage Hosting. As you already know we are waiting since over a week that exactly this will happen - a RUNNING REDMINE on SERVAGE HOSTING!

When will you start helping the customers?

Thanks Andi

Dec 28 - 15:56 GMT
Customer

 I added the path you just gave usr/lib/ruby, beside usr/bin/ruby

but nothing changed. We are still receiving the same error like days a go.

Application error
Rails application failed to start properly

Dec 28 - 17:39 GMT
Servage - Patricia

 Hello Andreas,

Thank you for your reply. ROR is supported on any of our clusters. You are welcome to install it. Please note we do unfortunately not support scripting issues.

Kind regards,
Patricia, Customer Care Manager
Servage Hosting

Dec 28 - 23:49 GMT
Customer

 Hi Patricia

It is not a scripting issue but an issue of your server configurations. They are quite strange. As you can see mysql.sock isn't found

Dec 29 - 00:44 GMT
Customer

 Hi Patricia

This is in absolut contrary what you (SERVAGE SUPPORT) mailed before. They actually offered their help to get REDMINE running on SEVAGE. The case - so it was said - was even sent to your admin to help us to get this running.

Now I think that, RUBY on RAILS isn't really working on SERVAGE and it is probably only an add trick to gain more customers, isn't it ;-)

I am so sorry about that. We are having problems to setup REDMINE as your server isn't configured for RUBY on RAILS and your FAQ isn't right at all.

Check our prvious posts and requests about that.
http://apapococ.blogspot.com/

Also we think you should warn customers about your service and support as there isn't any REAL support. Isn't it ;-)

If there is support, then please check why our REDMINE isn't running on your server. We have already transmitted all specs as requested from Julie yesterday. Thanks!
Posted by at 1 comment:
Labels:

RUBY ON RAILS PROBLEMS (Redmine)

Dec 28 - 08:51 GMT
Customer

 We are receiving an Application Error on http://www.t3log.info

Redmine Installation is in the /1_redmine Folder of our account

Calling dispatch.fcgi:13: uninitialized constant RailsFCGIHandler (NameError) - results in a Name Error as you can see

Same:
Calling dispatch.fcgi:1: undefined local variable or method `usr' for main:Object (NameError)

Can you please check and let us know what is wrong here. Thanks!

Dec 28 - 08:56 GMT
Servage - Julie

 Hello Andreas,

Thanks for submitting the ticket. Please use this path /usr/bin/ruby for the application.

Thank you :)


Kind regards,
Julie, Support Team Member
Servage Hosting

Dec 28 - 09:03 GMT
Customer

 Goodmorning Julie

I tried already with this - as you can read here:

I now switched back to this setting

here the dispatch.fcgi
usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
RailsFCGIHandler.process! '/var/log/redmine_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!
------------------------------------

But I am still receiving the same error

------------------------------------

I tried also the cgi version and had then another error that temp/mysql.sock isn't found. Perhaps that's the problem. Please help me to get this running I am really getting crazy and already contacted Steffan about ths missery here.

Simply go on my account and check the folder/files.

/1_redmine

http://www.t3log.info

Thanks
Andi

Dec 28 - 09:06 GMT
Customer

 Sorry Julie

here you can read all posts since you wrote last time about the same problem

http://apapococ.blogspot.com/

Dec 28 - 09:16 GMT
Customer

 You can even search google as this problem caused so much up in ranking that we are number one before servage itselfe! - all because the support hasn't solved the problem until now.

Search for

ruby servage
http://www.google.co.th/search?q=ruby+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

or for rails servage
http://www.google.co.th/search?q=rails+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

or even for
redmine servage
http://www.google.co.th/search?q=redmine+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

or typo3 servage
here we are at place 6 first page
http://www.google.co.th/search?q=typo3+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

or magento servage
here we are with the same problem like place 1 and to on place 3 and 4
http://www.google.co.th/search?q=magento+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

or lifetype servage
http://www.google.co.th/search?q=lifetype+servage&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

Now imagine how good it would be if we would place your adds on those sites. Lots of people meanwhile mailed us - but most of them only about even more problems with your support. I really wanna help you to improve this, but please first get the REDMINE running and the we will need to other Rails applications running next week too.

PLEASE PLEASE HELP and cooperate Thanks

Dec 28 - 10:00 GMT
Customer

 Any Solution available to get Redmine Running on Servage???

Dec 28 - 10:41 GMT
Servage - Julie

 Hello Andreas,

Kindly send us the server configuration required for Ruby on rails application. So that we can confirm regarding that. However the application should run properly as per server settings.

Please get back to us with the documentation of the application along with Ruby on Rails server configuration.

Thank you.

Kind regards,
Julie, Support Team Member
Servage Hosting

Dec 28 - 11:15 GMT
Customer

 Here is the REDMINE Website
http://www.redmine.org/

The actual Tar ball you can find in Folder: /xtar/redmine_** in my account

Here you find the sources:
http://rubyforge.org/frs/?group_id=1850

I am using the latest Version 0.6.3
http://rubyforge.org/frs/download.php/29428/redmine-0.6.3.tar.gz

In the WIKI you will find all specifications:
http://www.redmine.org/wiki/redmine/Guide

What is needed you will find here (SERVER Requirements)
http://www.redmine.org/wiki/redmine/RedmineInstall

it is only
* Ruby on Rails 1.2.6 or 2.0.2
* A database (see compatibility below)
----------------
AS Optional - if possible this would be nice to have if not then I need to use i.e. sourceforge:

* SVN binaries (>= 1.3), for repository browsing (must be available in your PATH)
* RMagick (Gantt export to a png image)
----------------

That is actual all you need to install Redmine on your server.

There is a prepared package available at http://bitnami.org/stack/redmine

As I have no ssh and no admin access I am not able to use it but perhaps it could help you setting up redmine sucessfully.

Thanks a lot Julie

Dec 28 - 13:07 GMT
Customer

 Hi Julie

Any Progres in the Redmine Case?

Dec 28 - 14:57 GMT
Customer

 Hi Julie

Why are you asking for manual and more and I send you all what you need to get Redmine as admin running and NOTHING Happened since?

I am again loosing 1 full day because your support is not helping at all!
Application error
Rails application failed to start properly

This will be published again online in our blog.
Enjoy reading. we are already number one with many searchwords concerning servage Hosting and its support
Posted by at No comments:
Labels:

Please inform the owner - YOUR BOSS! about the Problems here in

Please forward the whole Case and all former Support Requests to Steffan. Danke!

Servage GmbH
Steffan
Neustadt 16
24939 FLENSBURG
GERMANY

phone: +4946116098358
fax-no: +4946116098359
email: ssf@servage.net
email: sales@servage.net
email: patricia@servage.net
Posted by at No comments:
Labels:

RATING OF SUPPORT NO MORE WORKING

Dec 28 - 06:47 GMT
Customer

 Hi Your Rating System is no more showing up! Andi

Dec 28 - 07:01 GMT
Servage - Peter

 Hello Andreas,

Thank you for submitting the ticket.

Please do elaborate the issue so that we can assist you in better way.

Kind regards,
Peter, Servage - Support
Servage Hosting

Dec 28 - 07:36 GMT
Customer

 Das ist kein Problem von unserer Webseite, es ist EUER Rating System, dass gerade abgeschaltet wurde, wohl um weitere negative Bewertungen zu vermeiden.

Genau gesagt: Klickt man auf CLOSE and RATE THIS TCKET erscheint kein Rating mehr.
That's it

Bitte bringt endlich REDMINE auf eurem Server zum Laufen. Ich warte nun schon eber eine Woche auf qualifizierte Hilfe von Euch - ohne Erfolg!

Dec 28 - 07:51 GMT
Servage - Peter

 Hello Andreas,

Thank you for the reply.

Please do elaborate the issue in simple english so that we assist you in better way.

Kind regards,
Peter, Servage - Support
Servage Hosting

Dec 28 - 07:53 GMT
Customer

 Hallo Peter

KOPIERE soch nicht deinen vorherigen POST. BITTE! sondern beantworte die Fragemn die man dir stellt.

Dec 28 - 07:54 GMT
Customer

 As Servage is a German Company you should be able to speak German!

Dec 28 - 07:59 GMT
Customer

 Which Part of India is your Call Center situated?

Dec 28 - 07:59 GMT
Servage - Peter

 Hello Andreas,

Thank you for the reply.

Please do submitt the request in simple english language.

Kind regards,
Peter, Servage - Support
Servage Hosting

Dec 28 - 08:10 GMT
Customer

 I submitted the REQUESTS since over one week in simple English but until now NOBODY of your staff has solved the Problem, perhaps they aren't able to understand the english language to good.

Read all our previous posts here on our Blog, we are receivin huge amout of clicks since we hold this blog as people seem to be interested about what SUPPORT means to SERVAGE.

But read yourseve:
http://apapococ.blogspot.com/

------------------------
I am angry with you - as you took my money, you took my time - which means a lot more money as time is money, you even are taking our customers, as you promised things you are not holding.

I hope this is simple enough English for YOU - the so called PETER: By the way, what is your real name - or are you hiding it?

------------------------
Get REDMINE on http://www.t3log.info running and everything will be much much more successful for you and also for us and we even could collaborate . But if this isn't happening I need to continue writing about you in lots of Reviews all around the world.

Sorry for that.

Simply do your JOB and then I can do MY JOB! GET REDMINE RUNNING LIKE PROMISED DAYS AGO!
Posted by at No comments:
Labels:

RUBY ON RAILS CHAOS AT SERVAG HOSTING

Dec 28 - 07:33 GMT
Customer
Sorry, but where is your support you are advertising. Since over one week we are focusing a major problem and get no sufficient help in this case. You promised that the admin will check but nothing happened and still no answer.

Better you should start reading at the END > scroll down

Read more about all what happened in tis case here: http://apapococ.blogspot.com/
go to Servage Hosting and search for Redmine or Ruby on Rails

or search in Google for
Ruby on Rails Servage
------------------
We still have this application error - WHY IS NOBODY - even not the ADMIN you talked about able and willing to help and assis there?
------------------

Don't you wanna chane your Image?

-------------------
Disadvantages to using Servage:

* Servage web hosting does not provide adequate statistics (no search engine information, etc)
* Servage has NO guarantee. If you have any problems, even within the first 30 days you cannot get any money back.
* Servage does not have any live support (phone or live chat), they do not even provide a physical address.
seen here: http://www.wideopendoors.net/design/servage.html
-------------------
or here: http://www.reviewstream.com/reviews/?p=13467
The Downside of Servage
1. You have to pay yearly. Therefore if you are suspended or unhappy with the Servage, it is hard to get your money back.
2. Sometimes, the support can be vague. It seems like they copy and paste information, instead of typing it.
3. You can be suspended if your bandwidth reaches the limit for the day.
4. You are suspended if you reach 400000 hits.
5. FTP is limited to 50kb/s, if you have high speed connection, uploading would still be slow.
6. FTP times out very much.
7. No Cpanel
Servage calculates the bandwidth daily, unlike a few other hosts. The upside is you won’t have all the bandwidth taken in three days and have the remaining month none (therefore the site is down for a long time)
However, if you do not use the allocated bandwidth for one day, they do not give you the extra unused bandwidth for the following day. ... From personal experience, if I could afford more, I would move. They are not bad, but there are things they need to work on.
Rating: 4
---------------------
or here:http://www.v7n.com/forums/web-hosting-forum/20128-servage.html
This company claims to set up most sites within 30 minutes. Well.. they took the money from my account in 30 minutes, but over 2 weeks later and I still did not have an account with them. Despite requesting a refund on 5 occasions, I am still waiting and have had to threaten legal action against them. Each time I write to their accounts they keep requesting the details which I registered with them so they can find my account. I DON'T have an account with them! They failed to give me one! They just took the money and despite repeatedly telling them and giving them all the details I possibly can, I just keep on getting the same lack of response. My advice is to avoid this company like the plague, the have showed blatant incompetence in all respects.
---------------------
Just a bit below from NICK
---------------------
SERVAGE SUCKS
Servage is the worst. I'm from India and went for it 'cause my friend suggested. If the site doesnt generate lots of hits then are ok. For 6 months I was working on the site they were very kind then when I launched the site the first day I got 2,40,000 hits and by evening they had suspended the a/c. Can u imagine that? The bandwidth was well within limits and so was the space. I was told some crap about PHP load.

I managed to keep the hits within 2,00,000 since then but today within 2 weeks they suspended the domain itself & are asking me to go for a new one. Now they say CPU load. Everytime they come up with some new technical term to justify their incompetency.

They dont even bother to email or reply when the site is down. Neither do they suggest ways to reduce the so called load.

I lost my online business and customers due to them.

STAY AWAY FROM THEM LIKE PLAGUE.

Is there a place where we can complain the fraud & shut them down forever?
------------------------
even further down webhost 2007 writes
------------------------
Though a DNS change within 1 hour reduces traffic with 80%, they refused to respond to let our pages stay up. We asked if they'd kindly let our page up as a redirect, they simply did not respond.

More dishonest service is hard to find. If you have very low traffic, it may work ok. But their ads are incorrect and they should be closed by a court for such behavior. Nothing is worse than getting unwarranted downtime not violating any policy. Servage guarantees 99,98% uptime, but in reality they make sure you have downtime by bad intent...

The funny part is that they claim to host large sites with more than 3 mill. pageviews per day. But after 30,000 pageviews, the suspend your account without warning or even a small redirect to avoid downtime!

If you know a lawyer wanting to sue them, I'd be happy to assist. I'll now ask for the 5-day money back guarantee, but knowing such persons I assume I need to ask credit card company for a charge back.
-------------------------
ACTUALLY YOUR IDEA IS GOOD _ SO WHY PEOPLE WANNA SUE SERVAGE
-------------------------
We believe that our name describes our company well as it is our goal to serve our customers while always keeping our systems up-to-date with the most modern hard- and software.
-------------------------
BUT Julius Thijssen writes just below about it:
here: http://hostjury.com/reviews/Servage
-------------------------
I wish I had read these posts earlier. I've just lost 30 Gigabytes of storage there. And all BY THEIR OWN doing, entirely their decision and their loser-personnel. Nothing of it was my fault or related to overuse or anything close to that (you can find the emails in WHT forum), just amateurs too lazy to make backups or use their heads moving your account around like they're playing with apples or something, without even telling you about it. Idiots, is all I can say, they are absolute and utter fools.
-------------------------
he continues:
-------------------------
So yeah: AVOID SERVAGE AT ALL COST! Even if you're tempted, trust me: Don't do it. Their customer support is a big bunch of liars, no name is real either. They make promises they never keep in almost every message.
------------------------
this sounds like our experiences at the moment too!
------------------------
And if you're still a Servage customer: LEAVE NOW. Get your data out of there while you still can. I genuinely HATE them now, and I rarely hate anyone. They give a bad reputation to Danish and Northern German citizen. The worst IT-anonymous bunch I've EVER encountered. For crying out loud, I wasn't even using much of what I was entitled to!
------------------------
So you are in Flensburg - That's fine as then German law will take place :-) as you are advertising things you don't provide
------------------------
BUT SERVAGE SUPPORT CAN CHANGE AS JULIUS WROTE FURTHER
------------------------
Scott, Support

Servage Hosting"

Strangely though, the data isn't old at all. It's the exact same data the way I left it 30 hours earlier. I do notice that server response and download speed have gone WAY up as well. Just had to tell you this, so the review is true and complete. They've more than made up for their mistake(s).

I'm not sure if I'll be staying with servage forever, but they made VERY sure I would, for now I'm a happy camper again..

The Support rating should have an extra option added to the list: "Strange". Their support is actually not bad, it's just very weird. They change from being cold robots to nice friendly tolerating humans. They alter from BOsFH to lovable admins. You just never know what to expect or when..
---------------------
Alan Myers here: http://hostjury.com/reviews/Servage
---------------------
The pricing would be good if they could do all they claimed to be able to do. Unfortunately they don't hit the mark for me on any of their claims. The technical support is 'basic' to say the least. - They really don't seem to have the technical ability to manage the hardware
---------------------
Here is even a Writer about Servage collecting your Threads already from your support - interesting how similar they sound to us here: GLEN >>
--------------------
I guess there is no need to talk about reliability of a site who's tech support have no clue about what they are doing?

Just read following ticket content (from down up) and decide for yourself. Considering that I placed a ticket 10 hours after actual fail happens - make your own conclusions. Do you really want to loose your Web site; your backups; your files? Do you really want to get a lousy support?

Sign for Servage then.
...-
-----------------------
YAKUMO Adds
a BIG WARNING for SERVAGE HOSTING
-----------------------
http://hostjury.com/reviews/Servage
I'm a servage customer for almost a year now and let me warn you people, STAY AWAY FROM SERVAGE! From the start we were losing 1 or two folders which wasnt a big deal but recently, we lost the whole main directory! And of course servage said "it wasn't our fault". I find it hard to believe that they are unable to trace where a whole folder (holding more than 20 GB) went. After a few days, my friend also lost her whole directory, nothing was left from her website and again servage said it wasnt their fault and they dont really try to check what's going on.

Reason why you need to AVOID servage:

1. Poor support. They dont know a jack what's going on and they are painfully slow. I asked why my site was deleted, and they said they don't know why.
...
----------------------
KON-TIKI about your support http://hostjury.com/reviews/Servage
----------------------
This host's a total ripoff.

When we first put our site there, we had daily lag from about 5pm til about 6am. We contacted tech support of Servage about this, and they always gave one of these two answers:

1) Either they waited til the problem period was over and said: "I just tried your site out and it loads just fine"

2) They offered to move the site to a different cluster. We once went ahead with this, which resulted in a day downtime, but the problem remained.

After 3 months, they finally said: "Then it can be difficult to say what it wrong. This is shared hosting and it could be that another customer used a little more resources than allowed." Shouldn't they have had logs of it, and keep each and every account completely separated from the others? I know that that's the normal way of business for hosts, to make it so one customer doesn't affect another's account.

The problem wasn't solved after that, though. The lag was gone most of the time, but we still kept having near-daily SQL connection failures (as my inbox can prove, as each failure comes in there), and there was still a regular downtime of at least 4h every two weeks.
-------------------------
ALEX on the same site below writes
-------------------------
They have confirmed that their downtime was far from OK, which already breaks the hosting services agreement immediately, but they refused to make moneyback or even at least partial refund. Instead they replied with:

Servage - Steffan: “I have added one free month more - it is really the best I can do..”

Another free month of shame, no, thank you, Servage.

Think twice before going to Servage repeating my mistake!
------------------------
Richard below anotherone who wanna sue you WHY???
------------------------
Hi paid for 6 months of hosting up front (Bad mistake). All was OK for about 2 weeks then they suspended my account becuase of a DDOS which I think didn't happen. They refused to enter into any discussion about the DDOS and I'm now seeking legal advice re suing them. DO NOT TOUCH THEM EVER AS THEY ARE THEIVES! Best regards, Richard Georgiou.
-------------------------
JPearson
-------------------------
Servage also tried to make it look like they operate out of the United States by putting up a U.S. flag in their site on their home page. This is far from the truth as they are operated out of Germany.
-------------------------
Vielleicht sollte man einmal die Staatsanwaltschaft einschalten um anchzuforschen was hier wirklich vorgeht und we hier was verbockt. Die webseite traegt zumindest kein Impressum wie es dem deutschen Recht entsprechen wuerde was meint ihr.
-------------------------
Nun ehrlich gesagt habe ich kein Interesse daran Euch zu schaden, ich moechte nur die Ruby on Rails Redmine zum laufen bekommen und da warte ich nun schon seit Tagen auf eine Antwort.
Das Euer Support nicht qualifiziert ist ist klar abgesehen von der sogenannten Julie, die vielleicht August Nimmerlein heisst.

Das spielt auch keine Rolle.

Bringt bitte endlich REDMINE auf unserem Account zum laufen
Danke!


Dec 28 - 07:52 GMT
Customer

 http://www.servage.de > wird weitergeleitet auf http://www.servage.net - wodurch der eindruck entsteht es sei eine amerianische Firma, was Servage ja bekanntlich NICHT ist - oder?

Sei es drum bringt doch bitte die Redmine Sache zum Laufen. Ich erstelle ja u.a. auch eine der groessten Multidomain Seiten auf Euren Servern und im Moment denke ich eher dem Kunden zu empfehlen woanders seine Seitezu Hosten. Diese Seiten haben Euch in den Verganagenen Jahren gigantisch viel zulauf gebracht, da die in Google ganz oben mitschwammen. Wir benoetigen Redmine ganz ganz dringend, da wir Termine bei UNSEREM INTERNATIONALEN KUNDEN einhalten muessen. Au geht's bringt es endlich zum laufen. Danke!
Posted by at No comments:
Labels:

RUBY ON RAILS CAN'T FIND DATABASE RAKE ABORTED

Dec 28 - 05:40 GMT
Customer

 Calling http://www.t3log.info Redmine Installation which is placed in Folder /1_redmine

You can't execute:

rake aborted! No such file or directory - /tmp/mysql.sock

ALL SETTINGS ARE MADE LIKE FROM YOU ALREADY SUGGESTED.
http://apapococ.blogspot.com/

Dec 28 - 05:44 GMT
Customer

 where is your mysqld.sock or mysql.sock

Dec 28 - 05:47 GMT
Customer

 rake aborted! Permission denied - db/schema.rb

Dec 28 - 05:50 GMT
Customer

 Changing schema.db to webserver results in:

rake db:migrate RAILS_ENV="production"
(in /mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine)

Dec 28 - 05:56 GMT
Customer

 Strange PhpMy admin behavour

it is NOT showing the tablkes in the right column It shows 0 while it is showing all tables in the center. I have already reloaded twice

https://phpmyadmin-srv1.servage.net/phpMyAdmin/

Server: mysql1025.servage.net - Database: rmt3linfo071224

Dec 28 - 05:58 GMT
Customer

 Not populating the database with default data

rake redmine:load_default_data RAILS_ENV="production"

Dec 28 - 06:00 GMT
Customer

 IS THERE ANY SUPPORT HI?

Dec 28 - 06:11 GMT
Customer

 ANY SUPPORT AVAILABLE - You are advertising 24/7

Dec 28 - 06:22 GMT
Customer

 Hmm NO SUPPORT AT ALL AT SERVAGE HOSTING

Problem: Redmine - Ruby on Rails Application - still shows application error since over 1 week and nobody is helping to SOLVE this problem!
Posted by at No comments:
Labels:

DOES SERVAGE HOSTING HAS VALUABLE SUPPORT?

Dec 28 - 03:58 GMT
Customer
The answers seems to be very short and clear NO?

Since
Dec 21 - 12:02 GMT
http://apapococ.blogspot.com/2007/12/nameservers.html

We are testing SERVAGE HOSTING - especially its Support which is until now the worst we ever had.

Prepared paste and copy answers
they are not reading the complete posts
Answering only concerning ONE little problem where a prepared paste and copy answer fits and the rest will be skipped

They advertise i.e. RoR - Ruby on Rails Support - but Actually they are not able to get i.e. REDMINE a very well known RoR application running on their servers.

Read more about RoR on Servage Hosting and how the Support Team helps here and judge by yourself.
http://apapococ.blogspot.com/2007/12/redmine-on-servage.html
http://apapococ.blogspot.com/2007/12/redmine-ruby-on-rails-at-servage.html
http://apapococ.blogspot.com/2007/12/redmine-on-servage-hosting-3rd.html
http://apapococ.blogspot.com/2007/12/magento-redmine-ruby-on-rails-not.html
http://apapococ.blogspot.com/2007/12/dec-27-2007-0146-gmt-ruby-on-rails-on.html
http://apapococ.blogspot.com/2007/12/legal-information-about-servage-hosting.html
http://apapococ.blogspot.com/2007/12/ruby-on-rails-redmine-on-servage.html
http://apapococ.blogspot.com/2007/12/redmine-not-working-on-servage-hosting.html
http://apapococ.blogspot.com/2007/12/redmine-not-working-on-servage-hosting.html

Since a Weel they even don't give qualified answers concerning the real problem. REDMINE gives an Error Message? The answer WHY hasn't been even tried to discover.

---------------

At Servage Hosting you will have no SSH Access. Therefore for some actions you need assitance. Some friendly Staff from Servage will assist you here. Unfortunatly they aren't working always and very very rare. Those Staff Memberwith the preconfigured answers are really ruing the good image of servage in public with their awful support.

Like the problem of REDMINE or any other Ruby on Rails Application running on Servage Hosting you will need a friendly Support Member to get our application running due to the fact of a missing ssh access.

Another example of Servage Support Members imcompetence:

You have just unpacked a file which has also created (unpacked) symlinks. All these Symlinks will be belonging to the SYSADMIN. Therefore you can't delete them!

i.e. You wanna install TYPO3 a high quality Enterprise Content Management on Servage Hosting and unpack the Dummy Package. This will create lots of Symlinks. If you are running several TYPO3 instances from ONE Source you need to delete the typo3_src symlink but this won't be possible due to wrong ownership.

The workaround is renaming. On a developing site you perhaps have to rename your typo3_src several times which means you will have again and again to rename the symlink and your folders will be overwhelmed by actually unused symlings which can't be deleted. You have to ask the Staff to assist you but only a few Servage Support Members will really help you. Read more here and compare:
http://apapococ.blogspot.com/2007/12/not-able-to-delete-filesfolders.html
http://apapococ.blogspot.com/2007/12/file-not-deletable.html
http://apapococ.blogspot.com/2007/12/dec-27-0851-gmt-customer-current-path.html
http://apapococ.blogspot.com/2007/12/dec-27-0851-gmt-customer-current-path.html
http://apapococ.blogspot.com/2007/12/dec-27-1923-gmt-customer-we-cant-delete.html
This is actually a very simple problem to solve as they only need a routine after unpacking files and foldes and symlinks to give them the right ownership

If you need to zip. i.e. a complete folderstructure for BACKUP REASONS then you should know that this is not at all possible at SERVAGE HOSTING. If you are not the lucky one getting to one of the RARE friendly supporting Staff then you will be really lost at Servage trying to Backup your site.

They haven't implemented a BACKUP function and even not a COPY function which would help also to do some Backup. Therefore, if you are Hosting on Servage Hosting you will need another COMPANY with VERY GOOD and QUALIFIED SUPPORT to assist you with there knowledge and contacts to the servage staff. Then you can get many things running and Servage might be a very good place for your sites.

The Provided SSL Certicicate is not accessible when called and will block you site. Also here you won't get any help but nice trials and offers to buy another much more expensive product they are offering. But even here they aren't able to rovide you better information or knwoledge about how to implementt. Perhaps those more expensive Rapid Share Certificates aren't working ata all and you will run into a money grave at Servage Hosting.
Who knows?

If you need UTF-8 Support you will run in multiple problems at Servage if you are not knowing how to achieve it. All their reconfigured scripts will install only old latin_swedish_ci Versions which are useless if you wanna use utf-8.
You might ask another Company to assist you in this case.

RESULT:
MAGENTO running but without SSL
http://apapococ.blogspot.com/2007/12/magento-on-servage-hosting.html
REDMINE not running at all
RUBY on RAILS might be there but won't work (absolutly no support)
LIFETYPE working fine in a multisubdomain setting
TYPO3 running but you will have Problems with your SYMLINKS and you always need to switch owners while updating your extensions.

-------------
Thanks for your patience and in participating in this test.

We hope it will help you to improve your support and will gain you more and more customers as SERVAGE offers a god product probably the best shared product with the worst of all support at the moment.

I would like to thank Julie, Adam

We hope you replace the following Support Memebers soon by qualifies staff or simply try to mentor them much more and train them better: Victor, Peter, Scott, Josh, Jacob, Bob, John, Steven, Nick, Patricia, Rick, Sam, Mark

From 30 THREADS only 3 got solved sufficiently all others were timed out after hours and days of no response orterminated by really unqualified cpy and paste answers.

We would like to thank Julie and Adam for their support and also all people who made this test possible and who pointed us to servage clustered hosting Thank You!

We all hope that thigs got changed at servage very soon so that quality is really again quality at Serage Hosting.

Dec 28 - 06:23 GMT
Customer

 Anybody here for answering?

Dec 28 - 06:46 GMT
Customer

 NO SUPPORT AT ALL AT SERVAGE HOSTING THIS TIME I GUESS - NO 24/7
Posted by at No comments:
Labels:

RUBY ON RAILS APPLICATION NOT WORKING ON SERVAGE HOSTING

Dec 28 - 02:45 GMT
Customer

 Application error
Rails application failed to start properly

We were able to create the database but still get this application error.

It seems to be a TCP ERROR - which means that an address is already in use - could you please check.

Please check also the .htaccess configuration as it seems that the one you promote in your FAQ isn't the right one

----------------------
Here the dispatch.fcgi
----------------------
usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
# RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
# RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
# RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!
-----------------------------------

And Here the .htaccess in public:
-----------------------------------
# General Apache options

AddHandler fastcgi-script .fcgi


AddHandler fcgid-script .fcgi


AddHandler cgi-script .cgi

Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
# RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /public

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f

RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.cgi [QSA,L]


# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

---------------------------------------------
Problem URL:
http://www.t3log.info

---------------------------------------------
Problem URL:
http://www.t3log,info
---------------------------------------------

Dec 28 - 03:13 GMT
Servage - Peter

 Hello Andreas,

Thank you for submitting the ticket.

I suggest you to please once again go through the following installation path.

You are able to find more information about Ruby on Rails (ROR) at this url:
http://wiki.rubyonrails.org/rails

Here is the path you will need when installing Ruby on Rails script:
/usr/bin/ruby


Secondly the installation path for ror:-

Virtual host path to mount your root is yourapp/public.

permissions:

chmod 755 to the all folders/files in your application

change ownership of: yourapp/log/ yourapp/tmp/ (recusive, to 'webserver')

Paths:

change the path in yourapp/public/dispatch.cgi|fcgi|rb

to #!/usr/bin/ruby, from your local path.

.htaccess corrections: (to enable fast cgi)
This will enable your application, to use fcgi, with is about x10 faster then normal cgi

# General Apache options
AddHandler fcgid-script .fcgi
#AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi
Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
#RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
#RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

Kind regards,
Peter, Servage - Support
Servage Hosting


Dec 28 - 03:44 GMT
Customer

 Hi Peter we have done this already with Julie and some others. Simply read all posts about REDMINE and RUBY on Rails or do simply a SEARCH in the INTERNET for the complete passag you have just posted. You will find lots of entries - ALL COMING FROM SERVAGE PROBLEMS WITH RUBY ON RAILS and the Support which can only paste and copy prepared answers.

So nice Peter. Put away the mousebutton to copy and paste and start using your head instead for finding a solution for this problem which gets us stock since over one WEEK now.

You can compare the parts you pasted with the Parts I pasted from our scripts. i.e. you could create to text documents containing the same parts and do a diff and you will see that they are identical.
you could also use pspad (its an editor which compares those parts and its free. http://www.pspad.com/
------------------------

So RESULT is:
Still RoR REDMINE isn't working on Sevage.
Can and are you willing to assist in finding the problem

YES ---- NO ????

Dec 28 - 04:13 GMT
Customer

 Come on Peter

where is the problem, why is this Application Error showing up?
Andi

Dec 28 - 04:27 GMT
Customer

 Hi Peter
You give in the same thread 2 different advices which oppose themselves. What is the right one and plaese correct your FAQ accordingly as they are wrong!!!
--------------
You are writing
--------------
Here is the path you will need when installing Ruby on Rails script:
/usr/bin/ruby

--------------
You are not writing the install path
--------------
Secondly the installation path for ror:-

==
Our REDMINE is called by http://www.t3log.info
it resides in folder /1_redmine/ on your server
Should we now write (and where please???)
"-"
or
"1_redmine"
or
"/1_redmine"
or
http://www.t3log.info
or
/1_redmine/public
or
1_redmine/public
or
1_redmine/public/
or
/1_redmine/public/
==

Virtual host path to mount your root is yourapp/public.

permissions:

chmod 755 to the all folders/files in your application

==
We have changed them to 755 - actually they are since days 755
==

change ownership of: yourapp/log/ yourapp/tmp/ (recusive, to 'webserver')

==
We have changed them to webserver recursily - actually they were like thois since days
==

Paths:

change the path in yourapp/public/dispatch.cgi|fcgi|rb

----------------------
Above you just told us it is usr/bin/ruby - why now #!/usr/bin/ruby ???
----------------------

to #!/usr/bin/ruby, from your local path.

==
What do you mean with "from your local path" can't you simply write the right path in your FAQ??? This would make things much much easier
==

------------------------
Compare the follwin .htaccess part with the one we already posted - its the same
------------------------

.htaccess corrections: (to enable fast cgi)
This will enable your application, to use fcgi, with is about x10 faster then normal cgi

# General Apache options
AddHandler fcgid-script .fcgi
#AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi
Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
#RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /myrailsapp

----------------------------
Do we need to rewrite the BASE ???
----------------------------

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
#RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

Dec 28 - 04:35 GMT
Customer

 Hi Peter

Why This

#AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi

shouldn't it be:
#AddHandler fastcgi-script .fcgi
AddHandler fastcgi-script .fcgi

Dec 28 - 04:42 GMT
Customer

 After correcting from
AddHandler cgi-script .cgi
to
AddHandler fastcgi-script .fcgi

we are receiving ow the following message USING YOUR .htaccess (paste and copy :-)

Error Message:
usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
# RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
# RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
# RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!

Dec 28 - 04:45 GMT
Customer

 or - if we change back to #!/ it looks like this:

#!/usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
# RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
# RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
# RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!

Dec 28 - 04:46 GMT
Customer

 Can you please check the logfiles like mentioned we enabled them!

#!/usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!

Dec 28 - 04:50 GMT
Customer

 Still no changes

Dec 28 - 04:52 GMT
Customer

 Error http://www.t3log.info (message from - it won't get processed!!! 1_redmine/public/dispatch.fcgi)

usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
RailsFCGIHandler.process! '/var/log/redmine_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.proce

Dec 28 - 04:54 GMT
Customer

 Changing back to
# General Apache options
AddHandler fcgid-script .fcgi
#AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi
Options +FollowSymLinks +ExecCGI

in .htaccess results in
Application error
Rails application failed to start properly
-------------------------

Something seems to be wrong in the .htaccess you are providing. Can you please assist

Dec 28 - 04:57 GMT
Customer

 CHanged in .htaccess:
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
# RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

to

# For better performance replace the dispatcher with the fastcgi one
#
# Example:
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On
---------------
STILL THE SAME APPLICATION ERROR MESSAGE (.HTACCESS)

Dec 28 - 05:03 GMT
Customer

 Changed:

# RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
#RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

-----
TO
-----
# RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
#RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

------
ENABLE cgi instead of fcgi for testing
------
Leads to same Application Error

------
BUT
------
Additional Changing

usr/bin/ruby

to #!/usr/bin/ruby in dispatch.cgi

Gives the following Message:
Errno::ENOENT in WelcomeController#index

No such file or directory - /tmp/mysql.sock

RAILS_ROOT: /home81c/sub004/sc44977-AQJR/1_redmine/public/../config/..
Application Trace | Framework Trace | Full Trace

/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `real_connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:389:in `connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:152:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:82:in `mysql_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:262:in `connection_without_query_cache='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:230:in `retrieve_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in `connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/base.rb:763:in `columns'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:257:in `column_for'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:116:in `calculate'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:66:in `maximum'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/app/models/setting.rb:102:in `check_cache'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/app/controllers/application.rb:31:in `user_setup'

/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `real_connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:389:in `connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:152:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:82:in `mysql_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:262:in `connection_without_query_cache='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:230:in `retrieve_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in `connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/base.rb:763:in `columns'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:257:in `column_for'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:116:in `calculate'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:66:in `maximum'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:469:in `call'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:442:in `run'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:714:in `run_before_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:694:in `call_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:688:in `perform_action_without_benchmark'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/rescue.rb:83:in `perform_action'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/base.rb:435:in `process_without_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:684:in `process_without_session_management_support'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/session_management.rb:114:in `process'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/base.rb:334:in `process'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/railties/lib/dispatcher.rb:41:in `dispatch'
/home81c/sub004/sc44977-AQJR/1_redmine/public/dispatch.cgi:10

/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/vendor/mysql.rb:107:in `real_connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:389:in `connect'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:152:in `initialize'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:82:in `mysql_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:262:in `connection_without_query_cache='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection='
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:230:in `retrieve_connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in `connection'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/base.rb:763:in `columns'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:257:in `column_for'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:116:in `calculate'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/activerecord/lib/active_record/calculations.rb:66:in `maximum'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/app/models/setting.rb:102:in `check_cache'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/app/controllers/application.rb:31:in `user_setup'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:469:in `call'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:442:in `run'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:714:in `run_before_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:694:in `call_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:688:in `perform_action_without_benchmark'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/rescue.rb:83:in `perform_action'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/base.rb:435:in `process_without_filters'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/filters.rb:684:in `process_without_session_management_support'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/session_management.rb:114:in `process'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/actionpack/lib/action_controller/base.rb:334:in `process'
/mounted-storage/home81c/sub004/sc44977-AQJR/1_redmine/vendor/rails/railties/lib/dispatcher.rb:41:in `dispatch'
/home81c/sub004/sc44977-AQJR/1_redmine/public/dispatch.cgi:10

Request

Parameters: None

Show session dump

---
flash: !map:ActionController::Flash::FlashHash {}


Response
Headers: {"cookie"=>[], "Cache-Control"=>"no-cache"}

Dec 28 - 05:09 GMT
Customer

 This file is there!!! but it shows

No such file or directory - /tmp/mysql.sock

can you please check

Dec 28 - 05:12 GMT
Customer

 Hi Peter Where are you? Is the Servage Support still working?? YES / No?
Posted by at No comments:
Labels:

REDMINE NOT WORKING on SERVAGE HOSTING

Dec 27 - 21:56 GMT
Customer

 Application error
Rails application failed to start properly

We were able to create the database but still get this application error.

It seems to be a TCP ERROR - which means that an address is already in use - could you please check.

What RUBY Version are you working: 1.8.? and what Rails 2.? ?

----------------------
Here the dispatch.fcgi
----------------------
usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
# RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
# RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
# RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!
-----------------------------------

And Here the .htaccess in public:
-----------------------------------
# General Apache options

AddHandler fastcgi-script .fcgi


AddHandler fcgid-script .fcgi


AddHandler cgi-script .cgi

Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
# RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /public

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f

RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.cgi [QSA,L]


# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

---------------------------------------------
Problem URL:
http://www.t3log.info
---------------------------------------------

Dec 28 - 02:15 GMT
Support - Mark

 Hello Andreas,

You can check the RUBY and Rails version using the following URL:
http://c41.servage.net/phpinfo.php

Feel free to contact us again for further details. We will happy to assist you in a better way.


Kind regards,
Mark, Servage - Support
Servage Hosting

Dec 28 - 02:42 GMT
Customer

 Sorry MARK

BUT HOW STUPID IS YOUR SUPPORT AT ALL?

NOTHING HAS BEEN DONE!!! SINBCE 9 DAYS NOW !!! ONLY STUPID PRECONFIGURED ANSWERS LIKE YOURS !!!

You don't take care for customers
You don't read about the real problems
You only look for ONE perhaps matching word and post a small preconfigured command.

SORRY ABOUT THAT!

IT IS NOT SERVAGE - as SERVAGE HAS A GOOD OFFER AND A VERY GOOD PRODUCT but it is people like you who RUIN THE GOOD SERVAGE NAME IN PUBLIC caused by a COMPETLY UNQUALIFIED SUPPORT!!!

--------------------------------
READ HERE EXACTLY HERE!!!

REDMINE IS NOT WORKING SINCE 9 DAYS BECAUSE YOU OFFER SUPPORT IN YOUR ANSWERS BUT ACTUALLY DON'T DO ANYTHING. GET REDMINE and RUBY ON RAILS RUNNING ON YOUR SERVER AND WE ARE HAPPY - H A P P Y - AND GOD WILL TO!

Andi
Posted by at No comments:
Labels:
Subscribe to: Posts (Atom)