cancel
Showing results for 
Search instead for 
Did you mean: 

fresh install of magento is getting is getting old cache info

fresh install of magento is getting is getting old cache info

hi

 

I installed a fresh magento 2 store version 2.2.3

new database

deleted all old files

unziped the package and installed magento

 

for some reason when i look at 

/var/log/debug.log

text/x-log debug.log
ASCII text, with very long lines

[2018-05-11 03:39:57] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["BACKEND_MAINMENU"],"mode":"matchingTag"}} []
[2018-05-11 03:39:58] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["CONFIG"],"mode":"matchingTag"}} []
[2018-05-11 03:39:58] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["LAYOUT_GENERAL_CACHE_TAG"],"mode":"matchingTag"}} []
[2018-05-11 03:39:58] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["BLOCK_HTML"],"mode":"matchingTag"}} []
[2018-05-11 03:39:58] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["COLLECTION_DATA"],"mode":"matchingTag"}} []
[2018-05-11 03:39:58] main.DEBUG: cache_invalidate: {"method":"POST","url":"http://www.hijabgem.com/setup/index.php/install/start","invalidateInfo":{"tags":["REFLECTION"],"mode":"matchingTag"}} []

this is a tiny snippet of what it going onn, theres even bits looking for old template files

 

why is this happening, how do i stop it?

 

i flushed the cache and switched of super cache before installing, i don't understand

 

Kind regards

 

1 REPLY 1

Re: fresh install of magento is getting is getting old cache info

If you posted the path /var/log/debug.log it's likely you permissions on the var folder are not sufficient for your webserver to write into. If nginx or apache can't write on [project folder]/var they will write in the general log folder. There, Magento will not be able to clear properly cache.

 

Could be helpful for you to check out if you have the right permissions.

Here the official website: https://devdocs.magento.com/guides/v2.1/install-gde/prereq/file-system-perms.html

 

For example, each time i run composer install I have to reset permissions on my computer (cuz I'm lazy...)

 

I wrote this script (which does more than enough). But ensure you set the right ownership.

 

ME=`whoami`

if [ ! -d var ] || [ ! -d pub ] || [ ! -d vendor ]; then
        echo "You are not in a magento folder - exit"
        exit
fi

echo "Restoring ownership..."
sudo chown -R $ME:$ME ./
echo "Fixing files permissions (may take a while)..."

sudo find . -type f -exec chmod 644 {} \;
sudo find . -type d -exec chmod 755 {} \;
sudo find ./var -type d -exec chmod 777 {} \;

sudo chmod 775 -R bin
sudo find ./pub/static -type d -exec chmod 777 {} \;

sudo chmod 777 ./app/etc
sudo chmod 644 ./app/etc/*.xml

sudo chmod 775 -R var/log
sudo chmod 775 -R pub

 

Hope it helps.

 

Kind regards,

Angelo