MySQL errors, HeidiSQL crashes, new pc, same portable files


  • | 207 points

    Hi, Laragon has been great, working with portable Laragon on Wordpress has been fine.
    But on new Windows install, with same files (backed up, restored) on same dir on D drive Heidi/MySQL will not access the db.

    When i try to access my Wordpress db rc through HeidiSQL it hangs then crashes.
    I can access other & default db's, and when I delete /data, but after backup and restore of /data, as I've read on here, it hasn't worked to make rc work.
    I've replaced the files again with backup, allowed Mysqld through Firewall, taken ownership on Windows, administrator mode, added a mysql pass (as last step), and a bunch of other things I've read here, but no dice yet.

    Rc.test shows:
    Error establishing a database connection

    MySqld.log:
    2021-03-07T15:34:20.009703Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2021-03-07T15:34:20.009754Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path. 2021-03-07T15:34:20.010057Z 0 [Note] D:\MyApps\Laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld (mysqld 5.7.24) starting as process 15860 ...

    Laragon.log
    Check that mysqld is running on localhost and that the port is 3306. You can check this by doing 'telnet localhost 3306'

    2021-03-08 01:57:26: Graceful shutdown failed!!! Did you change the root's password? - trying to force it shutdown... ERROR: 2021-03-08 02:08:02: Graceful shutdown failed!!! Did you change the root's password? - trying to force it shutdown... ERROR:
    (Note the above was before adding any MySQL pass)`

    telnet localhost 3306 shows:
    Looking up host: localhost... Trying 127.0.0.1:3306... Connected to localhost. Escape key is ALT-]. J 5.7.24☻S 3♣YB☻§'az=[wpb§U,mysql_native_passwordConnection terminated.


Log in to reply
 

Looks like your connection to Laragon was lost, please wait while we try to reconnect.