Hey Greg,

I noticed a current thread on the vcl-dev list that I think explains the issue 
you are having (pasted below).

Hope this helps,

Patrick



Begin forwarded message:

> From: Mark Gardner <lil.lis...@gmail.com>
> Date: May 3, 2010 3:55:02 PM EDT
> To: vcl-...@incubator.apache.org
> Subject: Re: Question about user.uid
> Reply-To: vcl-...@incubator.apache.org
> 
> Debian/Ubuntu at least starts user IDs at 1000. 101 conflicted with syslogd.
> 
> Mark
> 
> On Mon, May 3, 2010 at 3:41 PM, Aaron Peeler <aaron_pee...@ncsu.edu> wrote:
> 
>> It's safe, there are no problems to change it.
>> It used to be 1, we figured 101 would be safe - guess not :)
>> -A
>> 
>> 
>> On 5/3/10 3:36 PM, Mark Gardner wrote:
>> 
>>> It appears that my reservation is failing because the Linux guest already
>>> has a user with ID 101:
>>> 
>>> 2010-05-03 15:06:08|7355|20:20|new|utils.pm:
>>> run_ssh_command(6180)|executing
>>> SSH command on vmguest-1:
>>> |7355|20:20|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>> vmguest-1 '/usr/sbin/useradd -u 101 -d /home/admin -m admin -g vcl' 2>&1
>>> 2010-05-03 15:06:08|7355|20:20|new|utils.pm:
>>> run_ssh_command(6262)|run_ssh_command
>>> output:
>>> |7355|20:20|new| useradd: UID 101 is not unique
>>> 
>>> It seems that the value comes from user.uid as shown below.
>>> 
>>> mysql>  select * from user where uid=101;
>>> 
>>> +----+------+---------+---------------+-----------+----------+---------------+----------------+--------------+----------+------+--------------+-------+--------+-----+-----------+-----------+-------------+-----------+---------------+---------------------+
>>> | id | uid  | unityid | affiliationid | firstname | lastname |
>>> preferredname
>>> | email          | emailnotices | IMtypeid | IMid | adminlevelid | width |
>>> height | bpp | audiomode | mapdrives | mapprinters | mapserial |
>>> showallgroups | lastupdated         |
>>> 
>>> +----+------+---------+---------------+-----------+----------+---------------+----------------+--------------+----------+------+--------------+-------+--------+-----+-----------+-----------+-------------+-----------+---------------+---------------------+
>>> |  1 |  101 | admin   |             1 | vcl       | admin    |
>>> | r...@localhost |            0 |        1 | NULL |            3 |  1024
>>> |
>>> 768 |  16 | local     |         1 |           1 |         1 |
>>> 1
>>> | 2007-05-17 09:58:39 |
>>> 
>>> +----+------+---------+---------------+-----------+----------+---------------+----------------+--------------+----------+------+--------------+-------+--------+-----+-----------+-----------+-------------+-----------+---------------+---------------------+
>>> 
>>> Would it cause problems if I changed it to some other value that doesn't
>>> conflict with the guest's user IDs? Say 1001 perhaps?
>>> 
>>> Mark
>>> 
>>> 
>> 
>> 
>> --
>> 
>> Aaron Peeler
>> Program Manager
>> Virtual Computing Lab
>> NC State University
>> aaron_pee...@ncsu.edu
>> 919-513-4571
>> 
>> 
> 
> 
> -- 
> Mark Gardner
> --


On May 6, 2010, at 2:16 PM, Duhon, Gregory D wrote:

> I can successfully reserve my Debian image but cannot logon to it after the 
> reservation.
> Further testing proved that I could ssh into the reserved image over the 
> private IP.
> The userid and password are not injected into the reserved image.
> If you direct me to the script that is doing the injecting, I can try to fix 
> it.
> I have searched through almost every log file I can think of but can’t find 
> out where the error is occurring.
>  
> Thanks,
> Gregory Duhon
> Infrastructure Architect
> Information Technology
> California State University, Northridge
> 818-677-4114
> gregory.du...@csun.edu
>  

Reply via email to