Linux redhat installation problem

Post by **mark** » Fri Jan 04, 2002 12:14 pm

When you change the schedule, it will print the new schedule in a gray bar at the top of the settings page. It will not print the schedule otherwise, except in the settings boxes.

The gethostbyname would seem to indicate that the machine doesn't know it's own name or it's name does not resolve to an IP address. It's not related to the install procedure. Use the system's "hostname" command to find the machine's idea of it's own name. Then use the system's "host" command to see if can be looked up. Or see if the name is listed in /etc/hosts. At the very least a machine's own name as printed by hostname should appear in /etc/hosts.

From a shell prompt run
texis -LS
to see what's scheduled and the status. If it says nothing is scheduled the problem is the registration process. Check your vortex.log file and/or the source of the resulting page when you change the schedule to find any related errors.

If it shows the schedule, the details there might be illustrative.

If a walk on the same profile is in progress it will not start a new one. An active walk of a different profile will not prevent it.

harold@dovesystems · Post by **harold@dovesystems** » Fri Jan 04, 2002 1:11 pm

Here's /etc/hosts:

[harold@kauko /etc]$ cat hosts
192.168.1.8 kauko.hallikainen.org
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
63.194.113.64 kauko.hallikainen.org
192.168.1.2 margaret.hallikainen.org
192.168.1.5 sony.hallikainen.org

Webinator is running on kauko.hallikainen.org which has a local ip of 192.168.1.8 . The router translates this to 63.194.113.64 for the outside world.

[harold@kauko /etc]$ hostname
kauko

[harold@kauko /etc]$ host kauko.hallikainen.org
kauko.hallikainen.org. has address 63.194.113.64
[harold@kauko /etc]$ host 63.194.113.64
64.113.194.63.in-addr.arpa. domain name pointer adsl-63-194-113-64.dsl.snlo01.pacbell.net.

[harold@kauko harold]$ texis -LS
Script: /home/harold/public_html/webinator/dowalk/dispatch.txt
Vars: profile=FccCsb what=sched
Schedule: weekly on fri at 1
Next run: 2002-01-11 01:00 (in 6d 14h)
Last run: never
First run: never
Status: runnable, 0 executions, first last, id 3c35e33a9
<H6 ALIGN=right><A HREF="http://www.thunderstone.com/" TARGET="_top"><IMG SRC="/copy.gif" BORDER
=0 WIDTH=304 HEIGHT=11 ALIGN=top ALT="Texis & Webinator Copyright (C) 2001 THUNDERSTONE - EP
I, Inc."></A></H6>

Looks like the one scheduled to run this morning is scheduled to run next week. There are LOTS of other walks scheduled that are not showing up here.

Here's today's vortex.log

000 Jan 4 07:30:24 /webinator/search

(7269) Terminated (signal 15); will exit ASAP
000 Jan 4 07:30:24 /webinator/search

(7269) exiting due to previous signal 15
000 Jan 4 07:41:31 /webinator/search

(7898) Terminated (signal 15); will exit ASAP
000 Jan 4 07:41:31 /webinator/search

(7898) exiting due to previous signal 15
000 Jan 4 07:41:39 /webinator/search

(7911) Terminated (signal 15); will exit ASAP
000 Jan 4 07:41:39 /webinator/search

(7911) exiting due to previous signal 15
000 Jan 4 07:47:50 /webinator/search

(8298) Terminated (signal 15); will exit ASAP
000 Jan 4 07:47:50 /webinator/search

(8298) exiting due to previous signal 15
000 Jan 4 07:52:58 /webinator/search

(8680) Terminated (signal 15); will exit ASAP
000 Jan 4 07:52:58 /webinator/search

(8680) exiting due to previous signal 15
000 Jan 4 07:54:11 /webinator/search

(8749) Terminated (signal 15); will exit ASAP
000 Jan 4 07:54:11 /webinator/search

(8749) exiting due to previous signal 15
000 Jan 4 07:56:46 /webinator/search

(8931) Terminated (signal 15)
000 Jan 4 07:59:12 /webinator/search

(9108) Terminated (signal 15); will exit ASAP
000 Jan 4 07:59:12 /webinator/search

(9108) exiting due to previous signal 15
000 Jan 4 08:01:01 /webinator/search

(9263) Terminated (signal 15); will exit ASAP
000 Jan 4 08:01:01 /webinator/search

(9263) exiting due to previous signal 15
000 Jan 4 08:02:33 /webinator/search

(9364) Terminated (signal 15); will exit ASAP
000 Jan 4 08:02:33 /webinator/search

(9364) exiting due to previous signal 15
000 Jan 4 08:09:44 /webinator/search

(9880) Terminated (signal 15); will exit ASAP
000 Jan 4 08:09:44 /webinator/search

(9880) exiting due to previous signal 15
000 Jan 4 08:10:36 /webinator/search

(9952) Terminated (signal 15); will exit ASAP
000 Jan 4 08:10:36 /webinator/search

(9952) exiting due to previous signal 15
000 Jan 4 08:11:27 /webinator/search

(10028) Terminated (signal 15); will exit ASAP
000 Jan 4 08:11:27 /webinator/search

(10028) exiting due to previous signal 15
000 Jan 4 08:15:35 /webinator/search

(10314) Terminated (signal 15); will exit ASAP
000 Jan 4 08:15:35 /webinator/search

(10314) exiting due to previous signal 15
000 Jan 4 08:20:19 /webinator/search

(10682) Terminated (signal 15); will exit ASAP
000 Jan 4 08:20:19 /webinator/search

(10682) exiting due to previous signal 15
000 Jan 4 08:32:49 /webinator/search

(11532) Terminated (signal 15); will exit ASAP
000 Jan 4 08:32:49 /webinator/search

(11532) exiting due to previous signal 15
000 Jan 4 08:36:28 /webinator/search

(11795) Terminated (signal 15); will exit ASAP
000 Jan 4 08:36:28 /webinator/search

(11795) exiting due to previous signal 15
002 Jan 4 10:15:13 /x: Can't open source file /home/harold/public_html/x: No such file or directory
002 Jan 4 10:16:02 /x: Can't open source file /home/harold/public_html/x: No such file or directory

By the way (perhaps from an earlier installation of an earlier version), I also have vortex.log in

locate vortex.log
/home/harold/webinator/texis/vortex.log
/usr/local/morph3/texis/vortex.log

A quick look through the source of dowalk after changing the schedule does not reveal any error messages (but there's a lot of stuff there, so I could have missed it).

Thanks for all your efforts on this. I am obviously able to start walks manually, so this is not a fatal problem. It would be nice to find out what went wrong, though.

Thanks!

Harold

Post by **mark** » Fri Jan 04, 2002 2:53 pm

As evidenced by hostname your machine thinks it is called kauko, not kauko.hallikainen.org . Set the hostname to kauko.hallikainen.org or add kauko to your /etc/hosts on the same line as kauko.hallikainen.org . See if that eliminates the gethostbyname errors.

It would appear that scheduling from the admin interface is only respecting the last thing scheduled. We'll have to look into that get back to you with a script fix.

BTW, you are supposed to look at the source of the page dowalk generates when you update your settings, not the source of dowalk itself. Errors should fairly easy to spot because they will look like they do in vortex.log but be inside HTML comments. eg:

harold@dovesystems · Post by **harold@dovesystems** » Mon Jan 07, 2002 11:01 am

Thanks! I'll watch for the script fix on scheduling. Meanwhile I'll start walks by hand.

Harold