I think I killed my pogo plug

This forum is for all other ARMv5 devices

I think I killed my pogo plug

Postby tzonis » Tue Mar 13, 2012 1:01 am

Hi everyone,

I was having issues installing Archlinux onto my pogoplug v2 on one usb external drive (it would hang during mkf2s during step 9 of the install instructions). So I figured I would try a USB flash drive just to see if I could get the install to work. The install ran just fine but after the reboot I can't SSH into the pogo plug. When it reboots it does get an IP address as it shows up in the DHCP table on my router.

Any idea?

I hope I didn't hose my Pogo Plug, but then again it seems like that is what has happened....

Thanks for the help!

-Tz
tzonis
 
Posts: 7
Joined: Tue Mar 13, 2012 12:49 am

Re: I think I killed my pogo plug

Postby WarheadsSE » Tue Mar 13, 2012 1:09 am

If it's in your router, it's not screwed.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: I think I killed my pogo plug

Postby tzonis » Tue Mar 13, 2012 1:40 am

I just don't know what to do next as I can't ssh into it.... Any idea?

Thanks,
Tz
tzonis
 
Posts: 7
Joined: Tue Mar 13, 2012 12:49 am

Re: I think I killed my pogo plug

Postby davygravy » Tue Mar 13, 2012 4:18 am

You say it gets an ip addr.

Try doing a port scan of that ip addr. Which ports are open?
davygravy
 
Posts: 27
Joined: Wed Jan 25, 2012 1:50 am

Re: I think I killed my pogo plug

Postby tzonis » Tue Mar 13, 2012 1:53 pm

It shows in my router:
alarm 192.168.1.109

But when I scan the known ports and noting came up.... Not sure what I managed to do here.

thank you very much for all of your insight.

-Tz
tzonis
 
Posts: 7
Joined: Tue Mar 13, 2012 12:49 am

Re: I think I killed my pogo plug

Postby WarheadsSE » Tue Mar 13, 2012 1:55 pm

Sounds like time to check the /etc/r.conf DAEMONS=() line.

And you port scanned this new x.109 address, yes?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: I think I killed my pogo plug

Postby tzonis » Tue Mar 13, 2012 3:13 pm

Hi WarheadsSE,

Yup I scanned the new x.109 address, even scanned another machine to make sure everything was working properly.

The rc.conf has this line:
$this->bbcode_second_pass_code('', '
DAEMONS=(set-oxnas-mac !hwclock syslog-ng network netfs crond sshd openntpd)
')
so my thought is that sshd should be starting. Does that make sense?

-Tz

here is the whole rc.conf file:
$this->bbcode_second_pass_code('', '

#
# /etc/rc.conf - Main Configuration for Arch Linux ARM
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes !hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
#
MODULES=(gmac )

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="alarm"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(set-oxnas-mac !hwclock syslog-ng network netfs crond sshd openntpd)
')
Last edited by WarheadsSE on Tue Mar 13, 2012 3:16 pm, edited 1 time in total.
Reason: adding code tags
tzonis
 
Posts: 7
Joined: Tue Mar 13, 2012 12:49 am

Re: I think I killed my pogo plug

Postby WarheadsSE » Tue Mar 13, 2012 3:15 pm

I thought you said this was a V2? Why is set-oxnas-mac here?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: I think I killed my pogo plug

Postby TheWalt » Tue Mar 13, 2012 3:44 pm

I might suggest in the router to clear the DHCP lease and force the Pogo to pull one again, just to 100% verify network address. I've had cached information mislead me in the past.
TheWalt
 
Posts: 23
Joined: Fri Feb 17, 2012 12:22 am

Re: I think I killed my pogo plug

Postby Philoo » Tue Mar 13, 2012 3:54 pm

if the plug got the same mac address then the ssh keys have changed and depending on your ssh client and settings the denial may be silent.
When I was moving back and forth between stock firmware and arch on sata I ended up removing the mac address file from the sata so that the arch would get a different ip address and I would not need to managed the keys manually all the time.

if you are on mac OS or Linux using ssh command line you can check ~/.ssh/known_hosts , make a back up remove the potentially offending line and try again.
If it does not change anything restore your know_hosts file.

there also is an openssl command that does that, you should find it using the search feature of the forum.

you can also:
$this->bbcode_second_pass_code('', 'nmap -p 22 -A 192.168.0.109')
to check what is going on it will produce something like
$this->bbcode_second_pass_quote('', 'P')ORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH <version info>
|_ ssh-hostkey: <size> xx:yy:zz:.....
Service Info: OS: Linux


the ssh server used by cloud engine is dropbear.

HTH

Oh, and as WHSE said make sure you've got the right image for the right HW, check the label under the foot
Philoo
 
Posts: 102
Joined: Wed Aug 10, 2011 9:20 pm

Next

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 3 guests