Hello, I don't normally post for problems like this, however, I can't seem to correct the issue. I was installing a php extension when their was some sort of error during installation. I am not sure what happened but I was stuck in a document of somekind describing some warnings with the install. I Control-Z'ed my way out of it and was unable to get a lock on apt-get so I descided to do a reboot by using the power cycle in host tools for the VM. When I restarted my websites weren't coming up so I went to terminal and I am getting this message when I try to restart apache Code: service apache2 restart * Restarting web server apache2 [Mon Feb 17 02:01:08 2014] [warn] The Alias directive in /etc/apache2/conf.d/squirrelmail.conf.save at line 1 will probably never match because it overlaps an earlier Alias. [Mon Feb 17 02:01:08 2014] [warn] NameVirtualHost *:443 has no VirtualHosts [Mon Feb 17 02:01:08 2014] [warn] NameVirtualHost *:80 has no VirtualHosts [Mon Feb 17 02:01:08 2014] [warn] The Alias directive in /etc/apache2/conf.d/squirrelmail.conf.save at line 1 will probably never match because it overlaps an earlier Alias. [Mon Feb 17 02:01:08 2014] [warn] NameVirtualHost *:443 has no VirtualHosts [Mon Feb 17 02:01:08 2014] [warn] NameVirtualHost *:80 has no VirtualHosts (30)Read-only file system: apache2: could not open error log file /var/log/apache2/error.log. Unable to open logs Action 'start' failed. The Apache error log may have more information. I tried restarting my server again by sudo reboot in the terminal, but no dice. This is a virtual machine via a Digital Ocean droplet. Anyone have any suggestions? Thanks a bunch for any help
Okay... now its working. Sorry about that. I am not sure how or why...but I did try doing "mount -o remount /". I also opened the error log. Maybe one of those had the effect. Or maybe just restarting it did do something I just needed to type "service apache2 restart"? I am not sure. But its fixed.
Apache told you, that there was an error with your log file /var/log/apache2/error.log. Maybe the mount-point was missing.
No, the issue is something else. My system is mounting as read-only. Apparently something in the file system is corrupt. I am working on locating the issues. Whatever it is wasn't fixed by fsck. So whenever I reboot the system it goes into read-only which prevents any services from starting. The only way to get anything running is by manually remounting the filesystem "mount -o remount /" and restarting each service. This isn't recommended if someone else is having the issue as mounting a corrupt filesytem can make matters worse. I am only doing it because I need this running or I won't be getting emails, and my web sites will all be down. Hopefully, I can find the source of the problem.
