lxcfs | FUSE filesystem for LXC | Continuous Deployment library

You are mixing things here.

You are using ll in your host, but /srv/jekyll/blog is inside the container.

Capstone seems to provide pkg-config .pc file. So, the following should work:

This can happen due to multiple reason. Please check if the app itself is running any demon from within. What do you see when you run ps aux || grep node. If you can post your app.js or server.js or index.js or anything which acts as main file of your application file here that would help to diagnose the issue.

if you are setting any environment variable like production you can do it explicitly i.e export NODE_ENV=production

You can start the server.js app without npm with pm2 with below command pm2 start server.js -- --prod This should work without any problem.

For anything more than this i would recommend the pm2 config file this is the right way of using pm2 scripts.

Use chmod command to change file access permission such as read(r), write(w) and execute(x).

Use chown command to change file owner and group information.

if you want to change file access permission then try it :

sudo chmod 777 /var/www/seekadventure.net

4 stands for read.

2 stands for write.

1 stands for execute.

0 stands for no permission.

First /dev/loop* are virtual devices to mount disk images used by snapd service, it is perfectly normal that they are at 100% because these are read only.

The error fork: Cannot allocate memory means that your server is swapping (It runs out of free memory). I am not sure why you were looking at df output but this is not a disk space related issue, unless you are looking for a swap partition related solution but I guess that is not the case here.

You mentioned "my server shows error after few day's", which seems to be a symptom of memory leak occurring somewhere.

If I were you I would start by finding out what is using up all the memory. You can run the following command to sort processes by memory usage:

• Your query_cache_size is 52428800 = 50M
• innodb_buffer_pool_size = 512M
• key_buffer_size = 88080384 = 84M

That's already ~650M, which leaves MySQL about 50M for 'other stuff'.

If you tweak down some of these settings, chances are that you can stay below 700M. Unless your version of MySQL really has a memory leak.

Try reducing some of these numbers by another 50M in total.

Bonus:

Just found this calculator: http://www.mysqlcalculator.com/. Might help you figure this out more accurately. Can't speak to how accurate this tool is though