I finally got round to implementing User Shares, but after starting it in the browser management utility, the MU hung and I haven't been able to return to it. I thought at first nothing had been executed because of the MU hanging, but later I found that it appears to have worked. However, I'd like to check whether I have duplicate files (I'm sure I do). The MU is not responding when I try to access it via a browse (even when using the IP address directly, which I checked using ifconfig), but I can telnet to the server.

 

This has been raised here and here on the 3.0 forum, but as I'm now on 4.21, I thought I should post here, in case the latest release handles things differently.

 

In both topics, reference is made to seeing duplicates listed in the log file. I assume there is only one log file (/var/log/syslog)? Looking at my logfile I get only this:

 

Tower login: root

 

[Disconnect bypassed -- root login allowed.]

Linux 2.6.22.5.

root@Tower:~# tail -f /var/log/syslog

Jan 29 18:56:32 Tower emhttp[1095]: shcmd (21): killall -HUP smbd

Jan 29 20:58:59 Tower emhttp[1095]: get_var: shareSplitLevel.1752459118 not foun

d

Jan 29 20:58:59 Tower emhttp[1095]: get_var: shareInclude.1752459118 not found

Jan 29 20:58:59 Tower emhttp[1095]: get_var: shareExclude.1752459118 not found

Jan 29 20:58:59 Tower emhttp[1095]: get_var: shareExport.1752459118 not found

Jan 29 20:58:59 Tower last message repeated 4 times

Feb  3 22:08:09 Tower in.telnetd[4414]: connect from 192.168.2.35 (192.168.2.35)

Feb  3 22:08:23 Tower login[4415]: ROOT LOGIN  on `pts/0' from `192.168.2.35'

Feb  5 05:36:55 Tower in.telnetd[5128]: connect from 192.168.2.35 (192.168.2.35)

Feb  5 05:37:16 Tower login[5129]: ROOT LOGIN  on `pts/0' from `192.168.2.35'

 

 

(I logged in a couple of days ago as well.) There are obviously no duplicates, which I don't quite believe. I could of course test the duplicates logging by creating a duplicate file, but this would also involve the slightly tedious task of shutting down the server from the command line and then restarting in order to get back to the MU and re-running User Shares, which I suspect will take a while.

 

However, it looks like there was a problem with the User Shares, but I don't know whether the command was completed or whether it hit a problem and stopped. And possibly this is why there are no duplicates listed in the log.

 

Can anyone shed light on the log entries?

 

Looks like you have a lot of files in the top level directories of one or more disks.

 

Before enabling User Shares, you should consolidate all your files under just a few top level directories, e.g.,

 

/Movies

/Video

/Backup

 

etc.  The way User Shares work is that each directory at the top level of each disk is exported as a User Share.  If you have a gazillion top level directories, then it ends up consuming all the memory until eventually the system crashes 

 

We really should have a check for this kind of issue in the s/w and indeed we put this on the bug list.

Thanks, that was indeed the problem. Tidied things up and everything looks fine.

 

What was quite gratifying, though, was that pre-tidying up, the server continued to respond (reading and writing worked OK) AND seemed to list the gazillion files as if the User shares had worked as expected. The only visible issue was that the web interface was no longer responding.