ISST-LTE: Samba server doesn't work well on Ubuntu 14.04.3 on ppc64el

[bugproxy]

Today we install ubuntu 14.04.3 on pole2lp1. We found that the samba server doesn't work well.

root@pole2lp1:/etc/samba# /etc/init.d/smbd status
 * smbd is running

root@pole2lp1:/etc/samba# smbclient -L pole2lp1
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

We also tried to add a user and got the same result.
root@pole2lp1:/etc/samba# smbpasswd -a root
New SMB password:
Retype new SMB password:

root@pole2lp1:/etc/samba# smbclient -L pole2lp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

root@pole2lp1:/etc/samba# testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        server string = %h server (Samba, Ubuntu)
        server role = standalone server
        map to guest = Bad User
        obey pam restrictions = Yes
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        usershare allow guests = Yes
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb

[printers]
        comment = All Printers
        path = /var/spool/samba
        create mask = 0700
        printable = Yes
        print ok = Yes
        browseable = No

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers

== Comment: #2 - Henish V. Patel <email address hidden> - 2015-07-08 07:29:58 ==
smbclient -L pole2lp1 -U root --debuglevel=10
INFO: Current debug levels:
  all: 10
  tdb: 10
  printdrivers: 10
  lanman: 10
  smb: 10
  rpc_parse: 10
  rpc_srv: 10
  rpc_cli: 10
  passdb: 10
  sam: 10
  auth: 10
  winbind: 10
  vfs: 10
  idmap: 10
  quota: 10
  acls: 10
  locking: 10
  msdfs: 10
  dmapi: 10
  registry: 10
  scavenger: 10
  dns: 10
  ldb: 10
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
  all: 10
  tdb: 10
  printdrivers: 10
  lanman: 10
  smb: 10
  rpc_parse: 10
  rpc_srv: 10
  rpc_cli: 10
  passdb: 10
  sam: 10
  auth: 10
  winbind: 10
  vfs: 10
  idmap: 10
  quota: 10
  acls: 10
  locking: 10
  msdfs: 10
  dmapi: 10
  registry: 10
  scavenger: 10
  dns: 10
  ldb: 10
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = WORKGROUP
doing parameter server string = %h server (Samba, Ubuntu)
doing parameter dns proxy = no
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 1000
doing parameter syslog = 0
doing parameter panic action = /usr/share/samba/panic-action %d
doing parameter server role = standalone server
doing parameter passdb backend = tdbsam
doing parameter obey pam restrictions = yes
doing parameter unix password sync = yes
doing parameter passwd program = /usr/bin/passwd %u
doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
doing parameter pam password change = yes
doing parameter map to guest = bad user
doing parameter usershare allow guests = yes
pm_process() returned Yes
lp_servicenumber: couldn't find homes
added interface eth0 ip=2002:903:15f:1130:586b:3eff:fe27:8d02 bcast= netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=10.33.8.14 bcast=10.33.255.255 netmask=255.255.0.0
Netbios name list:-
my_netbios_names[0]="POLE2LP1"
Client started (version 4.1.6-Ubuntu).
Enter root's password:
Opening cache file at /var/cache/samba/gencache.tdb
Opening cache file at /var/run/samba/gencache_notrans.tdb
sitename_fetch: No stored sitename for
internal_resolve_name: looking up pole2lp1#20 (sitename (null))
Adding cache entry with key=[NBT/POLE2LP1#20] and timeout=[Wed Dec 31 06:00:00 PM 1969 CST] (-1436353427 seconds in the past)
no entry for pole2lp1#20 found.
resolve_lmhosts: Attempting lmhosts lookup for name pole2lp1<0x20>
resolve_lmhosts: Attempting lmhosts lookup for name pole2lp1<0x20>
startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name pole2lp1<0x20>
remove_duplicate_addrs2: looking for duplicate address/port pairs
namecache_store: storing 1 address for pole2lp1#20: 127.0.1.1
Adding cache entry with key=[NBT/POLE2LP1#20] and timeout=[Wed Jul 8 06:14:47 AM 2015 CDT] (660 seconds ahead)
internal_resolve_name: returning 1 addresses: 127.0.1.1:0
Connecting to 127.0.1.1 at port 445
Socket options:
 SO_KEEPALIVE = 0
 SO_REUSEADDR = 0
 SO_BROADCAST = 0
 TCP_NODELAY = 1
 TCP_KEEPCNT = 9
 TCP_KEEPIDLE = 7200
 TCP_KEEPINTVL = 75
 IPTOS_LOWDELAY = 0
 IPTOS_THROUGHPUT = 0
 SO_REUSEPORT = 0
 SO_SNDBUF = 2626560
 SO_RCVBUF = 1062832
 SO_SNDLOWAT = 1
 SO_RCVLOWAT = 1
 SO_SNDTIMEO = 0
 SO_RCVTIMEO = 0
 TCP_QUICKACK = 1
 TCP_DEFER_ACCEPT = 0
 session request ok
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

[bugproxy (bugproxy)]

Default Comment by Bridge

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1472584/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-08 15:50 EDT-------
This bug is blocking our NFS testing. Need quick attention.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-08 17:57 EDT-------
Please provide output from the following:

cat /etc/services | egrep "netbios|microsoft|ipp"
netstat -l | egrep "netbios|microsoft|ipp"
lsof | egrep "netbios|microsoft|ipp"
ps awfux | egrep "smb[d]|nmb[d]"

I'm guessing the cups errors are benign in the log file you attached. I see those same messages on my system (probably just because nothing is listening on the ipp port) and I am not experiencing the problem you see.

Are there any other interesting logs in "/var/log/samba/"? There is a "cores" directory so please check that, and check /var/log/syslog for evidence of a crash in smbd or nmbd. Or anything else interesting in syslog. Do you see any errors when you restart smbd? Does restarting it have any effect on the problem?

Also, please collect the "sosreport" and attach it to the bug. You can "apt-get install sosreport" if not already installed.

You are using entirely the as-installed smbd configuration here, I assume, else you would have reported otherwise? Thx.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-08 19:23 EDT-------
(In reply to comment #9)
> Please provide output from the following:
>
> cat /etc/services | egrep "netbios|microsoft|ipp"
> netstat -l | egrep "netbios|microsoft|ipp"
> lsof | egrep "netbios|microsoft|ipp"
> ps awfux | egrep "smb[d]|nmb[d]"

root@pole2lp1:~# cat /etc/services | egrep "netbios|microsoft|ipp"
netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp
netbios-ssn 139/tcp # NETBIOS session service
netbios-ssn 139/udp
microsoft-ds 445/tcp # Microsoft Naked CIFS
microsoft-ds 445/udp
ipp 631/tcp # Internet Printing Protocol
ipp 631/udp
root@pole2lp1:~# netstat -l | egrep "netbios|microsoft|ipp"
tcp 0 0 *:netbios-ssn *:* LISTEN
tcp 0 0 *:microsoft-ds *:* LISTEN
tcp6 0 0 [::]:netbios-ssn [::]:* LISTEN
tcp6 0 0 [::]:microsoft-ds [::]:* LISTEN
udp 0 0 ip10-33-255-:netbios-ns *:*
udp 0 0 pole2lp1.iss:netbios-ns *:*
udp 0 0 *:netbios-ns *:*
udp 0 0 ip10-33-255:netbios-dgm *:*
udp 0 0 pole2lp1.is:netbios-dgm *:*
udp 0 0 *:netbios-dgm *:*
root@pole2lp1:~# lsof | egrep "netbios|microsoft|ipp"
smbd 1157 root 30u IPv6 47185 0t0 TCP *:microsoft-ds (LISTEN)
smbd 1157 root 31u IPv6 47186 0t0 TCP *:netbios-ssn (LISTEN)
smbd 1157 root 32u IPv4 47187 0t0 TCP *:microsoft-ds (LISTEN)
smbd 1157 root 33u IPv4 47188 0t0 TCP *:netbios-ssn (LISTEN)
nmbd 1402 root 11u IPv4 27694 0t0 UDP *:netbios-ns
nmbd 1402 root 12u IPv4 27695 0t0 UDP *:netbios-dgm
nmbd 1402 root 13u IPv4 15450 0t0 UDP pole2lp1.isst.aus.stglabs.ibm.com:netbios-ns
nmbd 1402 root 14u IPv4 15451 0t0 UDP ip10-33-255-255.isst.aus.stglabs.ibm.com:netbios-ns
nmbd 1402 root 15u IPv4 15452 0t0 UDP pole2lp1.isst.aus.stglabs.ibm.com:netbios-dgm
nmbd 1402 root 16u IPv4 15453 0t0 UDP ip10-33-255-255.isst.aus.stglabs.ibm.com:netbios-dgm
root@pole2lp1:~# ps awfux | egrep "smb[d]|nmb[d]"
root 1157 0.0 0.1 74944 27008 ? Ss 03:59 0:00 smbd -F
root 1240 0.0 0.0 74944 15168 ? S 03:59 0:00 \_ smbd -F
root 1402 0.0 0.0 27968 11776 ? Ss 03:59 0:00 nmbd -D

> I'm guessing the cups errors are benign in the log file you attached. I see
> those same messages on my system (probably just because nothing is listening
> on the ipp port) and I am not experiencing the problem you see.
>
> Are there any other interesting logs in "/var/log/samba/"? There is a
> "cores" directory so please check that, and check /var/log...

[bugproxy (bugproxy)]

------- Comment on attachment From <email address hidden> 2015-07-08 19:24 EDT-------

The checksum is: 9b50c62a9f60659f5a25de9bdd954424

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-09 02:09 EDT-------
Not sure what to suggest next except to increase the debug level of smbd and repeat the operation.

You can edit /etc/init/smbd.conf and add "-d 10" to the "exec smbd" cmdline. Then:

service smbd restart
tail -f /var/log/samba/log.smbd
smbclient -L localhost -U root

That will show the operation from the server side which will hopefully shed light on the problem.

Also: can you in fact connect from any client, or is it completely broken? Even trying the smbclient test from a different node might give a different result, possibly?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-09 03:01 EDT-------
(In reply to comment #13)
> Not sure what to suggest next except to increase the debug level of smbd and
> repeat the operation.
>
> You can edit /etc/init/smbd.conf and add "-d 10" to the "exec smbd" cmdline.
> Then:
>
> service smbd restart
> tail -f /var/log/samba/log.smbd
> smbclient -L localhost -U root
>
> That will show the operation from the server side which will hopefully shed
> light on the problem.
>
> Also: can you in fact connect from any client, or is it completely broken?
> Even trying the smbclient test from a different node might give a different
> result, possibly?

Hi?
We did your instructions and got the following output:

service smbd restart
tail -f /var/log/samba/log.smbd
smbclient -L localhost -U root

[2015/07/08 21:58:11.990413, 5, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:187(dbwrap_check_lock_order)
check lock order 2 for /var/run/samba/serverid.tdb
[2015/07/08 21:58:11.990489, 10, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:133(debug_lock_order)
lock order: 1:<none> 2:/var/run/samba/serverid.tdb 3:<none>
[2015/07/08 21:58:11.990571, 10, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap_tdb.c:59(db_tdb_log_key)
Locking key 403B000000000000FFFF
[2015/07/08 21:58:11.990665, 10, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap_tdb.c:143(db_tdb_fetch_locked_internal)
Allocated locked data 0x0x3fffeb866dc0
[2015/07/08 21:58:11.990743, 10, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap_tdb.c:59(db_tdb_log_key)
Unlocking key 403B000000000000FFFF
[2015/07/08 21:58:11.990805, 5, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:146(dbwrap_lock_order_state_destructor)
release lock order 2 for /var/run/samba/serverid.tdb
[2015/07/08 21:58:11.990861, 10, pid=15168, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:133(debug_lock_order)
lock order: 1:<none> 2:<none> 3:<none>
[2015/07/08 21:58:11.990943, 5, pid=15168, effective(0, 0), real(0, 0)] ../lib/util/util_net.c:848(print_socket_options)
Socket options:
SO_KEEPALIVE = 1
SO_REUSEADDR = 1
SO_BROADCAST = 0
TCP_NODELAY = 1
TCP_KEEPCNT = 9
TCP_KEEPIDLE = 7200
TCP_KEEPINTVL = 75
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_REUSEPORT = 1
SO_SNDBUF = 2626560
SO_RCVBUF = 1062720
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
TCP_QUICKACK = 1
TCP_DEFER_ACCEPT = 0
[2015/07/08 21:58:11.991497, 5, pid=15168, effective(0, 0), real(0, 0)] ../lib/util/util_net.c:848(print_socket_options)
Socket options:
SO_KEEPALIVE = 1
SO_REUSEADDR = 1
SO_BROADCAST = 0
TCP_NODELAY = 1
TCP_KEEPCNT = 9
TCP_KEEPIDLE = 7200
TCP_KEEPINTVL = 75
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_REUSEPORT = 1
SO_SNDBUF = 2626560
SO_RCVBUF = 1062720
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
TCP_QUICKACK = 1
TCP_DEFER_ACCEPT = 0
[2015/07/08 21:58:32.014703, 5, pid=15083, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:187(dbwrap_check_lock_order)
check lock order 2 for /var/run/samba/serverid.tdb
[2015/07/08 21:58:32.014770, 10, pid=15083, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:133(debug_lock_order)
loc...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-09 15:19 EDT-------
Well, I'm quickly exhausting my samba expertise here. I don't know how to interpret all the debug messages but I'll say: your output doesn't really contain anything different from mine, and on my system everything seems to be working.

Because there are no apparent errors from samba I'm starting to suspect some networking issue, for lack of better explanation. I guess Ubuntu uses "apparmor" instead of selinux here, and I'm not as familiar with apparmor, but it looks like you can do the following to shut it down. Suggest running the status first to see if anything odd:

service apparmor status
service apparmor teardown

If that doesn't help I am out of ideas.

Doing a broad search on NT_STATUS_IO_TIMEOUT doesn't point to anything specific. apparently it's a common problem that pops over recent years and most cases are either attributed to network problems or indeterminate.

Ubuntu: really need your help here. Please get this assigned and give us an initial read as soon as you can. thanks!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-10 06:49 EDT-------
(In reply to comment #16)
> Well, I'm quickly exhausting my samba expertise here. I don't know how to
> interpret all the debug messages but I'll say: your output doesn't really
> contain anything different from mine, and on my system everything seems to
> be working.
>
> Because there are no apparent errors from samba I'm starting to suspect some
> networking issue, for lack of better explanation. I guess Ubuntu uses
> "apparmor" instead of selinux here, and I'm not as familiar with apparmor,
> but it looks like you can do the following to shut it down. Suggest running
> the status first to see if anything odd:
>
> service apparmor status
> service apparmor teardown
>
> If that doesn't help I am out of ideas.
>
> Doing a broad search on NT_STATUS_IO_TIMEOUT doesn't point to anything
> specific. apparently it's a common problem that pops over recent years and
> most cases are either attributed to network problems or indeterminate.
>
> Ubuntu: really need your help here. Please get this assigned and give us an
> initial read as soon as you can. thanks!

Hi,
pole2lp1 is used to debug bug 127303 now and I used lakelp1 to verify your suggestion. I got the same result.

root@lakelp1:~# /etc/init.d/smbd status
* smbd is running

root@lakelp1:~# smbclient -L lakelp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

root@lakelp1:~# service apparmor status
apparmor module is loaded.
5 profiles are loaded.
5 profiles are in enforce mode.
/sbin/dhclient
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/ntpd
/usr/sbin/tcpdump
0 profiles are in complain mode.
2 processes have profiles defined.
2 processes are in enforce mode.
/sbin/dhclient (2329)
/usr/sbin/ntpd (2974)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

root@lakelp1:~# service apparmor teardown
* Unloading AppArmor profiles [ OK ]

root@lakelp1:~# smbclient -L lakelp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

root@lakelp1:~# smbpasswd -a root
New SMB password:
Retype new SMB password:
Added user root.

root@lakelp1:~# smbclient -L lakelp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

[Robie Basak (racb)]

> Ubuntu: really need your help here. Please get this assigned and give us an initial read as soon as you can. thanks!

Sorry, we don't use this bug tracker as a support forum. If you need help, please raise it through commercial support channels or use the community support channels listed at http://www.ubuntu.com/support/community

If you're reporting an actual bug, please describe in detail (steps to reproduce, expected results, actual results) and change the bug status back to New.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-10 22:24 EDT-------
Testing samba server running on the local host:

Expected result is like this (working system):

root@cellc10:~# smbclient -L cellc10 -U root
Enter root's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (cellc10 server (Samba, Ubuntu)) Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Server Comment
--------- -------
CELLC10 cellc10 server (Samba, Ubuntu)

Workgroup Master
--------- -------
WORKGROUP CELLC10

Actual result is this (failing system, reported here):

root@pole2lp1:/etc/samba# smbclient -L pole2lp1 -U root
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-13 03:15 EDT-------
We reached this bug on a fresh install and we didn't modify the samba config file.
The following is the samba packages we installed and the version.

root@pole2lp1:~# apt-cache search "^samba"
libwbclient-dev - Samba winbind client library - development files
libwbclient0 - Samba winbind client library
samba - SMB/CIFS file, print, and login server for Unix
samba-common - common files used by both the Samba server and client
samba-common-bin - Samba common files used by both the server and the client
samba-dbg - Samba debugging symbols
samba-dev - tools for extending Samba
samba-doc - Samba documentation
samba-dsdb-modules - Samba Directory Services Database
samba-libs - Samba core libraries
samba-vfs-modules - Samba Virtual FileSystem plugins
smbclient - command-line SMB/CIFS clients for Unix
gosa-plugin-samba - samba3 plugin for GOsa?
libnss-winbind - Samba nameservice integration plugins
samba-testsuite - test suite from Samba
smb4k - Samba (SMB) share advanced browser for KDE
root@lakelp1:~# apt-cache policy samba
samba:
Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.8
Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.8
Version table:
*** 2:4.1.6+dfsg-1ubuntu2.14.04.8 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages
100 /var/lib/dpkg/status
2:4.1.6+dfsg-1ubuntu2.14.04.7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main ppc64el Packages
2:4.1.6+dfsg-1ubuntu2 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages

Expected result is like this (working system):

root@cellc10:~# smbclient -L cellc10 -U root
Enter root's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (cellc10 server (Samba, Ubuntu)) Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Server Comment
--------- -------
CELLC10 cellc10 server (Samba, Ubuntu)

Workgroup Master
--------- -------
WORKGROUP CELLC10

Actual result is this (failing system, reported here):

root@pole2lp1:/etc/samba# smbclient -L pole2lp1 -U root
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

[Robie Basak (racb)]

I cannot reproduce this on a fresh Trusty system:

ubuntu@trusty:~$ smbclient -L localhost -U root
Enter root's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

 Sharename Type Comment
 --------- ---- -------
 print$ Disk Printer Drivers
 IPC$ IPC IPC Service (trusty server (Samba, Ubuntu))
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

 Server Comment
 --------- -------
 TRUSTY trusty server (Samba, Ubuntu)

 Workgroup Master
 --------- -------
 WORKGROUP
ubuntu@trusty:~$ dpkg-query -W samba
samba 2:4.1.6+dfsg-1ubuntu2.14.04.8
ubuntu@trusty:~$

Please provide steps to reproduce.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-13 15:18 EDT-------
Hi Robie,

I think we have provided the steps to reproduce, and the expected vs. actual result, and also verbose debug output from samba on the client-side and the server-side.

I can't explain why it's not reproducible on your system; it's not reproducible on mine, either. But I am testing with the BE builld of Ubuntu, not the LE build, so it's possible there is some bug in the LE version that I'm not seeing. You didn't say whether you are using BE or LE in your tests.

I have asked the IBM team several times if this is reproducible on a fresh system install with no changes to samba configuration, and they tell me is. Apologies if this turns out to be a configuration issue or some other not-a-bug, but at the moment we don't know what the problem is, so I think we need next steps for continued debugging. If you don't see anything suspicious in the log output provided, can you suggest some other debug to collect or or other tests to run?

We will endeavor to provide what you request in a timely fashion, so would appreciate it if you can kindly change the status from "incomplete" on the LP side. Thx.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-14 02:47 EDT-------
Hi,
We installed a new fresh system dilllp1 and this bug is still exist.

root@dilllp1:~# /etc/init.d/smbd status
* smbd is running

root@dilllp1:~# smbclient -L dilllp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

root@dilllp1:~# smbpasswd -a root
New SMB password:
Retype new SMB password:
Added user root.

root@dilllp1:~# smbclient -L dilllp1
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

root@dilllp1:~# uname -a
Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

root@dilllp1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-17 03:06 EDT-------
This bug blocks our cifs stress test. Any update? Thanks.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-17 14:18 EDT-------
Hi Canonical,

Can we get this assigned to someone who can look at it please? Apparently I don't have privileges to change the status on the launchpad side, and that's not really our role anyway. Thx.

[Dave Heller (hellerda)]

Ah, apparently my status change did work. If we are using that as a sort of a flag to indicate needed info is provided, fair enough. I think we've got the necessary info, please review. Thanks.

[Robie Basak (racb)]

Ah, so this is a ppc64el-specific issue? In that case I need internal (Canonical) resources to look further as I'll need a ppc64el machine to test, and it is likely to be a non-trivial fix. I can't proceed with just my Ubuntu hat. If you need Canonical to look into this as a priority, please raise a request through commercial channels.

[Adam Conrad (adconrad)]

FWIW, I can reproduce this on a fresh ppc64el VM:

root@trusty-test:~# apt-get update && apt-get dist-upgrade
[...]
root@trusty-test:~# apt-get install samba smbclient
[...]
root@trusty-test:~# smbpasswd -a root
New SMB password:
Retype new SMB password:
Added user root.
root@trusty-test:~# smbclient -L localhost -U root
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

[Diane Brent (drbrent)]

Assigning to Screen team at Canonical for heigthened awareness. We are still working it, but would like Canonical to engage as well to see if we can expedite.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-27 17:15 EDT-------
The same problem happen on 14.04.2 with 3.16 kernel:

ubuntu@ubuntu14042:~$ smbclient -L localhost -U root
Enter root's password:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT
ubuntu@ubuntu14042:~$ uname -a
Linux ubuntu140402 3.16.0-44-generic #59~14.04.1-Ubuntu SMP Tue Jul 7 15:08:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

[Steve Langasek (vorlon)]

This is a userspace tool and we certainly would not expect there to be any differences in the behavior as a result of running on an earlier kernel. However, there have been stable release updates (including security updates) for samba in the 14.04 series, so it's probably worth checking whether this problem is reproducible when installing an earlier version of the samba and smbclient packages.

[Steve Langasek (vorlon)]

For that matter, could you please include the version numbers of samba and smbclient that you *did* test with? There are different versions currently in the trusty-security vs. trusty-updates pockets.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-28 02:38 EDT-------
(In reply to comment #36)
> This is a userspace tool and we certainly would not expect there to be any
> differences in the behavior as a result of running on an earlier kernel.
> However, there have been stable release updates (including security updates)
> for samba in the 14.04 series, so it's probably worth checking whether this
> problem is reproducible when installing an earlier version of the samba and
> smbclient packages.
>
> For that matter, could you please include the version numbers of samba and
> smbclient that you *did* test with? There are different versions currently
> in the trusty-security vs. trusty-updates pockets.

Hi,
Ubuntu 14.04.3 is the first build for power system. I'm not sure if the early version supports power system. Could you tell me how to install the early version ? Thanks.

The version of samba & smbclient we tested:

root@pole2lp1:~# aptitude show samba
Package: samba
State: installed
Automatically installed: no
Version: 2:4.1.6+dfsg-1ubuntu2.14.04.8

root@pole2lp1:~# aptitude show smbclient
Package: smbclient
State: installed
Automatically installed: no
Version: 2:4.1.6+dfsg-1ubuntu2.14.04.8

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-29 19:52 EDT-------
> I just tried this on a ppc64le machine with the latest samba packages and
> what looks like the latest kernel. It worked fine:
>
> root@palm6-p1:~# lsb_release -r
> Release: 14.10
So, it seems that the problem does not happen on version 14.10?

[Steve Langasek (vorlon)]

> ------- Comment From <email address hidden> 2015-07-28 02:38 EDT-------
> (In reply to comment #36)

> Hi,

> Ubuntu 14.04.3 is the first build for power system. I'm not sure if the
> early version supports power system.

This is the first version that fully supports PowerVM mode, but the issue
has also been reproduced on PowerNV. In any case it is possible to install
the older versions of the samba packages on this system.

> Could you tell me how to install the early version ? Thanks.

To install the version from trusty-security, you would do:

# apt-get purge samba smbclient
# apt-get autoremove --purge
# apt-get install samba=2:4.1.6+dfsg-1ubuntu2.14.04.7 smbclient=2:4.1.6+dfsg-1ubuntu2.14.04.7

To install the version from trusty release, you would do:

# apt-get purge samba smbclient
# apt-get autoremove --purge
# apt-get install samba=2:4.1.6+dfsg-1ubuntu2 smbclient=2:4.1.6+dfsg-1ubuntu2

> ------- Comment From <email address hidden> 2015-07-29 19:52 EDT-------
> > I just tried this on a ppc64le machine with the latest samba packages and
> > what looks like the latest kernel. It worked fine:
> >
> > root@palm6-p1:~# lsb_release -r
> > Release: 14.10
> So, it seems that the problem does not happen on version 14.10?

For reference, Ubuntu 14.10 includes samba version 4.13, vs. the 4.16
included in 14.04.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-30 05:56 EDT-------
(In reply to comment #41)
> > (In reply to comment #36)
>
> > Hi,
>
> > Ubuntu 14.04.3 is the first build for power system. I'm not sure if the
> > early version supports power system.
>
> This is the first version that fully supports PowerVM mode, but the issue
> has also been reproduced on PowerNV. In any case it is possible to install
> the older versions of the samba packages on this system.
>
> > Could you tell me how to install the early version ? Thanks.
>
> To install the version from trusty-security, you would do:
>
> # apt-get purge samba smbclient
> # apt-get autoremove --purge
> # apt-get install samba=2:4.1.6+dfsg-1ubuntu2.14.04.7
> smbclient=2:4.1.6+dfsg-1ubuntu2.14.04.7
>
> To install the version from trusty release, you would do:
>
> # apt-get purge samba smbclient
> # apt-get autoremove --purge
> # apt-get install samba=2:4.1.6+dfsg-1ubuntu2 smbclient=2:4.1.6+dfsg-1ubuntu2
>
> > > I just tried this on a ppc64le machine with the latest samba packages and
> > > what looks like the latest kernel. It worked fine:
> > >
> > > root@palm6-p1:~# lsb_release -r
> > > Release: 14.10
> > So, it seems that the problem does not happen on version 14.10?
>
> For reference, Ubuntu 14.10 includes samba version 4.13, vs. the 4.16
> included in 14.04.
>
> --
> Steve Langasek Give me a lever long enough and a Free OS
> Debian Developer to set it on, and I can move the world.
> Ubuntu Developer http://www.debian.org/
> <email address hidden> <email address hidden>

Hi,
I've tried the samba version 2:4.1.6+dfsg-1ubuntu2.14.04.8 and still reached this bug. I couldn't find other samba version except 4.1.6 in the repositories. Could you tell me where I can get the samba version 4.16 or other versions? Thanks.

The output after commands "apt-get purge samba smbclient" and "apt-get autoremove --purge".
root@conelp2:~# apt-get install samba=2:4.1.6+dfsg-1ubuntu2.14.04.8 smbclient=2:4.1.6+dfsg-1ubuntu2.14.04.8
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libavahi-client3 libavahi-common-data libavahi-common3 libcups2
libhdb9-heimdal libkdc2-heimdal libldb1 libntdb1 libpython2.7 libsmbclient
libtalloc2 libtdb1 libtevent0 libwbclient0 python-crypto python-dnspython
python-ldb python-ntdb python-samba python-talloc python-tdb samba-common
samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules tdb-tools
Suggested packages:
cups-common python-crypto-dbg python-crypto-doc bind9 bind9utils ldb-tools
smbldap-tools winbind heimdal-clients cifs-utils
The following NEW packages will be installed:
libavahi-client3 libavahi-common-data libavahi-common3 libcups2
libhdb9-heimdal libkdc2-heimdal libldb1 libntdb1 libpython2.7 libsmbclient
libtalloc2 libtdb1 libtevent0 libwbclient0 python-crypto python-dnspython
python-ldb python-ntdb python-samba python-talloc python-tdb samba
samba-common samba-common-bin samba-dsdb-modules samba-libs
samba-vfs-modules smbclient tdb-tools
0 upgraded, 29 newly installed,...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-30 14:34 EDT-------
The GA is just a few days away. From the last hot bug call, Breno would document this issue on the Canonical wiki Power page while we continue to pursue the problem.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-03 17:08 EDT-------
I just documented this failure at https://wiki.ubuntu.com/ppc64el/Recommendations#Samba_on_14.04

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-04 15:52 EDT-------
Hi Canonical.

Can we get this addressed with some higher priority, please? This has been open for several weeks and all the necessary info was really provided from the start..

It looks like the problem is reproducible on a fresh install of 14.04.03 LE and *not* reproducible on the BE of the same release, and both these results have been reproduced on your side as well.

We've already provided detailed log output from both client and server side, and that does not seem to show any problem. If there is more info we can provide please let us know. But really, if its reproducible on you side that shouldn't be necessary.

Thank you!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-10 18:59 EDT-------
Hi Dave, Update from bug call today we discussed on the call today with Michael Hohnbaum that Diane has help prioritize some of the bugs. This one is on Canonical's list but others are taking higher priority since this one is not a regression and has been an issue on multiple releases.
.

[Brian Murray (brian-murray)]

Hello bugproxy, or anyone else affected,

Accepted samba into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-1ubuntu2.14.04.9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-14 09:09 EDT-------
Hi, I failed to install package samba=2:4.1.6+dfsg-1ubuntu2.14.04.9 by following the steps in https://wiki.ubuntu.com/Testing/EnableProposed . Please correct me if I did something wrong. Thanks.

1. Modify file /etc/apt/sources.list and add the following line to it.
"deb http://ports.ubuntu.com/ubuntu-ports trusty-proposed restricted main multiverse universe"

2. Add the following content to file /etc/apt/preferences.d/proposed-updates.
root@onyxlp1:~# cat /etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=trusty-proposed
Pin-Priority: 400

3. Couldn't find package samba=2:4.1.6+dfsg-1ubuntu2.14.04.9.
root@onyxlp1:~# apt-get install samba/trusty-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Release 'trusty-proposed' for 'samba' was not found

root@onyxlp1:~# apt-get install samba=2:4.1.6+dfsg-1ubuntu2.14.04.9
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2:4.1.6+dfsg-1ubuntu2.14.04.9' for 'samba' was not found

[bugproxy (bugproxy)]

------- Comment on attachment From <email address hidden> 2015-07-08 19:24 EDT-------

The checksum is: 9b50c62a9f60659f5a25de9bdd954424

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-15 16:31 EDT-------
> 3. Couldn't find package samba=2:4.1.6+dfsg-1ubuntu2.14.04.9.
The package version is 4.1.6+dfsg-1ubuntu2.14.04.9. You can find the binaries at:

https://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-1ubuntu2.14.04.9/+build/7796735

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-17 07:35 EDT-------
(In reply to comment #51)
> > 3. Couldn't find package samba=2:4.1.6+dfsg-1ubuntu2.14.04.9.
> The package version is 4.1.6+dfsg-1ubuntu2.14.04.9. You can find the
> binaries at:
>
> https://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-1ubuntu2.14.04.9/
> +build/7796735

Hi,
Could you tell me how to install the samba packages manually? I found that the dependency is really complex and many packages are not in the repository(e.g. package samba-common). If possiable, it's better to tell me how to install it from 'trusty-proposed' because it will not involve other issue (e.g. the dependency issue) into this bug. Thanks.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-17 09:53 EDT-------
Miao,

The documentation is quite complete at https://wiki.ubuntu.com/Testing/EnableProposed. I also told you that the package is 4.1.6+dfsg-1ubuntu2.14.04.9 and not 2:4.1.6+dfsg-1ubuntu2.14.04.9. Did you looked for it?

BTW, If you provide the access information about the machine, I will get it installed for you.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-08-18 10:21 EDT-------
With Breno's help, leeklp3 is installed the lastest version of samba & smbclient (2:4.1.6+dfsg-1ubuntu2.14.04.9) and this bug is fixed. Thanks, Breno. :)

root@leeklp3:~# smbclient -L leeklp3 -U root
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (leeklp3 server (Samba, Ubuntu))
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Server Comment
--------- -------
ABAG7 abag7 server (Samba, Ubuntu)
LEEKLP3 leeklp3 server (Samba, Ubuntu)

Workgroup Master
--------- -------
WORKGROUP ABAG7

root@leeklp3:~# apt-cache policy samba smbclient
samba:
Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.9
Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.9
Version table:
*** 2:4.1.6+dfsg-1ubuntu2.14.04.9 0
400 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages
100 /var/lib/dpkg/status
2:4.1.6+dfsg-1ubuntu2.14.04.8 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages
2:4.1.6+dfsg-1ubuntu2.14.04.7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main ppc64el Packages
2:4.1.6+dfsg-1ubuntu2 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
smbclient:
Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.9
Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.9
Version table:
*** 2:4.1.6+dfsg-1ubuntu2.14.04.9 0
400 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages
100 /var/lib/dpkg/status
2:4.1.6+dfsg-1ubuntu2.14.04.8 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages
2:4.1.6+dfsg-1ubuntu2.14.04.7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main ppc64el Packages
2:4.1.6+dfsg-1ubuntu2 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages

[Breno Leitão (breno-leitao)]

Tested already at IBM side. Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package samba - 2:4.1.6+dfsg-1ubuntu2.14.04.9

---------------
samba (2:4.1.6+dfsg-1ubuntu2.14.04.9) trusty; urgency=medium

  * debian/patches/0001-byteorder-do-not-assume-PowerPC-is-big-endian.patch:
    deal with the fact that POWER8 can be little-endian, so don't use special
    instructions to write in little-endian in that case. (LP: #1472584)

 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 12 Aug 2015 21:09:22 -0400

[Chris J Arges (arges)]

The verification of the Stable Release Update for samba has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-09-01 06:09 EDT-------
Today I installed the latest ubuntu 14.04.3 on pole2lp2, this bug is fixed. Thanks.

root@pole2lp2:~# apt-get install samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
attr libavahi-client3 libavahi-common-data libavahi-common3 libcups2
libfile-copy-recursive-perl libhdb9-heimdal libkdc2-heimdal libldb1 libntdb1
libpython2.7 libtalloc2 libtdb1 libtevent0 libwbclient0 python-crypto
python-dnspython python-ldb python-ntdb python-samba python-talloc
python-tdb samba-common samba-common-bin samba-dsdb-modules samba-libs
samba-vfs-modules tdb-tools update-inetd
Suggested packages:
cups-common python-crypto-dbg python-crypto-doc bind9 bind9utils ldb-tools
ntp smbldap-tools winbind heimdal-clients
The following NEW packages will be installed:
attr libavahi-client3 libavahi-common-data libavahi-common3 libcups2
libfile-copy-recursive-perl libhdb9-heimdal libkdc2-heimdal libldb1 libntdb1
libpython2.7 libtalloc2 libtdb1 libtevent0 libwbclient0 python-crypto
python-dnspython python-ldb python-ntdb python-samba python-talloc
python-tdb samba samba-common samba-common-bin samba-dsdb-modules samba-libs
samba-vfs-modules tdb-tools update-inetd
0 upgraded, 30 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,336 kB of archives.
After this operation, 64.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libavahi-common-data ppc64el 0.6.31-4ubuntu1 [21.2 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libavahi-common3 ppc64el 0.6.31-4ubuntu1 [19.7 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libavahi-client3 ppc64el 0.6.31-4ubuntu1 [22.4 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main libcups2 ppc64el 1.7.2-0ubuntu1.6 [173 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main libhdb9-heimdal ppc64el 1.6~git20131207+dfsg-1ubuntu1.1 [55.6 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libtalloc2 ppc64el 2.1.0-1 [21.5 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libtdb1 ppc64el 1.2.12-1 [36.1 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libtevent0 ppc64el 0.9.19-1 [22.2 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libldb1 ppc64el 1:1.1.16-1 [95.1 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports/ trusty/main libntdb1 ppc64el 1.0-2ubuntu1 [41.0 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main libpython2.7 ppc64el 2.7.6-8ubuntu0.2 [927 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main libwbclient0 ppc64el 2:4.1.6+dfsg-1ubuntu2.14.04.9 [26.7 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports/ trusty/main python-ldb ppc64el 1:1.1.16-1 [24.3 kB]
Get:14 http://ports.ubuntu.com/ubuntu-ports/ trusty/main python-talloc ppc64el 2.1.0-1 [7,346 B]
Get:15 http://ports.ubuntu.com/ubuntu-ports/ trusty/main python-dnspython all 1.11.1-1build1 [83.1 kB]
Get:16 http://ports.ubuntu.com/ubuntu-ports/ trusty/main python-ntdb ppc64el 1.0-2ubuntu1 [8,530 B]
Get:17 http://ports.ubuntu.c...