Drupal 8 memcache :- is any one installed memcache module in drupal 8 - drupal-8

View(active tab)
Edit
Status message Forum topic Drupal 8 memcache :- is any one installed memcache module in drupal 8 has been created.
Posted by dwivedi017 on 22 May 2017 at 11:14 UTC
Is any one installed memcache module in drupal 8 ? Please let me know I am getting errors while installing memcache moule.
Error is :-
[Mon May 22 16:34:09.466660 2017] [:error] [pid 4812:tid 1656] [client ::1:60911] Uncaught PHP Exception Drupal\Component\Serialization\Exception\InvalidDataTypeException: "A YAML file cannot contain tabs as indentation at line 8 (near "\t")." at D:\PHP server\xampp-win32-5.6.30-0-VC11\xampp\htdocs\drupal_8_4\core\lib\Drupal\Component\Serialization\YamlSymfony.php line 39, referer: http://localhost:8012/drupal_8_4/admin/modules
[Mon May 22 16:34:49.425660 2017] [:error] [pid 4812:tid 1648] [client ::1:60913] Uncaught PHP Exception Drupal\Component\Serialization\Exception\InvalidDataTypeException: "A YAML file cannot contain tabs as indentation at line 8 (near "\t")." at D:\PHP server\xampp-win32-5.6.30-0-VC11\xampp\htdocs\drupal_8_4\core\lib\Drupal\Component\Serialization\YamlSymfony.php line 39, referer: http://localhost:8012/drupal_8_4/admin/modules

Yes. We can integrate memcache with Drupal 8. And it works perfectly fine.
From your error, it seems that in one of your module, there is a syntax error in yaml file. Extra tab is there. It is not evident from your posted error that the issue is with memcache module.
Check in your custom module's yaml file for extra tab at line 8.
This could resolve the issue.

Related

Django project crashes server when admin backend is accessed

Problem
I am running apache2 on my local ubuntu server. I set up a Django project using django-admin startproject site and set up my virtual host to use a WSGI Daemon process to run the Django project. This worked and the site is accessible through its IP 192.168.1.3.
When I go to /admin, it allows me to log in and see the initial backend but loads for 5 minutes then goes to a 500 error when I click anything or reload, even when trying to access the non-admin index page. This persists until I run systemctl restart apache2 and completely restart apache or wait ~10-15 minutes until it fixes itself (only to break again immediately if I access /admin pages).
Versions
Django version 4.1.5
mod-wsgi version 4.9.4
My Attempts
If I run the project with python manage.py runserver, I can access it on 192.168.1.3:8000 and fully use the /admin backend, even creating new users, etc. I then thought it was the WSGI Daemon process somehow messing it up, so I followed the linked section of this page: https://pypi.org/project/mod-wsgi#using-mod-wsgi-express-with-django and ran the site with python manage.py runmodwsgi. The site completely works on 192.168.1.3:8000 along with the /admin, and I can create new users etc., which points to it having nothing to do with the WSGI setup (as well as the non-admin pages working fine on the virtual host WSGI).
I have fully deleted and restarted the Django project, as well as setting up new virtual host .conf files with the proper WSGI information, etc.
I read about an /admin loading issue back in Django 3.0, but I am on 4.1 so that is unrelated.
I am at a complete loss at what the issue could be at this point. Why won't my /admin section work on the virtual host??
EDIT:
The issue is actually definitely the WSGI somehow. I am getting this is my apache error log:
[Sun Jan 29 09:27:12.388714 2023] [wsgi:error] [pid 67623:tid 140212873184832] (70007)The timeout specified has expired: [client 192.168.1.10:63055] mod_wsgi (pid=67623): Failed to proxy response from daemon., referer: http://192.168.1.3/admin/
[Sun Jan 29 09:27:14.427470 2023] [wsgi:error] [pid 67624:tid 140211782657600] [client 192.168.1.10:63053] Timeout when reading response headers from daemon process 'Portfolio': /var/www/Portfolio/Portfolio/wsgi.py, referer: http://192.168.1.3/admin/auth/
[Sun Jan 29 09:27:14.949762 2023] [wsgi:error] [pid 67624:tid 140211279357504] [client 192.168.1.10:63056] Timeout when reading response headers from daemon process 'Portfolio': /var/www/Portfolio/Portfolio/wsgi.py, referer: http://192.168.1.3/admin/auth/
[Sun Jan 29 09:27:16.385674 2023] [wsgi:error] [pid 67623:tid 140212856399424] [client 192.168.1.10:63100] Truncated or oversized response headers received from daemon process 'Portfolio': /var/www/Portfolio/Portfolio/wsgi.py
I still do not know what the solution is, though.
https://forum.djangoproject.com/t/django-apache-deployment-not-working-as-intended/15800
I found the solution. Somehow during the whole setup, adding WSGIApplicationGroup %{GLOBAL} to the /etc/apache2/apache2.conf file was never recommended, at least not that I noticed, but it worked and all the admin functionality works on the virtual host through WSGI Daemon.
Hope this can help someone else.

Issue while creating costum module in Drupal 8

I am trying to create new custom module in drupal 8 . I got given below logs . and system is not responding now . I am unable to logged in in drupal 8 site .
Log is given below :-
[Mon May 01 19:15:28.999581 2017] [:error] [pid 1892:tid 1660] [client ::1:60090] Uncaught PHP Exception Symfony\Component\Routing\Exception\RouteNotFoundException: "Route "first_module.content" does not exist." at D:\PHP server\xampp-win32-5.6.30-0-VC11\xampp\htdocs\drupal_8\core\lib\Drupal\Core\Routing\RouteProvider.php line 187
Which files have you created for custom module. Drupal 8 requires only 1 file as a start.
custom_module.info.yml
name: Custom module name
description: 'Module Description'
type: module
core: 8.x
package: Custom
You have a route "first_module.content" in your code which is not available.
Make sure the route exist in your first_module.routing.yml and you have cleared your cache.
If the website is not responding and you are not able to clear cache, go to your database and TRUNCATE all the tables with prefix 'cache_'.

Deploy Pyramid App on AWS Elastic Beanstalk

I'm attempting to deploy my Pyramid Application on AWS via Elastic Beanstalk. The upload/deploy works fine but when I send a request to the application I'm met with the following error:
File "/opt/python/run/venv/lib/python3.4/site-packages/pkg_resources/__init__.py", line 839, in resolve
[Sat Jul 16 21:04:40.351021 2016] [:error] [pid 10837] [remote 76.202.70.172:28102] raise DistributionNotFound(req, requirers)
[Sat Jul 16 21:04:40.351110 2016] [:error] [pid 10837] [remote 76.202.70.172:28102] pkg_resources.DistributionNotFound: The 'MyAppName' distribution was not found and is required by the application
[Sat Jul 16 21:34:47.346311 2016] [:error] [pid 10837] [remote 76.202.70.172:28102] mod_wsgi (pid=10837): Target WSGI script '/opt/python/current/app/application.py' cannot be loaded as Python module.
...where "MyAppName" is the name of my application (aka the one I've developed and am attempting to use).
From what it looks like, my actual application is not installed during the app deployment. Typically, on a local machine, after developing the application you run:
pip install -e .
in order to install the actual application you are developing. I suppose my question, although it seems silly, is: How do I actually install the application I've written onto the ec2 instance during the upload/deploy process of Elastic Beanstalk? Is there something that should be included in requirements.txt to also install the application in which the requirements.txt exists? Is this done automatically? What am I missing here?

django-mssql not working in Apache w/ mod-wsgi, but works fine in dev server

I have a Django application using django-mssql to communicate w/ SQL Server.
This works just fine in the dev server (runserver) but under Apache/mod-wsgi, I get a fail related to it trying to find a .dll which does exist:
[Thu May 19 15:35:09 2011] [error] [client 127.0.0.1] File "C:\\Python27\\lib\\site-packages\\win32\\lib\\pywintypes.py", line 98, in
__import_pywin32_system_module__ [Thu May 19 15:35:09 2011] [error] [client
127.0.0.1] raise ImportError("No system module '%s' (%s)" % (modname, filename)) [Thu May 19 15:35:09 2011] [error] [client 127.0.0.1] ImportError: No system module 'pywintypes' (pywintypes27.dll)
pywintypes27.dll exists in C:\Windows\SysWOW64 (64 bit windows, but I installed 32 bit py and Apache)
Is there something in either httpd.conf or WSGIScriptAlias I need to do/specify to help it find this dll? Something else I should do? I've done a fair bit of Googling/Binging/Searching to no avail.
Some further info:
python27 (not Active State)
pywin32 is installed
Win Server 2008 (64 bit)
Apache 2.2
Django 1.3
Thanks
You mentioned that you have Apache 32bits and the official mod_wsgi site seems to only have win32 mod_wsgi binaries available, which in turn also require a 32 bits version of Python. From your description it is likely that you are using the pywin32 library for Windows 64 bits and you configuration expects the 32 bits one.

Apache mod_python with django issue

While running a django application on top of apache2 mod_python, I am getting this error message in my apache error log.
[Tue Dec 14 14:26:45 2010] [error] [client SOME_IP] IOError: Write failed, client closed connection., referer: http://example.com/
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1931, in ReportError
req.write(text)
IOError: Write failed, client closed connection.
[Tue Dec 14 14:26:45 2010] [error] [client SOME_IP] python_handler: Dispatch() returned non-integer., referer: http://example.com/
Can anyone please suggest some solution on this?
The better long-term solution is to not use mod_python, since mod_python is no longer in development, and will not be supported in future versions of Django. Consider using mod_wsgi instead.
The Django documentation has this to say about mod_python:
Support for mod_python has been deprecated, and will be removed in Django 1.5. If you are configuring a new deployment, you are strongly encouraged to consider using mod_wsgi or any of the other supported backends.
Indicates that the user HTTP client connection was dropped before the complete response could be written back. Nothing one can do about it. Your application should handle it gracefully.