Hello, I have big problem from seven days All my websites down and this massage appeared Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. I send to cpanel support and he said Hello, I went to the URL provided, and see an error related to nginx. Please note that we are unable to provide support for mod_rpaf or nginx, as they are 3rd party products. Once nginx is disabled, if you are still experiencing issues with your sites, please let me know so I can look into this further. when i open the logs grep "Oct 01" /etc/httpd/logs/error_log |grep -v "File does not exist" |tail -50 This errors appeared [Sat Oct 01 18:24:01 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:01 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:02 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:03 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:03 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:03 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:03 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:03 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:04 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! [Sat Oct 01 18:24:04 2011] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring! I Tried to restart nginx but this error appeared [alert]: could not open error log file: open() "/var /log/nginx/error.log" failed (30: Read-only file system) the configuration file /etc/nginx/nginx.conf syntax is ok 2011/10/02 09:26:31 [emerg] 20667#0: open() "/var/run/nginx.pid" failed (30: Read-only file system) configuration file /etc/nginx/nginx.conf test failed Can any one help me in my problem ? iam waiting you thanks alot
Hello there, Your error is as you already stated, "30: Read-only file system". This means your disks are in read only mode, which happens because the kernel saw something it did not like. Ask your DC to reboot the server and check the hard disks (fsck). Your services are not able to write to the disk, thus flagging up errors. Chris
Oct 3 04:08:21 server kernel: EXT3-fs error (device sda3): ext3_readdir: directory #20898340 contains a hole at offset 4096 Hi, I told it to DC but they said ' you make fsck by myself " Can you tell me how can i make fsck , please ? Iam waiting you thanks alot
Yea, i didnt want to tell you to use fsck until i seen the error, thats why i asked for the log info, to determine the exact error. This can be rather nasty, im hoping that you have backed anything that you can right now up to a safe location. I would force a fsck on reboot, after you backup what you can from the server. Seeing as the host is uncooperative in assisting you, i would move after this issue is resolved. Do NOT do the following until you at least attempt to back everything up on the server related to your websites. cd / touch /forcefsck reboot OR The -F option force fsck on reboot, login as root and type the following command to reboot and run fsck: # shutdown -rF now Code (markup):