Why website goes down? - nolandwasee1998
No, the website does not come apart because atomic number 2 was tired. There are other, more obvious reasons for that, and at present we have reasoned the 3 most likely of them. We assume that the site is "spinning" on a realistic server and if on a physical host, then everything is fine with ironware and in that respect are no hardware faults.
Over the magnetic disk space/unloose inodes
The most obvious conclude for the fall of the land site. During the operation of network services the like Apache, MySQL generate decent amounts of data – logs, temporary files, non to mention the user-uploaded data.
The avail plainly has nowhere to write far information and it "crashes". As wel, the reason for the fall of the same Apache can be an extremely large logarithm sizing.
We recommend the chase:
- In edict non to on a regular basis check disc space, set up a monitoring service to automate this serve. You can configure the same Zabbix or write a hand on bash to monitor disk space.
- Configure logrotate to rotate and compress basic service log files. As a reign, later instalmen logrotate, altogether the necessary settings will already be in the configuration files, the admin will only when have to shuffling sure that the logrotate is started automatically. Additional info can live found in man logrotate.
Break disk space
Where is the disk space?
- Temporary files, look in /tmp. As a regulation, from there you can delete all.
- Session files directory depends on the settings of the engine.
- Database to reduce the database size can represent optimized. You fire likewise endure specific engine queries. For example, for WordPress the succeeding query deletes comments with spam, which could importantly slenderize the size of the database:
DELETE FROM wp_commentmeta WHERE comment_id Non IN (SELECT comment_id FROM wp_comments)
- Mailboxes – few check mailboxes for standard mailboxes, but they can constitute spammed. They are normally stored in / var/mail. A couple of gigabytes of spam are rather real.
- Logs – view in /var/log. It is trump to configure logrotate to rotate and compress the logs, but if some logs are too big and due to their service does not starting line, you give notice cancel them.
- Backup – you may non have used the service to backup and set improving the creation of backups exploitation the system. In this case, check the backup directory and blue-pencil the oldest backups.
And now attention! Sometimes it is not the loose space that ends, but the free number of inodes (i-node). The result is the same – the system cannot create the file and the site "crashes" due to the hanging of the network servicing. Where are the inodes? Some engines, such Eastern Samoa Magento, generate besides many session files (usually stored in / var/session, but it wholly depends on the engine settings). Such files are very petite, they practically make out not necessitate up space, but they steal precious inodes. One of the tactics is to regularly clean the directory of sessions. The following script is added to cron:
cd /var/session for i in sess_*; do rm -fv $i; done
The disfavour of this method is arsenic follows:
- When you remove sessions erased all the info about the drug user, for example, its shopping cart and entropy about registration. The substance abuser comes to your computer storage, selects the products, and places them in the basket. Then run a script to clean the basket was erased, so atomic number 2 still offers to re-participate.
- One of the website's popularity was so much that session very quickly ate all the getable inodes. Had to flow them decent almost all hour, otherwise, the website was not workings properly. You know, every 60 minutes from all users, including managers, will be "tangled" from the site – it is not very good.
An mutually exclusive and more correct solution are to create another drive (or partition) with the data file system ReiserFS. She does not Shine in performance but allows in a single block to computer storage multiple files — while the block off sized is not filled. ReiserFS all solved the problem with the inodes. The server is now quietly holding millions of files inode and cleaned /var/session is quite rare – connected the server automatically cleans disconnected and is through manually by the administrator in one case a month during symmetric server maintenance.
The lack of new resources for the website
In addition to disk blank space, do non forget about the computer storage and processor resources. The htop command will help here, which shows not only gushing processes but also consumed resources.
One of the reasons for the decline of the internet site – lack of resources, especially if we are talk about atrocious engines like Magento. They are tender non exclusive to Aries the Ram but also to the number of cores.
You have Successfully Subscribed!
What's Your Reaction?
Source: https://sprintally.com/why-website-goes-down/
Posted by: nolandwasee1998.blogspot.com
0 Response to "Why website goes down? - nolandwasee1998"
Post a Comment