Error in drupal-commons installation - drupal

i´ve got drupal 7 installed on my pc running on localhost from Acquia Dev stack. Now i tried to installed Drupal-Commonns, but i got this error when the Install Profile stage is running:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows.
Path:
.......
siteChoose site color paletteEnter Homepage welcome textCreate the first groupFinished
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dc.watchdog' doesn't exist
what might it be?
thanks

You need to enable Database logging module.
This module will create watchdog table.
After that this error will go away.
Hope this will help. :)

Related

jupyterhub fails to spawn server with systemdspawner

I am trying to run jupyterhub on an Ubuntu 20.04 LTS server. My idea is to run python/jupyterhub in a conda virtual environment as a system service. As I want to be able to limit the resources available to individual users I installed the systemdspawner.
After installing everything and starting the jupyterhub service I can login through my web browser. However, when trying to start the server the spawner stucks and after a while I get an error message saying "Spawn failed: Timeout"
in journalctl I can see the following messages:
User logged in: me 302 POST /hub/login?next= -> /hub/spawn (me#::ffff:[my IP address]) 59.42ms
Adding role server to token: <APIToken('93c8...', user='me', client_id='jupyterhub')
Creating oauth client jupyterhub-user-me
pam_loginuid(login:session): Error writing /proc/self/loginuid: Operation not permitted
pam_loginuid(login:session): set_loginuid failed
pam_unix(login:session): session opened for user me by (uid=0)
Failed to open PAM session for me: [PAM Error 14] Cannot make/remove an entry for the specified session
Disabling PAM sessions from now on. user:me
Unit jupyter-me-singleuser in a failed state. Resetting state.
Disclaimer: My Jupyter/Python installation is replacing an former installation that was setup by someone else and got messed up a bit during time. I tried to remove everything related and start with a clean installation from scratch. However, as I had very little documentation about the old setup there is a certain risk that there might be some left-overs of the previous installation that may cause trouble.
Any ideas?
Solved it out myself. In the end the PAM related messages seem to be non-critical and were not related to the timeout at all. Instead I found a mistake in /etc/systemd/system/jupyterhub.service, where the PATH variable was not including the bin directory of my miniconda installation.

Kibana is stuck on "Kibana server is not ready yet"

After installing Inhanced-Table plugin, my Kibana is stuck on the following message
"Kibana server is not ready yet"
However after some minutes it completely became out of reach and I am facing with "Unable to connect" error on my browser.
I removed the plugin with the following command, but the error still exists.
./bin/kibana-plugin remove enhanced-table
Would you mind helping me in order to solve this problem. Also Kibana logfile is available via following link.
https://drive.google.com/file/d/1LILdo07Q9r0-VNG7hgkbTOaE2eJzhQPs/view?usp=sharing
Thanks
Best Regards
Looking through the log of your kibana, I've seen:
{ "type":"log",
"#timestamp":"2020-11-11T05:44:01Z",
"tags":["fatal","root"],"pid":2884,
"message":"{ Error: Optimizations failure.\n 9263 modules\n \n
ERROR in ./src/legacy/core_plugins/console/public/np_ready/application/components/editor_example.js\n
Module not found: Error: Can't resolve '../constants/help_example.txt' in 'D:\\Elastic\\Kibana\\kibana-7.6.1\\src\\legacy\\core_plugins\\console\\public\\np_ready\\application\\components'\n\n
So might be Kibana is still looking for the plugin, that's why the error occurred.
You should try stop kibana and start it again.
I installed a new clear kibana and problem fixed

After installed horizon (Openstack Train), When access http://controller_ip/dashboard, Got error “/auth/login/ was not found on this server”

I installed the Openstack horizon(Train version) by followed guide, no error showing in my install steps. After finished install, I access "http://controller_ip/dashboard", and got an error:
The requested URL /auth/login/ was not found on this server.
Can anyone help?
this
https://bugs.launchpad.net/horizon/+bug/1853651
By adding the following to the config file (and restarting httpd), the horizon dashboard then loads without issue:
WEBROOT = '/dashboard'

Drupal 7.41 [HTTP/1.0 500 Internal Server Error 19ms]

I'm trying to install Drupal locally on Fedora 22.
I've done all that drupal.org/documentation/install says to complete the installation but when I try to run Drupal it doesn't works.
On the URL I put: localhost/ and it works so it seems that I don't have any problem here, but when I write: localhost/drupal or localhost/drupal/install.php it doesn't works!
And everytime I get this error: GET http://localhost/drupal/install.php [HTTP/1.0 500 Internal Server Error 19ms]
Does someone know how can I fix it?
You have to take a look at your apache or nginx logs (error logs) to see what is the problem. Some server configuration output the errors in a file "error_log" in the root of your Drupal installation.
http://www.codeasite.com/index.php/linux-a-apache/94-how-do-i-find-apache-http-server-log-files
https://fedoraproject.org/wiki/Nginx
Maybe some PHP extensions are missing. Check Drupal requirements : https://www.drupal.org/requirements

Drupal 7 Search api Solr - 400 Bad request on indexing or cleaning

Trying to clean the index:
Apache_Solr_HttpTransportException: '400' Status: Bad Request em Apache_Solr_Service->_sendRawPost() (linha 364 de /home/mercado/public_html/sites/all/libraries/SolrPhpClient/Apache/Solr/Service.php
Trying to index itens:
Couldn't index items. Check the logs for details.
Log Says:
An error occurred while indexing: '400' Status: Bad Request.
Im using the latest release for apache solr and solrPHPclient. Everything seens ok, im using the schema.xml from the module and the module checks the solr server ok...
There is no log file in my path/to/solr/example/logs
Thanks in advance
I was having the same problem and realized I had the copied the wrong configuration files to the /Applications/apache-solr-3.6.1/example/solr/conf directory. Once I copied the correction version from sites/all/modules/search_api_solr/solr-conf/3.x it started to index properly.
Check your Apache solar is running on your server

Resources