Won't Install 5.7.0.1

Permalink
I was trying to install 5.7.0.1 for the first time and received an error after what appeared to be creating the DB tables and the admin user:

{"error":true,"message":"#0 [internal function]: Whoops\\Run->handleError(2, 'session_start()...', '\/hermes\/waloraw...', 147, Array)\n#1 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/symfony\/http-foundation\/Symfony\/Component\/HttpFoundation\/Session\/Storage\/NativeSessionStorage.php(147): session_start()\n#2 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/symfony\/http-foundation\/Symfony\/Component\/HttpFoundation\/Session\/Storage\/NativeSessionStorage.php(281): Symfony\\Component\\HttpFoundation\\Session\\Storage\\NativeSessionStorage->start()\n#3 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/symfony\/http-foundation\/Symfony\/Component\/HttpFoundation\/Session\/Session.php(89): Symfony\\Component\\HttpFoundation\\Session\\Storage\\NativeSessionStorage->getBag('attributes')\n#4 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Session\/Session.php(48): Symfony\\Component\\HttpFoundation\\Session\\Session->get('CLIENT_REMOTE_A...')\n#5 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Session\/Session.php(42): Concrete\\Core\\Session\\Session::testSessionFixation(Object(Symfony\\Component\\HttpFoundation\\Session\\Session))\n#6 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Session\/SessionServiceProvider.php(15): Concrete\\Core\\Session\\Session::start()\n#7 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/illuminate\/container\/Illuminate\/Container\/Container.php(498): Concrete\\Core\\Session\\{closure}(Object(Concrete\\Core\\Application\\Application), Array)\n#8 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/illuminate\/container\/Illuminate\/Container\/Container.php(425): Illuminate\\Container\\Container->build(Object(Closure), Array)\n#9 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/vendor\/illuminate\/container\/Illuminate\/Container\/Container.php(809): Illuminate\\Container\\Container->make('session')\n#10 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Support\/Facade\/Facade.php(52): Illuminate\\Container\\Container->offsetGet('session')\n#11 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Support\/Facade\/Facade.php(102): Concrete\\Core\\Support\\Facade\\Facade::resolveFacadeInstance('session')\n#12 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/User\/User.php(223): Concrete\\Core\\Support\\Facade\\Facade::__callStatic('has', Array)\n#13 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/User\/User.php(223): Concrete\\Core\\Support\\Facade\\Session::has('uID')\n#14 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/User\/User.php(47): Concrete\\Core\\User\\User->__construct()\n#15 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Package\/StartingPointPackage.php(238): Concrete\\Core\\User\\User::getByUserID(1, true, false)\n#16 [internal function]: Concrete\\Core\\Package\\StartingPointPackage->add_users()\n#17 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/controllers\/install.php(238): call_user_func(Array)\n#18 [internal function]: Concrete\\Controller\\Install->run_routine('elemental_full', 'add_users')\n#19 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Controller\/AbstractController.php(149): call_user_func_array(Array, Array)\n#20 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Routing\/ControllerRouteCallback.php(25): Concrete\\Core\\Controller\\AbstractController->runAction('run_routine', Array)\n#21 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Routing\/Router.php(59): Concrete\\Core\\Routing\\ControllerRouteCallback->execute(Object(Concrete\\Core\\Http\\Request), Object(Concrete\\Core\\Routing\\Route), Array)\n#22 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Support\/Facade\/Facade.php(116): Concrete\\Core\\Routing\\Router->execute(Object(Concrete\\Core\\Routing\\Route), Array)\n#23 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Application\/Application.php(281): Concrete\\Core\\Support\\Facade\\Facade::__callStatic('execute', Array)\n#24 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/src\/Application\/Application.php(281): Concrete\\Core\\Support\\Facade\\Route::execute(Object(Concrete\\Core\\Routing\\Route), Array)\n#25 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/bootstrap\/start.php(180): Concrete\\Core\\Application\\Application->dispatch(Object(Concrete\\Core\\Http\\Request))\n#26 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/concrete\/dispatcher.php(36): require('\/hermes\/waloraw...')\n#27 \/hermes\/waloraweb039\/b1550\/moo.teknoz\/clients\/teknoziz\/index.php(2): require('\/hermes\/waloraw...')\n#28 {main}"}{"error":{"type":"Whoops\\Exception\\ErrorException","message":"Unknown: open(\/var\/php_sessions\/sess_705a640e8852b36e272f0547691a9a1f, O_RDWR) failed: No such file or directory (2)","file":false,"line":0},"errors":["Unknown: open(\/var\/php_sessions\/sess_705a640e8852b36e272f0547691a9a1f, O_RDWR) failed: No such file or directory (2)"]}

TeKnoZiz
View Replies: View Best Answer
erniethepiper replied on at Permalink Reply
I seem to be having the same issue while installing on a fatcow server. The database table seem to build. I end up with 202 of them anyway and they are similar to what I have on 5.6 installs. I have double checked the chmod and made them 777 for all files and directories outside of the concrete folder itself. Any other ideas would be helpful.
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
LOL Mine is on a FatCow server as well. Going to check it on another of my servers...
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
I just tried it on one of the other hosting services I use, webhostinghub.com and am happy to say that it works there. Apparently, there is something wrong at FatCow. Have you submitted a ticket to them? I probably will, but their response time is pretty slow.
fischershaw replied on at Permalink Reply
Same issue. I posted elsewhere (http://www.concrete5.org/community/forums/5-7-discussion/install-stops-part-way-through-with-no-message/#662648). Did you find any resolution?
OKDnet replied on at Permalink Reply
OKDnet
Having the php memory limit set to 32MB is causing failures like this. I don't know about Fat Cow, but this is not an unusual setting for shared hosting, and while it was fine for previous versions of Concrete5, with 5.7 is is not.

Increasing to 128MB is definitely enough. I don't know if 64MB is enough or not.
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
I tried both 64 and 128 and got the same error both times. Sigh.
erniethepiper replied on at Permalink Reply
Could it be that he php version is only 5.3.13 and not 5.3.3? I saw somewhere that C5.7 needed the 5.3.3+. I'm not sure what is involved in getting Fatcow to upgrade but I may submit that request if I get the chance today.
erniethepiper replied on at Permalink Reply
Sorry, my bad. I shouldn't do basic math before coffee. 5.3.13 is way beyond 5.3.3.
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
:D
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
BTW they just contacted me and said:

We are currently still running version 5.6.0.1 on our shared hosting server and are not supporting 5.7 yet. At this time you will not be able to upgrade to that version until we roll that upgrade out server-wide. I apologize for any inconvenience this may cause you.

Yet I responded that I had been manually installing 5.6.3.1 and should be able to manually install 5.7.0.1 as well. We'll see what his reply is.
OKDnet replied on at Permalink Reply
OKDnet
Sounds like they move as slow as a fat cow. </grin>
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
Oddly enough, that was the fastest reply I've received from them in a very long time.
TeKnoZiz replied on at Permalink Best Answer Reply
TeKnoZiz
The solution to my issue came from this thread in the 5.7 discussion:
http://www.concrete5.org/developers/bugs/5-7-0-1/wont-install-5.7.0...
erniethepiper replied on at Permalink Reply
That worked for me as well. Thanks!
JeffPaetkau replied on at Permalink Reply
JeffPaetkau
Hi,

Yes,

Adding

<?php
return array(
    'session' => array(
        'handler' => 'database'
    )
);


to application/config/concrete.php worked for me.

Jeff
fischershaw replied on at Permalink Reply
The bug is marked resolved. I am wondering if manually adding this when a failure occurs is the resolution, or if some test on the temp directory will be made so that Concrete know what to do by default?
andrew replied on at Permalink Reply
andrew
It sounds like a host that has an unwritable directory set as the session directory is misconfigured. We wanted to allow listen to PHP regarding tmp directories and the link, so that we didn't have our own tmp directories filled with millions of files that weren't being garbage collected, etc... That said, if there's a better way we could grab the tmp directory then we'd be interested in that.
fischershaw replied on at Permalink Reply
Which PHP tmp setting are you looking at? Shouldn't Concrete just check access permissions during the initial system check and either give a green checkmark, or allow one to use the alternative configuration? Just like it should also check memory_limit for 128MB and provide a green checkmark for that.
andrew replied on at Permalink Reply
andrew
That would help. We will try and detect it prior to installation.
AlValSC replied on at Permalink Reply
I'm getting similar behavior in Azure. memory_limit does not appear to be an/the issue.

I am unable to view the aforementioned resolved bug to attempt and implement workaround.