Hi Nick, Yes I had a warning that I was out of disk space (I checked and found it wasn't normal disk space) but when I ran.................... $ sudo df -i I could see inodes 100% full. So I ran....................... $ find / -xdev -printf '%h\n' | sort | uniq -c | sort -k 1 -n And found these are the main culprits ............ 1155 /usr/src/linux-headers-4.4.0-62/include/linux 1155 /usr/src/linux-headers-4.4.0-65/include/linux 1155 /usr/src/linux-headers-4.4.0-66/include/linux 1155 /usr/src/linux-headers-4.4.0-70/include/linux 1155 /usr/src/linux-headers-4.4.0-71/include/linux 1155 /usr/src/linux-headers-4.4.0-72/include/linux 1155 /usr/src/linux-headers-4.4.0-75/include/linux 1155 /usr/src/linux-headers-4.4.0-78/include/linux 1155 /usr/src/linux-headers-4.4.0-79/include/linux 1155 /usr/src/linux-headers-4.4.0-81/include/linux 1155 /usr/src/linux-headers-4.4.0-83/include/linux 1155 /usr/src/linux-headers-4.4.0-87/include/linux 1155 /usr/src/linux-headers-4.4.0-89/include/linux 1155 /usr/src/linux-headers-4.4.0-91/include/linux 1155 /usr/src/linux-headers-4.4.0-92/include/linux 1514 /usr/src/linux-headers-4.4.0-62-generic/include/config 1516 /usr/src/linux-headers-4.4.0-65-generic/include/config 1516 /usr/src/linux-headers-4.4.0-66-generic/include/config 1516 /usr/src/linux-headers-4.4.0-70-generic/include/config 1516 /usr/src/linux-headers-4.4.0-71-generic/include/config 1516 /usr/src/linux-headers-4.4.0-72-generic/include/config 1516 /usr/src/linux-headers-4.4.0-75-generic/include/config 1517 /usr/src/linux-headers-4.4.0-78-generic/include/config 1517 /usr/src/linux-headers-4.4.0-79-generic/include/config 1517 /usr/src/linux-headers-4.4.0-81-generic/include/config 1517 /usr/src/linux-headers-4.4.0-83-generic/include/config 1517 /usr/src/linux-headers-4.4.0-87-generic/include/config 1517 /usr/src/linux-headers-4.4.0-89-generic/include/config 1517 /usr/src/linux-headers-4.4.0-91-generic/include/config 1517 /usr/src/linux-headers-4.4.0-92-generic/include/config 1517 /usr/src/linux-headers-4.4.0-93-generic/include/config Is it okay to delete these?? I not sure what old shm segments are and where they would be and how to get rid of them. Where do I get ipcs form? Thanks.....................Murray -----Original Message----- From: Nick Kew [mailto:niq@xxxxxxxxxx] Sent: Monday, 4 September 2017 11:37 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: Apache Restart Failure On Sun, 2017-09-03 at 22:44 +0000, Murray Hills wrote: > Thanks so much Eric for your suggestion which seems to have fixed the problem. > > The reason I deleted the /var/log/apache2/ was because my Inodes were full and somebody suggested I do it. I see now it was a bad idea. Your inodes were full??? If by that you mean you previously had an error about a full filesystem, it could be that you have old shm segments lying around. Your apache server could leave them if it crashed or is killed (as opposed to an orderly shutdown or restart), or due to a third-party module. Check that using ipcs. -- Nick Kew --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|