SSH key changes?

[stereo157]

Howdy folks!

I have a bit of an odd problem that I've not seen before. I built a 2nd PiaF box to play with while my mule does the heavy lifting.

I built PiaF Purple using the 1.7.5.5.5 cd Tuesday. All went well and seems to have installed correctly. I then added Incredible to it and went to bed. When I checked on the box in the morning, I discovered that Putty was complaining that the SSH RSA key had changed. I chalked it up to something in the Incredible install redoing the key, accepted it and went on even though I don't remember that happening with other installs. I began configuring the system. Every few hours, Putty would complain that the SSH key had changed. That evening, I noticed that I had some hardware problems (old junk box). I shut it down and swapped for slightly newer known good hardware.

I rebuilt on the new hardware last night. All seemed fine, installed Incredible and noticed once the install was finished Putty complained the SSH key had changed. Again, every few hours, Putty is complaining the key has changed.

Hardware is an HP D530 - 2.8GHz P4 with 1 gig of ram.
Sangoma A200 2 port FXS
This hardware has run PiaF before without incident.

Here is the output from statustofile:

Date and Time = 201105192356
PIAF color = PURPLE
Asterisk Status = ONLINE
Dahdi Status = ONLINE
Zaptel Status = OFFLINE
MySql Status = ONLINE
SSH Status = ONLINE
Apache Status = ONLINE
Iptables Status = ONLINE
Ip6tables Status = ONLINE
Fail2ban Status = ONLINE
IP Connect Status = ONLINE
Bluetooth Status = ONLINE
HIDD Status = ONLINE
NTPD Status = ONLINE
Sendmail Status = ONLINE
Samba Status = OFFLINE
Webmin Status = ONLINE
Ethernet 0 Status = ONLINE
Ethernet 1 Status = N/A
Wlan Status = N/A
PIAF Version = 1.7.5.5
Freepbx Version = 2.8.1.4
Running Asterisk = Asterisk 1.8.4
Asterisk Source Version = 1.8.4
Dahdi Source = 2.4.1.2+2.4.1
Zaptel Source = UNAVAILABLE
Libpri Source = 1.4.11.5
Addons Source = UNAVAILABLE
pbx.local on 10.10.10.133 - eth0
CentOS release 5.6 (Final) :32 Bit Kernel: 2.6.18-194.17.4.el5
********************************************************************
Ifconfig output
eth0 Link encap:Ethernet HWaddr 00:07:E9:0F:BF:66
inet addr:10.10.10.133 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe0f:bf66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:300788 errors:0 dropped:0 overruns:0 frame:0
TX packets:225522 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:343719767 (327.7 MiB) TX bytes:63911099 (60.9 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:90866 errors:0 dropped:0 overruns:0 frame:0
TX packets:90866 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15128293 (14.4 MiB) TX bytes:15128293 (14.4 MiB)

w1g1 Link encapoint-to-Point Protocol
UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1
RX packets:45215226 errors:0 dropped:0 overruns:0 frame:0
TX packets:45215226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:361721808 (344.9 MiB) TX bytes:361721808 (344.9 MiB)
Interrupt:217 Memory:f8d60000-f8d61fff

********************************************************************
Network Configuration output ifconfig-eth0
# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:07:E9:0F:BF:66
ONBOOT=yes
DHCP_HOSTNAME=pbx.local
********************************************************************
uname -a output
Linux pbx.local 2.6.18-194.17.4.el5 #1 SMP Mon Oct 25 15:51:07 EDT 2010 i686 i686 i386 GNU/Linux
********************************************************************

Please let me know if something looks out of place or if you need more info. I can't thank you guys enough for the help provided. This forum is the best source of info out there!

Thanks,
Chris

 

[johnny2000]

Anyone who has a solution on this? I am having the same problem too.

 

[jroper]

Hi

I had this issue a few days ago, and I hate to admit the reason as I was being a numpty - turned out I had two identical servers on the same IP address - and sometimes I was connecting to one, and the other times I was connecting to the other.

Any chance of this being the case here?

Joe