Trying to deploy/build for localhost and when running the app I keep getting:
Error: [$injector:unpr] Unknown provider: t
It's most likely because you haven't done properly annotated dependency injection. If your app runs ok in development, then it's almost certain.
Read more about it here
https://docs.angularjs.org/guide/production
Related
I installed Wordpress Packaged by Bitnami and made a website on it. It was working fine the whole month but now the website stopped working and when access any of the following
http://localhost/wordpress/
http://localhost/wordpress/wp-admin
http://localhost/wordpress/phpmyadmin
I get the following error "Error establishing a database connection"
Manger Tool > Manage Servers shows MariaDB Database Stopped, Apache Web Server Running
When try to Start MariaDB it doesn't start and I get the following:
Manger Tool > Server Events
Starting MariaDB Database... Exit code: 1 Stdout:
Stderr: Unknown error starting mysql
What's the cause and solution?
mysqld
I would recommend you to check the mysqld log file regarding the errors you have, which are triggering it to not to run.
which is in /bitnami/wordpress-5.8.1-2/mariadb/data/mysqld.log
in this file you will find detailed information about the error.
UPDATE
After attaching the log file, I discovered that this issue is similar to this one How to fix Error: MySQL shutdown unexpectedly on Xampp due to Plugin 'Aria', and solution might be applied following the steps:
Remove aria_log_control file from /bitnami/wordpress-5.8.1-2/mariadb/data/
Start the service
I've been trying to set up a Trellis local WordPress dev environment from the Roots stack. I did all the steps from the docs, have the recommended folder structure, downloaded all the dependencies, but I still get a few errors.
First I get some errors and warnings when I use "yarn" in my theme folder, as suggested here. They say to use the CLI from my host instead of Vagrant box, that's just the MacBook's terminal right? Or do I need a CLI from VirtualBox?
The second error happens when trying to call "vagrant up", and this is one that I can paste here as it's a bit more concise.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
After Googling this I got a lot of outdated suggestions to check my PATH and restart the VirtualBox, but these I tried and didn't help. I hope someone can help me set this up, thanks. :)
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
I have shiny running on a mac. These apps have previously been working. I'm getting the following error when I try to access any of them
The application failed to start.
The application exited during initialization.
su: illegal option -- p
usage: su [-] [-flm] [login [args]]
This is also all that is in the log. Any ideas on what is going on here? I know shiny server is not intended for mac which is why we are transitioning to a linux server, but in the meantime I need these apps which were previously working to continue working.
I'm learning Symfony2, really cool stuff. But I do run into some trouble when I want to try and visit the production environment. I have followed the Symblog Tutorial that is located here: http://tutorial.symblog.co.uk/
I have cleared the cache and I visit http://symfony.dev/ I have running locally. The page remains totally blank and this error is in the log:
Fatal error: Uncaught exception 'Doctrine\ORM\ORMException' with message 'Unknown Entity namespace alias 'DSBlogBundle'.'
in /Applications/MAMP/htdocs/symfony/vendor/doctrine/orm/lib/Doctrine/ORM/ORMException.php:236
Stack trace:
#0 /Applications/MAMP/htdocs/symfony/vendor/doctrine/orm/lib/Doctrine/ORM/Configuration.php(194): Doctrine\ORM\ORMException::unknownEntityNamespace('DSBlogBundle')
#1 /Applications/MAMP/htdocs/symfony/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php(554): Doctrine\ORM\Configuration->getEntityNamespace('DSBlogBundle')
#2 /Applications/MAMP/htdocs/symfony/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMetadataFactory.php(194): Doctrine\ORM\Mapping\ClassMetadataFactory->getFqcnFromAlias('DSBlogBundle', 'Blog')
#3 /Applications/MAMP/htdocs/symfony/vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php(295): Doctrine\Common\Persistence\Mapping\AbstractClassMetadataFactory->getMetadataFor('DSBlogBundle:Bl...')
#4 /Applications/MAMP/htdocs/symfony/vendor in /Applications/MAMP/htdocs/symfony/vendor/doctrine/orm/lib/Doctrine/ORM/ORMException.php on line 236
What I don't get is that the 'Unknown Entity namespace alias 'DSBlogBundle' is perfectly "known" in the development environment. Does anyone know what I am missing? Any help is much appreciated! Thank you!
Couple possibilities I can think of:
1) If your code functions properly in the development environment, then it could be a cache problem and/or a permissions problem. Make sure your files are readable by the user/process associated with your web server and make sure the prod cache directory is writable by that user so it can generate the necessary files. What I generally do is run the clear cache console command AS that user to avoid unexpected cache problems, like this (on linux):
sudo -u www-user php app/console cache:clear --env=prod
If you're developing on linux, you must be logged in as either root or another user with administrator privileges to run a command as a user other than yourself.
2) You may have configurations defined in the dev environment that don't exist in the prod environment. Double check the files in your app/config folder. My first guess would have been that the DSBlogBundle wasn't correctly defined in app/AppKernel.php but I believe that's environment independent so it couldn't work in dev but not prod.