[Bug 1298093] Re: iscsi_trgt: module verification failed
Just for fun, I un-installed all the iSCSI software: `sudo apt-get purge iscsitarget iscsitarget-dkms open-iscsi` Rebooted. Machine takes about 15 seconds to go from my entering my encryption key/passphrase, until I see the login dialog on the Lubuntu GUI screen. So, my 120+ second boot with iSCSI software, is iSCSI-related. I have uploaded the correcponding .PNG file from "bootchart" package for this 15 second boot. ** Attachment added: "bootchart corresponding to 15 second boot (no iSCSI s/w installed)" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+attachment/4047408/+files/bee005-trusty-20140327-3.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1298093] Re: iscsi_trgt: module verification failed
I installed "bootchart", which pulls in pybootchartgui and python-support, rebooted, and am uploading the .png file found in /var/log/bootchart. (let me know if you want the .tgz file) Interesting picture of the boot processes. Looks like there is long 120 second idle time, for something, but I'm new to reading this bootchart image. ** Attachment added: "Picture of all the boot processes" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+attachment/4045795/+files/bee005-trusty-20140326-1.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1298093] [NEW] iscsi_trgt: module verification failed
Public bug reported: I am on 64-bit Lubuntu Trusty Tahr (development branch) (64-bit Lubuntu nighlty build of 2014-03-14 with updates) (this machine is set up with RAID-1, LVM, Encryption, iSCSI Target and iSCSI client, in case that matters.) Versions of iSCSI: ii iscsitarget 1.4.20.3+svn499-0ubuntu1 ii iscsitarget-dkms 1.4.20.3+svn499-0ubuntu1 I have successfully set up an iSCSI target (and client). But if I peek inside the /var/log/syslog, I see this snippet: Mar 26 17:56:29 bee005 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="710" x-info="http://www.rsyslog.com";] start ... Mar 26 17:57:03 bee005 ntpd_intres[1148]: parent died before we finished, exiting [89 second gap] Mar 26 17:58:32 bee005 kernel: [ 191.597648] iscsi_trgt: module verification failed: signature and/or required key missing - tainting kernel Mar 26 17:58:32 bee005 kernel: [ 191.598233] iSCSI Enterprise Target Software - version trunk Mar 26 17:58:32 bee005 kernel: [ 191.598297] iscsi_trgt: Registered io type fileio Mar 26 17:58:32 bee005 kernel: [ 191.598299] iscsi_trgt: Registered io type blockio Mar 26 17:58:32 bee005 kernel: [ 191.598301] iscsi_trgt: Registered io type nullio ... The machine is taking a noticeable a mount of time to boot up. (2+ minutes). This snippet in syslog, makes me want to say that the iscsi_targt module in the kernel has delayed the booting up of the machine by 90-120 seconds due to the 89 second gap in the syslog file, and that it's been 2 minutes 3 seconds since beginning of the syslog. Did some signature/key not get packaged in the latest and greatest packages of iscsitarget and iscsitarget-dkms? (and the kernel waits (or retires) for 120 seconds before continuing on?) ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1298093 Title: iscsi_trgt: module verification failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1298093/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1291641] Re: iscsitarget-dkms 1.4.20.3+svn496-1ubuntu1: iscsitarget kernel module failed to build
I had logged bug 1293108, a duplicate of this bug, but I will log my comment here as well. Short Story: The bug fix mentioned in comment #5 solved my compile error during the installing of iscsitarget-dkms and iscsitarget. Longer Story: Today, 2014-03-26, I updated my 64-bit Lubuntu Trusty Tahr with all packages, specifically, iscsitarget-dkms, and iscsitarget version 1.4.20.3+svn499-0ubuntu1. I then re-installed them via: sudo apt-get install --reinstall iscsitarget-dkms sudo apt-get install --reinstall iscsitarget I was then able to proceed with setting up an iSCSI target on machine #1, and set up an iSCSI client on machine #2 (and machine #1). I was then able to backup files from machine #2, the iSCSI client, to machine #1, the iSCSI target, via the iSCSI protocol. I also was able to view and access this iSCSI target on machine #1 from machine #1. (yes the same machine) Note to self: Since machine #1, now has a firewall (UFW) set up, I had to allow tcp port 3260 so that machine #2 could make a connection. Note to self: Machine #1 takes an extra 90 seconds or so to boot up. Not sure who's causing this: RAID, LVM, Encryption, or the new iSCSI target and iSCSI client that I just got configured. I do see this 90 second gap in /var/log/syslog: ... Mar 26 17:24:05 bee005 ntpd_intres[1217]: parent died before we finished, exiting [89 second gap] Mar 26 17:25:34 bee005 kernel: [ 142.820882] iscsi_trgt: module verification failed: signature and/or required key missing - tainting kernel Mar 26 17:25:34 bee005 kernel: [ 142.827819] iSCSI Enterprise Target Software - version trunk Mar 26 17:25:34 bee005 kernel: [ 142.827883] iscsi_trgt: Registered io type fileio ... Thank you for fixing the compile problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1291641 Title: iscsitarget-dkms 1.4.20.3+svn496-1ubuntu1: iscsitarget kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1291641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1293108] [NEW] Setting up iscsitarget-dkms fails with error: ‘struct ipv6_pinfo’ has no member named ‘daddr’
Public bug reported:
I am on 64-bit Lubuntu Trusty Tahr (development branch)
(64-bit Lubuntu nighlty build of 2014-03-14 with updates)
(this machine is set up with RAID-1, LVM and Encryption, in
case that matters.)
and am trying to set up an iSCSI target (and client).
2 years ago, I successfully did this on PrecisePangolin following these
instructions:
http://www.howtoforge.com/using-iscsi-on-ubuntu-10.04-initiator-and-target
Today, on TrustyTahr, I can't get past the installing of the
iscsitarget-dkms package.
I'm getting a simple(?) compile error.
iscsitarget-dkms package is at version 1.4.20.3+svn496-1ubuntu1
(is there an alternative iSCSI target package that Ubuntu uses/blesses?)
-- begin of package installation
--
$ sudo apt-get install --reinstall iscsitarget-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 25 not upgraded.
1 not fully installed or removed.
Need to get 0 B/79.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 117830 files and directories currently installed.)
Preparing to unpack .../iscsitarget-dkms_1.4.20.3+svn496-1ubuntu1_all.deb ...
--
Deleting module version: 1.4.20.3+svn496
completely from the DKMS tree.
--
Done.
Unpacking iscsitarget-dkms (1.4.20.3+svn496-1ubuntu1) over
(1.4.20.3+svn496-1ubuntu1) ...
Setting up iscsitarget (1.4.20.3+svn496-1ubuntu1) ...
* Starting iSCSI enterprise target service
modprobe: FATAL: Module iscsi_trgt not found. [fail]
invoke-rc.d: initscript iscsitarget, action "start" failed.
dpkg: error processing package iscsitarget (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up iscsitarget-dkms (1.4.20.3+svn496-1ubuntu1) ...
Creating symlink /var/lib/dkms/iscsitarget/1.4.20.3+svn496/source ->
/usr/src/iscsitarget-1.4.20.3+svn496
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area
make KERNELRELEASE=3.13.0-17-generic -C /lib/modules/3.13.0-17-generic/build
M=/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build..(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.13.0-17-generic (x86_64)
Consult /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log for more
information.
Errors were encountered while processing:
iscsitarget
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- end of package installation
--
-- Contents of
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log ---
$ cat /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/make.log
DKMS make.log for iscsitarget-1.4.20.3+svn496 for kernel 3.13.0-17-generic
(x86_64)
Sun Mar 16 08:55:39 EDT 2014
make: Entering directory `/usr/src/linux-headers-3.13.0-17-generic'
LD /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/built-in.o
LD /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/built-in.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/tio.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/iscsi.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.o
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.c: In function
‘do_recv’:
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/nthread.c:147:1:
warning: the frame size of 1096 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
}
^
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/wthread.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/config.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/digest.o
CC [M] /var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.o
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.c: In function
‘conn_info_show’:
/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.c:51:19: error:
‘struct ipv6_pinfo’ has no member named ‘daddr’
&inet6_sk(sk)->daddr);
^
make[2]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel/conn.o]
Error 1
make[1]: *** [/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build/kernel] Error 2
make: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.3+svn496/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.13.0-17-generic'
-- end of make.log --
begin of snippet of conn.c
void conn_info_show(struct seq_file *seq, struct iscsi_session *session)
{
struct iscsi_conn *conn;
struct sock *sk;
char buf[64];
[Bug 678420] Re: smbd sometimes does not start on startup
Happens intermittently on our Ubuntu 10.04.3 LTS 64-bit systems. I just checked 2 machines where smbd was not started after a reboot. I notice the same "smbd respawning too fast, stopped" in /var/log/syslog. This message is appearing up to12 seconds prior to Network Manager acquiring an IP address, etc. So to me it looks like samba is failing cause the network is not established yet. Should smbd go to sleep and try again in a few minutes? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/678420 Title: smbd sometimes does not start on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/678420/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
similar to the stack trace in comment #6 above, winbind crashed today (on machine bee64) with this stack trace as gotten from gdb against the core file left behind: (gdb) bt #0 0x7f70d81fda75 in raise () from /lib/libc.so.6 #1 0x7f70d82015c0 in abort () from /lib/libc.so.6 #2 0x7f70da6a3460 in dump_core () at lib/fault.c:337 #3 0x7f70da6b428e in smb_panic (why=) at lib/util.c:1496 #4 0x7f70da6a385d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 get_cache (domain=0x0) at winbindd/winbindd_cache.c:139 #8 0x7f70da616888 in resolve_username_to_alias (mem_ctx=, domain=0x0, name=0x7f70db4aacb0 "gautam.naik", alias=0x7fffab4a4110) at winbindd/winbindd_cache.c:1019 #9 0x7f70da609016 in normalize_name_map (mem_ctx=0x7f70db496180, domain=0x0, name=0x7f70db4aacb0 "gautam.naik", normalized=0x7fffab4a4110) at winbindd/winbindd_util.c:1442 #10 0x7f70da6076ef in fill_grent_mem_domusers (domain=0x7f70db4b0d40, state=, group_sid=0x7f70db46ced0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffab4a44c8) at winbindd/winbindd_group.c:330 #11 fill_grent_mem (domain=0x7f70db4b0d40, state=, group_sid=0x7f70db46ced0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffab4a44c8) at winbindd/winbindd_group.c:578 #12 0x7f70da607a9f in getgrsid_sid2gid_recv (private_data=0x7f70db46ceb0, success=, gid=563) at winbindd/winbindd_group.c:866 #13 0x7f70da600ba0 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1115 #14 main (argc=, argv=, envp=) at winbindd/winbindd.c:1440 I am running the latest winbind of 2:3.4.7~dfsg-1ubuntu3.6 So the problem still persists after upgrading to 2:3.4.7~dfsg- 1ubuntu3.6. What other information do you want me to provide? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
Everything still working fine on all 80 machines since 2011-04-27. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
I pushed out the patch to 24 more machines ( 29 total) on Monday 2011-04-25 6:30 PM. All is fine since then. Pushing out the patch to the rest of the 80 machines, right now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
It's been 6 days, and the 5 machines that I have this patch on now, are doing fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736757] Re: [SRU] PANIC (pid 18442): internal error in winbindd
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash, as I call it, on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. Will still be monitoring this, and may even install it on a few more machines, today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/736757 Title: [SRU] PANIC (pid 18442): internal error in winbindd -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 753330] Re: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).
*** This bug is a duplicate of bug 736757 *** https://bugs.launchpad.net/bugs/736757 It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. Will still be monitoring this, and may even install it on a few more machines, today. Any date on when this proposed version will be generally available? Thank you. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/753330 Title: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package. This particular "rpc_pipe_np_smb_conn" crash, as I call it, is covered here https://bugs.launchpad.net/ubuntu/+source/samba/+bug/753330. So once this ~dfsg-1ubuntu3.6 package package is made generally available and I install it on my 80 machines, then I will go back to the original problem that I initiated here and try to get more information for you all. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
Instead of downloading the .deb files, i did the more appropriate, SynapticPackageManager --> repositories --> Updates and Click "Pre-released updated (lucid-proposed)" check box which when installing winbind, it pulled in the proposed versions of libwbclient0, samba, samba-common, and smbclient. I did this on 2 machines (bee02 and bee75). Will wait for winbind to crash. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
1.) Per https://launchpad.net/ubuntu/lucid/+package/winbind there are several "proposed" versions to choose from: winbind 2:3.4.7~dfsg-1ubuntu3.5 in amd64 (Proposed) winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) i will choose the newer "3.6" winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) since the version that is currently installed is: 2:3.4.7~dfsg-1ubuntu3.5 2.) I will also purge the samba-dbg package in case that is conflicting. 3.) I will choose 2 machines to install the winbind 2:3.4.7~dfsg-1ubuntu3.6 in amd64 (Proposed) and then wait and see what happens... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 753330] Re: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).
FYI: I have reported this exact same backtrace (at least the last 3 calls) here https://bugs.launchpad.net/ubuntu/+source/samba/+bug/667269?comments=all for us, winbind is dead, black screen on Console, no longer can ssh into machine using Active Directory credentials. I must kill any winbind processes running, then restart it. It's happening more frequently, (hourly) on 25% or more of our 80 64-bit LucidLinux machines, integrated with ActiveDirectory(winbind). I am desperate to get this bug fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/753330 Title: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
Please, can someone raise the importance of this bug from Medium to whatever the highest level is. This winbind crashing problem is critical for us and is occurring with more frequency on more machines, daily if not hourly. It's affecting the confidence level of all our developers and QA. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
I just did a backtrace on another machine(bee37), of another core file, the back trace takes a different path, but the final 3 calls are the same as my previous post and the same last e calls as Mau's back trace: rpc_pipe_np_smb_conn rpccli_set_timeout winbindd_lookup_sids ... Unfortunately these 3 back traces that have the same last 3 calls, are all different than my original backtrace I posted on 12/27/2010, but I'll take any winbind fix for any problem at this point. I had 22 of 80 machines experience a winbind problem yesterday, Monday 2011-04-18. I will throw one red herring of an idea out there. Is it possible that the cause of this is if a user is in a Windows group per his poilicy file but that group isn't active anymore? winbind can work for days at a time, so this problem is not deterministic. There's some other factor that is causing this to happen, and I can't figure it out. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
I thought I would just add another backtrace from a core file that occurred today on a machine where winbind crashed several times: #0 0x7f089b9b6a75 in raise () from /lib/libc.so.6 #1 0x7f089b9ba5c0 in abort () from /lib/libc.so.6 #2 0x7f089de5c450 in dump_core () at lib/fault.c:337 #3 0x7f089de6d27e in smb_panic (why=) at lib/util.c:1496 #4 0x7f089de5c84d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 rpc_pipe_np_smb_conn (p=0x0) at rpc_client/rpc_transport_np.c:402 #8 0x7f089df48048 in rpccli_set_timeout (rpc_cli=0x0, timeout=35000) at rpc_client/cli_pipe.c:2956 #9 0x7f089dde27a1 in winbindd_lookup_sids (mem_ctx=0x7f089e746290, domain=, num_sids=, sids=, domains=0x7fffa6901bd0, names=0x7fffa6901be0, types=0x7fffa6901bd8) at winbindd/winbindd_rpc.c:1221 #10 0x7f089dde5092 in lookup_groupmem (domain=0x7f089e7a4a00, mem_ctx=0x7f089e745eb0, group_sid=0x7f089e79ca60, num_names=0x7fffa6901f1c, sid_mem=, names=, name_types=0x7fffa6901ee8) at winbindd/winbindd_ads.c:1124 #11 0x7f089ddcc503 in lookup_groupmem (domain=, mem_ctx=, group_sid=, num_names=0x7fffa6901f1c, sid_mem=0x7fffa6901ed8, names=0x7fffa6901ee0, name_types=0x7fffa6901ee8) at winbindd/winbindd_cache.c:2211 #12 0x7f089ddbf5e7 in expand_groups (domain=0x7f089e7a4a00, state=, group_sid=, group_name_type=SID_NAME_DOM_GRP, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffa69022a8) at winbindd/winbindd_group.c:468 #13 fill_grent_mem (domain=0x7f089e7a4a00, state=, group_sid=, group_name_type=SID_NAME_DOM_GRP, num_gr_mem=, gr_mem=, gr_mem_len=0x7fffa69022a8) at winbindd/winbindd_group.c:604 #14 0x7f089ddc0a9f in getgrsid_sid2gid_recv (private_data=0x7f089e767140, success=, gid=4549) at winbindd/winbindd_group.c:866 #15 0x7f089ddb9ba0 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1115 #16 main (argc=, argv=, envp=) at winbindd/winbindd.c:1440 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
Can we get some traction on this bug? This problem still consistently occurs on at least 5 machines per week out of our 80 machines. Or throw me some ideas to either narrow down the problem further or work-arounds. I still feel that whatever winbind does to keep itself busy while being idle is causing it to go into this unresponsive state. Is it pinging our Active Directory server every X minutes and amassing a queue of awaiting responses back? Is it pinging DNS servers every X minutes, etc. It must be doing something, other than just merely authenticating a user when they log in. I think these background tasks is the core of the problem. I also can't believe no one is reporting this, unless we are the only establishment using ActiveDirectory on Ubuntu. Help, please. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
I didn't specifically reproduce the problem, but the problem has happened, on its own. There also happens to be a recent core file around. $ sudo find /var/log -type f | grep core | xargs sudo ls -al -rw--- 1 root root 1564672 2010-12-27 04:12 /var/log/samba/cores/winbindd/core I then run `gdb winbindd`, "core core", and then "bt" for a backtrace: Program terminated with signal 6, Aborted. #0 0x7f5862af1a75 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f5862af1a75 in raise () from /lib/libc.so.6 #1 0x7f5862af55c0 in abort () from /lib/libc.so.6 #2 0x7f5864f97430 in dump_core () at lib/fault.c:337 #3 0x7f5864fa825e in smb_panic (why=) at lib/util.c:1496 #4 0x7f5864f9782d in fault_report (sig=11) at lib/fault.c:52 #5 sig_fault (sig=11) at lib/fault.c:75 #6 #7 get_cache (domain=0x0) at winbindd/winbindd_cache.c:139 #8 0x7f5864f0a888 in resolve_username_to_alias (mem_ctx=, domain=0x0, name=0x7f5866dadf70 "puneet.arora", alias=0x7fff22b0bb00) at winbindd/winbindd_cache.c:1019 #9 0x7f5864efd016 in normalize_name_map (mem_ctx=0x7f5866d56530, domain=0x0, name=0x7f5866dadf70 "puneet.arora", normalized=0x7fff22b0bb00) at winbindd/winbindd_util.c:1442 #10 0x7f5864efb6ef in fill_grent_mem_domusers (domain=0x7f5866db2d60, state=, group_sid=0x7f5866d6eed0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fff22b0beb8) at winbindd/winbindd_group.c:330 #11 fill_grent_mem (domain=0x7f5866db2d60, state=, group_sid=0x7f5866d6eed0, group_name_type=, num_gr_mem=, gr_mem=, gr_mem_len=0x7fff22b0beb8) at winbindd/winbindd_group.c:578 #12 0x7f5864efba9f in getgrsid_sid2gid_recv (private_data=0x7f5866d6eeb0, success=, gid=563) at winbindd/winbindd_group.c:866 #13 0x7f5864ef4b98 in process_loop (argc=, argv=, envp=) at winbindd/winbindd.c:1109 #14 main (argc=, argv=, envp=) at winbindd/winbindd.c:1434 Is this helpful? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
I have just installed the samba-dbg package. When this problem happens again, what do I need to run, look at, provide back to this forum, etc? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/667269 Title: winbind crashes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
from my original post, I want to strike that there is a core file. Since then I have looked for a core file when the problem happens, and it is not there. So don't waste time debugging the attached core file. In regards to errr's note above, maybe why it is quick for him/her to fix, is that they are not using ActiveDirectory/LDAP and I am, and there is some time out period, and # of retries that "something" tries to do, hence why it takes about 2 1/2 minutes (5 tries of 30 second wait times each, maybe?) for me to get any command to complete. Restarting winbindd, does not always work (possibly never works). Well it may seem that it works, but there are still old winbindd processes still hanging around. Hence why my protocol is to `kill -9` the windbindd processes first. Then, restarting winbind via: `sudo /etc/init.d/winbind restart` Same as errr's comment above, that there is nothing in the log.winbindd file, except: [2010/11/03 16:25:25, 0] winbindd/winbindd.c:1252(main) winbindd version 3.4.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2010/11/03 16:25:25, 1] lib/tdb_validate.c:446(tdb_validate_and_backup) tdb '/var/cache/samba/winbindd_cache.tdb' is valid [2010/11/03 16:25:25, 1] lib/tdb_validate.c:456(tdb_validate_and_backup) Created backup '/var/cache/samba/winbindd_cache.tdb.bak' of tdb '/var/cache/samba/winbindd_cache.tdb' -- winbind crashes https://bugs.launchpad.net/bugs/667269 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] Re: winbind crashes
** Attachment added: "Core file found under: /var/log/samba/cores/winbindd/core" https://bugs.launchpad.net/bugs/667269/+attachment/1713033/+files/core -- winbind crashes https://bugs.launchpad.net/bugs/667269 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667269] [NEW] winbind crashes
Public bug reported: Binary package hint: samba Occasionally on various Ubuntu 64-bit LucidLynx systems (10.04.1), winbind goes into a state such that logging in fails. (we use ActiveDirectory for logging in. We do not use the Likewise-open product.) Although, it appears that there are 1 or more winbindd processes running, they are all dead/not_working/hung, etc. The only recourse to fix the problem, is that I log in with a local account that has sudo privilege, find and kill all the winbindd processes, and restart, nmbd, winbindd and samba. (not sure if I need to restart nmbd and samba, but I do it anyways.) This problem seems to happen more often on systems that are shared with other users. Some of those other users are connected from across the Wan via ssh. The problem seems to occur more often over the weekend. Meaning, Monday morning, is when we discover the machines are un-loginable with Active Directory account names. This problem does not happen with all 80+ machines. All machines are built out the same, and are on approximately the same type of hardware. This problem has existed since the onset of LucidLynx from what I can remember. The problem occurs frequently enough, that I had to set up a self-help web page for users with the problem. From there I have a script that will log into the machine in question, with a local sudo privileged account, kills all the winbind processes and restarts nmbd, winbindd and samba. Even with using the local account, each command takes about 2 1/2 minutes to complete. It takes about 12 minutes to accomplish the "fixing" of the machine due to the # of commands that need to be run. I am assuming the core file under /var/log/samba/cores/winbindd/core will be relevant to the problem I am having. $ lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 $ apt-cache policy winbind winbind: Installed: 2:3.4.7~dfsg-1ubuntu3.2 Candidate: 2:3.4.7~dfsg-1ubuntu3.2 Version table: *** 2:3.4.7~dfsg-1ubuntu3.2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2:3.4.7~dfsg-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- winbind crashes https://bugs.launchpad.net/bugs/667269 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
I have interleaved the information, removed the timestamps and substituted DOMAIN\first.last for the actual: $ passwd Changing password for DOMAIN\first.last passwd[30381]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[30381]: pam_winbind(passwd:chauthtok): getting password (0x0028) (current) NT password: passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access passwd[30381]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[30381]: pam_winbind(passwd:chauthtok): getting password (0x) Enter new NT password: Retype new NT password: passwd: password updated successfully passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' OK passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' password changed passwd[30381]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access gnome-keyring-daemon[30390]: gp11_module_get_slots: assertion `data->funcs' failed gnome-keyring-daemon[30390]: lookup_login_session: assertion `slot' failed gnome-keyring-daemon[30390]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed gnome-keyring-daemon[30390]: create_credential: assertion `GP11_IS_SESSION (session)' failed gnome-keyring-daemon[30390]: egg_error_message: assertion `error' failed gnome-keyring-daemon[30390]: couldn't create new login credential: (unknown) passwd[30381]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. $ and the password has changed via a test of `ssh`-ing into any Linux machine. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
FYI: I can get `passwd` to work if I change one line in common-password >From the winbind default-configured line of: password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass To: password [success=1 default=ignore] pam_winbind.so try_first_pass So looks like just the "use_authtok" parameter is misbehaving. (not sure what that really means or with whom the problem lies) -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
FYI: I can get `passwd` to work if I change the line in common-password From: password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass To: password sufficient pam_winbind.so I'm not sure if I'm creating other problems with the above edit, since I'm not PAM savvy. I have to wait one day to change my password again, but I will try a more minimal change of: password [success=1 default=ignore] pam_winbind.so try_first_pass Meaning, I will just remove the "use_authtok" to see if that is the problem. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
Is this what you need? $ cd /etc/pam.d $ cat common-auth common-session-noninteractive common-session common-password common-account | grep -v "^#" auth[success=2 default=ignore] pam_unix.so nullok_secure auth[success=1 default=ignore] pam_winbind.so krb5_auth krb5_ccache_type=FILE cached_login try_first_pass authrequisite pam_deny.so authrequiredpam_permit.so session [default=1] pam_permit.so session requisite pam_deny.so session requiredpam_permit.so session requiredpam_unix.so session optionalpam_winbind.so session [default=1] pam_permit.so session requisite pam_deny.so session requiredpam_permit.so sessionrequiredpam_mkhomedir.so skel=/etc/skel/ umask=0027 session requiredpam_unix.so session optionalpam_winbind.so session optionalpam_ck_connector.so nox11 password[success=2 default=ignore] pam_unix.so obscure sha512 password[success=1 default=ignore] pam_winbind.so use_authtok try_first_pass passwordrequisite pam_deny.so passwordrequiredpam_permit.so passwordoptionalpam_gnome_keyring.so account [success=2 new_authtok_reqd=done default=ignore]pam_unix.so account [success=1 new_authtok_reqd=done default=ignore]pam_winbind.so account requisite pam_deny.so account requiredpam_permit.so Here is the smb.conf, with comments removed and substituted in , , where appropriate. [global] workgroup = security = ADS password server = ..com, ..com realm = .COM server string = %h server (Samba, Ubuntu) dns proxy = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes map to guest = bad user idmap backend = idmap_rid:=50-99 idmap uid = 50-99 idmap gid = 50-99 allow trusted domains = no winbind offline logon = true template shell = /bin/bash template homedir = /home/%D/%U winbind normalize names = yes winbind use default domain = yes usershare allow guests = yes -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
i am not using likewise-open on Lucid cause likewise-open no longer supports setting up Samba shares with ActiveDirectory integration. Meaning from a Windows machine, I cannot access \\linuxmachinename\sharename and this is important to our Windows/Linux workplace. (And I no longer see the advantage or point to using likewise-open. It only adds another mysterious layer to the whole samba/winbind realm.) -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
Correct, `passwd` works with likewise-open on hardy, and fails with winbind on lucid. I do not know what the outcome of `passwd` is on hardy without likewise-open, nor the outcome of `passwd` on lucid with likewise-open. I will ask this on the Lucid forum at http://ubuntuforums.org/showthread.php?t=1459309 -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] Re: passwd : gives "Authentication token manipulation error"
Yes it works on HardyHeron. I used likewise-open to faciitate the ActiveDirectory integration on HardyHeron, rather than just the native samba/winbind integration on LucidLynx. But that may have nothing to do with it, but is worthy of mentioning. -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570944] [NEW] passwd : gives "Authentication token manipulation error"
Public bug reported: Binary package hint: samba `passwd` for ActiveDirectory account gives "Authentication token manipulation error" I have latest and greatest of LucidLynx updates. winbind2:3.4.7~dfsg-1ubuntu3 samba 2:3.4.7~dfsg-1ubuntu3 I have ActiveDirectory integration with Samba/Winbind. (not Likewise-Open) Logging into Console window or `ssh`-ing into machine works fine using DOMAIN\first.last account names. Trying to change password with the `passwd` program: $ passwd Changing password for DOMAIN\first.last (current) NT password: passwd: Authentication token manipulation error passwd: password unchanged $ In the /var/log/auth.log file I get this output in conjunction with the above passwd attempt: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[16109]: pam_winbind(passwd:chauthtok): getting password (0x002a) passwd[16109]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' granted access passwd[16109]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in /etc/passwd passwd[16109]: pam_winbind(passwd:chauthtok): getting password (0x0012) I don't see anything particularly wrong with that output, other than it seems to stop prematurely. This is my default-created /etc/pam.d/common-password file: password [success=2 default=ignore] pam_unix.so obscure sha512 password [success=1 default=ignore] pam_winbind.so use_authtok try_first_pass password requisite pam_deny.so password required pam_permit.so password optional pam_gnome_keyring.so I've Googled for "Authentication token manipulation error", but most cases involve local Linux accounts or other uninteresting problems. I don't think any entries in smb.conf have an effect on passwd, but here's a snippet of entries with the word "pass" or "encrypt" in them: password server = machine.domain.com encrypt passwords = true passdb backend = tdbsam unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes encrypt passwords = true I can successfully change password, using `passwd` for a local Linux account. $ passwd Changing password for localAccount. (current) UNIX password: Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully $ ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- passwd : gives "Authentication token manipulation error" https://bugs.launchpad.net/bugs/570944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
