Home.com not resolving

[Aldanga]

I upgraded to Fedora 14 and Amahi 6 a few weeks ago mostly without issues. I did have a problem with losing my Internet connection halfway through the process and screwing up my network connections, but I eventually got that figured out.

However, about a week and a half ago home.com stopped resolving. No apps can be accessed by their short addresses, and must instead be accessed directly by port.

My DNS server is running, all of my PCs (which are running Windows 7 x86 and x64) report my HDA as DNS and DHCP server, home.com is the connection-specific DNS suffix; everything seems to be how it should. I even checked my resolv.conf file and it's correct. I've rebooted the HDA and restarted the DNS and DHCP server to no avail. I've uninstalled and reinstalled applications and that has not changed anything.

Home.com resolves when accessed from the HDA itself, as do all apps, but this is not so on clients. Manually setting my hosts file to have home.com resolve to my HDA works, but it does not automatically resolve without such modification. http://hda still redirects to my HDA from all computers, so no problems there.

I'm at a loss as to what has gone wrong. I'd appreciate some help in this matter.

[bigfoot65]

Not sure what is going on here. Try the network troubleshooter at http://net.pommepause.com/network_troubleshooter/.

Also might consider shutting down your network and restarting it. I have seen things get confused and by powering down, then back up all works out. Just a thought.

[Aldanga]

I had tried the network troubleshooter. Everything checked out.

I just checked again, and everything but phpSysInfo is working without hosts file modifications. I haven't rebooted anything since my initial post—router uptime is 16 days, HDA uptime is 4 days—so I don't know what changed.

Come to think of it, this started happening when I initially installed phpSysInfo. Still, I don't know how it could affect things, unless a file got corrupted somewhere.

*edit*
I just installed Jinzora and that does not work either.

[bigfoot65]

There is something going on with your network obviously. Do you have a firewall on the clients that might prevent access? Also, did you do an manual modification to the HDA?

[Aldanga]

No firewalls. What do you mean by manual modifications? I cannot recall making any specific modifications.

phpSysInfo is now working after installing Jinzora.

[bigfoot65]

Interesting. What I meant about manual modifications is that some users make changes to config files and such on the HDA. They then break things and cannot figure out what went wrong.

Maybe check your router IP on amahi.org and make sure it matches your router. I have seen users mistakenly make the router there 192.168.1.1 and their router is actually 192.168.0.1.

Also, might check the log files in /var/log for any clue as to what is going on. There is an apps log there too. It might show there were some errors on install.

[Aldanga]

The only config files I've changed are those for applications I installed myself. I've changed no system config files. My router address is correct on amahi.org.

These are the log files where I found significant entries. These first two were seemingly unrelated to my current issue, but I fixed them per this topic from last May.

monit

Code: Select all

[CDT Mar 20 21:09:52] error : monit: Error reading pid from file '/var/run/mt-daapd.pid' [CDT Mar 20 21:10:21] error : 'mt-daapd' failed to start [CDT Mar 20 21:10:51] error : 'mt-daapd' process is not running [CDT Mar 20 21:10:51] info : 'mt-daapd' trying to restart [CDT Mar 20 21:10:51] info : 'mt-daapd' start: /etc/init.d/mt-daapd [CDT Mar 20 21:10:52] error : monit: Error reading pid from file '/var/run/mt-daapd.pid' [CDT Mar 20 21:11:21] error : 'mt-daapd' failed to start [CDT Mar 20 21:11:51] error : 'mt-daapd' process is not running [CDT Mar 20 21:11:51] info : 'mt-daapd' trying to restart [CDT Mar 20 21:11:51] info : 'mt-daapd' start: /etc/init.d/mt-daapd [CDT Mar 20 21:11:52] error : monit: Error reading pid from file '/var/run/mt-daapd.pid' [CDT Mar 20 21:11:53] info : 'mt-daapd' started [CDT Mar 20 21:12:23] info : 'mt-daapd' process is running with pid 28766

mt-daapd.log

Code: Select all

2011-03-20 21:10:51: Starting rendezvous daemon 2011-03-20 21:10:51: Client running 2011-03-20 21:10:51: Current database version: 8 2011-03-20 21:10:51: Starting signal handler 2011-03-20 21:10:52: Loading playlists 2011-03-20 21:10:52: Initializing database 2011-03-20 21:10:52: Starting mp3 scan 2011-03-20 21:10:52: Starting web server from /usr/share/mt-daapd/admin-root on port 3689 2011-03-20 21:10:52: Could not open port: Address already in use 2011-03-20 21:10:52: Error staring web server: Address already in use 2011-03-20 21:10:52: Aborting 2011-03-20 21:11:51: Starting rendezvous daemon 2011-03-20 21:11:51: Client running 2011-03-20 21:11:51: Current database version: 8 2011-03-20 21:11:51: Starting signal handler 2011-03-20 21:11:52: Loading playlists 2011-03-20 21:11:52: Initializing database 2011-03-20 21:11:52: Starting mp3 scan 2011-03-20 21:11:53: Starting web server from /usr/share/mt-daapd/admin-root on port 3689 2011-03-20 21:11:53: Registering rendezvous names 2011-03-20 21:11:53: Scanned 3285 songs in 2 seconds

These I found to be interesting log entries, but I can't say I totally understand their significance. From what I gather, the first is related to the fact that there are no PCs in Workgroup.

messages

Code: Select all

Mar 20 21:06:46 localhost nmbd[2085]: [2011/03/20 21:06:46.293071, 0] nmbd/nmbd_browsesync.c:350(find_domain_master_name_query_fail) Mar 20 21:06:46 localhost nmbd[2085]: find_domain_master_name_query_fail: Mar 20 21:06:46 localhost nmbd[2085]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP. Mar 20 21:06:46 localhost nmbd[2085]: Unable to sync browse lists in this workgroup.

Code: Select all

Mar 20 21:12:21 localhost kernel: [329205.471290] possible SYN flooding on port 41042. Sending cookies.

This is just some interesting entries I found in the logs. I don't know if they're related.

amahi-app-installer.log

Code: Select all

======= app install begin @ Mon Jan 10 00:00:05 -0600 2011 ========== Installing app id utilwkscf6 under /var/hda/platform/html ENV=production NOTICE: redirected 'http://downloads.sourceforge.net/project/ajaxplorer/ajaxplorer/3.2%20-%20Stable/ajaxplorer-core-3.2.zip' --> 'http://voxel.dl.sourceforge.net/project/ajaxplorer/ajaxplorer/3.2%20-%20Stable/ajaxplorer-core-3.2.zip' ... NOTE: file /tmp/amahi-download-cache/4bb31216fb7404b35a96deffc8f4260d12288593 written in cache WARNING: this application unpacks into more than one file/dir. PLEASE contact the authors and well them to unpack into one dir only as most other apps so! NOTE: check the unpack/ directory for all the files Your HDA services have been restarted. Your HDA services have been restarted. /usr/lib/ruby/1.8/net/http.rb:560:in `initialize': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/timeout.rb:53:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:93:in `timeout' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/net/http.rb:440:in `start' from /usr/bin/amahi-download:50:in `download' from /usr/bin/amahi-download:91:in `download_and_check_sha1' from /usr/bin/amahi-download:111:in `main' from /usr/bin/amahi-download:116 tar: ajaxplorer-3.1.1-patch.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors App: AjaXplorer installed ======= app install end @ Mon Jan 10 00:02:06 -0600 2011 ========== ======= app install begin @ Fri Jan 14 21:28:33 -0600 2011 ========== Installing app id 64woea2dr6 under /var/hda/platform/html ENV=production App: uShare installed ======= app install end @ Fri Jan 14 21:30:05 -0600 2011 ========== ======= app uninstall begin @ Fri Jan 14 21:30:06 -0600 2011 ========== Uninstalling app id ogiaus92x5 under /var/hda/platform/html ENV=production App: DLNA uninstalled ======= app uninstall end @ Fri Jan 14 21:30:16 -0600 2011 ========== /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/validations.rb:1090:in `save_without_dirty!': Validation failed: Identifier has already been taken (ActiveRecord::RecordInvalid) from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/dirty.rb:87:in `save_without_transactions!' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:200:in `save!' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:182:in `transaction' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:200:in `save!' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:208:in `rollback_active_record_state!' from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:200:in `save!' from /var/hda/platform/html/script/../app/models/app.rb:255:in `install_bg' from /var/hda/platform/html/script/install-app:90:in `install_or_uninstall' from /var/hda/platform/html/script/install-app:111:in `main' from /var/hda/platform/html/script/install-app:123 ======= app install begin @ Fri Jan 14 21:30:07 -0600 2011 ========== Installing app id 64woea2dr6 under /var/hda/platform/html ENV=production ======= app uninstall begin @ Fri Jan 14 21:45:38 -0600 2011 ========== Uninstalling app id 64woea2dr6 under /var/hda/platform/html ENV=production App: uShare uninstalled ======= app uninstall end @ Fri Jan 14 21:45:44 -0600 2011 ==========

This is from my app installations starting from when the problems first began. I was able to access Ajaxterm from the port address listed in the log, but the address does not resolve.

amahi-app-installer.log

Code: Select all

======= app uninstall begin @ Thu Mar 17 03:47:34 -0500 2011 ========== Uninstalling app id dek8819qts under /var/hda/platform/html ENV=production Your HDA services have been restarted. App: phpSysInfo uninstalled ======= app uninstall end @ Thu Mar 17 03:47:41 -0500 2011 ========== ======= app install begin @ Thu Mar 17 03:48:12 -0500 2011 ========== Installing app id dek8819qts under /var/hda/platform/html ENV=production NOTICE: redirected 'http://downloads.sourceforge.net/project/phpsysinfo/phpsysinfo/3.0.10/phpsysinfo-3.0.10.tar.gz' --> 'http://cdnetworks-us-1.dl.sourceforge.net/project/phpsysinfo/phpsysinfo/3.0.10/phpsysinfo-3.0.10.tar.gz' ... NOTE: file /tmp/amahi-download-cache/404bd3c446f23e7dfb9cd25bbefcbac1ff95b493 written in cache Your HDA services have been restarted. Your HDA services have been restarted. App: phpSysInfo installed ======= app install end @ Thu Mar 17 03:49:41 -0500 2011 ========== ======= app uninstall begin @ Sun Mar 20 19:35:11 -0500 2011 ========== Uninstalling app id dek8819qts under /var/hda/platform/html ENV=production Your HDA services have been restarted. App: phpSysInfo uninstalled ======= app uninstall end @ Sun Mar 20 19:35:14 -0500 2011 ========== ======= app install begin @ Sun Mar 20 19:35:43 -0500 2011 ========== Installing app id dek8819qts under /var/hda/platform/html ENV=production NOTE: file /tmp/amahi-download-cache/404bd3c446f23e7dfb9cd25bbefcbac1ff95b493 picked up from cache. Your HDA services have been restarted. Your HDA services have been restarted. App: phpSysInfo installed ======= app install end @ Sun Mar 20 19:36:16 -0500 2011 ========== ======= app install begin @ Sun Mar 20 19:54:10 -0500 2011 ========== Installing app id by73p2t5a3 under /var/hda/platform/html ENV=production NOTICE: redirected 'http://downloads.sourceforge.net/project/jinzora/Jinzora%202.0/Jinzora%202.8/jz280.tar.gz' --> 'http://iweb.dl.sourceforge.net/project/jinzora/Jinzora%202.0/Jinzora%202.8/jz280.tar.gz' ... NOTE: file /tmp/amahi-download-cache/51bd37b56537ca9dc1149c8e93a659a7baaf114a written in cache Your HDA services have been restarted. Your HDA services have been restarted. App: Jinzora installed ======= app install end @ Sun Mar 20 19:54:43 -0500 2011 ========== ======= app install begin @ Sun Mar 20 20:25:18 -0500 2011 ========== Installing app id k4nymnu42b under /var/hda/platform/html ENV=production Your HDA services have been restarted. Your HDA services have been restarted. AjaxTerm at http://localhost:8022/ pid: 11892 App: Ajaxterm installed ======= app install end @ Sun Mar 20 20:29:29 -0500 2011 ==========

[bigfoot65]

The app log files that show ruby errors indicate the app did not install correctly. In that case, you need to uninstall and reinstall.

We have seen some of these issues due to connectivity problems. We are still trying to run them down. For now, the best advice would be to remove any app that did not install correctly, then reinstall. If the errors persist, please let us know. The more details you can provide, then better.

Are most apps working now? Which ones are not and did they have errors in the log? I am sure we can get this sorted out, but it make take some time. So many variables to trace.

[Aldanga]

The app which had the errors was AjaXplorer. I've since uninstalled that app. Reinstallation for testing purposes is not possible since AjaXplorer is in Alpha for F14.

The only apps which aren't loading by their domain names are Jinzora and Ajaxterm. These are the last two apps I've installed. Everything else is functional. I haven't seen any errors for either app in any file in /var/log.

[bigfoot65]

This evidently is some fallout from upgrading. That's the only explanation I can come up with. No reason why all apps do not work.

Can you check the /etc/httpd/conf.d files for those 2 apps. Make sure there is a line in there for jinzora.home.com and ajaxterm.home.com respectively. If that is missing, it could be the cause. If not, then more analysis will be needed to sort this out.