Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    Yes, it should be reducing disk space, the only way it would not is if WebP is enabled, but I see no evidence of that in your plugin status. The delete originals option does nothing, unless you are using some of the conversion options like JPG2PNG or GIF2PNG. All optimizations are done “in place” otherwise.

    How much of a size increase are you seeing?

    The error message you are getting is because your php config is still trying to load the suhosin security module, which is deprecated, and apparently no longer available on your machine. If you are not the server admin, i would mention it to your webhost right away.

    Thread Starter kalel35

    (@kalel35)

    Processing 10K images has increased Disk Used by almost 1 GB if I remember where it started correctly. Ironically according to the plugin I have only saved 100MB in the process.

    The site is running on a VPS that I control. So how would I fix this?

    Thanks

    Plugin Author nosilver4u

    (@nosilver4u)

    Look in the /etc/php5 folder (might be slightly different location on RedHat/CentOS) for anything named suhosin, and delete it, then restart your php daemon or web server process.

    As far as the disk space, I would look in your uploads folder to see if there are any files that got orphaned with a .tmp or .prog file extension.

    Something like this should do the trick:

    find /var/www/ -iname '*.prog'

    And then of course repeat that for *.tmp

    The only other thing that will grow slightly is your mysql db, but all we are storing is filenames and sizes for each image processed. My local database with over 30,000 records is only 66M.

    Thread Starter kalel35

    (@kalel35)

    Sadly I can’t find the php5 folder in cPanel , and don’t really understand the rest of your recommendations. I guess I get to spend the day on YouTube teaching myself new things.

    Just for the record…if it matters…I am STILL getting those errors every couple seconds even though I am NOT running the EWWW plugin currently.

    Plugin Author nosilver4u

    (@nosilver4u)

    I don’t think you’ll find it in cpanel, but I’ve never used cpanel on a vps. The /etc/php5 folder is at the root of your filesystem, and I’m not sure cpanel will have access to it (I sure wouldn’t give it that kind of access).

    And yeah, you’ll get those errors on every single page load, no matter what you’re running. Even if it wasn’t wordpress, and just a simple php script, it would throw that error.

    Thread Starter kalel35

    (@kalel35)

    Well I can admit when I am beyond my depth. I don’t understand your explanation, so you can mark this as “resolved” if you want and I will find another solution. Thanks.

    Plugin Author nosilver4u

    (@nosilver4u)

    Is this a managed or unmanaged VPS?

    unmanaged = you setup the web server, php, mysql and everything from scratch, something like Digital Ocean or Ramnode

    managed = your webhost did all of that, but gives you dedicated resources for your website

    Thread Starter kalel35

    (@kalel35)

    It’s a managed VPS (HostDime)

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, then I would ask HostDime to fix your php configuration. I would suspect you don’t have full control over the server-level config files, probably only able to do vhost or directory specific php.ini configs.
    That said, I have had times myself where I could regenerate my php.ini, because I was referencing php modules that no longer existed, like yours seems to be doing with suhosin. If you’re not sure where to find that, again, ask HostDime for help.

    Really not sure what to think on the disk space issue, since I can’t think of a scenario where it would increase unless you had .prog or .tmp files being abandoned. You could probably even just look at the uploads sub-folders with your file manager to double-check that EWWW isn’t doing that.

    Thread Starter kalel35

    (@kalel35)

    This is the Reply that I received from them with regards to this ongoing error….

    ========================================================

    “The error you are receiving is result of the file it designates not existing. The contents of the folder /usr/local/lib/php/extensions/no-debug-non-zts-20090626/ are as follows:

    -rwxr-xr-x 1 root root 45212 Dec 18 14:21 pdo_mysql.so*
    -rwxr-xr-x 1 root root 135062 Dec 18 14:21 pdo.so*
    -rwxr-xr-x 1 root root 872737 Dec 18 14:21 pdo_sqlite.so*
    -rwxr-xr-x 1 root root 491845 Dec 18 14:21 sqlite.so*

    Most of the current disk space usage is confined to a single folder of thousands of images. That folder is /home/nationalticketag/public_html/wp-content/uploads/2014/12. We have created a sorted list of all the files located in this directory and their sizes sorted by order of size at /home/nationalticketag/sortedimagelist.txt.

    While we are not familiar with this specific plugin and are not able to provide any detailed support for it, based on the naming convention of the files located in this folder, it does appear that entries created before Dec 16th were named and described image names, such as “St-Louis-Blues-NHL-Mens-Long-Sleeve-V-Neck-Hockey-Jersey-Blue-XX-Large-0.jpg” where as images created after that date are in the naming convention of “ff_867128_xl-300×300.jpg” or “ff_1798242_xl.jpg”. This to us indicates that it is possible that this plugin may be creating a copy of each image on your site using this somewhat randomized number naming convention, and that while these final copies may be smaller files, their presence in the short term created what are essentially duplicates of each image, the original described image, and the compressed numbered image, as the previous tech suggested as a possibility. We recommend contacting the publisher of this plugin for confirmation and more detailed information, as well as how they would recommend proceeding.”

    ===============================================================

    Honestly…since I am using the minimal compress (no loss) the savings really isn’t worth it. I just upgraded to a larger VPS that is twice the disk size and memory.

    Is there anyway to remove the compressed images and go back to the images I was previously using?

    Anyone reading this should NOT interpret this as a negative review of this plugin.

    Please advise. Thanks

    Plugin Author nosilver4u

    (@nosilver4u)

    Those images don’t come from EWWW IO. What other plugins have you activated recently?

    If you could you send me the txt file that they gave you via https://ewww.io/contact-us/ I’ll take a look at it as well to see if I spot any patterns.

    Thread Starter kalel35

    (@kalel35)

    OK…I looked a little closer, and I was importing images via an Amazon Affiliate Plugin. On the 16th I switched over to WooCommerce All Import so that would account for the image name change. It still doesn’t account for the 1G of disk space I used up trying to compress images…especially since I only managed to compress about 10K images and only saved 100MB or so (according the plugin).

    The file is 23MB so I had to add it DropBox….

    https://www.dropbox.com/s/6f6pvbud2cbxvry/sortedimagelist.txt?dl=0

    Thanks for the help

    Plugin Author nosilver4u

    (@nosilver4u)

    The only images that get created by EWWW are the .tmp and .prog files which get cleaned up after optimization. As you can see in that folder listing, there are no .tmp or .prog files, so the plugin is operating as expected. Therefore, the disk space increase did not come from EWWW IO.

    A bit of a bummer that you only saw 100MB with 10k images, but everyone’s experience varies on that, and lossless compression can only do so much, especially if the images are already somewhat optimized.

    Thread Starter kalel35

    (@kalel35)

    Well I appreciate your help. I am still curious where an extra 1GB of data came from, but I suppose it will remain a mystery. Thanks for your time.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Increasing Disk Space Use’ is closed to new replies.