Hello!
It is a timeout problem and if you could not build it you cannot. Simply accept that or change to an expensive Internet service provider and get a dedicated server. Otherwise it will not work.
I have mentioned several times that telnet does not work on shared servers in such cases, most likely. Perhaphs on virtual servers. Since it basically only looks at the CPU usage and if it is more than the set time limit that the ISP have setup it simply kills the process of nph-build.cgi and that has nothing to do with telnet. Atleast it did not function in my case.
To beleive for yourself empty all the links you have from the database, import everytime 1000 links each time and build then everytime. And then you will find the cutoff point of your server. May be in the third of the fourth import the nph-build.cgi will not build anymore. Below the build page it shows the time taken. This is the total time taken in the processor.
It is a timeout problem and if you could not build it you cannot. Simply accept that or change to an expensive Internet service provider and get a dedicated server. Otherwise it will not work.
I have mentioned several times that telnet does not work on shared servers in such cases, most likely. Perhaphs on virtual servers. Since it basically only looks at the CPU usage and if it is more than the set time limit that the ISP have setup it simply kills the process of nph-build.cgi and that has nothing to do with telnet. Atleast it did not function in my case.
To beleive for yourself empty all the links you have from the database, import everytime 1000 links each time and build then everytime. And then you will find the cutoff point of your server. May be in the third of the fourth import the nph-build.cgi will not build anymore. Below the build page it shows the time taken. This is the total time taken in the processor.
