error message on Fedora boot - "FAILED" in red

[mraroid]

Hi...

I get a error message on boot. But the data flyers so fast across my screen, I can not read the error. I hit my Pause/Break key, but that will not stop it. How do I stop it to read the error message?

My install of Fedora (12.46) went fine. I did not do any updates after I installed Fedora. After Fedora was installed, I clicked on the desktop icon that said "Amahi Installed Icon". I typed in my code and hit the "Submit" button.

Then it looked like stuff was installing. I received no error messages. After it finished installing stuff, it said to reboot and/or click on the hyperlink that said: http://hda

I tried that, but the browser was not able to connect to anything. It was as if I did not have access to the web (my machines started off as a XP box with a ethernet cable plugged into it - that has not changed, the connection is good).

So, I decided to reboot.

When booting Fedora a lot of stuff passes by the screen quickly. I saw text that said something like welcome to Fedora (in blue), then a bunch of stuff happened. With every thing that was written, on the right, in green, it would say "OK". But one thing was in red and it said "Failed". I rebooted many times to try to read it, but it went past me too fast. I hit my pause/break key but that would not stop it.

I believe it said something like "Sanbzd". That was the thing that failed. But it had a line or two of text that I could not read. After that, the next thing that came up was something like "stating hard disk" but I can not be sure. All the rest of the stuff that comes up gets a green "OK". Then I boot to my Fedora screen.

After booting to my Fedora desktop, I launch Firefox. I get a message that says:

"Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your computer"

I don't know how Firefox could be running when I just booted the machine. But anyway, I try to reach google or any place, and I can not It says "server not found"

Can someone help me?

Thank you.

jack

[mraroid]

Here is some addition information.

It seems that while I have this fedora/amahi machine running and connected to my network, it brings my entire network down. I have to shut down my router/modem and then re start all the computers again. After we were all up and running again, I booted the Fedora/Amahi box, and again, it took the network down. So I turned it off, re started my modem/router, then turned the rest of the computers on.

Now everyting is fine until I turn the Fedora/Amahi box on. Then it will kill the network.

So I tried to install the Amahi installer again. In the wiki, it said:

*************************

Restart the amahi installer
service amahi-installer restart
To start the install process, make a connection to:

http://localhost:2000
And proceed from there!

If you already installed before, the installer will not start again. To force-start the installer you can do this:

rm -f /var/cache/hdactl.cache
service amahi-installer restart
Then connect to localhost:2000.

***************************************
As I had already installed it once, I went to terminal and typed this:

rm -f /var/cache/hdactl.cache
service amahi-installer restart
Then connect to localhost:2000.

When I tried to do this, I get ACCESS DENIED and FAILED

Gez, I thought this was turn key. Any help folks?

jack

[radioz]

Have you looked in the system logs yet?

Look in /var/log/messages for any error messages. The most recent boot cycle will be near the end of the file.
Post anything interesting, and we will try to help.

[cpg]

I believe it said something like "Sanbzd". That was the thing that failed.

this is a know minor issue that we will get to at some point. you can safely ignore it.

"Firefox is already running, but is not responding."

this was probably because firefox got shut down abruptly and it left a "lock file" laying around. this happens rarely (in fact i have not seen in in years ... though i usually shut down/reboot nicely).

[cpg]

Let me start with the punchline. Did you try the interactive network troubleshooter?

It seems that while I have this fedora/amahi machine running and connected to my network, it brings my entire network down.

Simply put, unless there is a hardware issue with your NIC in that machine, that's impossible.

can you describe in more detail what you mean by "having Amahi on makes the network go down"?

Putting a "worst case scenario" cap on ... it could be that _after a while_, if the machine is left loose on a network and the DHCP is on (which is the default, so that is not too hard), *and* assuming that the rest of the machines in the network request a new DHCP lease eventually (typically that is ever 1 to 24 hours or something), *and* assuming the Amahi HDA is not configured to see the router, *then* the machine that got the DHCP lease could not reach the external internet (though in that case, it should definitely reach http://hda).

If that is what you mean by "down" ... it's theoretically possible in a while, but not just turning it on and poof (unless there is hardware that is broken or something).

These days the installer has been really solid in detecting the network, however, if you changed your router settings or something, it's possible it did not get configured properly.

Geez, I thought this was turn key. Any help folks?

I really really really wish what went on here. If you could send us the install log (/root/hda-install.log) it would go a long way. you can simply type this and send us (or support at amahi dot org if you prefer) the url

Code: Select all

fpaste /root/hda-install.log

there has got to be something very obvious that either the installer is not doing right, or perhaps you accidentally did something that caused an issue or something.

you can try to do this in your HDA:

Code: Select all

hda-change-gw IPADDRESS

where the IPADDRESS above is the ip address of your gateway device, that may reconnect the machine to the network.

this is something we would like to debug, so feel free to come to the community channel.

[cpg]

I just thought of another possibility as to why your HDA would not connect to the internet.

Do you have an Apple device like an Airport Express or Airport Extreme?

Those are a royal pain in the ass to configure to not entirely rule your entire network with an iron fist and a sadistic whip (thank Apple).

[mraroid]

Thanks for the support. I decided to do a clean install (again). I started by testing my DVD. It said it was fine, no errors.

The install of Fedora (12.46) went perfect. It installed 1114 packages. No errors. This is my 3rd time at a full install. I am installing this on a Presario laptop that is about 7 years old. It had XP on it and it ran great.

I had the same error when I rebooted (Sanbzd) not sure of spelling. I sure would like to know how I can stop that scrolling and read that stuff. Anyone know? I also noticed that just before Sanbzd got the red FAILED message, something called Retrigger failed, but it did not get a red flag. Some text was written after the word Retrigger , but again, it moved too fast for me to read it. I sent my hardware profile if that helps.

I logged into my fedora desktop. All looked good. I let it sit for a couple of minutes to see if it needed any time to do something, then I clicked on Amahi Installer. Does fedora have a bar across the lower screen with nothing in it? I have some blue boxes on the right hand side, but that is it.

After I entered my install code, it started the down load. All seemed to go well. No error messages. Then I rebooted. Same loading errors as above. I logged in. I launched Firefox.

Server Not Found.

I went to terminal and typed in /var/log/messages and hit my enter key. It said "Permission Denied".

As I type this, my network is still up. It killed it before. Not sure how long it will take, or maybe I got lucky this time around.

Suggestions?

jack

[cpg]

yes, two suggestions: installation troubleshooter and come by the community channel.

this is very strange!

no need to reinstall so much, though!

what is the IP address of your gateway/router?
how about the IP you configured for your HDA?

[mraroid]

Let me start with the punchline. Did you try the interactive network troubleshooter?

Nope, but I will. Thanks for the tip.

It seems that while I have this fedora/amahi machine running and connected to my network, it brings my entire network down.

Simply put, unless there is a hardware issue with your NIC in that machine, that's impossible.

can you describe in more detail what you mean by "having Amahi on makes the network go down"?

Shure. I have a small wired network in my house. One Windows 7 box, one Vista box, One Mac Leopard box, one ubuntu box, and this latop. This laptop ran XP before I installed fedora/amahi on it.

All the computers could connect to the internet and have been. I can not recall any outages in my DSL servace. Everything always had worked. When I booted to my fedora/amahi desktop, a few minutes later (like 5 minutes at the most) none of the computers could reach the internet. This has never happened to me before. So I shut them all down, as well as the fedra/amahi box. I rebooted my DSL modem. When it came up, I booted up all the machines except the fedora/amahi box. All was well.

I booted the fedora/amahi box. About 5 minutes later all the compuers could not reach the internet. I did the same as above. I waited a coupe of hours. Network still up. Then I did a fresh install of fedora/amahi. When I booted to to the fedora/amahi screen, the network went down again.

I have a ATT 2Wire Gateway model number 2701HG-B. It has 4 ethernet ports in the back. Three go to computers, and one goes to a hub with 4 more ethernet ports.

Putting a "worst case scenario" cap on ... it could be that _after a while_, if the machine is left loose on a network and the DHCP is on (which is the default, so that is not too hard), *and* assuming that the rest of the machines in the network request a new DHCP lease eventually (typically that is ever 1 to 24 hours or something), *and* assuming the Amahi HDA is not configured to see the router, *then* the machine that got the DHCP lease could not reach the external internet (though in that case, it should definitely reach http://hda).

OK. I do not know how Amahi works.

If that is what you mean by "down" ... it's theoretically possible in a while, but not just turning it on and poof (unless there is hardware that is broken or something).

I do not know what to say. I am just reporting what happned to the best of my ability.

These days the installer has been really solid in detecting the network, however, if you changed your router settings or something, it's possible it did not get configured properly.

I did not change anything except blow away XP and do a fedora/amahi install.

Geez, I thought this was turn key. Any help folks?

I really really really wish what went on here. If you could send us the install log (/root/hda-install.log) it would go a long way.

OK. I just went to terminal and typed that in. It says "Permission denied".

Code: Select all

fpaste /root/hda-install.log

there has got to be something very obvious that either the installer is not doing right, or perhaps you accidentally did something that caused an issue or something.

Well, this is my 3rd attempt. The installs seem to go well except for the errors i have already reported.

you can try to do this in your HDA:

Code: Select all

hda-change-gw IPADDRESS

where the IPADDRESS above is the ip address of your gateway device, that may reconnect the machine to the network.

this is something we would like to debug, so feel free to come to the community channel.

I will try to do the IPADDRESS and report the results.
Thank you for your help.

jack

[mraroid]

I just thought of another possibility as to why your HDA would not connect to the internet.

Do you have an Apple device like an Airport Express or Airport Extreme?

Those are a royal pain in the ass to configure to not entirely rule your entire network with an iron fist and a sadistic whip (thank Apple).

No, no apple airport anything. The Mac is wired to my DLS modem
jack