Bug#692196: Debian installer 7.0 beta 3 on sparc Ultra 2 fails
Package: installation-reports Boot method: boot cdrom with net install version of ISO for installer 7, beta 3, sparc Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/sparc/iso-cd/debian-wheezy-DI-b3-sparc-netinst.iso Date: Nov 2, 2012 Machine: Sun Ultra 2 Processor: 2 x 400 Mhz Memory: 1 GB Partitions: 2 internal SCSI disks, left 10 MB free at disk start. RAID 1 partitions for /boot 90 MB / 30 GB /tmp 2 GB non-RAID swap partition with remaining space on each disk. Each file system was set as ext3. Output of lspci -knn (or lspci -nn): non-working, cannot produce Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [E] Install boot loader:[ ] Overall install:[ ] Comments/Problems: System hung during package installs for Desktop Environment, SSH services and basic system package sets. System hang was reproducible at same spot. Watched VT screen of F4 and there was no kernel dump or error. The system became unresponsive. Pressing numlock or caps lock had no effect on LED for same. One first attempt, used apt repo at Dal.ca. On second attempt used apt repo at uwaterloo.ca Computer Science club. No difference. Sorry I don't have the final line of the package that was being downloaded at the time the system stopped responding. I can tell you it did download perhaps 100 to 300 packages before it seized. It gave no error. It behaved as if it was taking a long time to download or whatever, except that when I checked after 30 minutes or so of no progress, I saw the keyboard wasn't responding with the standard numlock/capslock LED test of system health. Control-Alt F1, etc. were also attempted to see what another VT might show. Finally, a Stop-A was done, which should cause the PROM to pop us out to a ok prompt, and it did nothing. This failure was observed twice, once with the progress bar view, and once with the details view from F4 virtual terminal. System seemed healthy prior to install attempt - it had been running Solaris 10 with ZFS mirrored RAID on same disks for a few years and no hardware problems. --Donald Teed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
I installed these packages from sid this morning, onto an otherwise squeeze based system: samba-common2:3.5.6~dfsg-4 samba-common-bin2:3.5.6~dfsg-4 libwbclient02:3.5.6~dfsg-4 winbind 2:3.5.6~dfsg-4 I can see the pam library file is updated: ls -l /lib/security/pam_winbind.so -rw-r--r-- 1 root root 60168 Jan 15 16:04 /lib/security/pam_winbind.so winbind and saslauthd are restarted. Six hours later I check and the number of fd files and links is static at 8 files under each /proc/pid/fd where pid is a process id from saslauthd Based on prior experiences with the bug (leak growth appears within a few minutes), this bug is fixed in these package releases. --Donald
Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Mon, Jan 3, 2011 at 2:37 AM, Christian PERRIER bubu...@debian.orgwrote: Eh, that's really strange, but thanks for the detailed investigation. Could you check whether you still experience the bug with the 3.5.6~dfsg-3 packages? I suppose this is indeed what you're doing right now... I'm afraid the bug reappears with these packages: samba-common2:3.5.6~dfsg-3 samba-common-bin2:3.5.6~dfsg-3~test1 libwbclient02:3.5.6~dfsg-3 winbind 2:3.5.6~dfsg-3 I am seeing a growth in fd links. Also the pipes left open are visible from running: netstat -e | grep winbind It reports dozens of lines like: unix 3 [ ] STREAM CONNECTED 72840600 /var/run/samba/winbindd_privileged/pipe unix 3 [ ] STREAM CONNECTED 72819898 /var/run/samba/winbindd_privileged/pipe unix 3 [ ] STREAM CONNECTED 72811786 /var/run/samba/winbindd_privileged/pipe unix 3 [ ] STREAM CONNECTED 72799966 /var/run/samba/winbindd_privileged/pipe unix 3 [ ] STREAM CONNECTED 72765262 /var/run/samba/winbindd_privileged/pipe When I used all packages ending with ~test1 , I never catch any dangling pipes like this from netstat report. I'm up to 71 open fd links to sockets from 5 saslauthd processes since this morning (relatively slow as students and faculty are not back yet). --Donald
Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Wed, Dec 22, 2010 at 2:05 AM, Christian PERRIER bubu...@debian.orgwrote: Did you have any chance to test the amd64 packages I poointed you to? This fix is a good candidate for squeeze but I would like to have success reports before requesting a freeze exception to the release team. I've tested the test packages: libwbclient0 samba-common samba-common-bin smbclient winbind They have worked well with saslauthd and there is no longer growth in the file descriptors after a couple of days running. Regards, --Donald
Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER bubu...@debian.orgwrote: Hello, On http://people.debian.org/~bubulle/samba-test/http://people.debian.org/%7Ebubulle/samba-test/, you'll soon find packages which you may want to try. I just applied the patch from Samba's Bugzilla and recompiled these package. They're currently being uploaded and should be ready to download in about 10 minutes or so. If they fix this file descriptors leak problem, please report. Hello, This is awesome. I'd like to test this. Can we get the packages built for amd64 where it is required?
Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery r...@debian.org wrote: Looks like a file descriptor leak in pam_winbind. I think saslauthd isn't at fault here. I did a test today... I noticed the number of fds had grown overnight by 20 to 40 per process. I did a restart of winbind and looked at the fds under the saslauthd processes. It didn't change. Both winbind and saslauthd must be restarted as the workaround. Restarting winbind closes only the streams reported as /var/run/samba/winbindd_privileged/pipe . Developers would likely expect this, but I mention it here in case it might help others caught by the issue.
Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Wed, Dec 8, 2010 at 4:23 PM, Dan White dwh...@olp.net wrote: On 08/12/10 15:33 -0400, D G Teed wrote: Here is what one of the directories looked like: ls -l 15950/fd total 0 lrwx-- 1 root root 64 Dec 8 13:52 0 - /dev/null lrwx-- 1 root root 64 Dec 8 13:52 1 - /dev/null lrwx-- 1 root root 64 Dec 7 15:47 10 - socket:[38109596] lrwx-- 1 root root 64 Dec 7 15:47 11 - socket:[38112677] lrwx-- 1 root root 64 Dec 8 13:52 12 - socket:[38129166] lrwx-- 1 root root 64 Dec 8 13:52 13 - socket:[38177341] lrwx-- 1 root root 64 Dec 8 13:52 14 - socket:[38198508] lrwx-- 1 root root 64 Dec 8 13:52 15 - socket:[38256709] lrwx-- 1 root root 64 Dec 8 13:52 16 - socket:[38307912] lrwx-- 1 root root 64 Dec 8 13:52 17 - socket:[38351349] lrwx-- 1 root root 64 Dec 8 13:52 18 - socket:[38378460] Try doing a 'netstat -e' and see if you can match some of those sockets up with a connection, and see if you can determine what it's being used for, and what connection state it's in. I'm hoping you can tie the down to a particular type of connection, say, your pam_winbind attempts. If that's the case, then the problem might be due to a bug in that specific pam module, or could be due to a bug in the way saslauthd uses pam. OK... I've checked one process and here is what the matches look like: /proc/15951/fd# for socket in `ls -l | cut -d' ' -f12 | sed 's/socket:\[// ; s/\]//'` do netstat -e | grep $socket done unix 2 [ ] STREAM CONNECTED 38129397 unix 3 [ ] STREAM CONNECTED 40572411 unix 3 [ ] STREAM CONNECTED 40583464 unix 3 [ ] STREAM CONNECTED 40602800 unix 3 [ ] STREAM CONNECTED 40649673 unix 3 [ ] STREAM CONNECTED 40667667 unix 2 [ ] STREAM CONNECTED 38134508 unix 2 [ ] STREAM CONNECTED 38137874 unix 2 [ ] STREAM CONNECTED 38144166 unix 2 [ ] STREAM CONNECTED 38145796 unix 2 [ ] STREAM CONNECTED 38164643 unix 2 [ ] STREAM CONNECTED 38182983 unix 2 [ ] STREAM CONNECTED 38198634 unix 2 [ ] STREAM CONNECTED 38212091 unix 2 [ ] STREAM CONNECTED 38284314 unix 2 [ ] STREAM CONNECTED 38310069 unix 2 [ ] STREAM CONNECTED 38337364 unix 2 [ ] STREAM CONNECTED 38378155 unix 2 [ ] STREAM CONNECTED 38401805 unix 2 [ ] STREAM CONNECTED 38411640 unix 2 [ ] STREAM CONNECTED 38427190 unix 2 [ ] STREAM CONNECTED 38437192 unix 2 [ ] STREAM CONNECTED 38494440 unix 2 [ ] STREAM CONNECTED 38522319 unix 2 [ ] STREAM CONNECTED 38548115 unix 2 [ ] DGRAM38091087 unix 2 [ ] STREAM CONNECTED 38554551 unix 2 [ ] STREAM CONNECTED 38561940 unix 2 [ ] STREAM CONNECTED 38581911 unix 2 [ ] STREAM CONNECTED 38596779 unix 2 [ ] STREAM CONNECTED 38618951 unix 2 [ ] STREAM CONNECTED 38751702 unix 2 [ ] STREAM CONNECTED 38790002 unix 2 [ ] STREAM CONNECTED 38796236 unix 2 [ ] STREAM CONNECTED 38840751 unix 2 [ ] STREAM CONNECTED 38867792 unix 2 [ ] STREAM CONNECTED 38892274 unix 2 [ ] STREAM CONNECTED 38934651 unix 2 [ ] STREAM CONNECTED 38951610 unix 2 [ ] STREAM CONNECTED 38978113 unix 2 [ ] STREAM CONNECTED 38994165 unix 2 [ ] STREAM CONNECTED 39011149 unix 2 [ ] STREAM CONNECTED 39018267 unix 2 [ ] STREAM CONNECTED 39028043 unix 2 [ ] STREAM CONNECTED 39031157 unix 2 [ ] STREAM CONNECTED 39075371 unix 2 [ ] STREAM CONNECTED 39135341 unix 2 [ ] STREAM CONNECTED 39386630 unix 2 [ ] STREAM CONNECTED 39513199 unix 2 [ ] STREAM CONNECTED 39530596 unix 2 [ ] STREAM CONNECTED 39543718 unix 2 [ ] STREAM CONNECTED 39550671 unix 2 [ ] STREAM CONNECTED 39597986 unix 2 [ ] STREAM CONNECTED 39691351 unix 2 [ ] STREAM CONNECTED 39693413 unix 2 [ ] STREAM CONNECTED 39715649 unix 2 [ ] STREAM CONNECTED 39721749 unix 2 [ ] STREAM CONNECTED 39763508 unix 2 [ ] STREAM CONNECTED 39796730 unix 3
Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery r...@debian.org wrote: D G Teed donald.t...@gmail.com writes: I also count 200 connections like this: unix 3 [ ] STREAM CONNECTED 39854981 /var/run/samba/winbindd_privileged/pipe Most users are simply using port 25 and would not be authenticating, so I know these numbers cannot be current connections. Looks like a file descriptor leak in pam_winbind. I think saslauthd isn't at fault here. Is there a way the bug report can shuffle along to becoming a winbind bug report, or should I re-report it, referring to this bug report? --Donald
Bug#606350: sasl2-bin: Too many open files error with PAM - recovery with saslauthd restart
On Wed, Dec 8, 2010 at 10:02 PM, Russ Allbery r...@debian.org wrote: I'll reassign it. I wanted to see if anyone disagreed with me first. :) -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/http://www.eyrie.org/%7Eeagle/ This might be the same as the samba bug reported upstream against Debian 5: https://bugzilla.samba.org/show_bug.cgi?id=7265%20https://bugzilla.samba.org/show_bug.cgi?id=7265 That is showing a bug against samba 3.4, however it is status NEW, from March this year. A patch is mentioned. I don't see why there would be a delay to release it. This bug would effect apache, cyrus email, and many SMTP services using authentication, so I'd think it should be a priority to fix. --Donald
Bug#394821: Proprietary driver from Matrox resolved the problem
A user at DebianHelp.org suggested I try the Matrox driver from Matrox. Earlier I did a compile from Debian sources at sarge1 release level and it did not resolve the problem. I worked in vesa mode for a couple of days before installing the Matrox proprietary driver, which resolves the issue for me. However I believe mga driver was working without this driver from Matrox prior to the update. See this thread for some potential leads on what nm tracing revealed: http://www.debianhelp.org/node/1603#comment-1225 --Donald Teed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394821: mga_drv unresolved symbols after 4.3.0.dfsg.1-14sarge2 upgrade
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-14sarge2
I have a G400 that was working fine in the most previous
release (sarge1?) of xfree86 group of packages in Debian 3.1 stable.
On the first reboot following the upgrade to 4.3.0.dfsg.1-14sarge2
of the series of related xfree86 packages, X refuses to
run, with errors like so:
XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge2 20061002194300
[EMAIL PROTECTED])
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.18-1-686 i686 [ELF] Build Date: 02 October
2006
Module Loader present
OS Kernel: Linux version 2.6.16.18 ([EMAIL PROTECTED]) (gcc
version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP PREEMPT Sun Oct 22 12:47:58
ADT 2006 Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Sun Oct 22 23:52:30 2006
(==) Using config file: /etc/X11/XF86Config-4
Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o:
No symbols found
Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o:
No symbols found
Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o: No
symbols found
Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_vertex.o: No
symbols found
Skipping /usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o: No
symbols found
(WW) MGA(0): Failed to set up write-combining range
(0xf800,0x200)
Required symbol MGAValidateMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGASetMode from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGACloseLibrary from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol HALSetDisplayStart from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol HALSetDisplayStart from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAGetHardwareInfo from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAOpenLibrary from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Required symbol MGAGetBOARDHANDLESize from module
/usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
...and a few more lines like these before Fatal server error.
Everything was fine with the same XF86Config file
previously. If I switch to vesa, X starts OK.
However I need dual monitors so mga is a must.
It appears that Debian's Xfree86 sources are unique,
so compiling a solution as per http://dri.freedesktop.org/wiki/Building
doesn't seem to be an option within Debian stable.
I tried downgrading to sarge1, but it has not helped:
for pack in `COLUMNS=200 dpkg -l | grep x | grep 4.3.0.dfsg.1-14sarge2 | awk
'{print $2}'`; do apt-get -y install --reinstall $pack=4.3.0.dfsg.1-14sarge1;
done
Any more information needed, please ask me...
--Donald Teed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
