EEXIST: file already exists, mkdir ‘C:\Windows\system32\config\systemprofile’ exception #516

Comments

buinauskas commented Jun 18, 2016 •

I’ve got this little server, which runs fine on iisnode:

index.js

However, if I want to use Babel and rewrite my application like that:

index.js

server.js

Now if I navigate to localhost/test/foo , I receive this error message:

That’s the log from etw.bat :

The following code works fine if I run node index.js from command line in my application folder.

What do I have to modify in order to have my desired application, written in Babel, working on iisnode?

The text was updated successfully, but these errors were encountered:

jhiswin commented Jun 21, 2016 •

#518 I posted my current workaround in a following comment. You will have to serve your babel compiled files to iisnode.
My recommendation is just to use node directly when developing. It’s probably a «good thing» ™ anyways; it’ll force you not to depend on IIS specific behavior and you will have to build a compile step pipeline anyways. Added benefit it’ll keep newbies from deploying babel-register to production sites (which would be a terrible idea).

It kind of sucks, though, that this makes deving with ES2015 and IISNode a pita, and you don’t get the direct integration of node-inspector (which BTW is very problematic for me, doesn’t load properly).
This would have been a great low friction way for Windows users to dev nodejs apps.

buinauskas commented Jun 21, 2016

@jhiswin It’d be all fine, but only reason I started looking into iisnode was that I could use Windows Authentication for my apps. I guess for development I’ll have to mimic it.

jhiswin commented Jun 21, 2016 •

@buinauskasevaldas you might consider using a watch. It’s not quite as edit-run friendly, but it should work. Like a simple node_modules/.bin/watch \»npm run build\» src/ . Make sure you use a good build tool so rebuilds aren’t too slow.

buinauskas commented Jun 21, 2016 •

Modified my web.config this way and this is now resolved:

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Logging into phpMyAdmin error

I access the phpMyAdmin login page by 127.0.0.1/

When I try to go to 127.0.0.1/

username/phpmyadmin/setup I get the following error:

phpMyAdmin — Error Configuration already exists, setup is disabled!

I am trying to setup phpmyadmin with mysql which I downloaded and have spent the last 2 days trying every solution I’ve found on here.

At one point I was able to access 127.0.0.1/phpmyadmin/setup and created a server with my mysql password but now I can’t even access this

Below is my config.inc.php code:

I’m guessing something is wrong here but my mind is melting looking at all of this for so long.

Any ideas on what my issue is?

Thanks I am running macOS Sierra if that helps anything

Also when I try to login to my mysql I get these errors:

2002 — No such file or directory — The server is not responding (or the local server’s socket is not correctly configured).

mysqli_real_connect(): (HY000/2002): No such file or directory

2 Answers 2

After some initial research, I believe I have a solution for you.

I would try changing:

phpMyAdmin — Error Configuration already exists, setup is disabled!

This means you already have a config.inc.php in the root phpMyAdmin directory, so the setup script won’t run as a security precaution. You can move or rename config.inc.php in order to work with the setup script.

2002 — No such file or directory — The server is not responding (or the local server’s socket is not correctly configured).

This either means the MySQL daemon isn’t running at all, or that the socket path you’ve pointed phpMyAdmin to isn’t the socket used by MySQL. The way I suggest troubleshooting this is to use the command-line client to connect ( mysql -u root -p or use a different username if ‘root’ isn’t appropriate here). If you can connect, run the STATUS; command to see connection information, including socket path (if the connection is via socket; if it’s via tcp/ip networking you’ll see that and port 3306 instead of a socket path).

Note that you’ve set the host to ‘localhost’ which has special meaning to MySQL and basically overrides the connect_type definition. With ‘localhost’, you’re using sockets and in many cases on Mac systems, for some reason the default paths used by MySQL and PHP don’t match. The ideal solution is to edit your PHP configuration file to define the proper path to the socket, but phpMyAdmin also has the $cfg[‘Servers’][$i][‘socket’] directive for you to specific the path to the socket. If you wish/need to use the TCP/IP protocol instead, use the hostname 127.0.0.1.

ERROR: The file ‘wp-config.php’ already exists

I clicked on the ‘Update WordPress’ link in the admin dashboard of my WordPress site, and I am getting this error:

When I try to click the «installing now» link, it seems that WordPress is installing fresh. I want to keep all of the content of my WordPress installation.

I have tried to change the name of the wp-config.php file but that didn’t do anything.

15 Answers 15

Is just a browser cache.

On first URL load, you are redirected from domain.ext to domain.ext/wp-admin/setup-config.php

If you are on Chrome, just open the developers console, go to «Network» tab. Reload the page and right click anywhere in the console, and hit «Clear browser cache».

Now refresh again and you will see your website

I ran into this same issue while I was transferring a site. The issue ended up being with the .htaccess file. I fixed it by resetting my permalinks. There may be other causes to this issue but this worked for me:

1. Click on General => Permalinks
2. Click Save Changes (to reset permalinks)

Try to display the website first on the incognito tab. If it works correctly, clear the browser cache.

Once the page refresh has been completed, the website will appear.

You can use the following shortcuts to clear the browser cache.

Windows: Ctrl + F5 Mac OS: CMD + Shift + R

This usually happens when you use an old version of WordPress files or old database, and you use partly new files of WordPress.

All you need to do is to delete all WP files and install a fresh WordPress (new files unzipped from a new version of WordPress) and use an empty database. If you’re planning to migrate or move from another website, you should use the export/import function built in wordpress.

he file wp-config.php already exists. If you need to reset any of the configuration items in this file, please delete it first. You may try installing now.

Answer:- Please Clear Your browser’s cache.

Did I miss the party? Today I have a problem like what you experienced 5 years ago. The solution is: Remove all caching plugins (Cloudflare, Jetpack, Litespeed).

Maybe you could try to delete ‘wp-config.php’ file, or take a backup of this file in different folder and then try again.

If you are using bluehost and did not do the one click install :

I solved this problem by deleting the default error pages 404.php 500.php etc.

I do not know why exactly this was causing this issue. Sorry for the sloppy answer but tried clearing cache and recreating the .htaccess file it didn’t work.

I removed the added spaces that the WordPress’s own web ‘easy installer’ created in the wp-config.php file to help me out.

Guess the WordPress’s own wp-config.php ?checker? isn’t compatible with WordPress’s own installer. Wow.

Once the added spaces were removed, site comes up fine. I simply modeled the spacing that is in the wp-config-sample.php file.

Because you just installed wp.

Just hit ctrl+F5 done.

More likely it is cache issue and this error comes when we try to install one WordPress inside of another sub folder of the cpanel in the same WordPress installation and it will be mostly resolved when you try to check it in the private window or another browser

If someone is still for a solution. This happened to me on an existing site while trying to update. the problem was following line in wp-config.php near the end.

Removing this fixed the problem. Hope this helps.

RESOLVED: I had the same problem. post hack situation on other account, shared hosting and server NUKED. Luckily I had the backup files from one of the WP plugins but the main page didnt load, I could only go to 404 and from there to other pages but not main page, the error was wp-config eists. install. blah blah blah. so I tried everything, multiple re-installs, changed the wp_prefix as per previous install on the fresh install and nothing helped, even ordered paid support from the backup plugin developer as I was sure that it fooked because I had Opencart also installed there but the backup was intended for WP only, my web developer also did something, perhaps removed the OC bits from DB, but thank god i managed to resolve it on my own(and justhost),. so I contacted the justhost for the SECOND TIME and they told me that the account is on VARNISH i.e. some sort of automated cache limit, so I told them to take it off and they wanted to know what have I done to reduce the LOAD to the server, so I told this and that and two seconds later everything loaded perfectly. took me about 20 hours to get main page loading, plus probably it will take 10 hours for fine tuning of the site. anyway if you contact jour host make sure you ask them if they are not blocking cahce as the first time I got in contact they couldnt help me.

I also meet with same error and Mr Pierre R is right its just a cache. Just clear your cache or check in private window. All fine.

Configuration already exists, setup is disabled! — except it doesn’t exist #15480

Comments

murraycollingwood commented Oct 1, 2019

Describe the bug

Fresh install (new Debian 9 server) latest stable copies of everything
Used an «apt» install of phpmyadmin
Ran /usr/sbin/pma-configure
Went to visit http://server1/phpmyadmin/setup
Enter login credentials
Get this error: Configuration already exists, setup is disabled!
However when I look in /usr/share/phpmyadmin there is no config.inc.php

To Reproduce

I reproduced it on a second server with exactly the same steps.

Expected behavior

The setup configuration screen to appear

Screenshots

Server configuration

• Operating system: Debian 9
• Web server: Apache2
• Database version: MariaDB (latest stable)
• PHP version: 7.0
• phpMyAdmin version: 4:4.6.6-4

Client configuration

• Browser: Chrome
• Operating system: OSX Mojave

Additional context

The text was updated successfully, but these errors were encountered:

ibennetch commented Oct 1, 2019 •

Most likely what’s happened is that the Debian folks have changed the path (to fit Debian policy) and it appears they may have overlooked something when doing so. I’ve done some testing with versions 4.6.6 and 4.9 (the current phpMyAdmin release) and don’t have any trouble with this, so it seems very likely it’s a Debian-specific problem.

You may have some luck reporting this as a bug through the Debian bug tracker. I also know there’s a team trying to get a more recent phpMyAdmin in to Debian, but in the mean time I suggest installing your own https://docs.phpmyadmin.net/en/latest/setup.html#quick-install

murraycollingwood commented Oct 1, 2019

So I made a small change to the code:
if (file_exists(CONFIG_FILE)) <
PMA_fatalError(__(‘Configuration ‘.CONFIG_FILE.’ already exists, setup is disabled!’));
>
And now I get the message:
Configuration /etc/phpmyadmin/config.inc.php already exists, setup is disabled!

If this is wrong where should I fix it? This is the first problem I’ve come across on this install, however in my experience if I work around and continue I will likely come across many more issues stemming from this.

If it is a Debian setting that is wrong, where do I correct it?

murraycollingwood commented Oct 1, 2019

I’m having so many issues with phpmyadmin installation.

1. First the above with the location of the config.inc.php
2. To even get to access phpmyadmin we have to create a user/password in the htpasswd system.
   Now I have the config.inc.php configured
3. The login is failing: mysqli_real_connect(): (HY000/1698): Access denied for user ‘root’@’localhost’ . Which really doesn’t tell me what the problem is. Is this the connection to the database? Is it a security setting that is rejecting the ‘root’ username from logging in? It’s making me question whether it is actually the mysql root password I’m supposed to be using here. I know it is, but I’m still wondering what it is I’m doing wrong. I can login fine using a mysql client. Or perhaps this is the connection between php and mysql that isn’t configured correctly — I don’t know, phpmyadmin is usually the first application I run to check this connection.

I’ve been all through the README.Debian and I’m still not able to login.

Sorry, I just need to vent a little.

murraycollingwood commented Oct 1, 2019 •

It looks as though there is a difference between ‘root’@’127.0.0.1’ and ‘root’@’localhost’
That may be a MariaDB installation problem. Although it would be nice if phpmyadmin noticed this and told me.

This has taken me nearly a whole day to solve!

williamdes commented Oct 3, 2019

@murraycollingwood We are working on making 4.9.1 available in Debian (#15236)
I recommend you to chose between the following options :

• uninstall the package and install from our website
• go to the phpmyadmin directory and remove all contents and replace by the contents of 4.9.1 found on our website
• use the PPA linked in #15236 in order to install 4.9.1 from Ubuntu repository

Tell me if that solved your issue

We will not offer fixes for 4.6 versions, if you upgrade to 4.9 I will be able to help you if there is a bug somewhere

murraycollingwood commented Oct 3, 2019

No problem — I’ve move to Querious.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.