 |
mnichols
New User
Mar 31, 2004, 12:06 PM
Post #1 of 2
(3366 views)
Shortcut
|
|
Search Engine Failing
|
Can't Post
|
|
We have Article Manager running on a production server and a test server. When we attempt to search on the test server, we get...
Can't connect : No route to host at /web/apache/cgi-local/am-main/exec/search.cgi line 1776.
We get the same error messages when testing smtp services. Configured as localhost, and we get no route to host...
On the production server, it works fine. I have used perldigger to confirm the environment settings and that the hostname shown in the environment are resolvable by the server.
More info... it seems that the scripts are not resolving the local host name or the name configured on the server, although they are entered correctly in the /etc/hosts file and a normal user can ping them.
Please Help!
(This post was edited by mnichols on Mar 31, 2004, 12:09 PM)
|
|
| |
|
Eric
Product Specialist
Mar 31, 2004, 2:48 PM
Post #2 of 2
(3360 views)
Shortcut
|
|
Re: [mnichols] Search Engine Failing
[In reply to]
|
Can't Post
|
|
HI mnichols,
Article Manager has a feature that allows it to interpret SSI's and code (PHP, ASP, etc) in it's dynamically generated pages. Normally it isn't possible to have a page that is generated by one programming language (such as Perl like we use) to include programming from other languages (SSIs, PHP, ASP, etc). But with Article Manager we're able to this by having the script save a copy of the page that is returned on the website, and then have the script request it from the website so the webserver can interpret all the markup (the HTML, SSI code, PHP, etc).
To summarize, it seems your test server can't accept web requests from itself or localhost.
Here are some options for you:
1) We could search and replace on the template set and send you a copy that uses the old template include tags. The only thing that won't work is SSI and scripting code in dynamic pages (search results, advanced search form, etC), everything related to Article Manager should still work fine. This was how we included files previously into Article Manager's published pages.
2) You could contact your networking team and ask them if they know of any reason why we wouldn't be able to connect from the server to the server. And see if they could resolve the problem. (For example, there may be a firewall that is blocking connections to the server FROM the server.)
I hope this helps. If you have other questions please let me know.
Cheers,
Eric Lau - Product Specialist
support@interactivetools.com
|
|
| |
| | |
|
