I noticed that the MyBookLive has some weird system users whose home directories are set as /shared. Although by default the ssh access is allowed only to root and this can only be changed by root, I still saw this as a little security risk. Instead of deleting these users I locked them with "usermod —lock" and in case something should not work after that I can easily unlock them again.
These users I locked were : daapd, guest, ftp, admin-dfalias-wd, admin.
Although before doing that I took a quick look at the MBLive's web gui, but as I did not find anything that should have connected these users with the web-gui (the files were owned by root and ran under the privileges of www-data) I locked them. Also nowhere in the web gui's files there was mentioned these usersnames.
But after doing so some time later I discovered that the web gui is not working, so I unlocked them with "usermod —unlock". But somehow this did not solve the nonworking web gui. And although the web gui is not necessary if you have ssh access cause it's quite slow and limited, I still would like this to work in case I decide to sell my disk some day in the future.
I did have a closer look at the web gui's files after it stopped working and the problem seems to be only with displaying shares and users. The php errors occur when the script tries to execute some system commands with php exec() using sudo.
I know one option to get it working again is to restore the disk to factory defaults, but in that case I'd have to back up all my data and what's more important I'd lose all the packages and modifications I have installed and made. So is there anybody who maybe has had the same problem and knows how to solve it or maybe knows the web gui a little better and can maybe guess what might be the problem?
This is how the errors look like http://www.upload.ee/image/1191202/sc_wd.jpg