samba doesn't start with sane config, can't connect to itself
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu AMI Testing |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Testing the AMI RC image for EC2. At testcase ec2_014.
Samba was just cleanly installed using 'sudo apt-get update && sudo tasksel --section server' and selecting 'Samba server'.
It seems that the testcase fails with NT_STATUS_
ubuntu@
Enter ubuntu's password:
WORKGROUP
\\IP-10-251-105-23 ip-10-251-105-239 server (Samba, Ubuntu)
cli_start_
Additionally, on startup of smbd, it seems that something else is holding the socket/address that samba is expecting. Here is an excerpt of /var/log/
[2009/10/23 00:55:11, 0] smbd/server.
smbd version 3.4.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/23 00:55:11, 0] smbd/server.
smbd_
[2009/10/23 00:55:11, 0] smbd/server.
smbd_
And log.nmbd:
[2009/10/23 00:55:11, 0] nmbd/nmbd.
nmbd version 3.4.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/10/23 00:55:11, 0] nmbd/nmbd_
register_name: NetBIOS name IP-10-251-105-239 is too long. Truncating to IP-10-251-105-2
[2009/10/23 00:55:11, 0] nmbd/nmbd_
register_name: NetBIOS name IP-10-251-105-239 is too long. Truncating to IP-10-251-105-2
[2009/10/23 00:55:11, 0] nmbd/nmbd_
register_name: NetBIOS name IP-10-251-105-239 is too long. Truncating to IP-10-251-105-2
[2009/10/23 00:55:34, 0] nmbd/nmbd_
*****
Samba name server IP-10-251-105-239 is now a local master browser for workgroup WORKGROUP on subnet 10.251.105.239
*****
I seem to no longer be having this issue on a newly created image as of today, using ami-8d0eede4. I'm marking this invalid and attributing the issue to an error on my part... Sorry for the false positive.