I was adding modules and installing them yesterday and I get this error now: "The website encountered an unexpected error. Please try again later." I can't login at all or access anything from the url. I tried deleting the modules but it still isn't working. Any suggestions?
To expose what's up, add the following line to your settings.php
$config['system.logging']['error_level'] = 'verbose';
What's happening is that the code is failing fairly deep into the execution and it may not even be a syntax error. In my case, it was the MySQL user was not associated with the MySQL DB, so the connection was failing as what the application
The models are probably still in database even though you deleted it from code ?
If you have access to drush, you can in-install it via drush. If not you need to change entries in the database tables
Related
I am working on a Power BI project.
I started using a MySQL database that had a small amount of data. I managed myself to create the schema and a very basic dashboard.
After this, I tried to change the data source for a new mysql database with a much bigger amount of data in order to see its performance. The tables are the same. The only thing that changes is the name of the data base and the name of the schema.
The thing is that whenever I try to do this an error always pops up:
Fatal error encountered during data read.
Microsoft.Mashup.Evaluator.Interface.ErrorException
True
I dont know why this happend. I tried to follow some suggestions I saw in the official forums but they didnt worked for me.
I also deleted the cache but nothing happens ( File-> Options and Settings-> Options-> Data Load -> clear cache)
If you could give me any suggestions, they would be appreciated because I am new to power bi and to be honest I am quite lost with this error.
Are you using mysql with hosted environment? like AWS RDS database ?
Previously I had similar issue getting fatal error when import data via mysql view.
The issue is the processer that used in mysql database was not powerful to run on 100% cpu usage.
So I had to upgrade processer in to powerful and efficient one. And did some changes to query to be efficient.
In your case try to add indexing to the tables and if you are using hosted mysql connection try upgrade processor that can work with 100% usage.
I am using Django with Google cloud datastore i.e. Djange (https://djangae.org/)
I am new to these tech stacks and currently facing one strange issue.
when I persist data by calling Model.save(commit=true) . The data gets saved into cloud datastore but after 4/5 mins it gets reverted.
To test it further I tried to directly change the value in database but it also got reverted after sometime.
I am kind of confused as there is no error or exception I see . I am making atomit transaction and wrapped my code with try except to catch any exception but no luck.
could someone please advise me as how to debug further here.
I got some lead here. well I was pointing datastore with multiple versions of code and few of them were in infinite loop to hit the same Kind of datastore. currently killing all stale version makes the DB consistent with changes. . wanted to update so that others can get an idea if something similar happen
We recently upgraded our Single Instance API Manager from 1.90 to 1.10. Upgrade seemed to be mostly successful, but anytime I try to load one of the services in the publisher, it freezes up and the log reports:
Error while retrieving the lifecycle actions for lifecycle: APILifeCycle in lifecycle state: null
at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.getAllLifecycleActions(GovernanceArtifactImpl.java:783)
at org.wso2.carbon.apimgt.impl.APIProviderImpl.getAPILifeCycleData(APIProviderImpl.java:3306)
... 101 more
Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException: Resource at '/_system/governance/apimgt/applicationdata/provider/<User>/<API>/v1/api' not associated with aspect 'APILifeCycle'
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getResourceAspect(EmbeddedRegistry.java:2592)
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getAspectActions(EmbeddedRegistry.java:2627)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.getAspectActions(CacheBackedRegistry.java:474)
at org.wso2.carbon.registry.core.session.UserRegistry.getAspectActionsInternal
And Also (I replaced sensitive info with <>):
org.wso2.carbon.registry.core.exceptions.RegistryException: Resource at '/_system/governance/apimgt/applicationdata/provider/<USER>/<SERVICE>/v1/api' not associated with aspect 'APILifeCycle'
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getResourceAspect(EmbeddedRegistry.java:2592)
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getAspectActions(EmbeddedRegistry.java:2627)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.getAspectActions(CacheBackedRegistry.java:474)
I have spent a ton of time trying to locate the code that this error occurs with no luck (I'm not a java developer anyway). Do you guys have any ideas on what is causing this error? All of the services that are registered were registered pre-upgrade.
UPDATE:
As suggested below, this is because the migration is failing. I dug in a little deeper and discovered that the migration is failing due to bad SQL. Within the migration client, specifically the file MigrateFrom19To110.java, on Line 189 it is executing an Ad Hoc SQL statement :
"UPDATE IDN_OAUTH2_ACCESS_TOKEN SET AUTHZ_USER = ? WHERE AUTHZ_USER = ?"
This throws this error:
Must declare the scalar variable "#P0WHERE"
It seems like there is something wrong with the code that is building this statement, because the #POWHERE seems to be coming from the jdbc driver code. Can anyone shed more light on this?
Did you run the migration client during the upgrade? seems like migration hasn't gone correctly. Steps are given in https://docs.wso2.com/display/AM1100/Upgrading+from+the+Previous+Release
The reason I'm saying this is because as part of the migration we attach 'APILifeCycle' lifecycle to existing apis. Since the error says the api is not associated with the lifecycle I can guess the problem is with the migration
I've installed a new Sitecore 8 instance, setup a MongoDB instance and started it running.
I've deployed the analytics definitions.
When I go to The Path Analyser I get the following Error.
There was an error loading data, please try again. PathExplorer.PathMapDataLoaded() - PathMap is null.
Any idea what might be wrong? Any other steps I need to perform?
I logged this with support - This has been reported as a bug.
I'm occasionally but quite often getting an unhandled exception in cursor.execute (django1.1/db/models/sql/query.py line 2369), using psycopg2 with postgresql.
Looks like the database drops connection in some way, so Django crashes. For unhandled exception there is a ticket in Django's bugtrack (#11015), but I'm rather interested in reasons why db drops connection, not why Django doesn't catches it.
Using django's dev. server this error never happens (it runs db requests in order, concurrency never happens), so it's like it has something to do with db requests concurrency or what.
I have no access to postgresql config. or logs.
Any suggestions welcomed, maybe some postgresql tweaking, or some thoughts on how to debug this issue.
upd: looks like this question - Django + FastCGI - randomly raising OperationalError - addresses the same problem, but no solution provided :-(
The problem could be mainly with Imports. Atleast thats what happened to me. I wrote my own solution after finding nothing from the web. Please check my blogpost here: Simple Python Utility to check all Imports in your project
Ofcourse this will only help you to get to the solution of the original issue pretty quickly and not the actual solution for your problem by itself.