Note that there are some explanatory texts on larger screens.

plurals
  1. POWebsite Down After Performing PHP Action
    primarykey
    data
    text
    <p>Say I have a website hosted on a remote server. I navigate to a page on this website and attempt to perform a specific action (the details of which I can go into more depth if necessary, but for the time being let me just say that the action involves running a program on the server with data obtained from a database.)</p> <p>The page just continually loads. So, I attempt to navigate to the main website. That now continually loads without resolve as well. After about a day the website comes back, so perhaps there is some automated process that kills tasks after a certain time has passed. My question is this:</p> <p>Am I able to kill this task or perform any action to allow me to navigate to the website without waiting a full day? I can go into more detail if necessary.</p> <p>Thanks.</p> <p>By request, some more in-depth information.</p> <p>The PHP script retrieves text-based information from the database. Based on this information the PHP script calls an executable program. The output from the executable is output to the screen.</p> <p>I've checked mysql processlist and found a process that took a particularly long time. I killed it, so it may be that the executable is continually running. If so, how would I go about determining this, and if not is there anything else it could potentially be? Thanks. </p> <p><strong>Solved</strong>: Alright, so basically Mike Purcell's advice which was to show the process list of mysql processes and kill any ones that I saw that took a substantially long time. Once that was done, it was just a matter of restarting mysql and httpd. Thanks again to everyone who commented.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload