After restart of apache server, php script no longer works - php

after (just) restarting my apache server, which runs a php script,
the website no more works.
I can see the landing page, and that's it.
(cannot click buttons, no reaction, no backend entrance..)
I have checked log files of server:
Everything is ok & working.
I have checked log files of apache, and got these errors:
HTTPD
The timeout specified has expired:
[client 2.247.241.109:11131] AH01075: Error dispatching request to : (polling), referer: (ip of my server)
Do you know what is going on?
I guessed that apache won't execute php (script) any more, is that correct?
Or is it something different?
Big thanks to anyone who can help me out.

Try the following:
service httpd restart
systemctl restart httpd
Make sure no rerwite rules are added in the .htaccess file.

Related

The timeout specified has expired for a Wordpress cron

I am trying to run a script every three hours on my Wordpress installation using cron. The script consists of a foreach which is quite slow to execute. In local the cron job works well but in production on my Vultr server, I get the following error:
[proxy_fcgi:error] [pid 32369:tid 139804532532992] (70007)The timeout specified has expired: [client 45.11.111.111:47111] AH01075: Error dispatching request to : (polling)
I am a web developer but I have little to no experience in administrating a server. I read some answers about this problem and modified the timeout in /etc/apache2-rc/conf.d/mysite.conf :
<Proxy ${SOCK}>
ProxySet keepalive=On
ProxySet timeout=999990000000000
ProxySet retry=0
</Proxy>
This still doesn't work. Any idea how I could solve this problem? Thanks.
Update
The solution was to restart Apache. Thanks Noman.
The "ProxySet timeout" attribute should do the trick.
Please attempt to restart web server and check again.
You can restart by:
service apache2 restart

Ubuntu 14.04.3 LTS Server PHPMyAdmin client denied by server configuration: /usr/share/phpmyadmin

First of all, I searched now nearly an hour through the Questions and didn't find any matching ones. So, if I have overseen something, be patient with me.
I'm hosting a VServer on Ubuntu 14.04.3 LTS with a MySQL-Database on Apache 2.4.7. Everything runs fine with that. Now I want to install PHPMyAdmin to get easier access to the database.
Since I'm not that firm with Ubuntu Server I checked the tutorial on https://help.ubuntu.com/community/phpMyAdmin
After I ran through the installation and reconfiguring process I reloaded (and restarted) my apache2, but I still get a 403 with the message You don't have permission to access /phpmyadmin on this server. when I try to get to http://myserverip/phpmyadmin.
With the restart of my apache2 this message occured:[alias:warn] [pid 29422] AH00671: The Alias directive in /etc/phpmyadmin/apache.conf at line 3 will probably never match because it overlaps an earlier Alias.
In my apache error.log I found this entry saying not much to me: AH01797: client denied by server configuration: /usr/share/phpmyadmin
Any ideas? Thank you!
So, I'm going to answer my own question.
I added the Allow from line to my PHPMyadmim Config file. After that I granted all Privileges to my PHPMyAdmin user and tadaaaa, here wie go. Pretty simple thow there is still the warning when I restart my Apache2.. Anyone any idea?

php my admin default Timestamp is wrong even if I use correct timezone

I am experiencing problem in default timestamps I have this column name dateCreated type is TIMESTAMP and default as CURRENT_TIME whenever I insert a new row in my add member page the time generated is late for 2 hrs.
I currently live in ASIA/MANILA which is GMT +8.
I tried changing the php.ini (in my server) timezone to ASIA/MANILA.
but still the generated timestamp is late for 2hrs.
whenever I run the code echo date_default_timezone_get(); I get a result of ASIA/MANILA can somebody tell me what is the problem? and how can I FIX it? thanks in advance
You should restart httpd once. The the httpd RPM installs the /etc/rc.d/init.d/httpd Bourne script, which is accessed using the /sbin/service command.
To start your server, as root type:
/sbin/service httpd start
NOTE: If you are running the Apache HTTP Server as a secure server, you will be prompted to type your password.
To stop your server, type the command:
/sbin/service httpd stop
The command restart is a shorthand way of stopping and then starting your server. The restart command explicitly stops and then starts your server. You will be prompted for your password if you are running the Apache HTTP Server as a secure server. The restart command looks like the following:
/sbin/service httpd restart
If you just finished editing something in your httpd.conf file, you do not need to explicitly stop and start your server. Instead, you can use the reload command.
Note: If you are running the Apache HTTP Server as a secure server, you will not need to type your password when using the reload option as the password will remain cached across reloads.
The reload command looks like the following example:
/sbin/service httpd reload
By default, the httpd process will not start automatically when your machine boots. You will need to configure the httpd service to start up at boot time using an initscript utility, such as /sbin/chkconfig, /sbin/ntsysv, or the Services Configuration Tool program.
For more details about how to restart apache you can check the link Here

Setting up LAMP with CentOS 6.x

I am having errors setting up my webserver on my vps. At the moment I have followed this tutorial: https://www.howtoforge.com/apache_php_mysql_on_centos_6.5_lamp
I am stuck on the /etc/init.d/httpd start part. When I run this command, I get the following output:
[root#localhost conf]# service httpd restart
Stopping httpd: [FAILED]
Starting httpd: [Mon Feb 23 21:27:02 2015] [warn] NameVirtualHost *:80 has no VirtualHosts
[FAILED]
And there is no more output. Prior to this I was getting this error:
[root#localhost etc]# /etc/init.d/httpd start
Starting httpd: httpd: Could not reliably determine the server's fully
qualified domain name, using localhost.localdomain for ServerName [FAILED]
I googled and managed to get this error to disappear by editting /etc/httpd/conf/httpd.conf - I simply uncommented the ServerName variable and changed the value to localhost. So it looks like:
ServerName localhost - In my mind this makes sense since localhost is the external ip server anyways. [NOTE]: Even if I change it to ServerName <external-ip> I still get the same output when restarting httpd.
Can anyone help me get past this step? I've been googling for about 1-2 hours. Can't find anything. Anyone had the same error and mind pointing me in the right direction?
UPDATE 1:
cat /var/log/httpd/error_log
The output is basically normally operation until it reaches this point at which it just spams the rest of the log with it
(2)No such file or directory: httpd: could not open error log file
/srv/www/java-applet/logs/error.log - Unable to open logs
So I guess the error occurs since it cannot find the specified log file? Where can I change this? Why is this even occurring if I have a default installation of httpd?
Update 2:
Nevermind, I just solved it by making the directory that it said it was missing. Lame...

Forbidden error when trying to run update.php MediaWiki maintenance script on WAMP

I recently installed WAMP on Windows and have set up a local MediaWiki installation. After the installation, I tried to to install a new extension. For it to work, I have to run the maintenance script update.php. However, when I go to localhost/maintenance/update.php, I'm getting a 403 error.
Forbidden
You don't have permission to access /maintenance/update.php on this server.
Apache/2.4.9 (Win32) PHP/5.5.12 Server at 127.0.0.1 Port 80
How do I fix this? or is there another way to run the maintenance scripts on WAMP (perhaps with a command line)?
This is not an error, it is desired behaviour for the program, since the .htaccess file for the /maintenance/ directory has this:
Deny from all
This is because the update.php file is not meant to be loaded directly from a web browser. You must read the documentation for MediaWiki updating from a browser to utilize it correctly. You can also run it from the command line

Categories