• Hi there,

    everything is green/working. just the 2 MYSQL paths are wrong…

    Backup folder exists
    Backup folder is writable
    Checking MYSQL Dump Path …
    MYSQL dump path does NOT exist. Please check your mysqldump path under DB Options. If uncertain, contact your server administrator.
    Checking MYSQL Path …
    MYSQL path does NOT exist. Please check your mysql path under DB Options. If uncertain, contact your server administrator.
    Checking PHP Functions (passthru(), system() and exec()) …
    passthru() enabled.
    system() enabled.
    exec() enabled.
    Please Rectify The Error Highlighted In Red Before Proceeding On.

    best, Jan

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter JPredator

    (@jpredator)

    Hello? please help me πŸ˜›

    Well, the path’s url will depend on your web host. You should contact them, ideally, and ask, they’ll know πŸ™‚

    Otherwise, don’t you have an “Auto Detect” feature ?

    On *nux servers, most often this is
    path to mysqldump: /usr/bin/mysqldump
    path to mysql: /usr/bin/mysql
    But then again, it can vary a lot.

    Thread Starter JPredator

    (@jpredator)

    thx for your reply.
    hm okey…
    its on strato i think.
    where do i have to change that url? in which file?

    Thread Starter JPredator

    (@jpredator)

    ah okay i found where to write in the URL…
    Auto Detect doesent work… how to find out, now?
    by Try-n-Error?

    In this regard, try and error should be danger-free, at worst nothing happens and no dump is made, I believe.

    Or, if you can afford to lose a day, send an email to your web host, to ask them the information. Answering you is part of their jobs, you know πŸ™‚

    Thread Starter JPredator

    (@jpredator)

    yah i tried now… but by phone the guy doesnt know o.O
    ill try again by mail now…

    it is a strato-account. so the ftp is different to mysql.
    all theyr mysql databases are at “rdbms.strato.de”

    maybe someone runs wp-dbmanager on strato?
    and does it even work on different server-urls?
    …or what happens if the logins are different? πŸ™

    have a nice day. Jan

    Thread Starter JPredator

    (@jpredator)

    okay now it says /usr/bin/mysqldump works XD
    i ll try out now … πŸ˜›

    Ooops, I forgot the required addition: you may replace /mysql with /mysqldump

    Thread Starter JPredator

    (@jpredator)

    if he brings this message in the admin panel it should be fine, or?

    Checking MYSQL Dump Path (/usr/bin/mysqldump) …
    MYSQL dump path exists.

    Checking MYSQL Path (/usr/bin/mysql) …
    MYSQL path exists.

    Thread Starter JPredator

    (@jpredator)

    okay i get a .sql file. By Mail too.
    the file has 3.5 MB.
    i activated “Database Backup Type: Full (Structure and Data)”

    but the pictures/files and so on are not included at this little size i think.
    i thought it backups the whole wordpress-site including pictures and database?

    That’s because these are not the same things πŸ™‚

    Your blog is composed of two things:
    – the files
    – the database

    The files are
    (1) the files wordpress is using to work, just like the various gears you’ll find in a car engine. PHP, html, css, whatever. That also includes the plugins and the themes
    (2) the media you have uploaded to your blog through your activity. Mostly picture attachments, for the posts, or your user profile. This is the content of wp-content/uploads/ , and this is YOUR content, in opposition to all the other files
    You can browse the files in your FTP client.

    The database is a very special thing, you do NOT have access to the database itself (your web host stores it in some place you cannot browse, in a special format), all you can do is read and write it. To make the comparison with a car, this time the engine’s bulk is sealed shut so you cannot open it, but you are still allowed to drive the car.
    You can access your database through utilies like PhpMyAdmin, and your blog engine will access it through its own commands.

    The database does not contain files, it contains *information*. In there, your blog stores options, preferences, settings, user information submitted in the past. It also stores the contents of your blog posts: the entry, the date, the title, etcetera.

    Do you see the idea, now ? πŸ™‚

    As for the backups, with your database dump, you have saved the textual content of your posts, your user information, and every configuration for everything on your blog.
    But you haven’t saved your media (such as the attachments). You also haven’t saved your blog theme, or your current plugins.

    To make full backups of both your own files and your database, I recommend you read that page: https://codex.wordpress.org/WordPress_Backups , it looks scary at first but actually that’s pretty straightforward πŸ™‚

    Thread Starter JPredator

    (@jpredator)

    Thanks for your description πŸ™‚
    i know that these are 2 different things… but i read that this wp-dbmanager plugin should safe both.
    that would be just perfect (even if the backups would be big files because of all the jpgs…)

    but if the jpgs are not included … i think i can live with that πŸ˜›

    thank you. have a nice day.

    Glad to help πŸ™‚

    Wp-dbmanager won’t save both, but if you look at this ist of wordpress plugins: https://wordpress.org/plugins/search.php?q=backup , you’ll find you have quite a lot of choice to backup everything in one go.

    Additionally, it’s true, if you’re up to downloading stuff manually, WP-Dbmanager will store the backups of the database in a place that can be reached by FTP (wp-content/backup-db), so if you download by FTP your /wp-config.php and the entirety of your /wp-content/ folder right after you ran a backup in wp-dbmanager, you’re covered.

    Thread Starter JPredator

    (@jpredator)

    Perfect πŸ™‚ Yes, thats an easy way to just download it via FTP. I’ll do that.
    thanks again!

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘MYSQL dump path does NOT exist’ is closed to new replies.