Finally took the plunge and upgraded to the Plus version

 

However I'm trying to add new user accounts so I can put some more protection on the user shares. I fill in the username and password boxes and hit add, but the screen just refreshes and the new user isn't there....

 

I get this in my syslog:

 

Aug 12 22:13:30 Tower emhttp: shcmd (56): useradd -d / -g jhayes -s /bin/false -u 1000 jhayes
Aug 12 22:13:30 Tower emhttp: _shcmd: shcmd (56): exit status: 4
Aug 12 22:13:30 Tower emhttp: shcmd (57): chpasswd <<< jhayes:"*****"
Aug 12 22:13:30 Tower emhttp: _shcmd: shcmd (57): exit status: 1
Aug 12 22:13:30 Tower emhttp: shcmd (58): smbpasswd -L -s -a jhayes <<< "*****"$'\n'"*****"
Aug 12 22:13:30 Tower emhttp: _shcmd: shcmd (58): exit status: 1
Aug 12 22:13:30 Tower emhttp: shcmd (59): cp /etc/passwd /etc/samba/private/smbpasswd /boot/config

 

Any clues? I find it a bit odd that nothing happens including no error messages or anything.

 

I'm running 4.5.4.

 

Justin

Ahhhh think I might have figured it out  

 

Tried to run unraid's command manually:

 

root@Tower:/boot/config# useradd -d / -g jhayes -s /bin/false -u 1000 jhayes

 

and got this error:

 

useradd: uid 1000 is not unique

 

Checking /etc/password it looks like I (or unMenu) added an istat user account with the same uid:

 

istat:!:1000:100::/home/istat:

 

I guess unraid just starts at 1000 so I need to pick something different for istat?

Hmmm looking at the threads for istat via unmenu I can't seen anything telling me I should be creating that user account. Perhaps I added it in before it was available in unmenu and need to remove it.

 

Will give that a go.....

Nope removed it and rebooted and the user has come back, so I guess the istat package in unmenu is putting that user back in on reboot.

 

So I have to choose whether to have istat or more user accounts?

Figured I'd try removing the auto-install of istat from unmenu, and that would stop the istat user being created.

 

But it still comes back every reboot 

On reboot, unRAID uses the copies of the password files stored on the flash drive as a base. You need to perform the following commands AFTER you remove the iSTAT user. You even quoted it in the log section you provided.  

 

To properly delete a user, you should always perform the following steps together:

smbpasswd -x username

userdel username

 

 

cp /etc/passwd /etc/samba/private/smbpasswd /boot/config

Hehe yeah thanks - got there in the end. Finally stopped istat setting up it's user so I could create my samba users. Then turned istat install back on

 

Might be worth whoever maintains the istat package changing the install script to select a uid under 1000.....

Hehe yeah thanks - got there in the end. Finally stopped istat setting up it's user so I could create my samba users. Then turned istat install back on

 

Might be worth whoever maintains the istat package changing the install script to select a uid under 1000.....

Actually, the script does not specify any ID.

 

PACKAGE_INSTALLATION /usr/sbin/useradd istat 2>/dev/null

PACKAGE_INSTALLATION /usr/sbin/groupadd istat 2>/dev/null

The problem you are describing is a bug in unRAID and its handling of user ID 1000.

See here: http://lime-technology.com/forum/index.php?topic=7072.0

Ahh interesting Joe thanks. I noticed that the istat package wasn't specifying a user. Is there a special reason why the first one gets allocated 1000?

 

Hopefully it'll be fixed in v5 then