All of a sudden, Odoo login screen is damaged and the CSS styling becomes a mess as shown in the snapshot.
Symptoms:
This happens with certain databases, but when creating new database it doesn't happen.
Doesn't appear as long as I'm working on the same browser, when changing browser the problem appears.
What I tried:
I installed a fresh database and started installing modules one by one in order to see which one will crash, but nothing happened.
I'm using Odoo 11CE from the official docker image.
Restart your Odoo server and check your log at Odoo startup to find a python import error or warning because that normally it's associated with a python error loading your odoo modules from the addons paths. Not need to be installed modules.
Also the same could be happening when your Odoo server it's trying to load another Odoo database that fails to load due to a different Odoo version or because the lack of modules loaded for that database
This had happened to me many times, I usually solve it by just cleaning the cache/cookies of the browser and restarting the Odoo service.
In other note, i noticed this happening mostly when I log to different databases with the same browser without closing additional tabs with odoo pages loaded in or when I move from a different version all together without logging out from previous sessions.
if someone need help in this case i resolve it see my log in odoo after that delete in database ,
the line in the log is FileNotFoundError: [Errno 2] No such file or directory: 'rute' 9739bf1f391e10051ed840fef5b341f9351d0536
after that restart server and change the number and do this many time and reove you problem.
delete FROM "public"."ir_attachment" WHERE "public"."ir_attachment"."store_fname"LIKE '%9739bf1f391e10051ed840fef5b341f9351d0536%'
Related
I am getting strange issue with mysql server after every 2 days
I am working on moodle plugin development
so as normally I installed moodle in my xampp htdocs folder
before 2 days I was writing my plugin and it was working fine after weekend I open my system and now mysql is not running. This happened third or fourth times.
I am attaching the error
error what I am getting
Xampp error screenshot
enter image description here
I even changed my machine to high configuration by thinking that the other machine could be out of memory etc.
So far I tried to backup the data but if I do backup then it doesn't have my moodle database everytime.
I know I should take backup time to time but problem is why this error is coming after every 2-3 days
I tried running xampp as admin
tried changing port etc. and tried various solution also but If I do copy from backup folder it will wipe out all my moodle database and I need to start if from scratch
and Dont mark it as duplicate and I tried almost every solution but nothing working for me
I even tried this one(Error: MySQL shutdown unexpectedly XAMPP)
Updated here is the actual error before doing anything which coming after every 2 daysOriginal error
Because mysql.db is a system table used for authentication it aborts if it can't be opened.
Start the database with skip-grant-tables added the the configuration file.
After restarting run the SQL REPAIR TABLE:
REPAIR TABLE mysql.db EXTENDED
After this is complete. shutdown, remove the skip-grant-tables from the configuration file and start MariaDB again.
I'm having trouble with setting up ACORE API's and then having them work on a website.
Background:
Azerothcore running 3.3.5 on a debian standalone server, this has the Database, Core files and runs both the world and auth server basically a standard setup that is shown in the how-to wiki.
I also have a standalone web server, on the same subnet, but it's a separate server running linux and normal web server stuff, this has a wordpress installation with azerothcore plugin for user signup etc.
I'm trying to add the player map (https://github.com/azerothcore/playermap) and the ACORE-API set of functions (server status, arenastats, BG que and wow statistics) (https://github.com/azerothcore/acore-api)
Problem:
I understand the acore-api must be run in a container (docker or whatever) on the server, which I have done and it binds to port 3000, I can then go to the local ip:3000 and it brings up this error. (all db's etc are connecting and soap is working)
error 404 when navigating to IP:3000
I do get a few errors when running NPM install seen here: I'm not sure if they would be causing any issues or not.
screenshot of NPM errors on install
But further that, when I put say 'serverstatus' on the webserver (separate server) and configure the config.ts file I can't seem to get anything to display.
I'm not sure what I'm doing wrong but is the same scenario for all of the different functions for the acore-api
How are these meant to be installed and function? I feel I'm missing a vital step.
Likewise, with PLAYERMAP I have edited the comm_conf.php and set the realmd_id, but when loading the page, I do get the map, but the uptime is missing and no players are shown?
Could someone assist if possible?
Seems like an issue with NodeJS version. Update your NodeJS to latest LTS version 16.13.0 (https://nodejs.org)
I got to a point where Meteor seemed to just stop working, no HTML would load but the port was open, throwing basic console errors indicating that the most basic parts of the program weren't getting read.
After a lot of troubleshooting (clearing the database, restarting, logging out, using different ports), I just created a new Meteor project and copied and pasted my .html and .js files and the new project worked where the old project didn't.
So, question - how can I troubleshoot this in the future? Something was going on in the Meteor folder because the old and new files were exactly the same.
After a day, the error is happening all the time now and I can't create a single project. I tried uninstalling and reinstalling Meteor with no luck.
Also, the problem seems to be isolated to one port. I can open projects in other ports, but not in 3000.
Why is one port "breaking"? What can I do to fix this?
--Edit--
The HTML and CSS are loading, but in the default port 3000, the console reads
Uncaught ReferenceError: Package is not defined
It shows this code as the first error point:
/* Imports */
var Meteor = Package.meteor.Meteor;
Below is the Terminal:
--Edit--
So this is embarrassing, it seemed to be a cache problem. I cleared the cache, and I'm assuming it refreshed the .js files and now it works.
If anyone can answer why the errors were being thrown in the first place and how to fix besides creating an entirely new project, that would be hugely helpful!
please post your terminal so we have more clues to help you.
You definitely can run other ports, perhaps your port 3000 is used by another program.
Also, never run a meteor app as root.
Run meteor on a high port number. The default is 3000 when you don't give a --port argument. Connect to it via the URL printed in the console - e.g.
meteor --port 3001
http://localhost:3000/.
If you have settings.json then run meteor --settings settings.json
I am moving a site over to a different server to test.
getting this error
Call to undefined function field_attach_load() in my-path-to-root/my-site/includes/entity.inc on line 320
strange... if i try accessing a subdirectry http://www.mysite/randomstuff
i get this error
Fatal error: Call to undefined function user_access() in /home/borsodas3/digipowers.devserver2012.com/modules/overlay/overlay.module on line 130
Fatal error: Call to undefined function node_access_needs_rebuild() in /home/borsodas3/digipowers.devserver2012.com/sites/all/modules/taxonomy_access/taxonomy>_access.module on line 598
here are the two php.info files
going to this server [http://www.freeenergymedia.com/phpinfo-to.htm][1]
from this one [http://www.freeenergymedia.com/phpinfo-from.htm][2]
the drupal status report from the site I am migrating FROM looks like this...
Info
Drupal 7.8
OK
Access to update.php Protected
Error
CTools CSS Cache Unable to create
The CTools CSS cache directory, ctools/css could not be created due to a misconfigured files directory. Please ensure that the files directory is correctly configured and that the webserver has permission to create directories.
OK
Configuration file Protected
OK
Credit card encryption Credit card data is encrypted during checkout for maximum security.
OK
Cron maintenance tasks Last run 26 min ago
You can run cron manually.
To run cron from outside the site, go to mysite.com
OK
Database system MySQL, MariaDB, or equivalent
OK
Database system version 5.1.57-log
OK
Database updates Up to date
OK
Date API System date settings
The timezone has been set to America/New_York. The first day of the week has been set to Monday. The medium date format has been set to to F j, Y - g:ia.
Error
Drupal core update status Not secure! (version 7.12 available)
There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates.
OK
File system Writable (public download method)
OK
Fitvids library Installed
Fitvids Javascript Library. Download it from here, copy it to the module directory, and rename it to jquery.fitvids.js.
OK
GD library PNG support bundled (2.0.34 compatible)
OK
GD library rotate and desaturate effects bundled (2.0.34 compatible)
OK
Images Product image support has been automatically configured by Ubercart.
Error
Module and theme update status Not secure!
There are security updates available for one or more of your modules or themes. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates.
OK
Node Access Permissions 1832 permissions in use
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content and replace them with permissions based on the current modules and settings. Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed, content will automatically use the new permissions. Rebuild permissions
OK
PHP 5.3.2 (more information)
OK
PHP extensions Enabled
OK
PHP memory limit 300M
OK
PHP register globals Disabled
Warning
Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.
OK
Update notifications Enabled
Info
Upload progress Not enabled
Your server is capable of displaying file upload progress through APC, but it is not enabled. Add apc.rfc1867 = 1 to your php.ini configuration. Alternatively, it is recommended to use PECL uploadprogress, which supports more than one simultaneous upload.
OK
Web server Apache/2.2.3 (CentOS)
OK
cURL Enabled
The first thing I'd do is update to the latest version of Drupal Core. The error message you are seeing is coming from core, but could be from a contrib module. Update all your modules if any are as outdated as your Drupal core is. There are security issues in Drupal 7.8 and other issues which might affect your situation could well have been resolved. The current version of Drupal is 7.12 and a lot has been fixed since Drupal 7.8, which was released about 6 months ago, so you definitely want to upgrade core. Is it also possible that you are running different versions of core on the different machines? If so, the database might not be compatible, especially if you are taking a newer database (more recent modules and core) and loading it into a system with older modules/core.
After also updating other contrib modules and running update.php at appropriate times, if your problem still persists, you might want to use the "divide and conquer" method to identify which module is actually responsible. Remove groups of contrib modules and see where the problem disappears, then narrow it down to which one is causing the problem. It could also be a compatibility issue or configuration problem. Or you might have modules where the code has been updated, but update.php hasn't been run so the database isn't what it should be. You can also use tools such as the Devel module to try to track down issues, but it depends on how "broken" your site is. If you are getting "fatal errors", then you might first want to see what you can do to get past that.
I also notice you need to properly set the permissions/ownership of your files directory so that CSS caching can take place (among other tasks the webserver may be trying to do and which could also be involved in errors you are experiencing), even if not at the root of the "fatal errors".
Hope that helps some… troubleshooting can be a pain sometimes.
When I installed for the first time, I hadn`t checked "Create new database" and had the same bag but in line 321.
In drupal, keep getting an upgrade message all over site from htmlpurifier that a 4.0 is available. Ran upgrades (uploaded files and ran update.php) but still have message. No finds on this when I googled around.
Supposedly a flush.php in a maintenace folder will flush it's cache (which is invconveniently separate from the rest of Drupal's cache), but trying to execute in browser gets me an error.
Either upgrade is bad or needs cache flushed, or just shut off this message. Advice?
Did you install both the updated module and the library? The module is here while the library you should download here.