Still a believer - still frustrated

frustrated
Posts: 1
Joined: Sun Aug 29, 2010 8:04 pm

Still a believer - still frustrated

Postby frustrated » Sun Aug 29, 2010 8:21 pm

About a year ago I stumbled across Amahi and loved the concept. After installing a couple of different servers I pretty much came to the conclusion that it was workable but not ready for prime time. I don't mean that to be negative - rather it seemed that things weren't advanced enough to put live systems on an Amahi configuration.

A couple of weeks ago I tried again. Things went pretty smooth but it took a couple of attempts to get things working beside another Linux server and Windows Home Server. It looked like success was close. Then Friday will moving the server into a production location on UPS things went bad. While the server was booting the power cord came out. Upon rebooting:

the network interface starts I see...

Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Cannot find device "up"
Failed to bring up .

On the forum I found a person that had the exact same problem but there was no resolution. While trying to log into the forum I found that I couldn't get in. After a couple of days of troubleshooting and working with people to get on the forum I've basically given up.

Why? The premise of Amahi is an easy to use system with the typical support forum. I think Amahi has gotten to the point of easily installing, but I don't want to play admin regularly to debug problems, particularly something like this problem and without having a forum to back me up.

So how did I finally get on the forum? I set up a new account that clearly reflects my state of mind right now. :|

User avatar
gboudreau
Posts: 606
Joined: Sat Jan 23, 2010 1:15 pm
Location: Montréal, Canada
Contact:

Re: Still a believer - still frustrated

Postby gboudreau » Mon Aug 30, 2010 3:42 am

FYI, the above problem is caused by missing lines in /etc/sysconfig/network-scripts/ifcfg-eth0

Adding "DEVICE=eth0" at the top of the file should fix it.

Some details in the bug entry I created about this: http://bugs.amahi.org/issues/show/612
- Guillaume Boudreau

Who is online

Users browsing this forum: No registered users and 43 guests