Magento backup problem

michal · March 1, 2019, 8:19am

Hi there, I’ve got yet another problem after installing Magento 2.3. Yesterday I was about to install magento theme but since I’m a real newbie I’ve decided to make an backup as is seemed logical to do. I’ve enableb backups in setting, went to backup menu and clicked “system backup”. I’ve ticked the “maintenance mode” although it showed me message that my account didn’t have authorization for this. Anyway, I went with it and my page did go to maintenance mode and I can’t acces it since. First I thought it just takes some time, which I still believe to be true, but I did yesterday morning and my page still shows:

" Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."

Both front and back end. Did I do something really wrong? Can I stop/restart this via ssh?
Thanks in advance

digitalstartup · March 1, 2019, 10:42am

Hi @michal,

This is actually an easy one to get out of and you have some options.

Delete the flag
When you go into Maintenance Mode, Magento creates a blank file here:

<Magento root folder>/var/.maintenance.flag

When Magento has finished doing what it needs, it deletes that file afterwards. Because you ran into a problem, this never had a chance to happen. But it’s totally safe to delete it manually one of 2 ways:

You can delete the file via FTP (e.g. FileZilla)
Delete the file via the Command Line Interface using the below command

Run as magento user from the Magento root folder:

rm var/.maintenance.flag

Whitelist your IP (future-proofing)
When in Maintenance Mode, you can actually whitelist your IP address so that you can bypass this screen rather than get locked out of your own website. This is also done via the Command Line Interface:

Run as magento user from the Magento root folder:

bin/magento maintenance:allow-ips 123.123.123.123

Example Output

magento@DS-M23v:/var/www/html$ bin/magento maintenance:allow-ips 123.123.123.123
Set exempt IP-addresses: 123.123.123.123

Obviously the suitability of this depends on how often your IP address changes.

The original issue
Obviously this fixes the symptom, not the original issue. So, once you’re back up and running feel free to continue the discussion around why the issue occured to begin with.

Let me know how you get on.

michal · March 1, 2019, 6:32pm

Hi, thanks for the reply. Removing the flag obviously worked, however whitelisting my IP didn’t. I mean, I’ve checked IP through cmd line in windows, added it and it still shows the same message " Service Temporarily Unavailable…". And I think I should solve one thing before getting to the real problem

digitalstartup · March 1, 2019, 6:36pm

Sorry. I’ve edited my answer with the correct command.

michal · March 4, 2019, 4:10pm

So I did whitelist my IP now and its been working corectly. I can enable/disable mantenance mode via ssh although I still can’t do it by ticking the box “maintenance mode” while making backup but I;ve decided to go with it. Anyway. I’ve made both system and data + media backups.
At this point I’ve encountered another problem. I’ve triend to install a Unero theme for my website but something went wrong along the way (or at least so I presume). There was an error on both front and back end:

“An error has happened during application run. See exception log for details. Could not write error message to log. Please use developer mode to see the message.”

So I’ve set the mode to developer and front end shows this:

1 exception(s):
Exception #0 (Exception): Warning: Declaration of MGS\Mpanel\Block\Product\ImageBuilder::create() should be compatible with Magento\Catalog\Block\Product\ImageBuilder::create(?Magento\Catalog\Model\Product $product = NULL, ?string $imageId = NULL, ?array $attributes = NULL) in /var/www/html/app/code/MGS/Mpanel/Block/Product/ImageBuilder.php on line 0

Exception #0 (Exception): Warning: Declaration of MGS\Mpanel\Block\Product\ImageBuilder::create() should be compatible with Magento\Catalog\Block\Product\ImageBuilder::create(?Magento\Catalog\Model\Product $product = NULL, ?string $imageId = NULL, ?array $attributes = NULL) in /var/www/html/app/code/MGS/Mpanel/Block/Product/ImageBuilder.php on line 0
#0 /var/www/html/vendor/composer/ClassLoader.php(444): Magento\Framework\App\ErrorHandler->handler(2, 'Declaration of ...', '/var/www/html/a...', 0, Array)
#1 /var/www/html/vendor/composer/ClassLoader.php(444): include()
#2 /var/www/html/vendor/composer/ClassLoader.php(322): Composer\Autoload\includeFile('/var/www/html/v...')
#3 [internal function]: Composer\Autoload\ClassLoader->loadClass('MGS\\Mpanel\\Bloc...')
#4 [internal function]: spl_autoload_call('MGS\\Mpanel\\Bloc...')
#5 /var/www/html/vendor/magento/framework/ObjectManager/Relations/Runtime.php(38): class_exists('MGS\\Mpanel\\Bloc...')
#6 /var/www/html/vendor/magento/framework/Interception/Config/Config.php(166): Magento\Framework\ObjectManager\Relations\Runtime->has('MGS\\Mpanel\\Bloc...')
#7 /var/www/html/vendor/magento/framework/Interception/Config/Config.php(189): Magento\Framework\Interception\Config\Config->_inheritInterception('MGS\\Mpanel\\Bloc...')
#8 /var/www/html/vendor/magento/framework/Interception/ObjectManager/Config/Developer.php(61): Magento\Framework\Interception\Config\Config->hasPlugins('MGS\\Mpanel\\Bloc...')
#9 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(47): Magento\Framework\Interception\ObjectManager\Config\Developer->getInstanceType('MGS\\Mpanel\\Bloc...')
#10 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('MGS\\Mpanel\\Bloc...')
#11 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(160): Magento\Framework\ObjectManager\ObjectManager->get('MGS\\Mpanel\\Bloc...')
#12 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(246): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\\Catalog...', NULL, 'productImageBui...', 'MGS\\AjaxCart\\Mo...')
#13 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime('MGS\\AjaxCart\\Mo...', Array, Array)
#14 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('MGS\\AjaxCart\\Mo...', Array, Array)
#15 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('MGS\\AjaxCart\\Mo...')
#16 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(160): Magento\Framework\ObjectManager\ObjectManager->get('MGS\\AjaxCart\\Mo...')
#17 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(246): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'MGS\\AjaxCart\\Mo...', NULL, 'processor', 'MGS\\AjaxCart\\Co...')
#18 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime('MGS\\AjaxCart\\Co...', Array, Array)
#19 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('MGS\\AjaxCart\\Co...', Array, Array)
#20 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('MGS\\AjaxCart\\Co...')
#21 /var/www/html/vendor/magento/framework/Interception/PluginList/PluginList.php(250): Magento\Framework\ObjectManager\ObjectManager->get('MGS\\AjaxCart\\Co...')
#22 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(144): Magento\Framework\Interception\PluginList\PluginList->getPlugin('Magento\\Cms\\Con...', 'ajaxcart-action...')
#23 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#24 /var/www/html/generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php(39): Magento\Cms\Controller\Index\Index\Interceptor->___callPlugins('dispatch', Array, Array)
#25 /var/www/html/vendor/magento/framework/App/FrontController.php(159): Magento\Cms\Controller\Index\Index\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#26 /var/www/html/vendor/magento/framework/App/FrontController.php(99): Magento\Framework\App\FrontController->processRequest(Object(Magento\Framework\App\Request\Http), Object(Magento\Cms\Controller\Index\Index\Interceptor))
#27 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch(Object(Magento\Framework\App\Request\Http))
#28 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch', Array)
#29 /var/www/html/vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php(94): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#30 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#31 /var/www/html/vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php(69): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#32 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(135): Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#33 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#34 /var/www/html/generated/code/Magento/Framework/App/FrontController/Interceptor.php(26): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, NULL)
#35 /var/www/html/vendor/magento/framework/App/Http.php(135): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#36 /var/www/html/generated/code/Magento/Framework/App/Http/Interceptor.php(24): Magento\Framework\App\Http->launch()
#37 /var/www/html/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http\Interceptor->launch()
#38 /var/www/html/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http\Interceptor))
#39 {main}

Well, I guess answer is here but obviously I can’t find it. I’d really appreciate your help with this

The back end just loaded, showed me log in tab and as I logged it it showed some terribly formatted code:

PDOException: SQLSTATE[HY000] [2002] No such file or directory in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Abstract.php:128 Stack trace:
#0 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Abstract.php(128): PDO-&gt;__construct('mysql:host=loca...', 'adminsp', 'J&gt;scJ!__connect()
#2 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(406): Zend_Db_Adapter_Pdo_Mysql-&gt;_connect() #3 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Abstract.php(460): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;_connect()
#4 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract-&gt;query('SELECT `store_w...', Array) 
5 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(541): Zend_Db_Adapter_Pdo_Abstract-&gt;query('SELECT `store_w...', Array)
#6 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(615): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;_query('SELECT `store_w...', Array)
#7 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Abstract.php(737): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;query(Object(Magento\Framework\DB\Select), Array)
#8 /var/www/html/vendor/magento/module-store/App/Config/Source/RuntimeConfigSource.php(87): Zend_Db_Adapter_Abstract-&gt;fetchAll(Object(Magento\Framework\DB\Select))
#9 /var/www/html/vendor/magento/module-store/App/Config/Source/RuntimeConfigSource.php(57): Magento\Store\App\Config\Source\RuntimeConfigSource-&gt;getEntities('store_website', 'code')
#10 /var/www/html/vendor/magento/framework/App/Config/ConfigSourceAggregated.php(40): Magento\Store\App\Config\Source\RuntimeConfigSource-&gt;get('')
#11 /var/www/html/generated/code/Magento/Framework/App/Config/ConfigSourceAggregated/Proxy.php(95): Magento\Framework\App\Config\ConfigSourceAggregated-&gt;get('')
#12 /var/www/html/vendor/magento/module-store/App/Config/Type/Scopes.php(63): Magento\Framework\App\Config\ConfigSourceAggregated\Proxy-&gt;get()
#13 /var/www/html/vendor/magento/framework/App/Config.php(131): Magento\Store\App\Config\Type\Scopes-&gt;get('websites')
#14 /var/www/html/vendor/magento/module-store/Model/WebsiteRepository.php(183): Magento\Framework\App\Config-&gt;get('scopes', 'websites', Array)
#15 /var/www/html/vendor/magento/module-store/Model/WebsiteRepository.php(142): Magento\Store\Model\WebsiteRepository-&gt;initDefaultWebsite()
#16 /var/www/html/vendor/magento/module-store/Model/StoreResolver/Website.php(49): Magento\Store\Model\WebsiteRepository-&gt;getDefault()
#17 /var/www/html/vendor/magento/module-store/Model/StoresData.php(65): Magento\Store\Model\StoreResolver\Website-&gt;getAllowedStoreIds(NULL)
#18 /var/www/html/vendor/magento/module-store/Model/StoreResolver.php(138): Magento\Store\Model\StoresData-&gt;getStoresData('website', NULL)
#19 /var/www/html/vendor/magento/module-store/Model/StoreResolver.php(97): Magento\Store\Model\StoreResolver-&gt;getStoresData()
#20 /var/www/html/vendor/magento/module-store/Model/StoreManager.php(157): Magento\Store\Model\StoreResolver-&gt;getCurrentStoreId()
#21 /var/www/html/generated/code/Magento/Store/Model/StoreManagerInterface/Proxy.php(119): Magento\Store\Model\StoreManager-&gt;getStore(NULL)
#22 /var/www/html/vendor/magento/module-store/Model/Resolver/Store.php(30): Magento\Store\Model\StoreManagerInterface\Proxy-&gt;getStore(NULL)
#23 /var/www/html/vendor/magento/framework/App/Config/ScopeCodeResolver.php(49): Magento\Store\Model\Resolver\Store-&gt;getScope(NULL)
#24 /var/www/html/vendor/magento/framework/App/Config.php(69): Magento\Framework\App\Config\ScopeCodeResolver-&gt;resolve('stores', NULL)
#25 /var/www/html/vendor/magento/module-developer/Model/Logger/Handler/Debug.php(63): Magento\Framework\App\Config-&gt;getValue('dev/debug/debug...', 'stores')
#26 /var/www/html/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(31): Magento\Developer\Model\Logger\Handler\Debug-&gt;isHandling(Array)
#27 /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php(344): Monolog\Handler\AbstractProcessingHandler-&gt;handle(Array) #28 /var/www/html/vendor/magento/framework/Logger/Monolog.php(48): Monolog\Logger-&gt;addRecord(400, 'SQLSTATE[HY000]...', Array)
#29 /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php(707): Magento\Framework\Logger\Monolog-&gt;addRecord(400, 'SQLSTATE[HY000]...', Array)
#30 /var/www/html/vendor/magento/framework/App/Bootstrap.php(263): Monolog\Logger-&gt;error('SQLSTATE[HY000]...')
#31 /var/www/html/index.php(39): Magento\Framework\App\Bootstrap-&gt;run(Object(Magento\Framework\App\Http\Interceptor))
#32 {main} 

Next Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Abstract.php:144 Stack trace:
#0 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Mysql.php(111): Zend_Db_Adapter_Pdo_Abstract-&gt;_connect() #1 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(406): Zend_Db_Adapter_Pdo_Mysql-&gt;_connect()
#2 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Abstract.php(460): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;_connect()
#3 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract-&gt;query('SELECT `store_w...', Array)
#4 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(541): Zend_Db_Adapter_Pdo_Abstract-&gt;query('SELECT `store_w...', Array)
#5 /var/www/html/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(615): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;_query('SELECT `store_w...', Array)
#6 /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Adapter/Abstract.php(737): Magento\Framework\DB\Adapter\Pdo\Mysql-&gt;query(Object(Magento\Framework\DB\Select), Array)
#7 /var/www/html/vendor/magento/module-store/App/Config/Source/RuntimeConfigSource.php(87): Zend_Db_Adapter_Abstract-&gt;fetchAll(Object(Magento\Framework\DB\Select))
#8 /var/www/html/vendor/magento/module-store/App/Config/Source/RuntimeConfigSource.php(57): Magento\Store\App\Config\Source\RuntimeConfigSource-&gt;getEntities('store_website', 'code')
#9 /var/www/html/vendor/magento/framework/App/Config/ConfigSourceAggregated.php(40): Magento\Store\App\Config\Source\RuntimeConfigSource-&gt;get('')
#10 /var/www/html/generated/code/Magento/Framework/App/Config/ConfigSourceAggregated/Proxy.php(95): Magento\Framework\App\Config\ConfigSourceAggregated-&gt;get('')
#11 /var/www/html/vendor/magento/module-store/App/Config/Type/Scopes.php(63): Magento\Framework\App\Config\ConfigSourceAggregated\Proxy-&gt;get()
#12 /var/www/html/vendor/magento/framework/App/Config.php(131): Magento\Store\App\Config\Type\Scopes-&gt;get('websites')
#13 /var/www/html/vendor/magento/module-store/Model/WebsiteRepository.php(183): Magento\Framework\App\Config-&gt;get('scopes', 'websites', Array)
#14 /var/www/html/vendor/magento/module-store/Model/WebsiteRepository.php(142): Magento\Store\Model\WebsiteRepository-&gt;initDefaultWebsite()
#15 /var/www/html/vendor/magento/module-store/Model/StoreResolver/Website.php(49): Magento\Store\Model\WebsiteRepository-&gt;getDefault()
#16 /var/www/html/vendor/magento/module-store/Model/StoresData.php(65): Magento\Store\Model\StoreResolver\Website-&gt;getAllowedStoreIds(NULL)
#17 /var/www/html/vendor/magento/module-store/Model/StoreResolver.php(138): Magento\Store\Model\StoresData-&gt;getStoresData('website', NULL)
#18 /var/www/html/vendor/magento/module-store/Model/StoreResolver.php(97): Magento\Store\Model\StoreResolver-&gt;getStoresData()
#19 /var/www/html/vendor/magento/module-store/Model/StoreManager.php(157): Magento\Store\Model\StoreResolver-&gt;getCurrentStoreId()
#20 /var/www/html/generated/code/Magento/Store/Model/StoreManagerInterface/Proxy.php(119): Magento\Store\Model\StoreManager-&gt;getStore(NULL)
#21 /var/www/html/vendor/magento/module-store/Model/Resolver/Store.php(30): Magento\Store\Model\StoreManagerInterface\Proxy-&gt;getStore(NULL)
#22 /var/www/html/vendor/magento/framework/App/Config/ScopeCodeResolver.php(49): Magento\Store\Model\Resolver\Store-&gt;getScope(NULL)
#23 /var/www/html/vendor/magento/framework/App/Config.php(69): Magento\Framework\App\Config\ScopeCodeResolver-&gt;resolve('stores', NULL)
#24 /var/www/html/vendor/magento/module-developer/Model/Logger/Handler/Debug.php(63): Magento\Framework\App\Config-&gt;getValue('dev/debug/debug...', 'stores')
#25 /var/www/html/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(31): Magento\Developer\Model\Logger\Handler\Debug-&gt;isHandling(Array)
#26 /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php(344): Monolog\Handler\AbstractProcessingHandler-&gt;handle(Array)
#27 /var/www/html/vendor/magento/framework/Logger/Monolog.php(48): Monolog\Logger-&gt;addRecord(400, 'SQLSTATE[HY000]...', Array)
#28 /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php(707): Magento\Framework\Logger\Monolog-&gt;addRecord(400, 'SQLSTATE[HY000]...', Array)
#29 /var/www/html/vendor/magento/framework/App/Bootstrap.php(263): Monolog\Logger-&gt;error('SQLSTATE[HY000]...')
#30 /var/www/html/index.php(39): Magento\Framework\App\Bootstrap-&gt;run(Object(Magento\Framework\App\Http\Interceptor))
#31 {main}

digitalstartup · March 4, 2019, 5:16pm

Mode Switching
It’s standard practice to run the below command after switching to Developer Mode. Not sure if you’ve done this or will fix anything, but figured I’d mention. Run as magento user from Magento root:

rm -rf generated/metadata/* generated/code/*

Ownership Checks
Do the following outputs show the correct Owner and Group?

```
ls -la /var/www/html/
```
```
ls -la /var/www/html/var/
```

They should be either of these:

magento www-data
www-data www-data

Frontend Error
Usually, it’s the first 2-3 lines that will give away the biggest clues. According to the exception, it has an issue with something called MGS/Mpanel. A quick Google search appears to suggest this could be something called “MGS Frontend Builder Theme”. No idea if this is a standalone module you’ve installed or whether it’s part of the Unero theme you tried to install?

Anyway, I Google “Warning: Declaration of MGS\Mpanel\Block\Product\ImageBuilder” and found this in the Unero Themeforest comments.

Seems to be the same issue as you? Some sort of conflict. Therefore an issue with the Theme, not something you’ve done. If that doesn’t solve it, you might want to raise a support ticket directly with them.

Backend Error
Not sure if this will is also related to the Frontend error or not… But the following might (or might not) fix both. Run as magento user from Magento root:

```
composer update
```
```
bin/magento setup:upgrade
```

michal · March 4, 2019, 7:05pm

Mode switching
So I run that commend, doesn’t seem to do much in my case.

Ownership checks
That’s what I got after both commends.

magento@seampress:/var/www/html$ ls -la /var/www/html/
-bash: fork: Cannot allocate memory
magento@seampress:/var/www/html$
magento@seampress:/var/www/html$ ls -la /var/www/html/var/
total 60
drwxrwsr-x 10 magento  www-data 4096 Mar  4 19:46 .
drwxr-xr-x 14 magento  www-data 4096 Mar  4 14:52 ..
drwxrwx---  2 magento  www-data 4096 Mar  4 11:37 backups
drwxrwsr-x 13 www-data www-data 4096 Mar  4 17:15 cache
drwxrwsr-x  3 www-data www-data 4096 Feb 28 12:47 composer_home
-rw-rw-r--  1 magento  www-data  126 Feb 27 11:19 .htaccess
drwxrwsr-x  2 www-data www-data 4096 Mar  4 15:29 log
-rw-rw-r--  1 magento  www-data   14 Mar  4 10:58 .maintenance.ip
drwxrwsr-x 19 www-data www-data 4096 Mar  4 14:06 page_cache
drwxrwsr-x  2 www-data www-data 4096 Mar  4 16:54 report
-rw-rw-r--  1 magento  www-data 6557 Mar  4 19:46 .setup_cronjob_status
drwxrwsr-x  2 www-data www-data 4096 Mar  4 15:17 tmp
-rw-r--r--  1 magento  www-data  148 Mar  4 19:46 .update_cronjob_status
drwxrwsr-x  3 www-data www-data 4096 Mar  4 15:16 view_preprocessed

The first error “cannot allocate memory”. While installing all the modules from Unero theme I also got one line with something about memory allocation.

Frontend error
I guess I’ll raise a ticket there. The MGS module is a part of the Unero theme and I believie an important one as their documantaion says:

Module MGS_Mpanel is indispensable

Backend error
Another problem here

magento@seampress:/var/www/html$ bin/magento composer update
  Command "composer" is not defined.
magento@seampress:/var/www/html$ bin/magento setup:upgrade
-bash: fork: Cannot allocate memory

Note
Also I nearly forgot that I’ve put down one note I got while installing those modules which was related to modes of Magento.

NOTE: Manual static content deployment is not required in "default" and "developer" modes.
  In "default" and "developer" modes static contents are being deployed automatically on demand.
  If you still want to deploy in these modes, use -f option: 'bin/magento setup:static-content:d
  eploy -f'

and I believe that somewhere around content deployment I got that memory notifcation I mentiond earlier.

Too conclude, I’m rather lost in this. I’ve done backups and I’ve got them downloaded. Maybe there is an easy way to get myself clean Magento start to try it again? If not I guess I will be trying to fix mess I got here

digitalstartup · March 4, 2019, 7:22pm

Ownership Checks

Everything looks good here

Backend Error
I typo’d the composer command. I’ve updated my reply.

"Cannot allocate memory" Error
This error message means that you don’t have enough available PHP memory to execute the command. It’s a common issue on systems with 2GB or less of memory. Ideally a minimum of 4GB is the recommended allowance (2GB for PHP and 2GB for everything else). If your system does already have a minimum of 4GB of memory, then you need to check your .htaccess files.

Open .htaccess

nano .htaccess

Use your Arrow or Page Up/Down keys to work your way down the file and find a line containing memory_limit. You’ll actually find 2 instances in the file, one under mod_php5 and one under mod_php7. Just go ahead and change the instance under PHP 7.

Replace this:

php_value memory_limit 756M

with this:

php_value memory_limit 2G

To save your changes, press Ctrl+X . Then you’ll be asked if you want to save your changes. Simply Type “Y” and then Enter to do so.

Then re-run the below commands:

```
composer update
```
```
bin/magento setup:upgrade
```

michal · March 5, 2019, 10:42am

Composer did update but after I put second command it showed this:

magento@seampress:/var/www/html$ bin/magento setup:upgrade
SQLSTATE[HY000] [2002] No such file or directory

Which basically is the first sentence from my current web error.
Maybe I should simply rollback to Magento without my theme and try it again? Or is it pointless?

digitalstartup · March 5, 2019, 11:03am

I only have 2 suggestions and 1 longshot for this issue:

Disk Space
Unable to create required folder/files due to inadequate disk space. This sometimes happens when your error logs get out of hand. Might be worth a check. Run as any user from any directory:

df -h

Example Output

Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           396M   41M  356M  11% /run
/dev/vda1        78G  5.5G   72G   8% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/vda15      105M  3.4M  101M   4% /boot/efi
tmpfs           396M     0  396M   0% /run/user/1000

The Filesystem with the largest drive (e.g. 78G) is your disk space. Just check that the "Use% is not 100%. If it is, I’ll give you some tips on what to delete etc…

MySQL Crash
MySQL may have crashed at some point (possibly resource related). Try restarting it. Run as superuser from any directory:

sudo service mysql restart

Hopefully, that’ll jump start everything.

Longshot
Finally, I found this post that suggests you to “set the database hostname as 127.0.0.1 instead of localhost”. I’m not sure if this:

The setting in app/etc/env.php
The setting in phpMyAdmin (user/database)
or both?

As I’ve had to change this before. Obviously, you could do a rollback as suggested but it might be worth looking at the above 3 things first - For science

michal · March 5, 2019, 11:47am

Well.

Disk space
This one is fine. I use aroud 11%.

MySQL Crash
I’ve restarted it couple of times now and does’t seem to do much. Although on the front end I don’t get SQSTATE error but the MGS modul one. The back end loads terribly long but it sometimes gets to the point where I can log in. So maybe it did something after all.

Longshot
Changing it in app/etc/env.php didn’t change anything. And changing the database name via phpMyAdmin is really hard, I only could log in once and it kicked me in few seconds. Also phpMyAdmin shows the same error code as front end did #2002 - No such file or directory.

Conclusion
Am I running into two errors? One being problem with mySQL and php libraries and the second one being problem with MGS module in my theme?

And once again thanks so much for helping me

edit:
Also I’ve just raised a ticket with their support so we"ll see where it gets me

digitalstartup · March 5, 2019, 12:32pm

I think I agree, that there are 2 things going on here. The MGS module is definitely one of them, based on that comment I found on Themeforest.

Did restarting mysql give you back access to the backend? Or could you get on there anyway?

If backend is super-slow, it might be regenerating the cache. Or perhaps all the caches are currently disabled? That would definitely kill your load times for sure. You could either enable in System >Cache Management on the backend or via the Command Line Interface. Run as magento user in Magento root directory:

bin/magento cache:enable

You’ll either see:

There is nothing to change in cache status

or something like this:

Changed cache status:
                        config: 0 -> 1
                        layout: 0 -> 1
                    block_html: 0 -> 1
                   collections: 0 -> 1
                    reflection: 0 -> 1
                        db_ddl: 0 -> 1
               compiled_config: 0 -> 1
                           eav: 0 -> 1
         customer_notification: 0 -> 1
            config_integration: 0 -> 1
        config_integration_api: 0 -> 1
                     full_page: 0 -> 1
             config_webservice: 0 -> 1
                     translate: 0 -> 1
                        vertex: 0 -> 1

No problem. Despite the issues, this is how we learn. And hopefully you’ll have the opportunity to pass that knowledge and experience onto others.

michal · March 5, 2019, 3:08pm

I used the code and I got:

Changed cache status:
                        config: 0 -> 1
                        layout: 0 -> 1
                    block_html: 0 -> 1
                   collections: 0 -> 1
                    reflection: 0 -> 1
                        db_ddl: 0 -> 1
               compiled_config: 0 -> 1
                           eav: 0 -> 1
         customer_notification: 0 -> 1
            config_integration: 0 -> 1
        config_integration_api: 0 -> 1
                     full_page: 0 -> 1
             config_webservice: 0 -> 1
                     translate: 0 -> 1
                        vertex: 0 -> 1
Cleaned cache types:
config
layout
block_html
collections
reflection
db_ddl
compiled_config
eav
customer_notification
config_integration
config_integration_api
full_page
config_webservice
translate
vertex

And the back end finally works. It did load like 10 minutes or so but now it seems that it works pretty much normally. I will try to finish theme installation and see wheter it helps the front end as this one still shows MGS error.

edit:
So, I finalazied theme installation via admin panel. I had small problem there, while installing the theme I got the message “Can’t create directory, unable to access” and I ended up creating them manually through FileZilla until it worked. That raises up a qustion wheter all my settings are correct as it seems I simply don’t have all the rights on my admin account, the same problem I got with ticking “Maintanance mode” while making a backup.
And about the front end error I fixed by simply updating the theme. Which is really odd because I updated it as soon as I originally updated files on FTP server. I did it again and it worked. Anyway it works now, so thanks for helping

michal · March 6, 2019, 5:59pm

Sorry for two posts in a row but I think you didn’t see my second edit so here I post it again:

So as I thought I ran into problem with denying access. I tried to upload a logo and again I had to create directories manually via FTP and even after Magento can’t copy the logo (and doing it manually won’t work for some reason). I get this:

The file or directory "/var/www/html/pub/media/tmp/design/file/logo_4.png" cannot be copied to "/var/www/html/pub/media/logo/stores/1/logo_4.png" Warning!copy(/var/www/html/pub/media/logo/stores/1/logo_4.png): failed to open stream: Permission denied

So my question is did you ever ran into similar problem or perhaps know a solution to this? I have all the permissions set in user roles, I made another user, same problem. Don’t know what to do.

digitalstartup · March 6, 2019, 6:06pm

Sorry, I never saw your edit.

Glad you got the theme working

There is a known bug regarding the uploading of logos in Magento 2.3. Check the end of this post (Changing logo in magento 2.3.0). It should be fixed in the next patch (2.3.1) which is due at the end of the month. But the post I’ve linked to explains how to “fix” it in the meantime.

See how you get on with that.

michal · March 6, 2019, 6:27pm

No problem, I’ve already did that. I’m aware it’s not the safest method but I really don’t want to wait for the patch, I’ll keep it in mid and hopefully it will bea easy to revert the changes.
Anyway I am able to upload photos however I got an error afterwards:

That’s my problem from some time. I got same issue while installing theme, was unable to create some directories and did it manually via FTP. So I don’t know what the issue is as I’m pretty sure my admin has all the rights.

digitalstartup · March 6, 2019, 7:02pm

Looks like either:

Magento doesn’t have permission to write to the default folder
Magento doesn’t have permission to overwrite the logo_5.png file assuming that file exists already (perhaps owned by another user?)

When you upload via FTP are you using your magento user credentials? If you upload as someone else, it’ll break ownerships.

What output does the below give you?

ls -la /var/www/html/pub/media/logo/default/`

Best case scenario

drwxr-sr-x 2 www-data www-data  4096 Aug 21  2018 .
drwxr-sr-x 4 www-data www-data  4096 Oct 16 13:02 ..
-rw-r--r-- 1 www-data www-data  4211 Jul 17  2018 logo_5.png

Potential issue (wrong owner of existing file)

drwxr-sr-x 2 www-data www-data  4096 Aug 21  2018 .
drwxr-sr-x 4 www-data www-data  4096 Oct 16 13:02 ..
-rw-r--r-- 1 bob      www-data  4211 Jul 17  2018 logo_5.png

michal · March 7, 2019, 11:15am

The output is:

magento@seampress:~$ ls -la /var/www/html/pub/media/logo/default/
total 12
drwxr-sr-x 2 magento www-data 4096 Mar  4 15:02 .
drwxr-sr-x 4 magento www-data 4096 Mar  6 12:34 ..
-rw-r--r-- 1 magento www-data  514 Mar  4 15:02 logo.png

Which I think is a good one? When uploading via FTP I used magento user.

digitalstartup · March 7, 2019, 12:29pm

That looks spot-on. Hmm…

Out of curiosity, can you check that your cron is setup under the correct user. If you were to setup cron under the incorrect user, Magento would try and run tasks as that person resulting in an Ownership issue. Run below as magento user from any directory:

crontab -l

Sample Output (Expected)

* * * * * /usr/bin/php7.2 /var/www/html/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /var/www/html/var/log/magento.cron.log
* * * * * /usr/bin/php7.2 /var/www/html/update/cron.php >> /var/www/html/var/log/update.cron.log
* * * * * /usr/bin/php7.2 /var/www/html/bin/magento setup:cron:run >> /var/www/html/var/log/setup.cron.log

Sample Output (Bad)

no crontab for magento

Then you’d have to check who the cron tasks are setup under than change them so that magento user runs them instead.

Other than that, I’m not sure what else to think of right now - Unless of course it’s a bug I don’t know about.

michal · March 7, 2019, 1:58pm

Well, so it’s set correctly i suppose:

#~ MAGENTO START 40d1b2d83998fabacb726e5bc3d22129
* * * * * /usr/bin/php7.2 /var/www/html/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /var/www/html/var/log/magento.cron.log
* * * * * /usr/bin/php7.2 /var/www/html/update/cron.php >> /var/www/html/var/log/update.cron.log
* * * * * /usr/bin/php7.2 /var/www/html/bin/magento setup:cron:run >> /var/www/html/var/log/setup.cron.log
#~ MAGENTO END 40d1b2d83998fabacb726e5bc3d22129

Chcecked out of curiosity and still get the same error when trying to upload logo again. Although I get different error when choosing previously uploaded logo. I get this one:

header_logo_src does not contain field 'file'

Which is the same one I got before editing core code. So I don’t know. Am I to wait for the patch? I’m out of ideas at this point as I couldn’t find any anser in the web.