blog.Resource
July 22, 2013

Something Neos Part II - Completing the installation on a hosted server

By: Florian Weiss

The shell newb strikes back

The following article will have a very prosaic approach - if you are just interested in the details and possible error sources, just skip to the "What you really came here for" part.

Hire a local composer

Regarding the composer problem from part I you might also consider the solution ChristianM suggested in #typo3-neos (chat.freenode.net):
Use composer locally and upload the files via FTP to the host. (This will take a bit longer but should work well)

Return of the Putty

The last time I stopped at setting up the virtual host because it looked like the installation would fail because of the virtual host.

The good news is, that I was able to set up the virtual host via the GUI (in my case "Confixx") - which did not allow me to do the according entry for choosing the "development" or "productive" setting (you defenitely want to go "productive" when the site goes live to prevent error messages from showing up) - but for the moment this will be enough.

My hoster confirmed, that the virtual host was setup correctly via the GUI and was kind enough to setup the server in a way that allows me to access the php error log via FTP (or shell).

From this I could learn - that the problem is not the virtual host - but the maximum nesting level.

PHP Fatal error:  Maximum function nesting level of '100' reached, aborting! 

Well - if you happen to encounter the same problems as I did I hope you have a hoster reacts fast or you aren't in a hurry.
After the nesting level had been increased, I ran into:

Execution of subprocess failed with exit code 255 without any further output. 

which occurs due to a problem with the memory limit. Long story short my hoster increased it to 256 MB from 128MB and the process could complete.

After all the partial installing and cache building you could encounter:

file_exists(): Unable to find the wrapper "resource" - did you forget to enable it when you configured PHP?

This happens when your cache is partially built - just throw away "Data/Temporary/" and you should be good to go again. (This info was brought to you by "radmiraal" of #typo3-neos)

Now we are getting somewhere

It's finally done - calling the domain with the postfix /setup (f.e.: http://www.yourdomain.com/setup) I see the setup screen which asks for my Firstname, Lastname, Username, Passwort, Database user, Database password and of course the database location.

I guess I don't have to tell you details about choosing usernames or passwords - but what is interesting is the database location with a default of 127.0.0.1 (There's no place like it)

After submitting my details I was very disappointed to encounter the following error:

SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 111

To get more details about the error "aertmann" of #typo3-neos suggested to run the creation process manually.
This can be done by entering the correct settings in "Configuration/Settings.yaml" (If you haven't got a demo structure you can copy the one from "Configuration/Settings.yaml.example") and running:

./flow doctrine:create

This specified the error to:

Schema-Tool failed with Error 'SQLSTATE[HY000] [2013] Lost connection to
  MySQL server at 'reading initial communication packet', system error: 111' while executing DDL: CREATE TABLE typo3_flow_resource_resourcepointer (hash VARCHAR(255) NOT NULL, PRIMARY KEY(hash)) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE = InnoDB

Well... that helped didn't it - I... still had no clue what went wrong.
Luckily "ChristianM" (did I mention #typo3-neos?) suggested to change 127.0.0.1 to "localhost" which worked like a charm.

But why did this work? 127.0.0.1 is the equivalent of locahost?
You can find the details at: forums.mysql.com/read.php - but the short explaination is that it depends on the bind address variable in the .cnf file. (so it could also happen that "localhost" doesn't work - but 127.0.0.1 does)

Choose your destiny (well actually the choice is not THAT epic)

Having resolved this issue I got the choice between importing the Neos Demo Site and creating a new site.
This is an either/or decision (you don't fill out the fields if you import the Neos Demo Site) and if you just want to checkout Neos with a ready template knock yourself out with the Demo Option.
It gives you a complete page to play with and test the options - but bear in mind, that you can't change your decision afterwards.
When creating your own page you'll have to do the setup again. (I deleted my typo3neos install from the server, deleted the database and started over - but as soon as you are good to go that only takes about 10 minutes)

If you choose to opt for your own page just choose a package name (for example Yourcompanyname.pagename)

What you really came here for

Words - sooo many words! Give us the shinies!
Ok I heard you -you get all my installation experiences in a handy flow diagram.

http://www.weissheiten.at/Install_flow_diagram.svg
(I'll also put it up directly on buzz as soon as I get the allowance to add files)

I hope you'll rejoin me next time when I do the basic setup of the page.

 

 

 

 

 


comments

No comments yet. Be the first to comment on this!

Sorry, comments are closed for this post.