Hi Andreas,
after checking Holger's advice you may test this too:
a) Check the system/auth log files of the fai-server regarding any
ssh-authentication issues(e. g. authorizedkeys file world writable....)
b) Check to ssh from the installed client (When the client machine waiting
is waiting for <Return> to reboot) to the faiserver using the fai LOGUSER
c) check the local fai-logs at the waiting client (/var/log/fai I think)
---
After that you may add debug statements to the save-log-script
in $NFSROOT/usr/lib/fai/fai-savelog
There in function save_log_remote_shell ( ~ line 60 ) you can add some
temporary changes for debugging(backup the file and revert it later)
1) add line "set -x" before this line $remotecp -pr $LOGDIR/*
$LOGUSER@$LOGSERVER:$thislog
and "set +x" after it
2) change the line "$remotecp -pr $LOGDIR/* $LOGUSER@$LOGSERVER:$thislog"
Add -v or even -vv after $remotecp
Restart the installation.
Regards,
Tobias
Am 20.08.2015 um 18:03 schrieb Andreas Sindermann:
Dear all,
probably it's my stupidity but with a new FAI installation server I
have some scp problem of this type at the very end of the installation
process:
[...]
ERRORS found in log files. See /tmp/fai/error.log
savelog.LAST.source OK
Calling task_savelog
Save log file via ssh to x...@xxx.xxx.xxx.xxx:yyy//install-20150820_140000
lost connection
Calling task_faiend
Press <RETURN> to reboot.
[...]
So copying of the logfiles to the FAI server fails.
Any ideas?
$LOGUSER/.ssh/authorized_keys does exist.
An interactive ssh session to my personal account on the
FAI server does work properly.
But copying via scp to the $LOGUSER account fails:
root@faiclient:/# ll abc
-rw-r--r-- 1 root root 5 Aug 20 15:58 abc
root@faiclient:/# scp abc fai@trusty64srv:
lost connection
root@faiclient:/#
Thanks for any feedback.
Best
Andreas
