Magento backup problem

Magento 2
7

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 :wink: