Not so fast....Tried to install a new app, and could not load it until I did a "service named restart". Surely that should not be necessary? named log-file:- received control channel command 'freeze home.com' freezing zone 'home.com/IN' internal: success received control channel command 'f...

By following some hints in the data I collected, I found the named log-file at /var/named/data/named.run. In there I found some error messages:- zone 0.168.192.in-addr.arpa/IN/internal: journal rollforward failed: journal out of sync with zone zone 0.168.192.in-addr.arpa/IN/internal: not loaded due ...

Cool tool! (I had another power blip yesterday so today I'm running on a UPS!) Using the Network Troubleshooter, I failed step 4 - DNS resolving for internal hostnames. Here's a paste to help troubleshoot: http://pastebin.com/r0zKNN6T the problem is that the nslookups are not returning any of the lo...

If you could tell me what information you need, I'll certainly provide it.

HDA rebooted after a power outage now none of the installed apps will launch! Not a single one!
Is anyone able to help with this issue that affects several of us here?

Just tried to install Amahi Invaders but can't launch it, even when I try from the HDA itself.

^^ bump! ^^

Yes, HDA is providing both DHCP and DNS and I'm on the HDA when I'm trying to connect to these web-apps.
I also tried from a Win-XP box, same issue. I tried http://ampache as well as http://ampache.home.com.

I restarted httpd without any change. here is the error_log output:- [Tue Jun 14 15:30:34 2011] [notice] caught SIGTERM, shutting down [Tue Jun 14 15:30:34 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jun 14 15:30:35 2011] [notice] Digest: generating secret for digest aut...

I have the same issue on F14. Here is the tail-end on my amahi-app-installer.log file. Neither app works when I try the links from the HDA's Installed Apps tab - http://ampache and http://extplorer. Other apps I have installed do work eventually but I cant figure out what finally did it for them - m...

Yes, I can confirm that behaviour - at least for the DHCP service.

I did find a work-around until this gets fixed.
If you enable, then disable the check-boxes (Watchdog and start at boot-up), then kill the service, it stays stopped. If you reboot, you have to do this over again.