-
Notifications
You must be signed in to change notification settings - Fork 114
Installed patch, but unable to log into magento admin backend #23
Comments
php-pecl-memcache.x86_64 : Extension to work with the Memcached caching daemon These are available in the base repos on CentOS 7 - is that not what you want? |
Thank you so much for your reply, Darren. I had the server already set up using php 5 from the remi repo. So I followed the instructions on upgrading to php70 as outlined on webtatic. But under webtatic I was unable to find php-pecl-memcache at all, and I was unable to install it using pecl install memcache either. So are you saying I should use base repo? I am running centOS 6.7. Any help would be appreciated. Sincerely, Martin
|
Hello again. This time I upgraded to PHP 7 using the remi repo and it included memcache. So we are a step further here. However I am still unable to log in to Magento 1.9.2.4 admin (I did apply the patch Inchoo_PHP7 prior). What happens is strange. I go to the Magento admin login page and log in and I don't get a wrong password notice or nothing. Page just reloads to: .../index/index/key/30ffffede2aacc819a7739929a0ab3af/ (same login page). It should however log me in and go to .../dashboard/index/key/30ffffede2aacc819a7739929a0ab3af/ or something like that. I checked in system.log and found this: 2016-03-04T18:29:37+00:00 ERR (3): Recoverable Error: session_regenerate_id(): Failed to create(read) session ID: memcache (path: tcp://127.0.0.1:11211?persistent=1&weight=2&timeout=10&retry_interval=10) in /var/www/www.proproductssales.com/html/app/code/core/Mage/Core/Model/Session/Abstract/Varien.php on line 492 Anyone knows what is happening here? I really would like to test magento 1.9.2.4 on PHP 7. Seems really fast in the front end. Sincerely, Martin |
Seems like the same session error we already fixed for db and redis backends. But we never got to testing with memcache. If someone has got time to implement the same fix for memcache and make a pull request, it's welcome! |
So what can I do? Uninstall memcache, and use db and redis (I am sorry, but I don't know too much about db / redis for PHP). Please advise. Thanks. |
Hello all, It seems native php memcache extension currently has problem with session_regenerate_id(). Same situation was with php-redis few moths ago, php7 changed something related session_regenerate_id that broke similar php extensions. For example, it won't work if you simply try:
So, Magento is just using built in session handler for memcache, which isn't working at the moment. It seems php-memcache needs to be fixed, not Magento, and it will be eventually. I also tested memcacheD, which is newer extension and it seems memcached is working, so maybe it can be used instead in Magento. @mrlerch: I'm using Ubuntu, so different repos, I'm not sure what's the situation on CentOs, but try installing php memcached extension (it's php-memcached on Ubuntu) and change local.xml to something like this:
memcached instead of memcache, tcp:// removed for memcached. I never used memcached in production, but it works for me on my dev machine, login works. Hope it helps, |
Hello and thank you Ivan for the clear instructions. I was able to find and install memcached for php 7.0.4. I also made the changes in local.xml per your instructions, however here is a new issue now. Magento front end store page - blank entry in system.log: Here is another thing. I am really trying to get this setup for production. What is your hesitation with memcached instead of memcache? Is there another cache method that I could try? Here is what I have installed: [root@host log]# yum list installed php*
Oh yes, funny enough, phpMyAdmin runs perfectly fine (same nginx host as mangento - same web dir as a matter of fact). Thanks for any help you have for me Martin
|
Sorry, I am complete retard! I installed php7 and memcached and made the changes to the local.xml file, but didn't install the inchoo php7 patch - lol. That made a difference. So I am able to see, use (kind of) the front end and log in to the back end. Issues: AvaTax (from Avalara) (latest version 3.0.0) does not seem to work. Does not return tax calls, actually responds with an error message. under php 5.5 it workes just fine. How to trouble shoot this issue? Thanks |
What's the error message? |
So I can't find an error message in system.log. But in the AvaTax log inside Magento under Sales -> Tax - > AvaTax log I see an error message. And when I click on it I get a report with Request, Response, Additional The Requests seem to look identical to the requests under PHP 5.5. GetTaxResult Object
) Is there a better way to log what's going on and why there is an error? How do I enable logging in Magento's var/log folder for what is happening with this extension? Thanks. |
We can't fix extension incompatibilites here. @mrlerch, please check with extension maker. |
Hello,
So I installed the patch. I can access the magento site front end now, and the backend, but I can't log in to the backend (most likely not in the front end either). Here is the error message I am getting when I try to log in to admin:
Invalid Form Key. Please refresh the page.
Here is the error message in the magento system.log:
2016-03-03T04:22:59+00:00 ERR (3): Warning: session_module_name(): Cannot find named PHP session module (memcache) in /var/www/www.proproductssales.com/html/app/code/core/Mage/Core/Model/Session/Abstract/Varien.php on line 81
2016-03-03T04:22:59+00:00 ERR (3): Warning: session_start(): open(tcp://127.0.0.1:11211?persistent=1&weight=2&timeout=10&retry_interval=10/sess_2rvk3rvc73tp9pkdvkpecut234, O_RDWR) failed: No such file or directory (2) in /var/www/www.proproductssales.com/html/app/code/core/Mage/Core/Model/Session/Abstract/Varien.php on line 133
Please be advised that there currently does not seem to be a php 7 memcache installation via yum available. Does that mean that for now I have to revert back to PHP 5? Or is there another work around I can try. From what I saw the front end of Magento seems to be rocking fast with PHP 7
Please advise.
Thanks,
Martin
The text was updated successfully, but these errors were encountered: