ushare reports eth1 as down yet is working just fine

I can confirm I have the same problem with eth0

Same problem with eth0.

~$ ushare
Interface eth0 is down.
Recheck uShare's configuration and try again !
uShare (version 1.1a), a lightweight UPnP A/V and DLNA Media Server.
Benjamin Zores (C) 2005-2007, for GeeXboX Team.
See http://ushare.geexbox.org/ for updates.
Listening on telnet port 1337
Initializing UPnP subsystem ...
UPnP MediaServer listening on 192.168.1.100:49152
Sending UPnP advertisement for device ...
Listening for control point connections ...
Building Metadata List ...
Looking for files in content directory : ~/movies
scandir: No such file or directory
Found 2 files and subdirectories.

eth0 is most definitely not down. I'm using it to connect to the internet to write this right now. The output above uses the /etc/ushare.conf file for ushare config. On line #22 I've specified USHARE_DIR=~/movies as my default directory. The above output is incorrect in saying that I have only 2 files and subdirectories in ~/movies/. I have 18.

If I run ushare -c ~/movies ushare reports finding 21 files and subdirectories, which is closer to the correct number, but still wrong. Attached is my ushare.conf file.

ifconfig reports:
eth0 Link encap:Ethernet HWaddr 00:1b:fc:e3:76:43
          inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21b:fcff:fee3:7643/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:267995 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306811 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:151898353 (151.8 MB) TX bytes:264146272 (264.1 MB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:241 errors:0 dropped:0 overruns:0 frame:0
          TX packets:241 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:31492 (31.4 KB) TX bytes:31492 (31.4 KB)

Google searches primarily return suggestions about changing USHARE_IFACE. But that is mostly for people who want to change their interface to use their wireless networks.

This Ubuntu Forums archive seemed to be going somewhere but then just stopped. It does explain the problem I and others are having though. http://ubuntuforums.org/archive/index.php/t-881548.html

I'm guessing that the service isn't stopping properly.

I found that finding open instances and killing the remaining ushare processes via htop frees up the port to relaunch the service. Not the best workaround but it seems to work for me.

I get this fault with Ubuntu 11.10 / 64bit. It's still a bug.

same for me. Ushare was working fine until I reboot my computer, and then it displayed this message, no matter what I did elsewhere to get rid of it (killing ushare services and processes)