Randall J. Parr wrote:
> To work-around the problems I have been having with 
> choose_autoinstall_script() and my particular target/image naming I 
> linked my autoinstall_script to the name that was being searched for.
>
> # l /var/lib/systemimager/scripts
> total 48
> -rw-r--r--    1 root     root          468 Sep 16 13:31 cluster.txt
> -rw-r--r--    1 root     root         2860 Sep 13 13:51 hosts
> drwxr-xr-x    2 root     root         4096 Sep 10 10:44 post-install
> drwxr-xr-x    2 root     root         4096 Sep 10 10:44 pre-install
> lrwxrwxrwx    1 root     root           11 Sep 16 14:19 ws.master -> 
> wsng.master
> -rw-r--r--    1 root     root        31856 Sep 16 11:31 wsng.master
>
> # l /var/lib/systemimager/images
> tal 20
> -rw-r--r--    1 root     root          740 Mar 24 03:11 ACHTUNG
> -rw-r--r--    1 root     root          698 Mar 24 03:11 CUIDADO
> -rw-r--r--    1 root     root          613 Mar 24 03:11 
> DO_NOT_TOUCH_THESE_DIRECTORIES
> -rw-r--r--    1 root     root          613 Mar 24 03:11 README
> lrwxrwxrwx    1 root     root            4 Sep 16 15:38 ws -> wsng
> drwxr-xr-x   36 root     root         4096 Aug 26 17:03 wsng
>
> The install does find ws.master and proceeds until I get a message
>
> ======================================================================
> back and see the text that has passed off the top of the screen. You can use
> <alt>+<f2>, ....
> ...blah...
> ...blah...
> ...blah...
> ...
> ...blah...
> ...blah...
> ...blah...
> ...blah...
> ...blah...
> ...blah...
> ...blah...
> ...
> Have fun! http://systemimager.org
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Installation failed! Stopping report task.
> nc: cannot connect to remote host (192.168.1.10): Connection refused
>
>
> BusyBox v1.9.1 (2008-03-24 15:29:33 CET) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /scripts/pre-install #
> ========================================================================
>
> /var/log/systemimager/rsyncd shows:
> ------------------------------------------------------------------------
> 2008/09/16 15:34:16 [29765] connect from ws47 (192.168.1.147)
> 2008/09/16 15:34:16 [29765] rsync on 
> boot/i386/standard/boel_binaries.tar.gz from ws47 (192.168.1.147)
> 2008/09/16 15:34:16 [29765] building file list
> 2008/09/16 15:34:16 [29765] sent 6771908 bytes  received 136 bytes  
> total size 6770931
> 2008/09/16 15:34:18 [29771] connect from ws47 (192.168.1.147)
> 2008/09/16 15:34:18 [29771] rsync on scripts/ from ws47 (192.168.1.147)
> 2008/09/16 15:34:18 [29771] building file list
> 2008/09/16 15:34:18 [29771] sent 46073 bytes  received 307 bytes  total 
> size 45230
> -------------------------------------------------------------------------
>
> /tmp/si.log ends with:
> ------------------------------------------------------------------------
> parted -s -- /dev/sdb mkpart primary 0 0 || shellout
> Killing off running processes.
>
> write_variables
> Installation failed!! Stopping report task.
> ------------------------------------------------------------------------
>
> At the prompt I can
> # ping the 192.168.1.10 host
>
> I can even use
> # nc 192.168.1.10 873
>
> It is unclear to me what the install was trying to do that is getting 
> refused.
> It has already rsync'd from the server several times to get the tarball, 
> scripts, etc.
> There may be a way to scroll back up but that message is cut off.
> The logs do not show what it was trying to do that failed.
>
> Is there a way to tell the install to be more verbose?
> Maybe show the command that got refused?
>
> Any idea what connection is getting refused or what file not found?
>
> Thanks
> R.Parr, RHCE, Temporal Arts
> Portland, OR  U.S.A.

I discovered that the connection being refused was because 
systemimager-system-monitord had not been started and that port 8181 had 
not been opened in the server firewall.

The instructions state that systemimager-server-rsyncd needs to be 
started and port 873 opened but nothing about requiring 
systemimager-system-monitord and port 8181.

I would humbly suggest that some more/better error messages, or a 
verbose mode, would make it a lot easier to find these kind of problems

R.Parr

P.S. The above got me past this problem but not installed yet but that 
is for the next email :)



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to