Forum

I upgraded and added the repository according to the FAQ

Quote:[All Platforms] The APT repository at xbian.brantje.com seems to be unreachable

To fix the problem, you need to manually replace the APT repository. [...]

Code:

sudo sed -i 's/xbian.brantje.com/apt.xbian.org/g' /etc/apt/sources.list.d/xbian.list sudo sed -i 's/xbian.brantje.com/apt.xbian.org/g' /etc/apt/sources.list apt-get update -f

But during apt-get upgrade, I had a electricity cut in the house... Bad luck :-(
Now I can not access the rPi via SSH (verbose output):

Code:

ssh -vvvv xbian@192.168.0.29

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011

debug1: Reading configuration data /etc/ssh_config

debug1: /etc/ssh_config line 20: Applying options for *

debug1: /etc/ssh_config line 102: Applying options for *

debug2: ssh_connect: needpriv 0

debug1: Connecting to 192.168.0.29 [192.168.0.29] port 22.

debug1: connect to address 192.168.0.29 port 22: Connection refused

ssh: connect to host 192.168.0.29 port 22: Connection refused

And the xbian is stuck at "starting xbmc..." in endless loop. Other running services run fine when accessing via web browser (Transmission, Couchpotato).

I have a backup file somewhere and don't want to start over. What should I do to repair the SSH access?

@dafhus

sshd isn't started until XBMC is fully loaded. until then you should be able to telnet (telnet parameter in cmdline.txt) to RPI as user xbian.

so your problem would be just XBMC. if XBMC was updating at the time of power outage, it could be many things. xbmc binary or libraries messed, ... maybe some xbmc conf files not proper anymore.

try apt-get install --reinstall xbian-package-xbmc (assuming you get into RPI with telnet)

Thank you for your help.

I edited the xbianboot /cmdline.txt file with parameter ip=192.168.0.29 and tried to telnet to the rPi with telnet xbian@192.168.0.29, but it prints nodename nor servname provided, or not known.
I doublechecked the IP address...

@dafhus,

nono, you misunderstood. telnet parameter is present by default. then also if your xbmc is starting to start, xbian recognised and configured network.

so your RPI should be accessible via IP you are used to.

I was just saying, that because of looping xbmc (there is timeout of 100s for xbmc start) sshd is not started yet. but telnet is since root fs remount (or mount rw).

btw: ip= as kernel parameter is either ip=dhcp (then 1st visible network device is taken with dynamic ip config), otherwise format is that:

<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

ip=192.168.0.29:::255.255.255.0::eth0:
(in your case, but again, not needed)

Ok I see, but telnet 192.168.0.29 nor telnet xbian@192.168.0.29 still does not work, although pinging it is possible.
Sorry, what is the step I should try? I could not get it from your last reply.

@dafhus

can you with nmap scan the rpi and post output?

Code:

nmap 192.168.0.29

Code:

dafhus$ 

nmap 192.168.0.29

Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-17 12:42 CET

Nmap scan report for 192.168.0.29

Host is up (0.043s latency).

Not shown: 997 closed ports

PORT     STATE SERVICE

111/tcp  open  rpcbind

9091/tcp open  xmltec-xmlmail

9999/tcp open  abyss

Nmap done: 1 IP address (1 host up) scanned in 0.71 seconds

// output edited

So I better reinstall everything?

dafhus

mk01

dafhus

mk01

dafhus

mk01

dafhus

dafhus

dafhus