I had a mariaDB install and I messed up the root password. Now I can't get in. I've tried every tutorial to reset the password and only get ERROR 1045 (access denied for user 'root').
So I purged my install. I ran sudo mysql_secure_installation and I'm still getting this error 1045.
I could really use some help. I don't care if the DB's are gone, I just want to be able to use MariaDB and I'm stuck.
Thanks!
What I did do was super-ultra purge. I purged every mysql/mariadb package i could find. I manually removed the /etc/mysql folder and the var/whatevermariadbfolder I could find. After crash and burn i was able to totally reset and get back in.
Related
I realise this is a duplicate of thousands of posts across the internet, but I have only found solutions for version <2.0, and those solutions do not apply to >2.0.
Basically, I have installed Apache Airflow on an Ubuntu system. Everything installed fine, as far as I see from command line, and I first create a user:
airflow users create --role Admin --username admin --email admin --firstname admin --lastname admin --password admin
And then from here I start up the webserver and scheduler:
airflow webserver -p 8585 > ${AIRFLOW_HOME}/logs/webserver.log 2>&1 &
airflow scheduler > ${AIRFLOW_HOME}/logs/scheduler.log 2>&1 &
And then I can access the webserver via "http://<HOST_IP>:8585" - This loads to the log in screen no problem.
But when I try to log in using the user details initially created, or by using my OS user (on the off-chance), it just fails with "Invalid login." I've tried restarting the webserver and Ubuntu to no avail.
I've used Airflow <2.0 in the past and never even created a user and just logged in straight away, so I'm really blank on what the answer is here. I absolutely hate Airflow and am loosing my mind just trying to log in, so a massive thanks for any help!
Okay, sooo I managed to get it running with login potential. I think I've discovered the issue, at least, and can re-create the problem, though frankly I have ZERO idea why it IS an issue (software coded issue??).
Basically, I had to run the install processes above as ROOT user. I was trying to run it as my admin user, but it kept resulting in the log in issue above - I did notice however that all install guides appear to use the ROOT user, so I gave it a shot in case it was as annoyingly simple as that, and VOILA!! First time logged in.
I did stop the software running at this point, quickly restart it as my admin user and immediately got the same login issue. There's something odd going on here, and I don't know what it is, but when in doubt: Try ROOT.
Solution- Create user again
I ran into the same issue. I had created an Admin user using the same command and after some changes to my config file, I ran airflow db init. After this when I started the webserver, I tried logging in with my admin credentials, but no luck. When I checked the logs, it showed me -
WARNING - No user yet created, use flask fab command to do it.
So I created the user again and it worked.
I was working on updating some contents on my website and suddenly it keeps redirect to www.example.com/core/install.php and gives me this message: "Drupal already installed" . I don't know what is the reason because it was working fine.
Maybe it's file permission problem. Try to set the owner of the web-root of Drupal installation:
chown -R YOUR-USER:WEBSERVER-USER .
Especially it's file permission problem of the settings.php. If the web server can't read this file, the new install process is started and redirects to /core/install.php
If it helps so you can go on with more secure file permission setting described here:
https://www.drupal.org/node/244924
Check the mysql value of max_allowed_packet.
max_allowed_packet = 64M
I know this is a late reply but folks can have a look here https://www.drupal.org/project/drupal/issues/2974321
We ran into this issue as well. Our issue was a corrupted redis cache.
The fix for us was:
redis-cli FLUSHALL
Then restart redis.
We have also seen this when you temporarily lose your connection to the database (MySQL in ours). My guess is that the code assumes that if you cannot see the database, by gosh you must be installing Drupal!
I've been filtering through google to try to find an answer to this, but I still can't find one that fixes my issue. I have migrated a website to a new server. The framework is Symfony 2.8 on php5.6 using Nginx and PHP-FPM.
Here is a screenshot of the config.php page.
To resolve this, i've tried...
Changing the user for Nginx and php-fpm to both the user I log in with and Nginx, both didn't work
I've opened up the privileges on the cache and log folder to 777 within the app folder, and that didn't work, nope.
I've tried assigning the cache and logs folder to nginx:nginx, no go.
I've manually assigned app.php, app_dev.php, and the console file to have the umask(0000) and umask(0002), nope.
Restarted the Nginx service and php-fpm service after each change, nodda.
I've restarted the entire server thinking something might be stuck, but you guessed it. No!
That leaves me here. I've gone through everything that I can think of and it baffles me that Symfony still won't recognize the directory as writable. It seems like the most simple thing, but... nope.
Anything will help, please pass anything along.
After countless hours of research and scraping the internet for details, I have found the answer! I'm posting it here in case someone else is having the same issue... and hopefully I can save them some time. This took up two days of my life that i'll never get back.
For whatever reason, SELinux was causing this error. I came across this issue on superuser stack exchange, and it told me to temporarily disable SELinux to test. After running sudo setenforce 0 everything came back up. I then completely disabled it and everything has been working fine since.
This happened suddenly and i'm still unsure of the reason. The site worked for about a week before this was triggered.
You should read this to setup you directories permissions http://symfony.com/doc/current/setup/file_permissions.html
I always go for the point 3. with Debian/Apache, Unfortunately i never tried it with nginx.
I've never used SVN except to push updates to my WordPress plugins. All of the plugins I've ever worked with are under the same account at WordPress.org. I honestly don't remember how I setup SVN credentials the very first time I ever did one, but ever since then, I've never had to enter them again. Any new plugin I create just works for me.
Now, though, I've got a new plugin that I created on a different WordPress.org account. I was able to check out the new plugin repo from WordPress, but then when I try to check in my plugin files I get an authentication error.
I'm assuming this is because somewhere it has my primary account's credentials saved and that's what it's trying to use here, which won't work of course. It's never asking me for credentials of any kind.
I tried to specify different credentials at the command line like this...
svn ci -m "Adds files for 1.0.0 release" --username myusername --password mypassword
The thing is, my password has some )'s in it, and when I try that command I get this error back:
bash: syntax error near unexpected token `)'
So at this point I'm stuck and I don't know what to do. Any info on this would be greatly appreciated. Thanks!
UPDATE: I changed my password to something more basic, and now when I use the --username and --password options it works fine. So I guess one thing that would help is to figure out how I can use passwords with special characters in them from the command line without getting a syntax error..??
You can omit the --password option. Subversion asks you then for the password.
This is also saver as your password is not stored in cleartext in your history
I having a problem using vTiger.
Actually i had no problems but we had to format one of our servers and as the SQL has been backup'ed i had no worries about vTiger.
Just got vTiger folder backup'ed too, but when i had my server back and put the folder of vTiger into www and restored the database i had a few errors, mostly resolved by re-configuring config.inc.php because paths had changes. But after all the configuration is done again i can't login to my vTiger. He reachs the database but does not recognize any of the users. I alway get username or password is wrong. Have anyone experienced this? Is there any possible solution?
Had a similar problem a few days ago, it turns out my cookies were corrupt (Firefox). I cleared all related cookies, problem solved. Try first using some other browser to confirm. hth.
First I would check if the db is reached and populated with your data. Try connecting from the command line.
If you are working on Windows and have changed Vtiger's path, and you are using the bundled version, MySql path changes as well, but the Windows service can still be alive on the old path: in this case you must manually cancel the service and afterwards use the "Start Vtiger" button in order to create the new service.
Second, I would turn on the php debugging as explained here. In most cases, these steps should help you.
Have you checked user_privileges folder? in that you must have 2 files for particular user. eg. your user admin having id 1 in database then you must have user_privileges/sharing_privileges_1.php and user_privileges/user_privileges_1.php file
and open user_privileges_1.php file and check username/password in that file, if it's not same with your DB then change it manually.
Try this solution and let me know if it works.