Bug#815125: Boot failure with Debian linux 4.4.2 package
From: Ben Hutchings [b...@decadent.org.uk] > > This test version is now available at > https://people.debian.org/~benh/packages/unstable/ > > Please report back whether this does or doesn't fix the problem for > you. Hi Ben. The test kernel boots up okay for me: jim@perlap1308:~$ uname -a Linux perlap1308 4.4.0-1-amd64 #1 SMP Debian 4.4.2-3~a.test (2016-02-20) x86_64 GNU/Linux Thanks.
Bug#792653: Probably related to CapabilityBoundingSet
Alberto Gonzalez wrote: > Hi, Hi Alberto. I only just noticed now that you updated this case. > Did you run "systemctl daemon-reload" after changing the .service file? Yes, as per my original bug report I tried the following: Each time I edited the file, I tried the following commands before starting the service: systemctl reenable openvpn@.service systemctl daemon-reload systemctl daemon-reexec > I'll upload 2.3.10 soon, can you check if it works with it? I now have the new version of openvpn. If I re-add the following directives to my configuation with this version, openvpn now starts without error: user openvpn group nogroup iproute /usr/local/sbin/openvpn-ip And a ps listing shows the openvpn processes running as the openvpn user. With my phone I am able to connect to openvpn okay, but I was unable to browse anything with my web browser. If I remove the directives and restart openvpn and reconnect my phone again then browsing works. So I am now futher than I was before but something else is wrong. I compared the syslog entries for my connection when running openvpn at the root and openvpn users. I then compared routes. When running with the root user, an extra route is added when my phone connects. When running with the openvpn user, there is no extra route added when my phone connects. I edited the /usr/local/sbin/openvpn-ip script so that it looks like this: #!/bin/sh echo "openvpn-ip script invoked" >> /tmp/openvpn-ip.tmp /usr/bin/sudo /sbin/ip $* Then I connected with the phone while openvpn was running as the openvpn user. The /tmp/openvpn-ip.tmp file was not created. So it looks like the following directive in the configuration file is not having an effect, or for some reason openvpn is unable to run it: iproute /usr/local/sbin/openvpn-ip The permissions on the file are okay and the openvpn user is able to reach it: # sudo -u openvpn ls -l /usr/local/sbin/openvpn-ip -rwxr-xr-x 1 root staff 92 Feb 20 07:32 /usr/local/sbin/openvpn-ip So perhaps another capability is stopping this file from being run? I saw no other log messages relating to failure to access or run the /usr/local/sbin/openvpn-ip script anywhere. Regards, Jim.
Bug#815126: linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'
Package: src:linux Version: 4.4.2-1 Severity: critical Justification: breaks the whole system Dear Maintainer, I upgraded from linux-image-4.3.0-1-amd64 (version 4.3.5-1) to linux-image-4.4.0-1-amd64. On rebooting the system I am presented with grub, and then start booting into Linux. I only get to see 2 lines with the cursor below them on the lefthand side. Loading Linux 4.4.0-1 ... Loading initial ramdisk ... _ The system freezes at this point and is unresponsive. I have to hold my power button down for approx 10s to power off the laptop. Booting back into linux-4.3.0-1-amd64 works fine. I attempted to reinstall the kernel (from a different location/network) using: aptitude reinstall linux-image-4.4.0-1-amd64 This made no difference. Choosing to boot the same kernel using the (recovery mode) grub option results in the same problem. Because the boot hangs so early I can't provide any useful diagnostic information. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20BS0038AU product_version: ThinkPad X1 Carbon 3rd chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N14ET33W (1.11 ) board_vendor: LENOVO board_name: 20BS0038AU board_version: SDK0E50510 WIN ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:2227] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:2227] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI]) Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller [17aa:2227] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03) Subsystem: Lenovo Wildcat Point-LP MEI Controller [17aa:2227] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) I218-LM [8086:15a2] (rev 03) Subsystem: Lenovo Ethernet Connection (3) I218-LM [17aa:2227] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:2227] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 [8086:9c92] (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel
Bug#788243: quagga: suboptimal default pager settings for vtysh
Hi. I used to be able to override the pager used by vtysh by setting the VTYSH_PAGER environment variable. However it seems to be ignored these days. I've tried the following: export VTYSH_PAGER=/bin/more vtysh VTYSH_PAGER=/bin/more vtysh export VTYSH_PAGER='/usr/bin/less -EX' vtysh VTYSH_PAGER='/usr/bin/less -EX' vtysh All of them result in being presented with a blank screen with (END) at the bottom when I run vtysh (so the default 'less' configuration). Every command run results in me having to hit q afterwards, and the results from the previous command are cleared from the screen. The variable is definitely set: root@gw:~# env | grep VTYSH_PAGER VTYSH_PAGER=less -EX I'm not sure at what version of quagga this stopped working, but when I introduced it to my profile (years ago?) it used to work. Regards, Jim
Bug#792653: openvpn: Unprivileged mode results in sudo: unable to send audit message: Operation not permitted
Package: openvpn Version: 2.3.7-1 Severity: normal Dear Maintainer, I was trying to follow the directions in the OpenVPN HOWTO, to set up unprivileged mode to secure OpenVPN a bit more. Note that without using unprivileged mode, I have OpenVPN working properly when running as root. The 'Unprivileged mode (Linux only)' heading is found in the 'Hardening OpenVPN Security' section of the document that is at the following link: https://openvpn.net/index.php/open-source/documentation/howto.html#security I called my unprivileged user 'openvpn', created like so: adduser --system --no-create-home openvpn I added the following configuration to my /etc/sudoers.d/local file: openvpn ALL=(ALL) NOPASSWD: /sbin/ip I created /usr/local/sbin/openvpn-ip with the following contents: #!/bin/sh /usr/bin/sudo /sbin/ip $* I then put the following extra directives into my openvpn server configuration: user openvpn group nogroup iproute /usr/local/sbin/openvpn-ip When I try to run start up OpenVPN it fails. The error shown by 'journalctl _EXE=/usr/sbin/openvpn' follows: Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28020]: OpenVPN 2.3.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jul 7 2015 Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Diffie-Hellman initialized with 2048 bit key Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Socket Buffers: R=[212992-131072] S=[212992-131072] Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: TUN/TAP device tun0 opened Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: TUN/TAP TX queue length set to 100 Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: do_ifconfig, tt-ipv6=1, tt-did_ifconfig_ipv6_setup=1 Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: /usr/local/sbin/openvpn-ip link set dev tun0 up mtu 1500 Jul 17 14:22:43 gecko ovpn-openvpn-udp-1194[28023]: Linux ip link set failed: external program exited with error status: 1 I modified my /usr/local/sbin/openvpn-ip to capture and log the error like so: #!/bin/sh ERR=`/usr/bin/sudo /sbin/ip $* 21` RET=$? echo $ERR /tmp/openvpn-ip.err exit $RET The contents of the /tmp/openvpn-ip.err when I try to start OpenVPN is: sudo: unable to send audit message: Operation not permitted If I manually run the following command, the tun interface is brought up without error: sudo -u openvpn /usr/local/sbin/openvpn-ip link set dev tun0 up mtu 1500 I checked my system and selinux is disabled. I also tried to override the supplied /lib/systemd/system/openvpn@.service file by copying it to /etc/systemd/system and editing it using the 'systemctl edit --full openvpn@.service' command. First I tried adding CAP_AUDIT_WRITE CAP_AUDIT_READ CAP_AUDIT_CONTROL to the CapabilityBoundingSet= directive with no luck. I tried removing the CapabilityBoundingSet= directive completely with no luck. I also removed the DeviceAllow= lines in case some other device access was needed, but no luck. Finally I also removed the ProtectSystem=yes directive with no luck. Each time I edited the file, I tried the following commands before starting the service: systemctl reenable openvpn@.service systemctl daemon-reload systemctl daemon-reexec As far as I can tell, after my edits the service shouldn't be using any of systemd's features to lock down security on it. So I'm at a bit of a loss as to why the sudo command is failing to send an audit message when calling the /sbin/ip script. But systemd (and capabilities) are still a new concept to me, so there is bound to be something I'm missing. Any help/ideas would be appreciated. Also, since systemd defines a restricted set of capabilities for the OpenVPN service, am I just wasting my time trying to set up unprivileged mode anyway? Jim. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.57 ii init-system-helpers1.23 ii initscripts2.88dsf-59.2 ii iproute2
Bug#785672: Where are the amd64 packages?
Hi. This bug is reported to be fixed in the 4.0.4-1 source version with a 4.0.0-2 package version listed for all the architectures including amd64. But when I look at the Debian repositories, version 4.0.0-2 packages for the amd64 architecture seems to be missing? The other architectures are catered for though. I figured it would turn up eventually, but it's been a week now since the fixed package was released. I've tried looking directly in the http://ftp.debian.org/debian/pool/main/l/linux/ directory at all the linux-image-4.0.0-2-*.deb files. Here's a cut-and-paste of the linux-image-4.0.0-2 packages from a lynx session: [ ] linux-image-4.0.0-2-4kc-malta_4.0.4-1_mips.deb 2015-05-28 05:47 28M [ ] linux-image-4.0.0-2-4kc-malta_4.0.4-1_mipsel.deb 2015-05-28 12:43 28M [ ] linux-image-4.0.0-2-5kc-malta_4.0.4-1_mips.deb 2015-05-28 05:47 29M [ ] linux-image-4.0.0-2-5kc-malta_4.0.4-1_mipsel.deb 2015-05-28 12:43 29M [ ] linux-image-4.0.0-2-586_4.0.4-1_i386.deb 2015-05-27 03:58 32M [ ] linux-image-4.0.0-2-686-pae-dbg_4.0.4-1_i386.deb 2015-05-27 03:58 342M [ ] linux-image-4.0.0-2-686-pae_4.0.4-1_i386.deb 2015-05-27 03:58 33M [ ] linux-image-4.0.0-2-arm64-dbg_4.0.4-1_arm64.deb 2015-05-27 06:15 222M [ ] linux-image-4.0.0-2-arm64_4.0.4-1_arm64.deb 2015-05-27 06:15 22M [ ] linux-image-4.0.0-2-armmp-lpae_4.0.4-1_armhf.deb 2015-05-27 06:25 25M [ ] linux-image-4.0.0-2-armmp_4.0.4-1_armhf.deb 2015-05-27 06:25 25M [ ] linux-image-4.0.0-2-kirkwood_4.0.4-1_armel.deb 2015-05-28 02:15 19M [ ] linux-image-4.0.0-2-loongson-2e_4.0.4-1_mipsel.deb 2015-05-28 12:43 25M [ ] linux-image-4.0.0-2-loongson-2f_4.0.4-1_mipsel.deb 2015-05-28 12:43 25M [ ] linux-image-4.0.0-2-loongson-3_4.0.4-1_mipsel.deb 2015-05-28 12:43 27M [ ] linux-image-4.0.0-2-octeon_4.0.4-1_mips.deb 2015-05-28 05:47 24M [ ] linux-image-4.0.0-2-orion5x_4.0.4-1_armel.deb 2015-05-28 02:15 19M [ ] linux-image-4.0.0-2-powerpc-smp_4.0.4-1_powerpc.deb 2015-05-27 01:47 26M [ ] linux-image-4.0.0-2-powerpc64_4.0.4-1_powerpc.deb 2015-05-27 01:47 30M [ ] linux-image-4.0.0-2-powerpc64le_4.0.4-1_ppc64el.deb 2015-05-27 01:16 29M [ ] linux-image-4.0.0-2-powerpc_4.0.4-1_powerpc.deb 2015-05-27 01:47 25M [ ] linux-image-4.0.0-2-r4k-ip22_4.0.4-1_mips.deb 2015-05-28 05:47 17M [ ] linux-image-4.0.0-2-r5k-ip32_4.0.4-1_mips.deb 2015-05-28 05:47 22M [ ] linux-image-4.0.0-2-rt-686-pae-dbg_4.0.4-1_i386.deb 2015-05-27 03:58 342M [ ] linux-image-4.0.0-2-rt-686-pae_4.0.4-1_i386.deb 2015-05-27 03:58 33M [ ] linux-image-4.0.0-2-s390x-dbg_4.0.4-1_s390x.deb 2015-05-27 04:39 214M [ ] linux-image-4.0.0-2-s390x_4.0.4-1_s390x.deb 2015-05-27 04:39 22M [ ] linux-image-4.0.0-2-sb1-bcm91250a_4.0.4-1_mips.deb 2015-05-28 05:47 25M [ ] linux-image-4.0.0-2-sb1-bcm91250a_4.0.4-1_mipsel.deb 2015-05-28 12:43 25M [ ] linux-image-4.0.0-2-sparc64-smp_4.0.4-1_sparc.deb 2015-05-31 06:11 25M [ ] linux-image-4.0.0-2-sparc64_4.0.4-1_sparc.deb 2015-05-31 06:11 24M [ ] linux-image-4.0.0-2-versatile_4.0.4-1_armel.deb 2015-05-28 02:16 20M It skips from 686 to arm64 missing amd64. But it's not just the linux-image files, but everything amd64, like linux-headers. Thanks, Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785672: Where are the amd64 packages?
From: Albino Biasutti Neto [b...@riseup.net] Try: dpkg --print-foreign-architectures https://wiki.debian.org/Multiarch/HOWTO Hi. I'm not sure what you're asking of me here Albino. My amd64 systems do not have any foreign architectures added. Are you asking me to add the i386 architecture and install the 686-pae packages? I don't want to do that. I plan to stick with native 64 bit kernels on my amd64 systems. I was trying to point out that there are no version 4.0.0-2 amd64 Linux kernel packages available on the Debian repositories/mirrors. The amd64 version available on the Debian repos is still stuck at version 4.0.0-1, and so contains the ext4 corruption bugs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784398: open-vm-tools: VM locks up when a snapshot with file system quiesce is taken
Package: open-vm-tools Version: 2:9.10.0-2476743-4 Severity: important Dear Maintainer, Yesterday I upgraded open-vm-tools version 2:9.4.6-1770165-8 to version 2:9.10.0-2476743-3 on a few VMs. Overnight, our VMs are backed up via Symantec NetBackup. The backup begins by creating a snapshot that quiesces the guest file system. All VMs with the newer version of open-vm-tools effectively lock up. The following error is in the /var/log/syslog file on the VM when the snapshot is taken: vmsvc[6299]: [ warning] [vmbackup] Failed to send event to the VMX: Guest is not privileged enough to invoke RPC. After this, most services on the host become unresponsive. The hosts are sort of still operating, but really slow, and most services are unresponsive. We were forced to reboot the VMs to return the service back to normal. We did some testing this morning and we can reproduce the problem like so: - Login to vCenter - Right-click on the VM and choose 'Take Snapshot...' - Untick 'Snapshot the virtual machine's memory' - Tick 'Quiesce guest file system (Needs VMware Tools installed)' - Click 'OK' to start the snapshot process. This was done on a test VM that had no activity on it. We also upgraded from 2:9.10.0-2476743-3 to 2:9.10.0-2476743-4 this morning on the test VM and it still has the same problem. Backing out open-vm-tools to version 2:9.4.6-1770165-8 again fixes the problem. Our VMware environment is version 5.1 for both the ESXi hosts and the vCenter server. This reportbug was generated on the test VM that is running the unstable distribution of Debian whilst running the latest open-vm-tools package again. Regards, Jim Barber -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages open-vm-tools depends on: ii init-system-helpers 1.23 ii libc62.19-18 ii libdumbnet1 1.12-6 ii libfuse2 2.9.3-15+b1 ii libgcc1 1:5.1.1-4 ii libglib2.0-0 2.44.0-2 ii libicu52 52.1-8 ii libmspack0 0.5-1 ii libprocps3 2:3.3.9-9 ii libssl1.0.0 1.0.2a-1 ii libstdc++6 5.1.1-4 ii libxerces-c3.1 3.1.1-5.1 ii libxml-security-c17 1.7.2-3+b1 Versions of packages open-vm-tools recommends: ii ethtool 1:3.16-1 pn zerofree none Versions of packages open-vm-tools suggests: pn open-vm-tools-desktop none -- Configuration Files: /etc/modprobe.d/open-vm-tools.conf b0209ace275d68946b7f67daad5d4b20 [Errno 2] No such file or directory: u'/etc/modprobe.d/open-vm-tools.conf b0209ace275d68946b7f67daad5d4b20' /etc/vmware-tools/tools.conf changed: /etc/xdg/autostart/vmware-user.desktop a00f6f451c319d17d319763b915415ce [Errno 2] No such file or directory: u'/etc/xdg/autostart/vmware-user.desktop a00f6f451c319d17d319763b915415ce' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784398: open-vm-tools: VM locks up when a snapshot with file system quiesce is taken
Correction to the above (in case it matters). The versions of vCenter and ESXi is 5.5 not 5.1. Specifically: - ESXi 5.5.0 Build 1881737 - vCenter 5.5.0 Build 1750787 Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781508: fprintd: Please upgrade to version 0.6.0
From: Matteo F. Vescovi [mailto:mfvesc...@gmail.com] On Behalf Of Matteo F. Vescovi Actually, the support has been already added via the libfprint 0.6.0 package in the experimental suite. I'm using it right now, on the same laptop, and it works just fine. Hi Matteo. My mistake. I had the experimental repository in my sources, but I checked the versions of the libpam-fprintd and fprintd packages that shows 0.5.1-1. I failed to check the version of the libfprint0 package that has a 1:0.6.0-1 version. It sounds like this is all I need, and so this bug can be closed. Thanks. Jim Barber
Bug#781508: fprintd: Please upgrade to version 0.6.0
Source: fprintd Version: 0.5.1-1 Severity: wishlist Dear Maintainer, I have a Lenovo X1 Carbon Gen 3 laptop. It has a Validity Sensors, Inc. VFS5011 finger print reader. Support for this reader was added in version 0.6.0 of the libfprint software. The changelog can be seen here: http://cgit.freedesktop.org/libfprint/libfprint/log/ This is a wish for you to please upgrade the version of the fprintd packages from 0.5.1 to 0.6.0. Thanks, Jim Barber -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fprintd depends on: ii dbus 1.8.16-1 ii libc6 2.19-17 ii libdbus-1-31.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libfprint0 1:0.5.1-1 ii libglib2.0-0 2.42.1-1 ii libpolkit-gobject-1-0 0.105-8 ii policykit-10.105-8 fprintd recommends no packages. fprintd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760303: squid 3.3.8-1.2 segfaults during initscript start/restart
I just wanted to add that I am also getting these errors on 2x Debian/testing hosts. I am not using squidclamav but instead I'm using the libc-icap-mod-virus-scan package. Details of the installed packages that I think may be relevant are: $ dpkg --list | grep -P 'clam|icap|squid' ii c-icap1:0.3.4-2 amd64 ICAP server implementation ii clamav0.98.6+dfsg-1 amd64 anti-virus utility for Unix - command-line interface ii clamav-base 0.98.6+dfsg-1 all anti-virus utility for Unix - base package ii clamav-freshclam 0.98.6+dfsg-1 amd64 anti-virus utility for Unix - virus database update utility ii libc-icap-mod-virus-scan 1:0.3.2-2 amd64 Antivirus Service for c-icap ii libclamav60.98.6+dfsg-1 amd64 anti-virus utility for Unix - library ii libicapapi3 1:0.3.4-2 amd64 ICAP API library ii squid-langpack20140506-1all Localized error pages for Squid ii squid33.4.8-6 amd64 Full featured Web Proxy cache (HTTP proxy) ii squid3-common 3.4.8-6 all Full featured Web Proxy cache (HTTP proxy) - common files I currently have ICAP daemon disabled: $ grep START /etc/default/c-icap START=no $ ps -ef | grep icap jimb 1936 793 0 11:10 pts/100:00:00 grep icap I have not defined icap_enabled (my 'icap_enabled on' directive is currently commented out), and so it should default to 'off' However I still have configuration in place for icap in squid, and this seems to be enough to trigger the error. The icap config changes made in /etc/squid/squid3.conf are: # Disable for now... #icap_enable on icap_preview_size 1024 adaptation_send_client_ip on icap_client_username_header X-Authenticated-User icap_service service_avi_req reqmod_precache icap://localhost:1344/avscan bypass=on icap_service service_avi_resp respmod_precache icap://localhost:1344/avscan bypass=on adaptation_access service_avi_req allow all adaptation_access service_avi_resp allow all Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778664: pam_tty_audit: Cannot make/remove an entry for the specified session
Package: libpam-modules Version: 1.1.8-3.1 Severity: normal Dear Maintainer, I tried to configure the pam_tty_audit module. I edited the /etc/pam.d/common-session file and at the end of it added the following line as per the the pam_tty_audit(8) man page: session required pam_tty_audit.so disable=* enable=root After doing that, I try to gain root access by running 'su -' and I'm presented with an error and the su fails: $ su - Password: su: Cannot make/remove an entry for the specified session $ In the /var/logl/auth.log file are the corresponding errors: Feb 18 13:55:54 dwper-ansible su[41264]: Successful su for root by jimb Feb 18 13:55:54 dwper-ansible su[41264]: + /dev/pts/0 jimb:root Feb 18 13:55:54 dwper-ansible su[41264]: pam_unix(su:session): session opened for user root by jimb(uid=1000) Feb 18 13:55:54 dwper-ansible su[41264]: pam_tty_audit(su:session): error setting current audit status: Invalid argument Feb 18 13:55:54 dwper-ansible su[41264]: pam_open_session: Cannot make/remove an entry for the specified session Removing the line from the /etc/pam.d/common-session file allows the su command to work again. The host is running the Debian testing distribution with all current updates installed. Regards, Jim Barber -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libpam-modules depends on: ii debconf [debconf-2.0] 1.5.55 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libdb5.3 5.3.28-7~deb8u1 ii libpam-modules-bin 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 libpam-modules recommends no packages. libpam-modules suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739721: systemd: NFS shares are not automatically mounted during boot
Somewhere along the line my particular problem with NFS mounts failing to work at boot with systemd has been fixed on all of my systems. I've kept up to date with upgrading Debian packages on all of my systems, and one of these seems to have addressed my problems. But I couldn't say which one it is. Regards, Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739721: systemd: NFS shares are not automatically mounted during boot
Am 31.10.2014 um 01:30 schrieb Jim Barber: My network config on the host is very simple: $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 Try changing that to auto eth0 Hi. I have made the change to my network configuration but there is no change in behaviour. The result from the systemctl status command is still the same. $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.1.1.2/24 gateway 10.1.1.1 ethernet-wol g # This is an autoconfigured IPv6 interface iface eth0 inet6 auto And: $ systemctl status -l usr-local-share.mount ● usr-local-share.mount - /usr/local/share Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Mon 2014-11-03 08:12:37 AWST; 20s ago Where: /usr/local/share What: gecko:/usr/local/share Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 394 ExecMount=/bin/mount -n gecko:/usr/local/share /usr/local/share -t nfs -o _netdev,noatime,nolock,bg,rsize=8192,wsize=8192 (code=exited, status=32) Nov 03 08:12:37 trex mount[394]: mount.nfs: Network is unreachable Nov 03 08:12:37 trex systemd[1]: usr-local-share.mount mount process exited, code=exited status=32 Nov 03 08:12:37 trex systemd[1]: Failed to mount /usr/local/share. Nov 03 08:12:37 trex systemd[1]: Unit usr-local-share.mount entered failed state. On my other i386 system that exhibits the same problem I was already using the 'auto' rather than 'allow-hotplug' directive in the /etc/network/interfaces file. None of my NFS file systems are mounted after boot, but once logged in I can manually mount them. Regards, Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739721: systemd: NFS shares are not automatically mounted during boot
Package: systemd Version: 215-5+b1 Hi. I have a similar problem, and I think it belongs in this bug report. On boot, NFS file systems used to work fine. It was after upgrading from initscripts version 2.88dsf-53.4 to 2.88dsf-57 that all my NFS mounts no longer mount on boot. I was going to report the bug against that package but the change log for it states: Version 2.88dsf-55.1 says: * Skip the mountnfs hook when being triggered by the networking SysV init script and instead use the systemd built-in mechanisms to mount remote file systems. This avoids a deadlock caused by the rpcbind SysV init script depending on $network and the $network LSB facility being provided by the networking SysV init script. (Closes: #746587) So I figured it is likely to be systemd now... Once I log in and run a 'mount -a' all NFS file systems are mounted just fine. I have done a number of boots on this system and also another system and they consistently fail to mount NFS after the upgrade above. This system I am reporting about is an amd64 architecture box, and the other is running an i386 version of Debian. Note that I have a couple of other NFS mounts too, all of which fail in the same way. Two of the mounts from come my main Linux server, and the other mount comes from a Synology NAS. Looking at one of my filesystems I see: $ systemctl status -l usr-local-share.mount ● usr-local-share.mount - /usr/local/share Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Fri 2014-10-31 07:51:39 AWST; 5min ago Where: /usr/local/share What: gecko:/usr/local/share Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 341 ExecMount=/bin/mount -n gecko:/usr/local/share /usr/local/share -t nfs -o _netdev,noatime,nolock,bg,rsize=8192,wsize=8192 (code=exited, status=32) Oct 31 07:51:39 trex systemd[1]: usr-local-share.mount mount process exited, code=exited status=32 Oct 31 07:51:39 trex mount[341]: mount.nfs: Network is unreachable Oct 31 07:51:39 trex systemd[1]: Failed to mount /usr/local/share. Oct 31 07:51:39 trex systemd[1]: Unit usr-local-share.mount entered failed state. This seems to suggest my network wasn't ready. My network config on the host is very simple: $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 10.1.1.2/24 gateway 10.1.1.1 ethernet-wol g # This is an autoconfigured IPv6 interface iface eth0 inet6 auto The journalctl output suggests my network was up before the NFS filesystems attempted to start as you can see in the first 2 lines of the below followed by the NFS mount attempt: Oct 31 07:51:39 trex kernel: sky2 :03:00.0 eth0: Link is up at 1000 Mbps, full duplex, flow control both Oct 31 07:51:39 trex kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Oct 31 07:51:39 trex kernel: Key type dns_resolver registered Oct 31 07:51:39 trex kernel: NFS: Registering the id_resolver key type Oct 31 07:51:39 trex kernel: Key type id_resolver registered Oct 31 07:51:39 trex kernel: Key type id_legacy registered Oct 31 07:51:39 trex ifup[326]: mount.nfs: Network is unreachable Oct 31 07:51:39 trex systemd[1]: usr-local-share.mount mount process exited, code=exited status=32 Oct 31 07:51:39 trex mount[340]: mount.nfs: Network is unreachable Oct 31 07:51:39 trex mount[341]: mount.nfs: Network is unreachable Oct 31 07:51:39 trex ifup[326]: mount.nfs: Network is unreachable Oct 31 07:51:39 trex systemd[1]: Failed to mount /usr/local/share. At least it looks that way to me. It doesn't say when the IPv4 address was applied, but since it is static, I'd imagine it was immediate. The /etc/fstab file: $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass # / was on /dev/sda2 during installation LABEL=root / ext4 relatime,errors=remount-ro 0 1 # swap was on /dev/sda1 during installation LABEL=swap noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/sdb1
Bug#763865: The needrestart package needs to depend on the libterm-readkey-perl package.
Package: needrestart Version: 1.2-1 Severity: normal Dear Maintainer, After upgrading to needrestart from version 1.1-1 to version 1.2-1 it fails with the following error: $ sudo needrestart Can't locate Term/ReadKey.pm in @INC (you may need to install the Term::ReadKey module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/share/perl5/NeedRestart/UI.pm line 29. BEGIN failed--compilation aborted at /usr/share/perl5/NeedRestart/UI.pm line 29. Compilation failed in require at /usr/sbin/needrestart line 29. BEGIN failed--compilation aborted at /usr/sbin/needrestart line 29. Using apt-file, I found that the ReadKey.pm module is in the libterm-readkey-perl package. Installing that package fixes the problem. The needrestart package should have a dependency on the libterm-readkey-perl package to make sure it gets installed if it isn't already. Regards, Jim -- Package-specific info: needrestart output: Running kernel seems to be up-to-date. Services to be restarted: user@1000.service user@65534.service -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages needrestart depends on: ii dpkg 1.17.13 ii libmodule-find-perl0.12-1 ii libmodule-scandeps-perl1.15-1 ii libproc-processtable-perl 0.50-2+b1 ii libsort-naturally-perl 1.03-1 ii perl 5.20.1-1 needrestart recommends no packages. needrestart suggests no packages. -- Configuration Files: /etc/needrestart/needrestart.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754339: winbind: ntlm_auth not working due to winbindd_privileged directory problem
Package: winbind Version: 2:4.1.9+dfsg-1 Severity: normal Dear Maintainer, I am setting up a Squid3 server using winbind and ntlm_auth to authenticate users. I have successfully done this before with a much older version of Debian. But with the new version I was having issues. I have winbind working properly. I have added the 'proxy' user to the 'winbindd_priv' group. I have the following auth_param config in the /etc/squid3/squid.conf file: auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp auth_param ntlm children 256 startup=0 idle=1 When using the proxy with a Firefox browser, a window popped up asking for credentials. After entering them, I am re-prompted to enter them over and over. The error in the /var/log/squid3/cache.log is: ERROR: NTLM Authentication validating user. Error returned 'BH NT_STATUS_UNSUCCESSFUL NT_STATUS_UNSUCCESSFUL' Eventually I tracked the cause down to the following: I was (incorrectly) assuming that the /run/samba/winbindd_privileged directory was being used by ntlm_auth. This directory is set up by the /etc/init.d/winbind script and looks like so: drwxr-x--- 2 root winbindd_priv 40 Jul 9 10:58 /run/samba/winbindd_privileged But the contents of this directory is empty: # ls -l /run/samba/winbindd_privileged/ total 0 Instead, there is another directory that I found like so: drwxr-x--- 2 root root 4096 Jul 10 11:44 /var/lib/samba/winbindd_privileged This directory contains the socket file needed: # ls -l /var/lib/samba/winbindd_privileged/ total 0 srwxrwxrwx 1 root root 0 Jul 10 11:44 pipe I corrected the group permission on the directory so it looks like: drwxr-x--- 2 root winbindd_priv 4096 Jul 10 11:44 /var/lib/samba/winbindd_privileged I restarted squid, and authentication started working correctly. So the problem is there is both the following directories: /run/samba/winbindd_privileged /var/lib/samba/winbindd_privileged Only the second one is where the socket is created. But the second one has the wrong group permissions on it to enable access by adding appropriate uses to the winbindd_priv group. I'm not sure what the correct fix is. I guess either /var/lib/samba/winbindd_privileged should be a symlink to /run/samba/winbindd_privileged instead of being a directory. Or all winbind products need to be correctly configured (at compile time?) to use /run/samba/winbindd_privileged and then remove the /var/lib/samba/winbindd_privileged directory. Or something else of your choosing. Jim. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages winbind depends on: ii libbsd0 0.6.0-2 ii libc6 2.19-4 ii libcomerr2 1.42.10-1.1 ii libkrb5-26-heimdal 1.6~rc2+dfsg-7 ii libldap-2.4-2 2.4.39-1 ii libpopt01.16-8 ii libtalloc2 2.1.1-1 ii libtdb1 1.3.0-1.1 ii libtevent0 0.9.21-1 ii libwbclient02:4.1.9+dfsg-1 ii multiarch-support 2.19-4 ii samba 2:4.1.9+dfsg-1 ii samba-libs 2:4.1.9+dfsg-1 winbind recommends no packages. Versions of packages winbind suggests: ii libnss-winbind 2:4.1.9+dfsg-1 ii libpam-winbind 2:4.1.9+dfsg-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
On 6/06/2014 2:24 AM, Andreas Cadhalpun wrote: Control: tags -1 fixed-upstream pending Hi Jim, upstream fixed the problem and I have backported the fix for Debian, so that it will be included in the next upload. Until then just disable ScanOnAccess to work around the problem. Best regards, Andreas After reading the discussion on the upstream bug report, it looks like perhaps these error messages in the logs were relevant after all... - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted - ScanOnAccess: clamd must be started by root Is ScanOnAccess something that is toggled depending on how you answer dpkg configuration questions? Or is it something I manually need to change in the /etc/clamav/clamd.conf ? I didn't see a question relevant to it at installation time. I have done a fresh install of clamav-daemon on a virtual machine and ScanOnAccess is set to false. To my knowledge I never manually set it to true on the system that I have the issue with. So I can only guess that it was enabled in one of the older clamav-daemon packages and subsequent upgrades have preserved the setting? I've been using this Debian system for many years (I think since around 2009) Either that, or I set it so long ago I just can't remember doing it. Thanks for all your help resolving the issue Andreas. I look forward to the fixed packages appearing in the Debian mirror. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
Hi Andreas. On 29/05/2014 5:10 PM, Andreas Cadhalpun wrote: Thanks for your help in finding the cause. Since the logs are inconclusive, it would really help if you could get us a backtrace, when clamd is hanging. For this install clamav-dbg and gdb. When it hangs again, please determine the PIDs of all clamd threads, e.g. with: ps -eL | grep clamd The second column contains this number. For every thread of clamd, run (replacing PID with the actual number): sudo gdb /usr/sbin/clamd PID And then in gdb: bt full The output of this should help to figure out, where exactly clamd is hanging. Okay, I have a hang, and I have the gdb output that you want. First the PID and Threads: # ps -eL | grep -P 'LWP|clamd' PID LWP TTY TIME CMD 26124 26124 ?00:00:11 clamd 26124 26126 ?00:00:00 clamd Then connecting to the first thread via gdb: # gdb /usr/sbin/clamd 26124 GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/clamd...Reading symbols from /usr/lib/debug/usr/sbin/clamd...done. done. Attaching to program: /usr/sbin/clamd, process 26124 warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? Reading symbols from /usr/lib/libclamav.so.6...Reading symbols from /usr/lib/debug/usr/lib/libclamav.so.6.1.23...done. done. Loaded symbols for /usr/lib/libclamav.so.6 Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libpthread-2.18.so...done. done. [New LWP 26126] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.18.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libxml2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libxml2.so.2 Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1 Reading symbols from /lib/x86_64-linux-gnu/libbz2.so.1.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libbz2.so.1.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libltdl.so.7...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libltdl.so.7 Reading symbols from /usr/lib/x86_64-linux-gnu/libffi.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libffi.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.18.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libdl-2.18.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libgcc_s.so.1 Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.18.so...done. done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/x86_64-linux-gnu/liblzma.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/liblzma.so.5 Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libnss_compat-2.18.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_compat.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libnsl-2.18.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libnsl.so.1 Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...Reading symbols from
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
Hi Andreas. On 29/05/2014 5:10 PM, Andreas Cadhalpun wrote: On 28.05.2014 02:55, Jim Barber wrote: On 2014-05-27 18:39, Andreas Cadhalpun wrote: I think the problem here is that there is a second 'Restarting on-access scan' message only 4 seconds after another one and without the usual 'ERROR: ScanOnAccess: fanotify_init [...]' between them. This looks as if the reload is started again, while the previous reload is not yet finished. Probably this should not happen, as it seems to cause a deadlock. It does appear that way. Higher up in the log there are also instances where two restarts happened within seconds of each other, but I guess were far enough apart to avoid the race/deadlock situation that the daemon seems to be encountering. Yes, it's strange. I tried to reproduce this, but failed. What I did: * Set ScanOnAccess to true. * Set SelfCheck to 10 seconds. * Stop the freshclam daemon: sudo service clamav-freshclam stop * Delete /var/lib/clamav/bytecode.cvd. * Run 'freshclam --daemon-notify=/etc/clamav/clamd.conf'. Repeating the last two steps, I saw three different patterns in the log. * Only one reload, triggered by freshclam. * Two reloads, but far enough apart, so that the 'ERROR:' message appears between them. * Two reloads, but without the 'ERROR:' message between them. Since it didn't hang in any of my tries, there must either be a really precise timing to cause the hang and I was lucky not to have it or there is something else needed. Since I enabled 'Debug true' in clamd.conf I haven't had a crash. Doing that must have modified the timing just enough to avoid the race/deadlock situation by the looks of things. It's been quite a number of days since I did this change now... I have upgraded to 0.98.4-rc1 again, but at this stage I've left the freshclam notications on to see if we can find the cause of the hangs. Thanks for your help in finding the cause. Since the logs are inconclusive, it would really help if you could get us a backtrace, when clamd is hanging. For this install clamav-dbg and gdb. When it hangs again, please determine the PIDs of all clamd threads, e.g. with: ps -eL | grep clamd The second column contains this number. For every thread of clamd, run (replacing PID with the actual number): sudo gdb /usr/sbin/clamd PID And then in gdb: bt full The output of this should help to figure out, where exactly clamd is hanging. Okay. When I get a chance I'll install the -dbg packages and I'll set 'Debug false' again since it seems to be preventing the hang, and I'll see if it hangs with the dbg packages in place and get the gdb info. If the -dbg packages also prevent the hang because of different timings then I guess we're out of luck to find the real cause of the hangs... Regards, Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
Hi Andreas On 2014-05-27 18:39, Andreas Cadhalpun wrote: Hi Jim, You could try it with 0.98.1, but I'm not sure if that would help. I think I'll keep moving on with the new versions, and hopefully we can find the real problem. I think the problem here is that there is a second 'Restarting on-access scan' message only 4 seconds after another one and without the usual 'ERROR: ScanOnAccess: fanotify_init [...]' between them. This looks as if the reload is started again, while the previous reload is not yet finished. Probably this should not happen, as it seems to cause a deadlock. It does appear that way. Higher up in the log there are also instances where two restarts happened within seconds of each other, but I guess were far enough apart to avoid the race/deadlock situation that the daemon seems to be encountering. Shall I upgrade to 0.98.4~rc1 again and reconfigure freshclam to no longer notify the ClamAV daemon when an update is available? Yes, please try this and let us know, if it helps. I have upgraded to 0.98.4-rc1 again, but at this stage I've left the freshclam notications on to see if we can find the cause of the hangs. Also could you please check, if /var/log/clamav/freshclam.log contains 'Clamd successfully notified about the update.' around the time 'Mon May 26 22:52:23 2014', where the hang happened, or if there is a related error message. The freshclam logs around this time are as follows: Mon May 26 21:52:15 2014 - -- Mon May 26 22:52:15 2014 - Received signal: wake up Mon May 26 22:52:15 2014 - ClamAV update process started at Mon May 26 22:52:15 2014 Mon May 26 22:52:15 2014 - main.cld is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) Mon May 26 22:52:16 2014 - Downloading daily-19034.cdiff [100%] Mon May 26 22:52:17 2014 - daily.cld updated (version: 19034, sigs: 968759, f-level: 63, builder: neo) Mon May 26 22:52:19 2014 - Database updated (3392984 signatures) from db.local.clamav.net (IP: 117.104.160.194) Mon May 26 22:52:23 2014 - Clamd successfully notified about the update. Mon May 26 22:52:23 2014 - -- Mon May 26 23:52:23 2014 - Received signal: wake up Mon May 26 23:52:23 2014 - ClamAV update process started at Mon May 26 23:52:23 2014 Mon May 26 23:52:23 2014 - main.cld is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo) Mon May 26 23:52:23 2014 - daily.cld is up to date (version: 19034, sigs: 968759, f-level: 63, builder: neo) Mon May 26 23:52:24 2014 - -- It looks like freshclam believes the notification was successful. You can set 'Debug true' in clamd.conf. I have done this to see if there is more information the next time version 0.98.4-rc1 hangs. There is also a 'LogVerbose false' parameter. Is it worth settng that to true? Or is that pointless when you have Debug enabled? Is the problem perhaps related to these messages? - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted - ScanOnAccess: clamd must be started by root I don't think this is related, but if the above doesn't help, you could try disabling ScanOnAccess or running clamd as root. Okay, I'll hold off on doing that for now since I also think this is probably not related. Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
The ClamAV daemon hung again after rolling back to 0.98.3. It went longer than a day this time, but still less than 2 days. Here's the havp log (with URL removed). 25/05/2014 08:51:59 === Starting HAVP Version: 0.92 25/05/2014 08:51:59 Running as user: havp, group: havp 25/05/2014 08:51:59 Use parent proxy: localhost:3130 25/05/2014 08:51:59 --- Initializing Clamd Socket Scanner 25/05/2014 08:51:59 Clamd Socket Scanner passed EICAR virus test (Eicar-Test-Signature) 25/05/2014 08:51:59 --- All scanners initialized 25/05/2014 08:51:59 Process ID: 23108 26/05/2014 23:20:04 Error: Some scanner has timed out! (lasturl: url removed) The complete ClamAV log from when I started it after backing out to the older version, to when I restarted it when I noticed it was hung is as follows: Sun May 25 08:51:01 2014 - +++ Started at Sun May 25 08:51:01 2014 Sun May 25 08:51:01 2014 - clamd daemon 0.98.3 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) Sun May 25 08:51:01 2014 - Log file size limited to 4294967295 bytes. Sun May 25 08:51:01 2014 - Reading databases from /var/lib/clamav Sun May 25 08:51:01 2014 - Not loading PUA signatures. Sun May 25 08:51:01 2014 - Bytecode: Security mode set to TrustSigned. Sun May 25 08:51:05 2014 - Loaded 3384653 signatures. Sun May 25 08:51:05 2014 - LOCAL: Unix socket file /var/run/clamav/clamd.ctl Sun May 25 08:51:05 2014 - LOCAL: Setting connection queue length to 15 Sun May 25 08:51:05 2014 - Limits: Global size limit set to 104857600 bytes. Sun May 25 08:51:05 2014 - Limits: File size limit set to 26214400 bytes. Sun May 25 08:51:05 2014 - Limits: Recursion level limit set to 10. Sun May 25 08:51:05 2014 - Limits: Files limit set to 1. Sun May 25 08:51:05 2014 - Limits: MaxEmbeddedPE limit set to 10485760 bytes. Sun May 25 08:51:05 2014 - Limits: MaxHTMLNormalize limit set to 10485760 bytes. Sun May 25 08:51:05 2014 - Limits: MaxHTMLNoTags limit set to 2097152 bytes. Sun May 25 08:51:05 2014 - Limits: MaxScriptNormalize limit set to 5242880 bytes. Sun May 25 08:51:05 2014 - Limits: MaxZipTypeRcg limit set to 1048576 bytes. Sun May 25 08:51:05 2014 - Limits: MaxPartitions limit set to 50. Sun May 25 08:51:05 2014 - Limits: MaxIconsPE limit set to 100. Sun May 25 08:51:05 2014 - Archive support enabled. Sun May 25 08:51:05 2014 - Algorithmic detection enabled. Sun May 25 08:51:05 2014 - Portable Executable support enabled. Sun May 25 08:51:05 2014 - ELF support enabled. Sun May 25 08:51:05 2014 - Mail files support enabled. Sun May 25 08:51:05 2014 - OLE2 support enabled. Sun May 25 08:51:05 2014 - PDF support enabled. Sun May 25 08:51:05 2014 - SWF support enabled. Sun May 25 08:51:05 2014 - HTML support enabled. Sun May 25 08:51:05 2014 - Self checking every 3600 seconds. Sun May 25 08:51:05 2014 - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted Sun May 25 08:51:05 2014 - ScanOnAccess: clamd must be started by root Sun May 25 08:51:59 2014 - /var/spool/havp/havp-UoR2B0: Eicar-Test-Signature(003059cf287f5a591fce287f:68) FOUND Sun May 25 09:51:06 2014 - No stats for Database check - forcing reload Sun May 25 09:51:06 2014 - Restarting on-access scan Sun May 25 09:51:07 2014 - Reading databases from /var/lib/clamav Sun May 25 09:51:11 2014 - Database correctly reloaded (3384653 signatures) Sun May 25 09:51:11 2014 - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted Sun May 25 09:51:11 2014 - ScanOnAccess: clamd must be started by root Sun May 25 10:51:10 2014 - Restarting on-access scan Sun May 25 10:51:11 2014 - Reading databases from /var/lib/clamav Sun May 25 10:51:15 2014 - Database correctly reloaded (3385141 signatures) Sun May 25 10:51:15 2014 - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted Sun May 25 10:51:15 2014 - ScanOnAccess: clamd must be started by root Sun May 25 12:45:23 2014 - SelfCheck: Database status OK. Sun May 25 14:12:17 2014 - SelfCheck: Database status OK. Sun May 25 15:12:17 2014 - SelfCheck: Database status OK. Sun May 25 16:12:17 2014 - SelfCheck: Database status OK. Sun May 25 17:16:51 2014 - SelfCheck: Database status OK. Sun May 25 18:27:02 2014 - SelfCheck: Database status OK. Sun May 25 20:15:13 2014 - SelfCheck: Database status OK. Sun May 25 21:24:16 2014 - SelfCheck: Database status OK. Sun May 25 22:45:52 2014 - SelfCheck: Database status OK. Sun May 25 22:51:29 2014 - Restarting on-access scan Sun May 25 22:51:29 2014 - Reading databases from /var/lib/clamav Sun May 25 22:51:33 2014 - Database correctly reloaded (3385585 signatures) Sun May 25 22:51:33 2014 - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted Sun May 25 22:51:33 2014 - ScanOnAccess: clamd must be started by root Mon
Bug#749027: [Pkg-clamav-devel] Bug#749027: The ClamAV daemon stops working.
On 2014-05-24 22:23, Sebastian Andrzej Siewior wrote: I see. Could you please go back to 0.98.3 and see if the issue goes away? It might be a regression in the comming up 0.98.4 of clamav. Just want to make sure. Sebastian Yes, I now have the following clamav packages installed on the system: # dpkg --list | grep clam | cut -c1-60 ii clamav 0.98.3+dfsg-1 amd64 ii clamav-base 0.98.3+dfsg-1 all ii clamav-daemon 0.98.3+dfsg-1 amd64 ii clamav-freshclam0.98.3+dfsg-1 amd64 ii libclamav6 0.98.3+dfsg-1 amd64 ii libclamunrar6 0.98.1-1 amd64 I'll provide an update in a few days if there have been no hangs. Or earlier if a hang occurs. Jim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749027: clamav-daemon: The ClamAV daemon seems to stop working and needs to be restarted.
23 01:03:57 2014 - Reading databases from /var/lib/clamav Fri May 23 01:04:01 2014 - Database correctly reloaded (3380802 signatures) Fri May 23 01:04:01 2014 - Restarting on-access scan The only errors I see above are: - ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted - ScanOnAccess: clamd must be started by root But I don't think they are related since web browsing is fine immediately after the clamav daemon restart. I'm not sure which event triggered the error. It was either the upgrade of clamav to version 0.98.4~rc1+dfsg-2, or it could be that I also resolved an issue with clamav-freshclam a few days ago. I had the same problem as described in the following bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748670 I ran the dpkg-reconfigure clamav-freshclam to remove the '10' from the private mirror. I upgraded clamav on May 19th, and I fixed the freshclam issue on May 23rd at 23:14:17 local time. My first ClamAV daemon hang was at May 21st at 03:58:04 local time. So it is probably a combination of the new version of ClamAV combined with getting updates from freshclam that is triggering the problem. (Perhaps it is the restarts that the ClamAV daemon does when new definitions have been downloaded?) Regards, Jim Barber -- Package-specific info: --- configuration --- Checking configuration files in /etc/clamav Config file: clamd.conf --- LogFile = /var/log/clamav/clamav.log StatsHostID = auto StatsEnabled disabled StatsPEDisabled = yes StatsTimeout = 10 LogFileUnlock disabled LogFileMaxSize = 4294967295 LogTime = yes LogClean disabled LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose disabled LogRotate = yes ExtendedDetectionInfo = yes PidFile = /var/run/clamav/clamd.pid TemporaryDirectory disabled DatabaseDirectory = /var/lib/clamav OfficialDatabaseOnly disabled LocalSocket = /var/run/clamav/clamd.ctl LocalSocketGroup = clamav LocalSocketMode = 666 FixStaleSocket = yes TCPSocket disabled TCPAddr disabled MaxConnectionQueueLength = 15 StreamMaxLength = 26214400 StreamMinPort = 1024 StreamMaxPort = 2048 MaxThreads = 12 ReadTimeout = 180 CommandReadTimeout = 5 SendBufTimeout = 200 MaxQueue = 100 IdleTimeout = 30 ExcludePath disabled MaxDirectoryRecursion = 15 FollowDirectorySymlinks disabled FollowFileSymlinks disabled CrossFilesystems = yes SelfCheck = 3600 DisableCache disabled VirusEvent disabled ExitOnOOM disabled AllowAllMatchScan = yes Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = clamav AllowSupplementaryGroups = yes Bytecode = yes BytecodeSecurity = TrustSigned BytecodeTimeout = 6 BytecodeUnsigned disabled BytecodeMode = Auto DetectPUA disabled ExcludePUA disabled IncludePUA disabled AlgorithmicDetection = yes ScanPE = yes ScanELF = yes DetectBrokenExecutables disabled ScanMail = yes ScanPartialMessages disabled PhishingSignatures = yes PhishingScanURLs = yes PhishingAlwaysBlockCloak disabled PhishingAlwaysBlockSSLMismatch disabled PartitionIntersection disabled HeuristicScanPrecedence disabled StructuredDataDetection disabled StructuredMinCreditCardCount = 3 StructuredMinSSNCount = 3 StructuredSSNFormatNormal = yes StructuredSSNFormatStripped disabled ScanHTML = yes ScanOLE2 = yes OLE2BlockMacros disabled ScanPDF = yes ScanSWF = yes ScanArchive = yes ArchiveBlockEncrypted disabled ForceToDisk = yes MaxScanSize = 104857600 MaxFileSize = 26214400 MaxRecursion = 10 MaxFiles = 1 MaxEmbeddedPE = 10485760 MaxHTMLNormalize = 10485760 MaxHTMLNoTags = 2097152 MaxScriptNormalize = 5242880 MaxZipTypeRcg = 1048576 MaxPartitions = 50 MaxIconsPE = 100 ScanOnAccess = yes OnAccessIncludePath disabled OnAccessExcludePath disabled OnAccessExcludeUID disabled OnAccessMaxFileSize = 10 DevACOnly disabled DevACDepth disabled DevPerformance disabled DevLiblog disabled DisableCertCheck = yes Config file: freshclam.conf --- StatsHostID disabled StatsEnabled disabled StatsTimeout disabled LogFileMaxSize = 4294967295 LogTime = yes LogSyslog disabled LogFacility = LOG_LOCAL6 LogVerbose disabled LogRotate = yes PidFile = /var/run/clamav/freshclam.pid DatabaseDirectory = /var/lib/clamav Foreground disabled Debug disabled AllowSupplementaryGroups disabled UpdateLogFile = /var/log/clamav/freshclam.log DatabaseOwner = clamav Checks = 24 DNSDatabaseInfo = current.cvd.clamav.net DatabaseMirror = db.local.clamav.net, database.clamav.net PrivateMirror disabled MaxAttempts = 5 ScriptedUpdates = yes TestDatabases = yes CompressLocalDatabase disabled ExtraDatabase disabled DatabaseCustomURL disabled HTTPProxyServer disabled HTTPProxyPort disabled HTTPProxyUsername disabled HTTPProxyPassword disabled HTTPUserAgent disabled NotifyClamd = /etc/clamav/clamd.conf OnUpdateExecute disabled OnErrorExecute disabled OnOutdatedExecute disabled LocalIPAddress disabled ConnectTimeout = 30 ReceiveTimeout = 30 SubmitDetectionStats disabled DetectionStatsCountry disabled DetectionStatsHostID disabled
Bug#749027: The ClamAV daemon stops working.
Sorry, That last paragraph should have said that I fixed freshclam on the 20th May. Not the 23rd. So the sequence of events was the upgrade on the 19th; freshclam on the 20th; then the first hang on the 21st. Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748187: open-vm-tools: Move /lib/modules-load.d/open-vm-tools.conf to open-vm-tools-dkms package
Package: open-vm-tools Version: 2:9.4.0-1280544-6 Severity: wishlist Dear Maintainer, I was wondering if you could change the packaging for the open-vm-tools products so that the /lib/modules-load.d/open-vm-tools.conf file is moved from the open-vm-tools package to the open-vm-tools-dkms package instead. It is possible to install and use the open-vm-tools package without needing the open-vm-tools-dkms package. When doing so, boot up results in an error message being written to the console about failing to load the vmhgfs module. My logic behind this request is that most of the VMware kernel modules are part of the standard Linux kernel these days. Installing the open-vm-tools-dkms package only results in the following VMware kernel modules being built on the current Debian kernels: - /lib/modules/$(uname -r)/updates/dkms/vmhgfs.ko - /lib/modules/$(uname -r)/updates/dkms/vmxnet.ko - /lib/modules/$(uname -r)/updates/dkms/vsock.ko The first two are the only extra modules, with the last one replacing the following module that comes with the standard kernel: /lib/modules/$(uname -r)/kernel/net/vmw_vsock/vsock.ko In our environment we have no need for the extra two modules. Avoiding installing the open-vm-tools-dkms package means there is no need to install the dkms; gcc compiler; libraries; and other dependencies, resulting in a leaner, more secure installation. Since the vmhgfs.ko module is not part of the standard kernel, there is no point trying to load it unless it has been compiled, and that doesn't happen unless the open-vm-tools-dkms package has been installed anyway. Regards, Jim Barber -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-tools depends on: ii libc6 2.18-6 ii libdumbnet1 1.12-4 ii libfuse2 2.9.3-10 ii libgcc1 1:4.9.0-3 ii libglib2.0-0 2.40.0-3 ii libicu52 52.1-3 ii libprocps31:3.3.9-4 ii libstdc++64.9.0-3 Versions of packages open-vm-tools recommends: ii ethtool 1:3.13-1 pn zerofree none Versions of packages open-vm-tools suggests: pn open-vm-tools-desktop none -- Configuration Files: /etc/vmware-tools/tools.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739254: [Pkg-nagios-devel] Bug#739254: nagios-plugins-basic: check_ssh causing remote servers to log Connection reset by peer messages.
Hi Jan. I have installed version 1.5-3 of the nagios-plugins* packages. I can confirm that I no longer have the remote systems reporting ssh connections being reset. So this bug is fixed and can be closed I'd say. Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739254: [Pkg-nagios-devel] Bug#739254: nagios-plugins-basic: check_ssh causing remote servers to log Connection reset by peer messages.
On 17/02/2014 5:21 PM, Jan Wagner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jim, thanks for taking the time to report the issue. Maybe this is caused due the fix of #734811. But could you please describe the system that is affected? Thanks, Jan. Hi Jan. I'm not 100% sure what you are asking of me, but I'll try to answer your question. We have an Icinga monitoring server that runs numerous checks against various hosts around our network. This is the host that I upgraded the nagios-plugin* packages on, and then had to back them out again to the older version. One of those checks run by the Icinga server is using the check_ssh plugin, and it is that check that is causing the remote monitored hosts to log the error message. The Icinga server is primarily running Debian 'testing' packages, but has a couple of 'unstable' packages that didn't filter down to testing yet. The remote monitored hosts are all Debian systems of various ages. The versions of the openssh-server package that I've seen installed on these hosts are: 6.0p1-4 6.2p2-3 6.2p2-4 6.4p1-2 6.4p1-3 All of these are outputting the error when the Icinga server is checking their SSH daemon via check_ssh, so it doesn't seem to matter what the version of the remote SSH daemon is. Many of these monitored hosts are on the same 10Gbit LAN as the Icinga server, while some are across a WAN with a 10Mbit connection. The speed of the link doesn't seem to have an impact on the results seen above. Is there anything specific that you need to know that I haven't covered above? Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739254: nagios-plugins-basic: check_ssh causing remote servers to log Connection reset by peer messages.
Package: nagios-plugins-basic Version: 1.5-2 Severity: normal Dear Maintainer, Today I updated the nagios-plugins* packages from version 1.5-1 to 1.5-2 on our Icinga server. After that, remote hosts being monitored by the check_ssh plugin were logging error messages like the following: sshd[7315]: fatal: Read from socket failed: Connection reset by peer [preauth] The rsyslog daemon on the monitored hosts is placing these messages in their /var/log/auth.log files by default. The Icinga server is checking these hosts around every 5 mins each, and they all email these messages back to the system administrators via logcheck. I downgraded the nagios-plugins* packages back to version 1.5-1 on the Icinga server again and the messages ceased to occur on the monitored hosts. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nagios-plugins-basic depends on: ii iputils-ping 3:20121221-5 ii libc6 2.17-97 ii libssl1.0.01.0.1f-1 ii nagios-plugins-common 1.5-2 ii procps 1:3.3.9-2 ii ucf3.0027+nmu1 nagios-plugins-basic recommends no packages. Versions of packages nagios-plugins-basic suggests: ii icinga 1.9.3-2+b1 -- no debconf information Regards, -- Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735375: open-vm-tools: Failed to get vmstats message every 30s
Package: open-vm-tools Version: 2:9.4.0-1280544-5 Severity: normal Hi Bernd, After upgrading open-vm-tools* packages from version 2:9.2.3-1031360-7+b1 to version 2:9.4.0-1280544-5 I am seeing the following messages in /var/log/syslog every 30 seconds: Jan 15 10:00:11 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. Jan 15 10:00:41 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. Jan 15 10:01:11 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. Jan 15 10:01:41 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. Jan 15 10:02:11 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. Jan 15 10:02:41 monitor vmsvc[1497]: [ warning] [guestinfo] Failed to get vmstats. . . . This seems to be a partial re-occurrance of bug 639767 that I reported in Aug 2011. I suspect it may also be related to bug 734547 since it is the lack of procps support that causes this error. Regards, Jim Barber -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-tools depends on: ii libc6 2.17-97 ii libdumbnet1 1.12-4 ii libfuse2 2.9.2-4 ii libgcc1 1:4.8.2-12 ii libglib2.0-0 2.36.4-1 ii libicu52 52.1-3 ii libstdc++64.8.2-12 Versions of packages open-vm-tools recommends: ii ethtool 1:3.11-1 ii open-vm-tools-dkms 2:9.4.0-1280544-5 ii zerofree1.0.2-1 Versions of packages open-vm-tools suggests: pn open-vm-tools-desktop none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729540: closed by Bernd Zeimetz b...@debian.org (Bug#729540: fixed in open-vm-tools 2:9.4.0-1280544-1)
]; \ ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/./shared/vmci_iocontrols.h:64:4: note: in expansion of macro ‘ASSERT_ON_COMPILE’ ASSERT_ON_COMPILE(sizeof (void *) == 8); ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/./shared/vmci_iocontrols.h: In function ‘VMCIPtrToVA64’: /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/./shared/vm_assert.h:366:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs] typedef char AssertOnCompileFailed[AssertOnCompileMisused]; \ ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/./shared/vmci_iocontrols.h:93:4: note: in expansion of macro ‘ASSERT_ON_COMPILE’ ASSERT_ON_COMPILE(sizeof ptr = sizeof (VA64)); ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/linux/af_vsock.c: In function ‘__VSockVmciCreate’: /var/lib/dkms/open-vm-tools/9.4.0/build/vsock/linux/af_vsock.c:3150:18: error: incompatible types when assigning to type ‘uid_t’ from type ‘kuid_t’ vsk-owner = current_uid(); ^ make[4]: *** [/var/lib/dkms/open-vm-tools/9.4.0/build/vsock/linux/af_vsock.o] Error 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.4.0/build/vsock] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-amd64' make: *** [vsock.ko] Error 2 make: Leaving directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vsock' It also failed for the 3.10 kernel that I was previously running, but I didn't keep the log for that. Some packages that are installed on the system I tried to compile it for that may be of relevance are: # dpkg --list | grep -P '^ii\s+(open-vm|linux-(headers|image|kbuild|libc)|dkms|make\s|gcc(\s|-4))' ii dkms2.2.0.3-1.2allDynamic Kernel Module Support Framework ii gcc 4:4.8.2-1 amd64 GNU C compiler ii gcc-4.8 4.8.2-10 amd64 GNU C compiler ii gcc-4.8-base:amd64 4.8.2-10 amd64 GCC, the GNU Compiler Collection (base package) ii gcc-4.8-doc 4.8.2-2all documentation for the GNU compilers (gcc, gobjc, g++) ii gcc-4.8-multilib4.8.2-10 amd64 GNU C compiler (multilib files) ii linux-headers-3.12-1-amd64 3.12.6-2 amd64 Header files for Linux 3.12-1-amd64 ii linux-headers-3.12-1-common 3.12.6-2 amd64 Common header files for Linux 3.12-1 ii linux-headers-amd64 3.12+55amd64 Header files for Linux amd64 configuration (meta-package) ii linux-image-3.12-1-amd643.12.6-2 amd64 Linux 3.12 for 64-bit PCs ii linux-image-amd64 3.12+55amd64 Linux for 64-bit PCs (meta-package) ii linux-kbuild-3.12 3.12.6-1 amd64 Kbuild infrastructure for Linux 3.12 ii linux-libc-dev:amd643.12.6-2 amd64 Linux support headers for userspace development ii make3.81-8.3 amd64 An utility for Directing compilation. ii open-vm-tools 2:9.4.0-1280544-1 amd64 Open VMware Tools for virtual machines hosted on VMware (CL ii open-vm-tools-dkms 2:9.4.0-1280544-1 allOpen VMware Tools for virtual machines hosted on VMware (DK Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725937: needrestart: Exclude sudo from list of services to restart
Package: needrestart
Version: 0.3-1
Severity: minor
Hi Patrick,
When performing updates via 'sudo aptitude' then often (always?)
needrestart recommends that sudo be restarted.
Since sudo isn't a service, then it should probably be added to the
$nrconf{blacklist} variable in the /etc/needrestart/needrestart.conf
to skip it.
Regards,
Jim Barber
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages needrestart depends on:
ii dpkg 1.17.1
ii libmodule-find-perl 0.11-1
ii perl 5.18.1-4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721810: needrestart: Always wants to restart openssh-server and dbus
Regarding the restart of dbus. I made the mistake of answering Y to a restart of dbus on a desktop system. This immediately killed X (and so all my X applications) and gdm outright and dropped me back to a login: prompt on the text based virtual console. Further research shows that it seems to be a bad idea to restart the dbus process. I'm not sure if there are ways to determine if it is safe to restart dbus or not, I've restarted it in the past on headless systems without encountering any issues, but perhaps I was just lucky? Maybe dbus should be added to a list of processes that needrestart shouldn't restart? Regards, -- Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717154: open-vm-tools-dkms: Fails to build against Linux 3.10
Hi. The latest entry in the /usr/share/doc/open-vm-tools-dkms/changelog.Debian.gz file says: open-vm-tools (2:9.2.3-1031360-6) unstable; urgency=low * Correcting syntax of file entries in copyright. * Adding section override for open-vm-tools-dkms. * Enforcing build with gcc 4.7 for the time being. * Orphaning package. -- Daniel Baumann m...@daniel-baumann.ch Tue, 16 Jul 2013 10:18:50 +0200 Does that last entry, Orphaning package, mean that open-vm-tools no longer has a maintainer and so has no one to fix this bug? The 3.10 kernel and open-vm-tools-dkms have both gone into testing now, and testing no longer has the 3.9 kernel. Regards, -- Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680714: Please package Bacula 5.2.13
Hi. Bacula 5.2.6 is quite old now and there have been a number of improvements made to Bacula since then. The latest version as far as I can tell is Bacula 5.2.13 released on 19th Feb 2013. If you have time to package up a newer version it would be appreciated. Thanks, -- Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715730: [Mayhem] Bug report on nagios-plugins-basic: check_by_ssh crashes with exit status 139
I believe the problem is caused by the 'fix' to bug 709297. The package maintainer has tried to introduce the ability to pass parameters to Nagios checks by changing them from: command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' to: command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' '$ARG1$' If no extra arguments are passed, it forces an empty parameter to be passed to the command which causes a problem. I suspect the fix it not to wrap the $ARG1$ within quotes like so: command_line/usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' $ARG1$ This means the parameters passed by the user can still be done, but if nothing was passed, does not result in an empty positional parameter being passed to the command. Regards, Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677810: snort: white/blacklist
Package: snort Version: 2.9.2.2-2 I have also encountered this problem when installing snort for the first time on a freshly installed Debian host. To get the package to configure I did the following steps: - I edited /etc/snort/snort.conf and changed the following two lines: var WHITE_LIST_PATH ../rules var BLACK_LIST_PATH ../rules to: var WHITE_LIST_PATH ./rules var BLACK_LIST_PATH ./rules - Then I created empty white/black list files like so: touch /etc/snort/rules/black_list.rules touch /etc/snort/rules/white_list.rules - Then I could get the package to configure by running: dpkg --configure --pending Regards, -- Jim Barber -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652679: My previous email is not a solution
Previously I had posted what worked for me. It had been working for a while but I'm now back in a state where it isn't working after winbind was restarted. I suspect after a reboot I would be good as per Dale's comments above, but I can't during this time. All the usual stuff works, except group name mapping is flaky. I also get errors like the following in my winbind log files: [2012/07/17 08:00:11.778372, 0] winbindd/winbindd_ads.c:1084(lookup_groupmem) ads_ranged_search failed with: Time limit exceeded I'll probably have to back out to 3.5.11 again when I get a chance. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652679: Possible solution to bug 652679?
Hi. Tonight I had a chance to tackle this problem again. I upgraded to version 3.6.6-2 of the winbind package and I still had the same problem. I ran a 'testparm -s' and it reported that the following entries in my configuration file were deprecated: idmap uid = 1-2 idmap gid = 1-2 They were just the example entries in the /etc/samba/smb.conf file that I uncommented. I commented these entries out again and replaced them with the following lines: idmap config * : backend = rid idmap config * : range = 1-2 I then restarted winbind. At first, when running ls against my home directories the UIDs and GIDs were just showing numbers. But a short while later they all looked correct (like it was building some sort of index somewhere). Anyway, the problem now seems to have been fixed. So maybe winbind not only deprecated those old options, but now doesn't work with them? Anyway, it's something for the others who are having this problem to try. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672801: apt-cache-ng cronjob fails
I have also seen these errors recently on three separate installs of apt-cacher-ng that I have at different sites. Two of the sites have fast fibre channel links to the Internet and one has a much slower ADSL connection. The most recent cronjob failure reports the following: /etc/cron.daily/apt-cacher-ng: Error(s) occured while updating volatile index files for apt-cacher-ng. Please visit http://proxy:3142/acng-report.html to rerun the expiration manually or check the error message(s) in the current log file(s). Check error messages in /var/log/apt-cacher-ng/maint_1337639106.log The log file above contains a number of 2 Resource temporarily unavailable error messages in it. The errors are intermittent, although seem to be more likely to occur than to not. When I manually use the web GUI to run the 'Start Scan and/or Expiration' then often it fails with: 502 Resource temporarily unavailable Then subsequent runs may or may not exhibit this problem. The version of apt-cacher-ng I am running at all sites is: ||/ NameVersion Description +++-===-===-== ii apt-cacher-ng 0.7.3-1 caching proxy server for software repositories I am using the 'sid' distribution at one location and the 'testing' distribution at the other two. -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502305: ulogd2: Status of package?
Hi Pierre. In your last email from Nov last year, you mention a partial fix for the Multiarch problems. The package files at https://www.wzdftpd.net/downloads/ulogd2-deb/ haven't been updated since 27th Dec 2010. It sounds like you've made a few changes since then. Would you be able to put your more up to date files somewhere so that we can build them please? Based on the old files, to fix the build dependencies for sid as it stands today I need to apply the following patch: --- ulogd-2.0.0~beta4/debian/control.orig 2010-12-27 18:21:25.0 +0800 +++ ulogd-2.0.0~beta4/debian/control2012-05-16 12:58:33.977786179 +0800 @@ -7,11 +7,11 @@ libnfnetlink-dev (= 0.0.13), libnetfilter-conntrack-dev (= 0.0.28), libnetfilter-log-dev (= 1.0), -libmysqlclient15-dev | libmysqlclient-dev, +libmysqlclient-dev, libpq-dev, -libpcap-dev, -libsqlite-dev, -libdbi0-dev +libpcap-dev | libpcap0.8-dev, +libsqlite3-dev, +libdbi-dev Standards-Version: 3.9.1 Homepage: http://www.netfilter.org/projects/ulogd/ #Vcs-Git: git://git.debian.org/collab-maint/ulogd.git However as Nils Olav Fossum reports, the build will still fail because it can't find libraries that are now in the multiarch area. I think mysql libraries are now also in the multiarch area along with the pcap libraries that Nils Olav Fossum identified. So I guess somehow the LDFLAGS should have a -L/usr/lib/$(DEB_HOST_MULTIARCH) parameter added to expand the library search path. I wasn't really sure how to do that though... I have some theories but not enough time to try. I figured it would be better just to email and see if we can get access to your latest package files and then work from there. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657948: udev: Please re-enable /dev/sg* devices again.
Package: udev Version: 175-1 Severity: wishlist Dear Maintainer, In version 175-1 of udev there is the following changelog entry: * 80-drivers.rules: stop automatically loading the obsolete sg driver. By doing this, if I upgrade udev from version 1.72-1 to 175-1 or newer, then I can no longer control a tape library changer. The Linux kernel can see the tape library changer as /dev/sch0 with the new udev package, but the mtx package has no way of talking to this sort of device. Nor is there any other package in Debian (that I can find) that is able to talk to the /dev/sch0 device. Therefore, in order to use the tape library I need to use the mtx package which is only able to talk to the /dev/sg* devices that used to be created. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652679: [Pkg-samba-maint] Bug#652679: Winbind authentication and wbinfo, -i user no longer work after upgrading to 3.6.1
I also encountered this problem. The 'winbind -i user' seems to work for some of my users in the AD but not for others. It might have to do with the level of nesting of OUs that the users are within? Anyway, I tried upgrading to the 3.6.2-1 Debian package of Winbind and the problem still exists in this version also. I've have to back out to version 3.5.11 for now. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651130: console-common breaking services
Hi. I also have a similar problem but it is also making the new udev uninstallable (hopefully that hasn't made my system unbootable). Here's the output I have at the moment: Setting up console-common (0.7.86) ... Looking for keymap to install: NONE insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service hwclock at depth 13 insserv: loop involving service checkroot at depth 12 insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mtab at depth 13 insserv: There is a loop between service nfs-common and hwclock if started insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mountnfs at depth 10 insserv: loop involving service nfs-common at depth 9 insserv: loop involving service rpcbind at depth 8 insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service mdadm-raid at depth 2 insserv: loop involving service nfs-kernel-server at depth 16 insserv: There is a loop between service mountall and checkfs if started insserv: loop involving service resolvconf at depth 16 insserv: loop involving service urandom at depth 27 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing console-common (--configure): subprocess installed post-installation script returned error exit status 1 Setting up udev (175-3) ... Stopping the hotplug events dispatcher: udevd. Starting the hotplug events dispatcher: udevd. update-initramfs: deferring update (trigger activated) insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service hwclock at depth 13 insserv: loop involving service checkroot at depth 12 insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mtab at depth 13 insserv: There is a loop between service nfs-common and hwclock if started insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mountnfs at depth 10 insserv: loop involving service nfs-common at depth 9 insserv: loop involving service rpcbind at depth 8 insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service mdadm-raid at depth 2 insserv: loop involving service nfs-kernel-server at depth 16 insserv: There is a loop between service mountall and checkfs if started insserv: loop involving service resolvconf at depth 16 insserv: loop involving service urandom at depth 27 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing udev (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.1.0-1-686-pae Errors were encountered while processing: console-common udev -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages console-common depends on: ii console-data 2:1.12-1 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.1 ii lsb-base 3.2-28 Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627107: ITP: rtsadmin -- administration tool for managing LIO core target
Hi. I might be able to help you out with the testing of this package. We have an old Windows server that was running SANmelody to turn it into a SAN server. As of a couple of days ago we decommissioned it. It is a SuperMicro server with a 3WARE RAID card and some hot swappable disks. It is running a pair of QLogic 2462 Fibre Channel host bus adapters. My plan would be to turn this into a SAN for a couple of VMware ESXi servers via the Fibre Channel connections. I would like to try a Linux solution to still use it as a fibre channel attached SAN server. Do you know if the QLogic Fibre Channel part of RTSadmin is ready? -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627107: ITP: rtsadmin -- administration tool for managing LIO core target
Also I noticed an announcment to the Linux-SCSI mailing list on the 20-Sep-2011 that RTSadmin was being renamed to targetcli. The GIT repository for RTSadmin was no longer being updated and that a new git://linux-iscsi.org/targetcli.git repository has been created instead. A link to the announcement is below. http://www.spinics.net/lists/linux-scsi/msg54586.html Does you experimental package take into account this fairly recent change? Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648686: Bug in bonding_err_ plugin
Package: munin-node
Version: 1.4.6-1
Severity: normal
Dear Maintainer,
I rebooted a system that was using kernel 2.6.32 into one running kernel 3.0.0
After that the /usr/share/munin/plugins/bonding_err_ plugin stopped working.
Here is an example of the results returned.
$ telnet localhost munin
Trying ::1...
Connected to localhost.
Escape character is '^]'.
# munin node at wwvrt01.nsw.ddihealth.com
fetch bonding_err_bond0
if_eth0.value if_eth1.value if_eth2.value if_eth3.value
.
The code for this plugin contains the following line:
grep -A 2 ^Slave Interface: ${if} ${PROCDIR}/${BONDINGIF} | grep
Link Failure Count: | cut -d -f 4
The 'grep -A 2' only returns two lines after the matched line.
So for eth0 (which is part of bond0) I get the following results when just
running the grep:
$ grep -A 2 ^Slave Interface: eth0 /proc/net/bonding/bond0
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Those lines don't contian the 'Link Failure Count:' line that grep looks for in
the pipeline.
The full set of entries for interfaces that form the bond0 device look as
follows:
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:71:9a:f0
Aggregator ID: 4
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:71:9a:f1
Aggregator ID: 4
Slave queue ID: 0
Slave Interface: eth2
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:71:9a:f4
Aggregator ID: 4
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:71:9a:f5
Aggregator ID: 4
Slave queue ID: 0
Instead of 'grep -A 2' it should instead match all the lines from the 'Slave
Interface:' line up to the next blank line or EOF.
This way it'll work no matter the order of the lines nor how many get added in
the future.
I have achieved this by using sed instead of grep.
I've replaced:
grep -A 2 ^Slave Interface: ${if} ${PROCDIR}/${BONDINGIF} | grep
Link Failure Count: | cut -d -f 4
With:
sed 0,/^Slave Interface: ${if}/d; /^\$/,\$d ${PROCDIR}/${BONDINGIF} |
grep Link Failure Count: | cut -d -f 4
Or in patch form it is as follows:
--- bonding_err_.orig 2011-11-14 12:42:18.332577791 +1100
+++ bonding_err_2011-11-14 12:44:24.594788291 +1100
@@ -97,7 +97,7 @@
grep ^Slave Interface: ${PROCDIR}/${BONDINGIF} | while read a b if; do
fieldname=$(clean_fieldname $if)
echo -n if_${fieldname}.value
- grep -A 2 ^Slave Interface: ${if} ${PROCDIR}/${BONDINGIF} | grep Link
Failure Count: | cut -d -f 4
+ sed 0,/^Slave Interface: ${if}/d; /^\$/,\$d ${PROCDIR}/${BONDINGIF} | grep
Link Failure Count: | cut -d -f 4
done
After making this change, the results are now returned.
# telnet localhost munin
Trying ::1...
Connected to localhost.
Escape character is '^]'.
# munin node at wwvrt01.nsw.ddihealth.com
fetch bonding_err_bond0
if_eth0.value 0
if_eth1.value 0
if_eth2.value 0
if_eth3.value 0
.
Regards,
Jim Barber
--
DDI Health
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages munin-node depends on:
ii adduser 3.113
ii gawk1:3.1.8+dfsg-0.1
ii libnet-server-perl 0.99-3
ii lsb-base3.2-28
ii munin-common1.4.6-1
ii perl5.12.4-6
ii procps 1:3.2.8-11
Versions of packages munin-node recommends:
ii libnet-snmp-perl 6.0.1-2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616689: Root-on-LVM setup fails often due to timing issues
I too have issues with this problem. For all of our Dell PowerEdge servers I've needed to use the rootdelay parameter. Ages ago I used to have it set to rootdelay=10 Then a number of months ago after some upgrades the failure was happening again. I had to bump it up to rootdelay=20 Today I upgraded a virtual machine running on VMware VSphere from kernel 2.6.32 to 3.0.0. It is also exhibiting the boot problem of not finding the volume group fro the root mount point. Adding rootdelay to it fixed it. The rootdelay parameter seems to be a moving target, and increasing it too much adds an unnecessary delay to boots. I was finally going to report this when I came across this bug report. I'll try the scsi_mod.scan=sync option as maybe this won't cause unnecessary delays? But it would be good to have this fixed as standard. Francesc, maybe try 'dpkg-reconfigure grub-pc' and specify the parameters that way? You might have more luck with that... -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644960: munin-limits cannot use send_nsca to send more than one message
Package: munin Version: 1.4.6-1 Severity: normal Dear Maintainer, I upgraded the munin package from version 1.4.5-3 to 1.4.6-1 Since then, I noticed that the passive checks in Nagios were not being updated properly. Further investigation led me to the following errors in the /var/log/munin/munin-limits.log file: [PERL WARNING] print() on closed filehandle $pipe at /usr/share/perl5/Munin/Master/LimitsOld.pm line 708. After googling I came to the following bug report: http://munin-monitoring.org/ticket/732 The final post of which lead to the following fix: http://munin-monitoring.org/changeset/4400 I applied these changes to my Munin installation and the passive checks for Nagios started to work again. Also note that the above fixes made the cron job noisy since stdout from the send_nsca program was no longer being thrown away. To fix this I had to change my config from: contact.nagios.command /usr/sbin/send_nsca -H nagios.ddihealth.com -c /etc/send_nsca.cfg -to 60 To: contact.nagios.command /usr/sbin/send_nsca -H nagios.ddihealth.com -c /etc/send_nsca.cfg -to 60 /dev/null Regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages munin depends on: ii adduser3.113 ii cron 3.0pl1-120 ii libdigest-md5-perl none ii libhtml-template-perl 2.10-1 ii liblog-log4perl-perl 1.29-1 ii librrds-perl 1.4.3-3.1+b2 ii libstorable-perl none ii munin-common 1.4.6-1 ii perl [libtime-hires-perl] 5.12.4-4 ii perl-modules 5.12.4-4 ii rrdtool1.4.3-3.1+b2 ii ttf-dejavu 2.33-2 Versions of packages munin recommends: ii libdate-manip-perl 6.25-1 ii munin-node 1.4.6-1 Versions of packages munin suggests: ii apache2-mpm-worker [httpd] 2.2.21-1 ii libnet-ssleay-perl 1.36-3 ii lynx-cur [www-browser] 2.8.8dev.9-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639767: open-vm-tools: Warning messages every 30s.
Package: open-vm-tools Version: 2:8.4.2+2011.08.21-471295-1 Severity: normal Every 30 seconds I am getting two log entries written to syslog: vmsvc[712]: [ warning] [guestinfo] Failed to get nic info. vmsvc[712]: [ warning] [guestinfo] Failed to get vmstats. This makes the /var/log/syslog file grow unnecessarily and tools like logcheck end up spamming me about the messages. Apparently the 'nic info' message is produced if open-vm-tools is compiled using --without-dnet and the 'vmstats' message is produced if open-vm-tools is compiled using --without-procps. I can turn these messages off by adding the following to the /etc/vmware-tools/tools.conf file: [logging] vmsvc.level=error However that would turn off all other warnings so probably isn't a good default to have. Possible solutions I can think of to fix this are: - Demote the message levels for these two messages from warning to debug. - Link against the appropriate libraries. Although for amd64 there seems to be specific check to turn off libproc linking that might be there for a good reason? I'm sure you can probably think of others. Regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-tools depends on: ii libc6 2.13-16Embedded GNU C Library: Shared lib ii libfuse2 2.8.5-4Filesystem in Userspace (library) ii libgcc1 1:4.6.1-4 GCC support library ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libicu44 4.4.2-2International Components for Unico ii libstdc++64.6.1-4GNU Standard C++ Library v3 Versions of packages open-vm-tools recommends: ii ethtool 1:2.6.39-1 display or change Ethernet device ii open-vm-sour 2:8.4.2+2011.08.21-471295-1 Source for VMware guest systems dr ii zerofree 1.0.1-2 zero free blocks from ext2/3 file- Versions of packages open-vm-tools suggests: pn open-vm-toolbox none (no description available) -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635478: debian-installer: Enable VMware modules on installer images.
Subject: debian-installer: Enable VMware modules on installer images. Package: debian-installer Severity: wishlist *** Please type your report below this line *** Hi. For quite a while now, the linux-image-* packages have had support for the VMware modules such as vmxnet3 and vmw_pvscsi. However, the daily builds for the Debian installer do not. It would be very handy if at least the vmxnet3 and vmw_pvscsi modules were enabled by default in the businesscard/netinstaller ISO files. That way, new virtual machines created on VMware ESX/ESXi can use the VMXNET3 network adapter; and a Paravirtual SCSI controller on the boot drive. Without these modules, both the network and hard disk can't be detected at install time unless the slower E1000 network adapter and LSI SCSI controllers are used instead. The E1000 network adapter can easily be changed to a VMXNET3 adapter after the install, but the Paravirtual SCSI change on the boot device is non-trivial. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632804: DNAT/REDIRECT generating wrong port number for ctorigdstport
It appears that reportbug left my subject off when I submitted the report. If anyone has the access to add a proper subject, it was submitted as something like: DNAT/REDIRECT generating wrong port number for ctorigdstport Some more information on this bug. The problem only occurs for rules that are taking traffic to one port and directing it to a different port (whether it be on the same host or on a remote host). It does not occur for rules that DNAT traffic to another host on the same destination port number. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632804: (no subject)
Package: iptables Version: 1.4.11.1-2 Severity: important I have encountered a problem with iptables and kernels older than 2.6.39. I manage firewall rules with shorewall, and I have rules to redirect outgoing HTTP traffic to a transparent proxy server. An example of such a rule in shorewall is: HTTP(DNAT) lan dmz:$PROXY:3129 - - - !$PROXY_BYPASS The server is running the following kernel package: ii linux-image-2.6.38-2-amd642.6.38-3 Linux 2.6.38 for 64-bit PCs Running 'iptables -L -n' shows the following rule (white-space compacted): ~excl0 tcp -- 0.0.0.0/0 10.128.6.3 tcp dpt:3129 ctorigdstport 20480 /* HTTP */ The 20480 value assigned to the ctorigdstport parameter is incorrect. This should be 80. I created a virtual machine to reproduce the probem and found that it happened with a 2.6.32 and 2.6.38 kernel. But once I booted it into the 2.6.39 kernel, all was fine. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages iptables depends on: ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libnfnetlink0 1.0.0-1Netfilter netlink library iptables recommends no packages. iptables suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626906: libnet-snmp-perl: Deprecation warnings with perl 5.12
Package: libnet-snmp-perl Version: 5.2.0-4 Severity: normal Hi. I've upgraded from perl version 5.10.1-20 to 5.12.3-6, and the new version produces deprecation warnings. When using the SNMP perl module located in /usr/share/perl5/Net/SNMP.pm I get messages like the following: Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 588. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 655. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 708. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 764. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 869. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 952. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1028. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1103. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1168. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1325. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1531. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1549. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1563. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1577. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1591. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1613. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1633. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1653. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1674. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1702. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1737. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1846. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1968. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1973. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1978. Use of :locked is deprecated at /usr/share/perl5/Net/SNMP.pm line 1983. Maybe a newer version of the SNMP perl module will fix the problem? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619877: rpc.mountd: svc_tli_create: could not bind to requested address
I had the exact same problem. I couldn't workout out what was wrong because I didn't have the time to do so. In my /var/log/daemon.log file I got the following messages when trying to start the nfs-common init script: Mar 28 22:17:14 gecko rpc.statd[9340]: Version 1.2.3 starting Mar 28 22:17:14 gecko sm-notify[9341]: Version 1.2.3 starting Mar 28 22:17:14 gecko sm-notify[9341]: Already notifying clients; Exiting! Mar 28 22:17:14 gecko rpc.statd[9340]: failed to create RPC listeners, exiting I ended up going back to the 1.2.2-5 version of the packages which worked again. The following system information is from when I went back to the older version of the package, but gives an idea of where everything else is at. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.38-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1scripts for initializing and shutt ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1support for getting/setting POSIX. ii libcomerr2 1.41.12-2 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9+dfsg-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.2-1 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii librpcsecgss30.19-2 allows secure rpc communication us ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii netbase 4.45Basic TCP/IP networking system ii portmap 6.0.0-3 RPC port mapper ii ucf 3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614318: logcheck sends an email even when there are no entries after filtering
Hi. This has just started happening on one of our virtual machines running (VM) on an ESXi server. Logcheck started sending me the same empty emails after the VM was rebooted early Feb 20th and some packages were upgraded immediately afterwards. I don't know if it was one of the updates below, or if the reboot triggered it somehow (putting some other package that was previously upgraded into effect). The version of logcheck in question is: ||/ NameVersion Description +++-===-===-== ii logcheck1.3.13 mails anomalies in the system logfiles to the administrator I am also running logcheck version 1.3.13 on a number of other VMs that are not exhibiting the problem. However these VMs have not been rebooted and haven't had the newer versions of the packages below installed on them. They are in production use so can't mess with them at this stage. But I can work with the VM that is exhibiting this problem if you need me to try anything. The packages that were upgraded after the reboot were: ||/ NameVersion Description +++-===-===-== ii bash4.1-3 The GNU Bourne Again SHell ii bash-completion 1:1.3-1 programmable completion for the bash shell ii groff-base 1.21-4 GNU troff text-formatting system (base system components) ii iproute 20110107-2 networking and traffic control tools ii libgeoip1 1.4.7~beta10+dfsg-4 A non-DNS IP-to-country resolver library ii libgnutls26 2.10.4-2the GNU TLS library - runtime library ii libgpg-error0 1.10-0.3library for common error values and messages in GnuPG components ii libpipeline11.1.0-1 pipeline manipulation library ii libsensors4 1:3.2.0-1 library to read temperature/voltage/fan sensors ii libusb-0.1-42:0.1.12-17 userspace USB programming library ii libwireshark-data 1.4.3-2 a network packet dissection library -- data files ii libwireshark0 1.4.3-2 a network packet dissection library -- shared library ii libwiretap0 1.4.3-2 a network packet capture library -- shared library ii libwsutil0 1.4.3-2 network packet dissection utilities library -- shared library ii libx11-62:1.4.1-4 X11 client-side library ii libx11-data 2:1.4.1-4 X11 client-side library ii libxcb-render0 1.7-2 X C Binding, render extension ii libxcb1 1.7-2 X C Binding ii libxext62:1.2.0-2 X11 miscellaneous extension library ii login 1:4.1.4.2+svn3283-3 system login tools ii man-db 2.5.9-4 on-line manual pager ii passwd 1:4.1.4.2+svn3283-3 change and administer password and group data ii rsyslog 5.7.3-1 enhanced multi-threaded syslogd ii tshark 1.4.3-2 network traffic analyzer - console version ii ttf-dejavu 2.32-1 Metapackage to pull in ttf-dejavu-core and ttf-dejavu-extra ii ttf-dejavu-core 2.32-1 Vera font family derivate with additional characters ii ttf-dejavu-extra2.32-1 Vera font family derivate with additional characters ii wireshark-common1.4.3-2 network traffic analyzer - common files Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614318: logcheck sends an email even when there are no entries after filtering
I have found the package that is at fault. It was the upgrade of rsyslog from version 4.6.4-2 to 5.7.3-1 As per rsyslog bug #612829 the daemon no longer strips off trailing blanks from the syslog output. In my /var/log/syslog file there are blank lines every time my snmp daemon logs something: eg. Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Instead of: Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] The fix is to add the following pattern to the ignore.d.server list for logcheck: ^\s*$ This stops it reporting on the blank lines, or lines that consist of only white-space. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612829: rsyslog and embedded whitespace
I've found my SNMP daemon is also logging a blank line after each entry: eg. Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] The old version would have logged it as follows instead: Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] Feb 21 13:28:51 monitor snmpd[1310]: Connection from UDP: [10.128.0.1]:37645-[10.128.0.6] This is the cause of bug #614318 against the logcheck package. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502305: Temporary packages for ulogd2 : Build dependency wrong
Hi. I just tried to build your packages on a Debian unstable (sid) server for the i386 architecture. I used the following technique... - Downloaded the following files from: https://www.wzdftpd.net/downloads/ulogd2-deb/ ulogd_2.0.0~beta4-1.debian.tar.gz ulogd_2.0.0~beta4-1.dsc ulogd_2.0.0~beta4.orig.tar.bz2 - Unpacked the sources and moved into the unpacked directory: dpkg-source -x ulogd_2.0.0~beta4-1.dsc cd ulogd-2.0.0~beta4 - Made sure I had the build dependencies installed: dpkg-checkbuilddeps It revealed I had to install the following packages: autotools-dev libdbi0-dev libmysqlclient15-dev | libmysqlclient-dev libnetfilter-conntrack-dev libnetfilter-log-dev libpcap-dev libpq-dev libsqlite-dev I satisfied the libsqlite-dev dependency by installing libsqlite0-dev. The libmysqlclient15-dev package does not exist in sid. But libmysqlclient16-dev does instead. I installed the libmysqlclient-dev package which pulls it in anyway. - Built it using the following: dpkg-buildpackage -b -tc -uc -us The build failed because it needed the libsqlite3-dev package installed. Note that the libsqlite3-dev package does not supply the libsqlite-dev dependency as mentioned in the Build-Depends. Further I noticed the package doesn't need libsqlite0-dev at all. So I redid the steps above, but in the debian/control control file I changed the libsqlite-dev build dependency to libsqlite3-dev. I then uninstalled libsqlite0-dev from my system to prove it wasn't needed. Now the build worked successfully. So in summary, the changes to the Build-Depends line in the debian/control file to correct the build are: - Change sqlite-dev to sqlite3-dev - Remove libmysqlclient15-dev OR change it to libmysqlclient16-dev Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502305: Temporary packages for ulogd2 : Configuration changes
Hi. Further to my previous email, I've now installed the newly built package and here are some observations. There is a lack of documentation in the built package. If the build also formatted the doc/ulogd.sgml file in the source area into txt and html files to be installed under the /usr/share/doc/ulogd/ directory, then there will be a lot more useful information on how to configure the new ulogd daemon. I made the following changes to the /etc/ulogd.conf file. Take and leave each of them as you like. I've attached the patch that makes all of these changes to the final installed configuration file. - I've made changes to produce logs in the /var/log/ulogd/ directory like the old ulogd v1.23 did. This way users upgrading from the old ulogd to the new ulogd will still find the files in the same location as before. Likewise I adjusted log file names to match what they were before (removed leading ulogd_) If the package doesn't create the /var/log/ulogd/ directory as part of its install, then it would need to be modified to do this as well. - I changed the log level to notice. I guess you can ignore this, but I've left it in the patch. - I've enabled the ULOG support. This way, people upgrading from the old ulogd daemon to the new one will still have their logging working. This will give them a chance to transition over from ULOG to NFLOG at their convenience. - There was no XML output plugin built with the package. So I've commented that plugin out to remove the error message about it not being found. I guess the other approach is to get the package to build that plugin if possible. - I added commented out plugin entries for the SQLITE3 output plugin, and the PWSNIFF filter plugin (which maybe you don't want to include). - Added a [sqlite3] section for the SQLITE3 plugin to match the example for SQLLITE3 on the old version of ulogd. Regards, -- -- Jim Barber DDI Health --- /etc/ulogd.conf.dpkg-dist 2011-01-07 14:00:16.0 +0800 +++ /etc/ulogd.conf 2011-01-07 14:54:57.0 +0800 @@ -9,10 +9,10 @@ # logfile for status messages -logfile=/var/log/ulogd.log +logfile=/var/log/ulog/ulogd.log # loglevel: debug(1), info(3), notice(5), error(7) or fatal(8) -loglevel=1 +loglevel=5 ## # PLUGIN OPTIONS @@ -26,7 +26,7 @@ plugin=/usr/lib/ulogd/ulogd_inppkt_NFLOG.so -#plugin=/usr/lib/ulogd/ulogd_inppkt_ULOG.so +plugin=/usr/lib/ulogd/ulogd_inppkt_ULOG.so plugin=/usr/lib/ulogd/ulogd_inpflow_NFCT.so plugin=/usr/lib/ulogd/ulogd_filter_IFINDEX.so plugin=/usr/lib/ulogd/ulogd_filter_IP2STR.so @@ -35,15 +35,17 @@ plugin=/usr/lib/ulogd/ulogd_filter_HWHDR.so plugin=/usr/lib/ulogd/ulogd_filter_PRINTFLOW.so #plugin=/usr/lib/ulogd/ulogd_filter_MARK.so +#plugin=/usr/lib/ulogd/ulogd_filter_PWSNIFF.so plugin=/usr/lib/ulogd/ulogd_output_LOGEMU.so plugin=/usr/lib/ulogd/ulogd_output_SYSLOG.so -plugin=/usr/lib/ulogd/ulogd_output_XML.so +#plugin=/usr/lib/ulogd/ulogd_output_XML.so #plugin=/usr/lib/ulogd/ulogd_output_OPRINT.so #plugin=/usr/lib/ulogd/ulogd_output_NACCT.so #plugin=/usr/lib/ulogd/ulogd_output_PCAP.so #plugin=/usr/lib/ulogd/ulogd_output_PGSQL.so #plugin=/usr/lib/ulogd/ulogd_output_MYSQL.so #plugin=/usr/lib/ulogd/ulogd_output_DBI.so +#plugin=/usr/lib/ulogd/ulogd_output_SQLITE3.so plugin=/usr/lib/ulogd/ulogd_raw2packet_BASE.so # this is a stack for logging packet send by system via LOGEMU @@ -53,7 +55,7 @@ #stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU # this is a stack for ULOG packet-based logging via LOGEMU -#stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU +stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU # this is a stack for packet-based logging via LOGEMU with filtering on MARK #stack=log2:NFLOG,mark1:MARK,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU @@ -148,15 +150,15 @@ #numeric_label=0 # optional argument [emu1] -file=/var/log/ulogd_syslogemu.log +file=/var/log/ulog/syslogemu.log sync=1 [op1] -file=/var/log/ulogd_oprint.log +file=/var/log/ulog/oprint.log sync=1 [xml1] -directory=/var/log/ +directory=/var/log/ulog/ sync=1 [pcap1] @@ -202,6 +204,11 @@ pass=changeme procedure=INSERT_OR_REPLACE_CT +[sqlite3] +table=ulog +db=/path/to/sqlite/db +buffer=200 + [dbi1] db=ulog2 dbtype=pgsql
Bug#589388: Another user that had to make a change to get the Logitech DiNovo Edge keyboard working
I have a Logitech DiNovo Edge keyboard that also doesn't work with udev 160-1.
Output of lsusb is:
Bus 004 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 2040:9941 Hauppauge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 004: ID 046d:c714 Logitech, Inc. diNovo Edge Keyboard
Bus 008 Device 003: ID 046d:c713 Logitech, Inc.
Bus 008 Device 002: ID 046d:0b04 Logitech, Inc.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Setting the following in the 70-hid2hci.rules file worked for me:
# Logitech devices (hidraw)
KERNEL==hiddev*, ATTRS{idVendor}==046d, ATTRS{idProduct}==c70[35e], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
KERNEL==hidraw*, ATTRS{idVendor}==046d,
ATTRS{idProduct}==c70[4abc]|c71[34bc], \
RUN+=hid2hci --method=logitech-hid --devpath=%p
Which is basically what Claus Feichtinger in this same bug report did.
So if the next udev version makes sure that 046d:c713 and 046d:c714 are
assigned to hidraw instead of hidev, that would be great :)
Regards,
--
--
Jim Barber
DDI Health
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586168: mimedefang: Please package Miemdefang v 2.69
Package: mimedefang Version: 2.67-3 Severity: wishlist Hi. Today MIMEDefang 2.69 was announced on the mailing list. It is a minor update from 2.68. Version 2.68 was released late Feb 2010 and contains a number of bug fixes for version 2.67 which is currently packaged for Debian. This is a request to package up the newest version please. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages mimedefang depends on: ii adduser 3.112 add and remove users and groups ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib ii libdigest-sha1-perl 2.12-1 NIST SHA-1 message digest algorith ii libio-stringy-perl2.110-4Perl modules for IO from scalars a ii libmailtools-perl 2.06-1 Manipulate email in perl programs ii libmilter1.0.18.14.3-9.1 Sendmail Mail Filter API (Milter) ii libmime-tools-perl5.427-2Perl5 modules for MIME-compliant m ii libperl5.10 5.10.1-13 shared Perl library ii libunix-syslog-perl 1.1-2 Perl interface to the UNIX syslog( ii perl [libmime-base64-perl]5.10.1-13 Larry Wall's Practical Extraction ii psmisc22.11-1utilities that use the proc file s mimedefang recommends no packages. Versions of packages mimedefang suggests: ii clamav 0.96.1+dfsg-1 anti-virus utility for Unix - comm pn graphdefangnone(no description available) pn libarchive-zip-perlnone(no description available) pn libfile-scan-perl none(no description available) ii libhtml-parser-perl3.65-1collection of modules that parse H pn sanitizer none(no description available) ii sendmail 8.14.3-9.1powerful, efficient, and scalable ii spamassassin [libmail-spam 3.3.1-1 Perl-based spam filter using text pn tk8.3 | wish none(no description available) pn wv none(no description available) -- Configuration Files: /etc/default/mimedefang changed [not included] /etc/mail/mimedefang-filter changed [not included] /etc/mail/mimedefang.pl.conf changed [not included] /etc/mail/sa-mimedefang.cf changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584993: libvpb0 hangs during install.
Package: libvpb0 Version: 4.2.46-1 Severity: normal I am trying to install libvpb0 since it is a dependency of asterisk. The server I am installing to has a Sangoma A101 ISDN card in it. It seems that at install time, the package hangs. It prompts me for the country code, but hangs when generating configuration for the ISDN card. Here is the output: r...@pbx:~# aptitude install libvpb0 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information... Done Initializing package states... Done The following NEW packages will be installed: libvpb0 The following packages are RECOMMENDED but will NOT be installed: vpb-driver-source 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/198kB of archives. After unpacking 610kB will be used. Writing extended state information... Done Preconfiguring packages ... Selecting previously deselected package libvpb0. (Reading database ... 31036 files and directories currently installed.) Unpacking libvpb0 (from .../libvpb0_4.2.46-1_amd64.deb) ... Processing triggers for man-db ... Setting up libvpb0 (4.2.46-1) ... Voicetronix hardware configuration helper 4.2.46. This will scan the PCI bus to determine what cards you have and create a set of default config files for them. Scanning PCI bus found 1 cards. Processing ISDN cards... = Card [1] = It is stuck at this line. I've left it for a long time and it won't continue. A ps listing shows that the installation is running the following command: /usr/bin/perl -w /usr/sbin/VpbConfigurator --country=61 If I press ^C to abort the install and run this script manually, I get the following: r...@pbx:~# /usr/bin/perl -w /usr/sbin/VpbConfigurator --country=61 Voicetronix hardware configuration helper 4.2.46. This will scan the PCI bus to determine what cards you have and create a set of default config files for them. Scanning PCI bus found 1 cards. Processing ISDN cards... = Card [1] = Is this a single span [S|s], dual [D|d] or Logging [L|l] card?: [1] is Single span A total of 1 ports will now be configured. = Port [1] = Is this port E1 or T1 ? [E|e|T|t](e): port 1 is E1 Is this port CAS or CCS ? [cas|ccs](ccs): port is CCS Is this port Client or Network? [C|c|N|n](c): port 1 is Client Making wanpipe config files now Done wanpipe1.conf Making openpri.conf config file now... Created OpenPRI config file Processing Analog cards... Found 0 OpenLine4's, 0 OpenSwitch12's and 0 OpenPCI's. Created 1 card config files... On a total of 1 'spans'... Creating vpb.conf file... Done As you can see I am prompted with some questions, of which I answered as per the above. Once the above is done I can then get the package to configure like so: r...@pbx:~# dpkg --configure --pending Setting up libvpb0 (4.2.46-1) ... Things I have tried (with no luck), to try to get the package to install without hanging are: - Assume I can't see the installation questions and blindly answer them. Either it isn't asking me at all, or my input is not being sent to the VpbConfigurator program. - Install and compile the vpb-driver-source package and install the resulting modules prior to install. - Change my debconf question priority from low to high prior to install. - Change debconf to use readline instead of dialog in the hope of seeing installation questions. - Configure Sangoma Wanpipe dirvers first so that they are using the ISDN card, prior to the install. In the end, I don't think I even want this to use my ISDN card anyway? The only reason it is being installed is to satisfy dependencies for Asterisk. I just want to use the Sangoma wanpipe drivers in conjunction with Asterisk DAHDI. So I'd be happy if libvpb0 didn't even try to generate configuration for the ISDN card. Regards, -- Jim Barber -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages libvpb0 depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-1GCC support library ii libpci3 1:3.1.7-3Linux PCI
Bug#583075: open-vm-source: pvscsi removed, but Debian doesn't come with kernel 2.6.33 or later.
Package: open-vm-source Version: 2010.04.25-253928-2 Severity: normal The pvscsi driver was removed as of open-vm-source version 2010.04.25-253928-1. The reason being is because it was added to Linux kernel version 2.6.33. However the latest kernel shipped with Debian is 2.6.32 and the pvscsi driver does not appear to have been backported to it. If I were to compile these sources and install the resulting modules on a virtual machine that is using the VMware paravirtualised SCSI driver, then the hard disk using that driver would not be accessible. Therefore, these versions of open-vm-source should have a dependency on kernels = versions that supply their own pvscsi module. OR the pvscsi driver should be reintroduced to open-vm-source and only compiled if the target kernel version is kernel versions that supply their own pvscsi module. I'd imagine the second option is preferable. Regards, Jim Barber -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-source depends on: ii bzip2 1.0.5-4high-quality block-sorting file co ii debhelper 7.4.20 helper programs for debian/rules ii make 3.81-8 An utility for Directing compilati ii quilt 0.48-7 Tool to work with series of patche Versions of packages open-vm-source recommends: ii module-assistant 0.11.3 tool to make module package creati ii open-vm-tools2010.03.20-243334-4 tools and components for VMware gu Versions of packages open-vm-source suggests: pn open-vm-toolbox none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572310: gamin: Possible memory leak
Package: gamin Version: 0.1.10-2+b1 Severity: normal I am seeing the following errors many times a day in my logs. Mar 3 13:09:46 mail kernel: [67796.754558] WARNING: at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b() Mar 3 13:09:46 mail kernel: [67796.754561] Hardware name: VMware Virtual Platform Mar 3 13:09:46 mail kernel: [67796.754563] inotify closing but id=0 for entry=dd237b80 in group=f22f8b00 still in idr. Probably leaking memory Mar 3 13:09:46 mail kernel: [67796.754565] Modules linked in: iptable_filter ip_tables x_tables vmsync vmmemctl vmhgfs loop ide_cd_mod cdrom ata_generic libata ide_pci_generic snd_pcm snd_timer snd soundcore snd_page_alloc parport_pc floppy serio_raw parport evdev pcspkr i2c_piix4 intel_agp vmci psmouse shpchp ac piix container vmxnet3 i2c_core processor pci_hotplug agpgart ide_core button ext3 jbd mbcache sd_mod crc_t10dif thermal fan thermal_sys mptspi mptscsih mptbase scsi_transport_spi scsi_mod Mar 3 13:09:46 mail kernel: [67796.754644] Pid: 2759, comm: gam_server Tainted: GW 2.6.32-trunk-686 #1 Mar 3 13:09:46 mail kernel: [67796.754646] Call Trace: Mar 3 13:09:46 mail kernel: [67796.754652] [c1030ba1] ? warn_slowpath_common+0x5e/0x8a Mar 3 13:09:46 mail kernel: [67796.754655] [c1030bff] ? warn_slowpath_fmt+0x26/0x2a Mar 3 13:09:46 mail kernel: [67796.754657] [c10d6048] ? idr_callback+0x2a/0x4b Mar 3 13:09:46 mail kernel: [67796.754662] [c112ed09] ? idr_for_each+0x5a/0x91 Mar 3 13:09:46 mail kernel: [67796.754664] [c10d601e] ? idr_callback+0x0/0x4b Mar 3 13:09:46 mail kernel: [67796.754667] [c10d600f] ? inotify_free_group_priv+0x12/0x21 Mar 3 13:09:46 mail kernel: [67796.754669] [c10d48b9] ? fsnotify_final_destroy_group+0x16/0x1e Mar 3 13:09:46 mail kernel: [67796.754671] [c10d6184] ? inotify_release+0x16/0x22 Mar 3 13:09:46 mail kernel: [67796.754674] [c10b2b73] ? __fput+0xd5/0x170 Mar 3 13:09:46 mail kernel: [67796.754677] [c10b0274] ? filp_close+0x4e/0x54 Mar 3 13:09:46 mail kernel: [67796.754680] [c1032324] ? put_files_struct+0x60/0xa6 Mar 3 13:09:46 mail kernel: [67796.754682] [c103397f] ? do_exit+0x1d4/0x5c6 Mar 3 13:09:46 mail kernel: [67796.754686] [c101c488] ? do_page_fault+0x271/0x287 Mar 3 13:09:46 mail kernel: [67796.754696] [c1033dd0] ? do_group_exit+0x5f/0x82 Mar 3 13:09:46 mail kernel: [67796.754699] [c1033e04] ? sys_exit_group+0x11/0x14 Mar 3 13:09:46 mail kernel: [67796.754702] [c10030fb] ? sysenter_do_call+0x12/0x28 Mar 3 13:09:46 mail kernel: [67796.754705] ---[ end trace 350063aef129cabe ]--- Mar 3 13:09:46 mail kernel: [67796.754707] entry-group=(null) inode=(null) wd=1024 They seem to indicate a problem with gamin and its interaction with inotify and reports Probably leaking memory. The process referred to is gam_server. The version of the Linux kernel installed is: linux-image-2.6.32-trunk-686 2.6.32-5 The Linux instance is running on VMware VSphere 4 and is using open-vm-tools. It is an email server using the courier-imap-ssl daemon which makes use of FAM/GAMIN. Regards, -- Jim Barber DDI Health -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages gamin depends on: ii libc62.10.2-6Embedded GNU C Library: Shared lib ii libgamin00.1.10-2+b1 Client library for the gamin file ii libglib2.0-0 2.22.4-1The GLib library of C routines gamin recommends no packages. gamin suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572166: bacula: New upstream release 5.0.1
Package: bacula Version: 5.0.0-5 Severity: wishlist Hi. There is a newer upstream version of Bacula that fixes some release bugs found in version 5.0.0. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/4 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532348: openswan: installs dupliate init script /etc/init.d/setup
This problem still exists in version 1:2.6.23+dfsg-1 of openswan. The sysv-rc package is blaming openswan for not being able to convert to a dependency based boot. It's message is as follows: │ Unable to migrate to dependency-based boot system │ │ │ │ Tests have determined that problems in the boot system exist which prevent migration to dependency-based boot sequencing:│ │ │ │ package openswan left obsolete init.d script behind, insserv: script setup: service openswan already provided!, │ │ │ │ If the reported problem is a local modification, it needs to be fixed manually. If it's a bug in the package, it should be │ │ reported to the BTS and fixed in the package. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more │ │ information about how to fix the problems preventing migration. │ │ │ │ To reattempt the migration process after the problems have been fixed, run dpkg-reconfigure sysv-rc. │ Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556536: winbind segfaults many time per second
Now that the Kerberos packages are working again with Samba/winbind, I upgraded to version 3.4.5 of Winbind. The 'many segfaults per second' problem didn't occur, so I guess the newer version fixed the problem. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566977: Samba, MIT krb5 and allow_weak_crypto
Is there a known work around for this problem? The older v1.7 krb5 libraries are now nowhere to be found on the Debian repositories so I can't downgrade and wait for a fix. Of is there a place where older libkrb5-3 debian packages can be found and manually downloaded and installed from so that I have a working system again? -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556536: winbind segfaults many time per second
I should add that in order to fix my problem I found a system where I have winbind-3.4.2 installed. I copied the /usr/sbin/winbindd binary across to the server with winbind-3.4.3 installed and that stopped the crashes. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556536: winbind segfaults many time per second
For my set up, winbind is talking to 2x Windows Server 2008 domain controllers and one Windows Server 2003 domain controller. The Linux kernel version installed is linux-image-2.6.30-2-686 version 2.6.30-8, so I haven't upgraded to 2.6.30-8squeeze1 yet). Like Dale, I am able to run 'wbinfo -u' and 'wbinfo -g' just fine. But I got many emails per second showing that it was panicing. The mail software running on the winbind server (sendmail based) was reporting it was unable to deliver messages to local users since they were unknown. Output from testparm is: [global] workgroup = DDIHEALTH realm = DDIHEALTH.COM server string = %h server security = ADS 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 = 5 disable netbios = Yes name resolve order = host dns proxy = No panic action = /usr/share/samba/panic-action %d idmap uid = 1-2 idmap gid = 1-2 template homedir = /home/%U winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes winbind offline logon = Yes [homes] comment = Home Directories valid users = %S create mask = 0700 directory mask = 0700 browseable = No browsable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 printable = Yes browseable = No browsable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556536: I also have this problem.
I just did the upgrade tonight and hit the same problem. Unfortunately 3.4.2 is gone from the Debian repositories so I can't downgrade again. Any ideas how to fix it? -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556434: bacula: Please package up newer version of Bacula
Package: bacula Version: 3.0.2-3 Severity: wishlist Bacula version 3.0.3 was released on 18th Oct 2009. It fixes some segfaults in the storage daemon. I'm having the storage daemon crash on me semi-regularly and I'm hoping these fixes solve it. I was hoping that the new version would be packaged up for Debian soon. Thanks. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/4 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages bacula depends on: ii bacula-client 3.0.2-3network backup, recovery and verif ii bacula-server 3.0.2-3network backup, recovery and verif bacula recommends no packages. Versions of packages bacula suggests: pn bacula-docnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551564: amanda-common: $localstatedir incorrect in some utilities.
Package: amanda-common Version: 1:2.6.1p1-2 Severity: normal I'm setting up a new Amanda server for the first time. I tried to run the amserverconfig utility and received the following error: $ amserverconfig DailySet1 Logging to /var/log/amanda/amserverconfig.20091019111837.debug /etc/amanda/template.d directory created ERROR: mkdir:/var/lib/lib/amanda/gnutar-lists failed: No such file or directory Further research shows that /usr/sbin/amserverconfig is trying to mkdir $amandahomedir/gnutar-lists. The $amandahomedir variable is set to: $localstatedir/lib/amanda The $localstatedir variable is set to: /var/lib Instead it should be set to /var (according to the build scripts I've read for Amanda). It is defined incorrectly in the following two files: /usr/lib/amanda/perl/Amanda/Paths.pm /usr/sbin/amaddclient The breaks the amserverconfig and amaddclient commands. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/4 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages amanda-common depends on: ii adduser3.111 add and remove users and groups ii bsd-mailx [mailx] 8.1.2-0.20090911cvs-2 simple mail user agent ii debconf [debconf-2 1.5.27Debian configuration management sy ii libc6 2.9-25GNU C Library: Shared libraries ii libglib2.0-0 2.22.0-1 The GLib library of C routines ii libncurses55.7+20090803-2shared libraries for terminal hand ii libreadline6 6.0-5 GNU readline and history libraries ii openbsd-inetd [ine 0.20080125-3 The OpenBSD Internet Superserver ii perl [perl5] 5.10.1-5 Larry Wall's Practical Extraction ii tar1.22-2GNU version of the tar archiving u ii update-inetd 4.35 inetd configuration file updater amanda-common recommends no packages. Versions of packages amanda-common suggests: ii amanda-server1:2.6.1p1-2 Advanced Maryland Automatic Networ -- debconf information: amanda-common/merge_amandates: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551564: More related issues to amserverconfig
Hi. I've found another couple of problems that prevent the amserverconfig script from running. After manually fixing the $localstatedir error I wrote about above I now get the following error: $ amserverconfig DailySet1 --template tape-changer --tapetype LTO3-400 --changerdev /dev/sg6 Logging to /var/log/amanda/amserverconfig.20091019112549.debug /etc/amanda/template.d directory created ERROR: copy dumptypes failed: No such file or directory After researching, also in the /usr/lib/amanda/perl/Amanda/Paths.pm file the $amdatadir is incorrectly defined. It is set to the /usr/share/amanda directory which doesn't exist. Instead $amdatadir should be set to the /var/lib/amanda directory. Also, I needed to copy the /usr/share/doc/amanda-common/examples/template.d directory to /var/lib/amanda/template.d and also ungzip all the .gz files in there. Once done, then the script works: $ amserverconfig DailySet1 --template tape-changer --tapetype LTO3-400 --changerdev /dev/sg6 Logging to /var/log/amanda/amserverconfig.20091019114735.debug /etc/amanda/template.d directory created /var/lib/amanda/gnutar-lists directory exists /etc/amanda/DailySet1/advanced.conf created and updated curinfo and index directory created tapelist file created disklist file created Creating custom configuration using templates custom amanda.conf created /var/lib/amanda/example/xinetd.amandaserver contains the latest Amanda server daemon configuration. Please merge it to /etc/xinetd.d/amandaserver. DONE. However the last message about the xinetd.amandaserver is wrong, but doesn't really apply to the Debian install anyway from what I can tell. Regards, -- -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531936: open-vm-source: Will not build with module-assistant
Package: open-vm-source Version: 2009.04.23-162451-1 Severity: important This is similar to bug reports #525816 and #518014, except the kernel in this case is the linux-image-2.6.26-2-686 Debian package. I am trying to build the modules using the following command as root: module-assistant auto-build open-vm The log file shows the following: QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 rm -rf .pc debian/stamp-patched dh_testdir dh_testroot rm -f build-stamp rm -f config/config.guess config/config.sub # Cleaning package [ ! -f Makefile ] || /usr/bin/make distclean make[1]: Entering directory `/usr/src/modules/open-vm' /usr/bin/make -C modules/linux/pvscsi clean make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi' make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi' make[1]: Leaving directory `/usr/src/modules/open-vm' /usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules make[1]: Entering directory `/usr/src/modules/open-vm' QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 No patch removed rm -rf .pc debian/stamp-patched dh_testdir dh_testroot rm -f build-stamp rm -f config/config.guess config/config.sub # Cleaning package [ ! -f Makefile ] || /usr/bin/make distclean make[2]: Entering directory `/usr/src/modules/open-vm' /usr/bin/make -C modules/linux/pvscsi clean Using standalone build system. make[3]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi' Makefile:161: Makefile.normal: No such file or directory make[3]: *** No rule to make target `Makefile.normal'. Stop. make[3]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi' make[2]: *** [clean] Error 2 make[2]: Leaving directory `/usr/src/modules/open-vm' make[1]: *** [clean] Error 2 make[1]: Leaving directory `/usr/src/modules/open-vm' make: *** [kdist_build] Error 2 The key error being: Makefile:161: Makefile.normal: No such file or directory The following Makefile* files are in the unpacked source: /usr/src/modules/open-vm/modules/linux/pvscsi/Makefile /usr/src/modules/open-vm/modules/linux/pvscsi/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmblock/Makefile /usr/src/modules/open-vm/modules/linux/vmblock/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmblock/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmci/Makefile /usr/src/modules/open-vm/modules/linux/vmci/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmci/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmhgfs/Makefile /usr/src/modules/open-vm/modules/linux/vmhgfs/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmhgfs/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmmemctl/Makefile /usr/src/modules/open-vm/modules/linux/vmmemctl/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmmemctl/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmsync/Makefile /usr/src/modules/open-vm/modules/linux/vmsync/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmxnet3/Makefile /usr/src/modules/open-vm/modules/linux/vmxnet3/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmxnet3/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmxnet/Makefile /usr/src/modules/open-vm/modules/linux/vmxnet/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vmxnet/Makefile.normal /usr/src/modules/open-vm/modules/linux/vsock/Makefile /usr/src/modules/open-vm/modules/linux/vsock/Makefile.kernel /usr/src/modules/open-vm/modules/linux/vsock/Makefile.normal Note the lack of the following files (the first of which the error is about): /usr/src/modules/open-vm/modules/linux/pvscsi/Makefile.normal /usr/src/modules/open-vm/modules/linux/vmsync/Makefile.normal Both of these directories reference the missing file from their Makefile: # grep Makefile.normal /usr/src/modules/open-vm/modules/linux/pvscsi/Makefile include $(SRCROOT)/Makefile.normal # grep Makefile.normal /usr/src/modules/open-vm/modules/linux/vmsync/Makefile include $(SRCROOT)/Makefile.normal Therefore I believe that the problem is kernel independent. If the missing Makefile.normal files were included, I suspect this and bugs #525816 and #518014 would be solved. Regards, Jim Barber -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale
Bug#484235: Panic or segfault in Samba
Hi. I installed version 3.3.4-1 of your Winbind package on May 4th. Since then I haven't seen a single panic. I think by this stage it is most likely safe to say that the fix that went into Samba/Winbind v3.3.4 has resolved this bug. Thanks for your help. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484235: Panic or segfault in Samba
Just a quick update. The panics are still not fixed for winbind 3.3.3-1 So I'm eagerly awaiting the release of version 3.3.4. The log file reports: [2009/04/29 05:26:11, 4] winbindd/winbindd_dual.c:fork_domain_child(1439) child daemon request 17 [2009/04/29 05:26:11, 3] winbindd/winbindd_ads.c:query_user_list(168) ads: query_user_list winbindd: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. [2009/04/29 05:26:14, 0] lib/fault.c:fault_report(40) === [2009/04/29 05:26:14, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 6 in pid 20787 (3.3.3) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/04/29 05:26:14, 0] lib/fault.c:fault_report(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/04/29 05:26:14, 0] lib/fault.c:fault_report(44) === [2009/04/29 05:26:14, 0] lib/util.c:smb_panic(1673) PANIC (pid 20787): internal error [2009/04/29 05:26:14, 0] lib/util.c:log_stack_trace(1777) BACKTRACE: 25 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x81421e4] #1 /usr/sbin/winbindd(smb_panic+0x80) [0x8142341] #2 /usr/sbin/winbindd [0x812f5ee] #3 [0xb7f82420] #4 /lib/libc.so.6(abort+0x188) [0xb7caafd8] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7ca2840] #6 /usr/lib/libldap_r-2.4.so.2 [0xb7df36de] #7 /usr/sbin/winbindd [0x834d420] #8 /usr/sbin/winbindd(ads_do_search_all_args+0xee) [0x834d84c] #9 /usr/sbin/winbindd [0x83535ee] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3e) [0x83541c9] #11 /usr/sbin/winbindd(ads_search_retry+0x4d) [0x8354281] #12 /usr/sbin/winbindd [0x80c7d93] #13 /usr/sbin/winbindd [0x80aedc3] #14 /usr/sbin/winbindd(winbindd_dual_list_users+0x89) [0x80cf2f3] #15 /usr/sbin/winbindd [0x80cbd2f] #16 /usr/sbin/winbindd [0x80ccbcd] #17 /usr/sbin/winbindd(async_request+0x208) [0x80cd58c] #18 /usr/sbin/winbindd(init_child_connection+0x294) [0x80a59ad] #19 /usr/sbin/winbindd(async_domain_request+0x123) [0x80cd7f3] #20 /usr/sbin/winbindd [0x80a5bf1] #21 /usr/sbin/winbindd(rescan_trusted_domains+0x52) [0x80a6048] #22 /usr/sbin/winbindd(main+0xc65) [0x809b434] #23 /lib/libc.so.6(__libc_start_main+0xe5) [0xb7c95775] #24 /usr/sbin/winbindd [0x8098f71] [2009/04/29 05:26:14, 0] lib/util.c:smb_panic(1678) smb_panic(): calling panic action [/usr/share/samba/panic-action 20787] Failed to read a valid object file image from memory. [2009/04/29 05:26:15, 0] lib/util.c:smb_panic(1686) smb_panic(): action returned status 0 [2009/04/29 05:26:15, 0] lib/fault.c:dump_core(231) dumping core in /var/log/samba/cores/winbindd And the email sent shows the following root wrote: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 20787 (/usr/sbin/winbindd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the problem persists, you are encouraged to first install the samba-dbg package, which contains the debugging symbols for the Samba binaries. Then submit the provided information as a bug report to Debian. For information about the procedure for submitting bug reports, please see http://www.debian.org/Bugs/Reporting or the reportbug(1) manual page. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7b046e0 (LWP 20787)] 0xb7d16e0e in waitpid () from /lib/libc.so.6 #0 0xb7d16e0e in waitpid () from /lib/libc.so.6 #1 0xb7cb6dfb in ?? () from /lib/libc.so.6 #2 0x081423b9 in smb_panic () #3 0x0812f5ee in ?? () #4 0x08417b3b in ?? () #5 0x in ?? () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
. This is the same error I'm seeing on both boxes. Calls I can see in the /var/log/samba/log.winbindd file around the time are: [2008/11/26 05:33:08, 3] winbindd/winbindd_misc.c:winbindd_interface_version(757) [ 5149]: request interface version [2008/11/26 05:33:08, 3] winbindd/winbindd_misc.c:winbindd_priv_pipe_dir(790) [ 5149]: request location of privileged pipe [2008/11/26 05:33:08, 3] winbindd/winbindd_group.c:winbindd_getgroups(1384) [ 5149]: getgroups root Details of the packages installed are: ii ldap-utils 2.4.11-1OpenLDAP utilities ii libldap-2.4-2 2.4.11-1OpenLDAP libraries ii libldap-2.4-2-dbg 2.4.11-1Debugging information for OpenLDAP libraries ii libwbclient02:3.2.4-1 client library for interfacing with winbind service ii samba 2:3.2.4-1 a LanManager-like file and printer server for Unix ii samba-common2:3.2.4-1 Samba common files used by both the server and the client ii samba-dbg 2:3.2.4-1 Samba debugging symbols ii samba-doc 2:3.2.4-1 Samba documentation ii smbclient 2:3.2.4-1 a LanManager-like simple client for Unix ii winbind 2:3.2.4-1 service to resolve user and group information from Windows NT servers Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
() from /lib/libc.so.6 #6 0xb7cd4d78 in abort () from /lib/libc.so.6 #7 0xb7ccc590 in __assert_fail () from /lib/libc.so.6 #8 0xb7e166de in ldap_parse_result () from /usr/lib/libldap_r-2.4.so.2 #9 0x0826e064 in ads_do_paged_search_args () #10 0x0826e40c in ads_do_search_all_args () #11 0x08273f5e in ads_do_search_retry_internal () #12 0x08274185 in ads_ranged_search_internal () #13 0x08274ac1 in ads_ranged_search () #14 0x080b519f in lookup_groupmem () #15 0x0809e4f3 in lookup_groupmem () #16 0x08092b87 in fill_grent_mem () #17 0x08094f00 in getgrsid_sid2gid_recv () #18 0x080c3a70 in winbindd_sid2gid_recv () #19 0x080bd200 in do_async_recv () #20 0x080bc817 in async_reply_recv () #21 0x0808ce6b in rw_callback () #22 0x0808ded9 in main () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Corresponding log.winbind entry: [2008/11/21 16:00:04, 1] libsmb/clikrb5.c:ads_krb5_get_fwd_ticket(1830) ads_krb5_get_fwd_ticket: krb5_fwd_tgt_creds failed (Requested effective lifetime is negative or too short) winbindd: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. [2008/11/21 16:00:04, 0] lib/fault.c:fault_report(40) === [2008/11/21 16:00:04, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 6 in pid 19193 (3.2.4) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/11/21 16:00:04, 0] lib/fault.c:fault_report(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/11/21 16:00:04, 0] lib/fault.c:fault_report(44) === [2008/11/21 16:00:04, 0] lib/util.c:smb_panic(1663) PANIC (pid 19193): internal error [2008/11/21 16:00:04, 0] lib/util.c:log_stack_trace(1767) BACKTRACE: 23 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x812b184] #1 /usr/sbin/winbindd(smb_panic+0x80) [0x812b2e1] #2 /usr/sbin/winbindd [0x8118b63] #3 [0xb7fa0420] #4 /lib/libc.so.6(abort+0x188) [0xb7cd4d78] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7ccc590] #6 /usr/lib/libldap_r-2.4.so.2 [0xb7e166de] #7 /usr/sbin/winbindd [0x826e064] #8 /usr/sbin/winbindd(ads_do_search_all_args+0x6d) [0x826e40c] #9 /usr/sbin/winbindd [0x8273f5e] #10 /usr/sbin/winbindd(ads_ranged_search_internal+0xb3) [0x8274185] #11 /usr/sbin/winbindd(ads_ranged_search+0x17f) [0x8274ac1] #12 /usr/sbin/winbindd [0x80b519f] #13 /usr/sbin/winbindd [0x809e4f3] #14 /usr/sbin/winbindd [0x8092b87] #15 /usr/sbin/winbindd [0x8094f00] #16 /usr/sbin/winbindd [0x80c3a70] #17 /usr/sbin/winbindd [0x80bd200] #18 /usr/sbin/winbindd [0x80bc817] #19 /usr/sbin/winbindd [0x808ce6b] #20 /usr/sbin/winbindd(main+0xfa2) [0x808ded9] #21 /lib/libc.so.6(__libc_start_main+0xe5) [0xb7cbf455] #22 /usr/sbin/winbindd [0x808b7c1] [2008/11/21 16:00:04, 0] lib/util.c:smb_panic(1668) smb_panic(): calling panic action [/usr/share/samba/panic-action 19193] [2008/11/21 16:00:05, 0] lib/util.c:smb_panic(1676) smb_panic(): action returned status 0 [2008/11/21 16:00:06, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/winbindd Details of the packages installed are: ii ldap-utils 2.4.11-1OpenLDAP utilities ii libldap-2.4-2 2.4.11-1OpenLDAP libraries ii libldap-2.4-2-dbg 2.4.11-1Debugging information for OpenLDAP libraries ii libwbclient02:3.2.4-1 client library for interfacing with winbind service ii samba 2:3.2.4-1 a LanManager-like file and printer server for Unix ii samba-common2:3.2.4-1 Samba common files used by both the server and the client ii samba-dbg 2:3.2.4-1 Samba debugging symbols ii samba-doc 2:3.2.4-1 Samba documentation ii smbclient 2:3.2.4-1 a LanManager-like simple client for Unix ii winbind 2:3.2.4-1 service to resolve user and group information from Windows NT servers Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Winbind still panics after upgrading to the latest Samba packages. The panic dump from yesterday is as follows: [Thread debugging using libthread_db enabled] [New Thread 0xb7af16d0 (LWP 31075)] 0xb7cf18fe in waitpid () from /lib/libc.so.6 #0 0xb7cf18fe in waitpid () from /lib/libc.so.6 #1 0xb7c94b7b in ?? () from /lib/libc.so.6 #2 0x0812b359 in smb_panic () #3 0x08118b63 in sig_fault () #4 signal handler called #5 0xb7c87556 in raise () from /lib/libc.so.6 #6 0xb7c88d78 in abort () from /lib/libc.so.6 #7 0xb7c80590 in __assert_fail () from /lib/libc.so.6 #8 0xb7dca6de in ldap_parse_result (ld=0x8407070, r=0x0, errcodep=0x0, matcheddnp=0x0, errmsgp=0x0, referralsp=0x0, serverctrls=0xbff53558, freeit=0) at error.c:272 #9 0x0826e064 in ads_do_paged_search_args () #10 0x0826e48d in ads_do_search_all_args () #11 0x08273c9e in ads_do_search_retry_internal () #12 0x08274879 in ads_do_search_retry () #13 0x08274931 in ads_search_retry () #14 0x080b7bcb in query_user_list () #15 0x080a04cc in query_user_list () #16 0x080be8c5 in winbindd_dual_list_users () #17 0x080bb6bf in fork_domain_child () #18 0x080bb88d in schedule_async_request () #19 0x080bcb57 in async_request () #20 0x080974bd in init_child_connection () #21 0x080bcdbe in async_domain_request () #22 0x08097701 in add_trusted_domains () #23 0x08097abb in rescan_trusted_domains () #24 0x0808dc94 in main () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] I couldn't find any corresponding error messages in the samba and winbind log files. Details of the packages installed are: ii ldap-utils 2.4.11-1OpenLDAP utilities ii libldap-2.4-2 2.4.11-1OpenLDAP libraries ii libldap-2.4-2-dbg 2.4.11-1Debugging information for OpenLDAP libraries ii libwbclient02:3.2.4-1 client library for interfacing with winbind service ii samba 2:3.2.4-1 a LanManager-like file and printer server for Unix ii samba-common2:3.2.4-1 Samba common files used by both the server and the client ii samba-dbg 2:3.2.4-1 Samba debugging symbols ii samba-doc 2:3.2.4-1 Samba documentation ii smbclient 2:3.2.4-1 a LanManager-like simple client for Unix ii winbind 2:3.2.4-1 service to resolve user and group information from Windows NT servers Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
NT servers So maybe it was something other dependent library that changed? Looking through the dependencies above the only packages I can see that has been updated since the last crash were: - libcups2 - libsasl2-2 But neither of these seem related... Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495904: mailscanner v4.71 available
Version 4.71 of MailScanner is available. It fixes the water marking feature so that it works properly with Exim. This feature alone could greatly reduce the amount of spam we get. Regards, -- -- Jim Barber -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Hi again. As of last night the packages are now as follows: ii ldap-utils 2.4.10-3OpenLDAP utilities ii libldap-2.4-2 2.4.10-3OpenLDAP libraries ii libldap-2.4-2-dbg 2.4.10-3Debugging information for OpenLDAP libraries ii libwbclient02:3.2.3-1 client library for interfacing with winbind service ii samba 2:3.2.3-1 a LanManager-like file and printer server for Unix ii samba-common2:3.2.3-1 Samba common files used by both the server and the client ii samba-dbg 2:3.2.3-1 Samba debugging symbols ii samba-doc 2:3.2.3-1 Samba documentation ii smbclient 2:3.2.3-1 a LanManager-like simple client for Unix ii winbind 2:3.2.3-1 service to resolve user and group information from Windows NT servers The panic is still occurring. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
] #8 /usr/sbin/winbindd(ads_do_search_all_args+0x6d) [0x83adf8c] #9 /usr/sbin/winbindd [0x83b977e] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3e) [0x83ba359] #11 /usr/sbin/winbindd(ads_USN+0x69) [0x83aa031] #12 /usr/sbin/winbindd [0x80c9bfc] #13 /usr/sbin/winbindd [0x80af45f] #14 /usr/sbin/winbindd [0x80af64b] #15 /usr/sbin/winbindd [0x80b1a6f] #16 /usr/sbin/winbindd(winbindd_lookup_sid_by_name+0x48) [0x80a7588] #17 /usr/sbin/winbindd(winbindd_dual_lookupname+0x110) [0x80d3758] #18 /usr/sbin/winbindd [0x80d01ff] #19 /usr/sbin/winbindd [0x80d03cd] #20 /usr/sbin/winbindd(async_request+0x184) [0x80d16b0] #21 /usr/sbin/winbindd(async_domain_request+0x57) [0x80d184b] #22 /usr/sbin/winbindd(do_async_domain+0x133) [0x80d3aed] #23 /usr/sbin/winbindd(winbindd_lookupname_async+0x277) [0x80d48b4] #24 /usr/sbin/winbindd(winbindd_getgroups+0x3ad) [0x80a3531] #25 /usr/sbin/winbindd [0x809e809] #26 /usr/sbin/winbindd [0x809e91b] #27 /usr/sbin/winbindd [0x809f1cb] #28 /usr/sbin/winbindd(main+0xf6a) [0x80a0201] #29 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c92450] #30 /usr/sbin/winbindd [0x809db51] [2008/08/07 12:01:56, 0] lib/util.c:smb_panic(1671) smb_panic(): calling panic action [/usr/share/samba/panic-action 19289] warning: .dynamic section for /usr/lib/libldap_r-2.4.so.2 is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for /usr/lib/liblber-2.4.so.2 is not at the expected address (wrong library or version mismatch?) Failed to read a valid object file image from memory. [2008/08/07 12:01:59, 0] lib/util.c:smb_panic(1679) smb_panic(): action returned status 0 [2008/08/07 12:01:59, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/winbindd [2008/08/07 12:01:59, 3] winbindd/winbindd_ads.c:sequence_number(1116) ads: fetch sequence_number for PRY [2008/08/07 12:01:59, 3] winbindd/winbindd_cm.c:connection_ok(1522) connection_ok: Connection to zeus.pry.com.au for domain PRY has died or was never started (fd == -1) [2008/08/07 12:01:59, 1] libsmb/clientgen.c:cli_rpc_pipe_close(554) cli_rpc_pipe_close: cli_close failed on pipe \lsarpc, fnum 0x4008 to machine zeus.pry.com.au. Error was SUCCESS - 0 Is it worth me installing the libc6-dbg package as well? Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
] #3 [0xb7f32420] #4 /lib/libc.so.6(abort+0x101) [0xb7c72541] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7c6a230] #6 /usr/lib/libldap_r-2.4.so.2(ldap_parse_result+0x48a) [0xb7dab25a] #7 /usr/sbin/winbindd [0x83adbe4] #8 /usr/sbin/winbindd(ads_do_search_all_args+0x6d) [0x83adf8c] #9 /usr/sbin/winbindd [0x83b977e] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3e) [0x83ba359] #11 /usr/sbin/winbindd(ads_USN+0x69) [0x83aa031] #12 /usr/sbin/winbindd [0x80c9bfc] #13 /usr/sbin/winbindd [0x80af45f] #14 /usr/sbin/winbindd [0x80af64b] #15 /usr/sbin/winbindd [0x80b1a6f] #16 /usr/sbin/winbindd(winbindd_lookup_sid_by_name+0x48) [0x80a7588] #17 /usr/sbin/winbindd(winbindd_dual_lookupname+0x110) [0x80d3758] #18 /usr/sbin/winbindd [0x80d01ff] #19 /usr/sbin/winbindd [0x80d03cd] #20 /usr/sbin/winbindd(async_request+0x184) [0x80d16b0] #21 /usr/sbin/winbindd(async_domain_request+0x57) [0x80d184b] #22 /usr/sbin/winbindd(do_async_domain+0x133) [0x80d3aed] #23 /usr/sbin/winbindd(winbindd_lookupname_async+0x277) [0x80d48b4] #24 /usr/sbin/winbindd(winbindd_getpwnam+0x31f) [0x80a2594] #25 /usr/sbin/winbindd [0x809e809] #26 /usr/sbin/winbindd [0x809e91b] #27 /usr/sbin/winbindd [0x809f1cb] #28 /usr/sbin/winbindd(main+0xf6a) [0x80a0201] #29 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c5d450] #30 /usr/sbin/winbindd [0x809db51] [2008/08/05 07:18:02, 0] lib/util.c:smb_panic(1671) smb_panic(): calling panic action [/usr/share/samba/panic-action 6827] Failed to read a valid object file image from memory. [2008/08/05 07:18:02, 0] lib/util.c:smb_panic(1679) smb_panic(): action returned status 0 [2008/08/05 07:18:02, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/winbindd [2008/08/05 07:18:02, 3] winbindd/winbindd_ads.c:sequence_number(1116) ads: fetch sequence_number for PRY [2008/08/05 07:18:02, 3] winbindd/winbindd_cm.c:connection_ok(1522) connection_ok: Connection to zeus.pry.com.au for domain PRY has died or was never started (fd == -1) [2008/08/05 07:18:02, 1] libsmb/clientgen.c:cli_rpc_pipe_close(554) cli_rpc_pipe_close: cli_close failed on pipe \lsarpc, fnum 0x17 to machine zeus.pry.com.au. Error was SUCCESS - 0 [2008/08/05 07:18:02, 1] libsmb/clientgen.c:cli_rpc_pipe_close(554) cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x400a to machine zeus.pry.com.au. Error was SUCCESS - 0 The /var/log/samba/log.winbindd file didn't have panic information. But just in case it's useful, the entries for the same time in this file were: [2008/08/05 07:18:02, 3] winbindd/winbindd_misc.c:winbindd_interface_version(757) [28142]: request interface version [2008/08/05 07:18:02, 3] winbindd/winbindd_misc.c:winbindd_priv_pipe_dir(790) [28142]: request location of privileged pipe [2008/08/05 07:18:02, 3] winbindd/winbindd_group.c:winbindd_getgroups(1383) [28142]: getgroups root [2008/08/05 07:18:02, 3] winbindd/winbindd_misc.c:winbindd_interface_version(757) [28155]: request interface version [2008/08/05 07:18:02, 3] winbindd/winbindd_misc.c:winbindd_priv_pipe_dir(790) [28155]: request location of privileged pipe [2008/08/05 07:18:02, 3] winbindd/winbindd_pam.c:winbindd_pam_auth(831) [28155]: pam auth test Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
, 0] lib/util.c:smb_panic(1646) smb_panic(): action returned status 0 [2008/07/22 03:59:33, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/winbindd The /var/log/samba/log.winbindd file seems to have details about the sencond crash: [2008/07/22 04:00:06, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(491) [26721]: request interface version [2008/07/22 04:00:06, 3] nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(524) [26721]: request location of privileged pipe [2008/07/22 04:00:06, 3] nsswitch/winbindd_user.c:winbindd_list_users(754) [26721]: list users [2008/07/22 04:00:06, 3] nsswitch/winbindd_ads.c:query_user_list(169) ads: query_user_list winbindd: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. [2008/07/22 04:00:06, 0] lib/fault.c:fault_report(41) === [2008/07/22 04:00:06, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 6 in pid 19395 (3.0.31) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/07/22 04:00:06, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/07/22 04:00:06, 0] lib/fault.c:fault_report(45) === [2008/07/22 04:00:06, 0] lib/util.c:smb_panic(1633) PANIC (pid 19395): internal error [2008/07/22 04:00:06, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 20 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x81208dd] #1 /usr/sbin/winbindd(smb_panic+0x5d) [0x8120a0d] #2 /usr/sbin/winbindd [0x810b328] #3 [0xb7fcd420] #4 /lib/libc.so.6(abort+0x101) [0xb7d1f541] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7d17230] #6 /usr/lib/libldap_r-2.4.so.2(ldap_parse_result+0x48a) [0xb7e4725a] #7 /usr/sbin/winbindd [0x8235ed7] #8 /usr/sbin/winbindd(ads_do_search_all_args+0x73) [0x8236293] #9 /usr/sbin/winbindd [0x823f7da] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3e) [0x823fd6e] #11 /usr/sbin/winbindd(ads_search_retry+0x4d) [0x823ff3d] #12 /usr/sbin/winbindd [0x80b5575] #13 /usr/sbin/winbindd [0x809be26] #14 /usr/sbin/winbindd(winbindd_list_users+0xf3) [0x808d073] #15 /usr/sbin/winbindd [0x808b735] #16 /usr/sbin/winbindd [0x808be10] #17 /usr/sbin/winbindd(main+0x9cf) [0x808c83f] #18 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d0a450] #19 /usr/sbin/winbindd [0x808a8e1] [2008/07/22 04:00:06, 0] lib/util.c:smb_panic(1638) smb_panic(): calling panic action [/usr/share/samba/panic-action 19395] Failed to read a valid object file image from memory. Cannot access memory at address 0x4bc3 [2008/07/22 04:00:07, 0] lib/util.c:smb_panic(1646) smb_panic(): action returned status 0 [2008/07/22 04:00:07, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/winbindd There are no other clues in any other logs as far as I can tell. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
The output from log.winbindd for one of the crashes last night follows. I grabbed a few lines earlier, although I'm not sure they are relevant. Do I need to increase the logging level for winbind to be above 4? [2008/07/15 08:57:06, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(491) [24910]: request interface version [2008/07/15 08:57:06, 3] nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(524) [24910]: request location of privileged pipe [2008/07/15 08:57:06, 3] nsswitch/winbindd_user.c:winbindd_list_users(754) [24910]: list users [2008/07/15 08:57:06, 3] nsswitch/winbindd_ads.c:sequence_number(1010) ads: fetch sequence_number for PRY [2008/07/15 08:57:06, 3] nsswitch/winbindd_ads.c:query_user_list(169) ads: query_user_list winbindd: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. [2008/07/15 08:57:07, 0] lib/fault.c:fault_report(41) === [2008/07/15 08:57:07, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 6 in pid 16179 (3.0.30) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/07/15 08:57:07, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/07/15 08:57:07, 0] lib/fault.c:fault_report(45) === [2008/07/15 08:57:07, 0] lib/util.c:smb_panic(1633) PANIC (pid 16179): internal error [2008/07/15 08:57:07, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 20 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x81200ed] #1 /usr/sbin/winbindd(smb_panic+0x5d) [0x812021d] #2 /usr/sbin/winbindd [0x810aaf8] #3 [0xb7fa1420] #4 /lib/libc.so.6(abort+0x101) [0xb7cf1541] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7ce9230] #6 /usr/lib/libldap_r-2.4.so.2 [0xb7e1966e] #7 /usr/sbin/winbindd [0x8235767] #8 /usr/sbin/winbindd(ads_do_search_all_args+0xf4) [0x8235ba4] #9 /usr/sbin/winbindd [0x823f05a] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3e) [0x823f5ee] #11 /usr/sbin/winbindd(ads_search_retry+0x4d) [0x823f7bd] #12 /usr/sbin/winbindd [0x80b5515] #13 /usr/sbin/winbindd [0x809be56] #14 /usr/sbin/winbindd(winbindd_list_users+0xf3) [0x808d013] #15 /usr/sbin/winbindd [0x808b6f5] #16 /usr/sbin/winbindd [0x808bdc0] #17 /usr/sbin/winbindd(main+0x9cf) [0x808c7ef] #18 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7cdc450] #19 /usr/sbin/winbindd [0x808a8a1] [2008/07/15 08:57:07, 0] lib/util.c:smb_panic(1638) smb_panic(): calling panic action [/usr/share/samba/panic-action 16179] Failed to read a valid object file image from memory. Cannot access memory at address 0x3f33 [2008/07/15 08:57:09, 0] lib/util.c:smb_panic(1646) smb_panic(): action returned status 0 [2008/07/15 08:57:09, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/winbindd Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Steve Langasek wrote: Aha, well, that handily answers the question of which of the three assert statements in ldap_parse_result() is being hit. And essentially, this points to a failure in ldap_search_ext_s(), because this function isn't returning an error but is returning a NULL res value which then fails this assert in ldap_parse_result(). I'm not sure yet how that could happen; perhaps some more logs will make it clearer. The installation of version 2.4.10-2 of the LDAP libraries hasn't fixed the problem. Unfortunately I can't see an associated message in my /var/log/log.winbind* files. There seems to be gaps in the timestamps in these files for some reason. -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Jim Barber wrote: There seems to be gaps in the timestamps in these files for some reason. Oh, I've found the problem with the logs. I had 'max log size = 1000' defined in /etc/samba/smb.conf (the default value). The log.winbind file is reaching this size every hour with the debug level 4 turned on. So it gets cycled to log.winbind.old replacing the previous .old file and so losing the logging info. I've increased this value significantly, so hopefully for the next crash I'll have some useful information. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: Bug#484235: Bug#484235: panic-action called for /usr/sbin/winbindd
Steve Langasek wrote: You previously reported that you were using libldap-2.4-2 version 2.4.9-1. There is a new upstream version of this package, 2.4.10-2, available in unstable; could you please install this and see if it helps? From the backtrace, this is most likely an openldap problem rather than a samba problem. Could you also send the contents of /var/log/samba/log.winbindd? In particular, anything immediately before a backtrace. If you don't already have debug level set in smb.conf, you'll want to set this to 4 and capture another crash to get a log.winbindd with useful information. Cheers, Thanks for that Steve. I've now installed the newer ldap packages like so: ii ldap-utils 2.4.10-2OpenLDAP utilities ii libldap-2.4-2 2.4.10-2OpenLDAP libraries I've also added the following to the /etc/samba/smb.conf file and restarted samba. Does it look right? log level = winbind:4 However I don't think I thought to check the log.winbind before... So here is what I've found with the default log level (which I guess is 0?) winbindd: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. [2008/07/04 13:35:06, 0] lib/fault.c:fault_report(41) === [2008/07/04 13:35:06, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 6 in pid 12996 (3.0.30) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/07/04 13:35:06, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/07/04 13:35:06, 0] lib/fault.c:fault_report(45) === [2008/07/04 13:35:06, 0] lib/util.c:smb_panic(1633) PANIC (pid 12996): internal error [2008/07/04 13:35:06, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 20 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x811f03d] #1 /usr/sbin/winbindd(smb_panic+0x5d) [0x811f16d] #2 /usr/sbin/winbindd [0x8109d9a] #3 [0xb7eee420] #4 /lib/libc.so.6(abort+0x101) [0xb7c49541] #5 /lib/libc.so.6(__assert_fail+0xf0) [0xb7c41230] #6 /usr/lib/libldap_r-2.4.so.2(ldap_parse_result+0x48a) [0xb7d7120a] #7 /usr/sbin/winbindd [0x823001c] #8 /usr/sbin/winbindd(ads_do_search_all_args+0x6f) [0x823039f] #9 /usr/sbin/winbindd [0x82395d9] #10 /usr/sbin/winbindd(ads_do_search_retry+0x3a) [0x8239b4a] #11 /usr/sbin/winbindd(ads_search_retry+0x4d) [0x8239d1d] #12 /usr/sbin/winbindd [0x80b4ce5] #13 /usr/sbin/winbindd [0x809bc4e] #14 /usr/sbin/winbindd(winbindd_list_users+0xee) [0x808cf6e] #15 /usr/sbin/winbindd [0x808b630] #16 /usr/sbin/winbindd [0x808bc19] #17 /usr/sbin/winbindd(main+0x9a9) [0x808c6c9] #18 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c34450] #19 /usr/sbin/winbindd [0x808a871] [2008/07/04 13:35:06, 0] lib/util.c:smb_panic(1638) smb_panic(): calling panic action [/usr/share/samba/panic-action 12996] Failed to read a valid object file image from memory. Cannot access memory at address 0x32c4 [2008/07/04 13:35:07, 0] lib/util.c:smb_panic(1646) smb_panic(): action returned status 0 [2008/07/04 13:35:07, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/winbindd Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: Bug#484235: panic-action called for /usr/sbin/winbindd
This crash is still happening once or twice a day at least. Now at the following versions: ii samba 2:3.0.30-3 a LanManager-like file and printer server for Unix ii samba-common2:3.0.30-3 Samba common files used by both the server and the client ii samba-dbg 2:3.0.30-3 Samba debugging symbols ii samba-doc 2:3.0.30-3 Samba documentation ii winbind 2:3.0.30-3 service to resolve user and group information from Windows NT servers A dump from this version looks as follows: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb7b416d0 (LWP 13661)] 0xb7d3b6be in waitpid () from /lib/libc.so.6 #0 0xb7d3b6be in waitpid () from /lib/libc.so.6 #1 0xb7ce302e in ?? () from /lib/libc.so.6 #2 0x0812027e in smb_panic (why=0x8272950 internal error) at lib/util.c:1639 #3 0x0810aaf8 in sig_fault (sig=6) at lib/fault.c:47 #4 signal handler called #5 0xb7cd5d96 in raise () from /lib/libc.so.6 #6 0xb7cd7541 in abort () from /lib/libc.so.6 #7 0xb7ccf230 in __assert_fail () from /lib/libc.so.6 #8 0xb7dff20a in ldap_parse_result () from /usr/lib/libldap_r-2.4.so.2 #9 0x08235767 in ads_do_paged_search_args (ads=0x8322d58, bind_path=0x82ceeb8 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x8261aed (objectCategory=user), attrs=0xbf83d468, args=0x0, res=0xbf83d488, count=0xbf83d2d4, cookie=0xbf83d2d8) at libads/ldap.c:700 #10 0x08235b23 in ads_do_search_all_args (ads=0x8322d58, bind_path=0x82ceeb8 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x8261aed (objectCategory=user), attrs=0xbf83d468, args=0x0, res=0xbf83d488) at libads/ldap.c:772 #11 0x0823f05a in ads_do_search_retry_internal (ads=0x8322d58, bind_path=0x8354638 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x8261aed (objectCategory=user), attrs=0xbf83d468, args=0x0, res=0xbf83d488) at libads/ldap_utils.c:60 #12 0x0823f5ee in ads_do_search_retry (ads=0x8322d58, bind_path=0x8354638 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x8261aed (objectCategory=user), attrs=0xbf83d468, res=0xbf83d488) at libads/ldap_utils.c:124 #13 0x0823f7bd in ads_search_retry (ads=0x8322d58, res=0xbf83d488, expr=0x8261aed (objectCategory=user), attrs=0xbf83d468) at libads/ldap_utils.c:139 #14 0x080b5515 in query_user_list (domain=0x8354878, mem_ctx=0x837a120, num_entries=0xbf83d744, info=0xbf83d748) at nsswitch/winbindd_ads.c:178 #15 0x0809be56 in query_user_list (domain=0x8354878, mem_ctx=0x837a120, num_entries=0xbf83d744, info=0xbf83d748) at nsswitch/winbindd_cache.c:1140 #16 0x0808d013 in winbindd_list_users (state=0x86eeed0) at nsswitch/winbindd_user.c:777 #17 0x0808b6f5 in request_recv (private_data=0x86eeed0, success=1) at nsswitch/winbindd.c:315 #18 0x0808bdc0 in rw_callback (event=0x86eeedc, flags=1) at nsswitch/winbindd.c:398 #19 0x0808c7ef in main (argc=) at nsswitch/winbindd.c:854 The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: Bug#484235: panic-action called for /usr/sbin/winbindd
=0xbf9ede18, args=0x0, res=0xbf9ede38) at libads/ldap.c:772 #11 0x082395d9 in ads_do_search_retry_internal (ads=0x834ded8, bind_path=0x832d0d8 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x825bb6d (objectCategory=user), attrs=0xbf9ede18, args=0x0, res=0xbf9ede38) at libads/ldap_utils.c:60 #12 0x08239b4a in ads_do_search_retry (ads=0x834ded8, bind_path=0x832d0d8 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x825bb6d (objectCategory=user), attrs=0xbf9ede18, res=0xbf9ede38) at libads/ldap_utils.c:124 #13 0x08239d1d in ads_search_retry (ads=0x834ded8, res=0xbf9ede38, expr=0x825bb6d (objectCategory=user), attrs=0xbf9ede18) at libads/ldap_utils.c:139 #14 0x080b4ce5 in query_user_list (domain=0x834e8f8, mem_ctx=0x8374b20, num_entries=0xbf9ee0f4, info=0xbf9ee0f8) at nsswitch/winbindd_ads.c:178 #15 0x0809bc4e in query_user_list (domain=0x834e8f8, mem_ctx=0x8374b20, num_entries=0xbf9ee0f4, info=0xbf9ee0f8) at nsswitch/winbindd_cache.c:1140 #16 0x0808cf6e in winbindd_list_users (state=0x83dc1e8) at nsswitch/winbindd_user.c:777 #17 0x0808b630 in request_recv (private_data=0x83dc1e8, success=1) at nsswitch/winbindd.c:315 #18 0x0808bc19 in rw_callback (event=0x83dc1f4, flags=1) at nsswitch/winbindd.c:398 #19 0x0808c6c9 in main (argc=) at nsswitch/winbindd.c:854 The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Hi. I've upgraded to the new version and also installed the samba-dbg package this time. No changes were made to the Samba configuration. The LDAP libraries were also updated. I still experience crashes. The versions of packages that have changed since the previous list are as follows: ii libldap-2.4-2 2.4.9-1 OpenLDAP libraries ii samba 2:3.0.30-2 a LanManager-like file and printer server for Unix ii samba-common2:3.0.30-2 Samba common files used by both the server and the client ii samba-dbg 2:3.0.30-2 Samba debugging symbols ii samba-doc 2:3.0.30-2 Samba documentation ii winbind 2:3.0.30-2 service to resolve user and group information from Windows NT servers The panic dump is as follows: Using host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb7b276d0 (LWP 29078)] 0xb7cfd6be in waitpid () from /lib/libc.so.6 #0 0xb7cfd6be in waitpid () from /lib/libc.so.6 #1 0xb7ca502e in ?? () from /lib/libc.so.6 #2 0x0811f1c8 in smb_panic (why=0x826cb24 internal error) at lib/util.c:1639 #3 0x08109d9a in sig_fault (sig=6) at lib/fault.c:47 #4 signal handler called #5 0xb7c97d96 in raise () from /lib/libc.so.6 #6 0xb7c99541 in abort () from /lib/libc.so.6 #7 0xb7c91230 in __assert_fail () from /lib/libc.so.6 #8 0xb7dc120a in ldap_parse_result () from /usr/lib/libldap_r-2.4.so.2 #9 0x0823001c in ads_do_paged_search_args (ads=0x8374b78, bind_path=value optimized out, scope=2, expr=0x834d998 (objectSid=\\01\\05\\00\\00\\00\\00\\00\\05\\15\\00\\00\\00\\CC\\37\\5A\\F6\\52\\D1\\77\\BB\\2F\\2E\\71\\FD\\8B\\29\\00\\00), attrs=0xbf9ec918, args=0x0, res=0xbf9ec928, count=0xbf9ec814, cookie=0xbf9ec818) at libads/ldap.c:700 #10 0x0823039f in ads_do_search_all_args (ads=0x8374b78, bind_path=0x83749f0 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x834d998 (objectSid=\\01\\05\\00\\00\\00\\00\\00\\05\\15\\00\\00\\00\\CC\\37\\5A\\F6\\52\\D1\\77\\BB\\2F\\2E\\71\\FD\\8B\\29\\00\\00), attrs=0xbf9ec918, args=0x0, res=0xbf9ec928) at libads/ldap.c:772 #11 0x082395d9 in ads_do_search_retry_internal (ads=0x8374b78, bind_path=0x834d928 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x834d998 (objectSid=\\01\\05\\00\\00\\00\\00\\00\\05\\15\\00\\00\\00\\CC\\37\\5A\\F6\\52\\D1\\77\\BB\\2F\\2E\\71\\FD\\8B\\29\\00\\00), attrs=0xbf9ec918, args=0x0, res=0xbf9ec928) at libads/ldap_utils.c:60 #12 0x08239b4a in ads_do_search_retry (ads=0x8374b78, bind_path=0x834d928 dc=PRY,dc=COM,dc=AU, scope=2, expr=0x834d998 (objectSid=\\01\\05\\00\\00\\00\\00\\00\\05\\15\\00\\00\\00\\CC\\37\\5A\\F6\\52\\D1\\77\\BB\\2F\\2E\\71\\FD\\8B\\29\\00\\00), attrs=0xbf9ec918, res=0xbf9ec928) at libads/ldap_utils.c:124 #13 0x08239d1d in ads_search_retry (ads=0x8374b78, res=0xbf9ec928, expr=0x834d998 (objectSid=\\01\\05\\00\\00\\00\\00\\00\\05\\15\\00\\00\\00\\CC\\37\\5A\\F6\\52\\D1\\77\\BB\\2F\\2E\\71\\FD\\8B\\29\\00\\00), attrs=0xbf9ec918) at libads/ldap_utils.c:139 #14 0x080b482c in query_user (domain=0x834e8f8, mem_ctx=0x82c9b38, sid=0xbf9eca28, info=0xbf9ec98c) at nsswitch/winbindd_ads.c:462 #15 0x0809a970 in query_user (domain=0x834e8f8, mem_ctx=0x82c9b38, user_sid=0xbf9eca28, info=0xbf9ec98c) at nsswitch/winbindd_cache.c:1654 #16 0x0808f237 in winbindd_dual_userinfo (domain=0x834e8f8, state=0xbf9ecae4) at nsswitch/winbindd_user.c:148 #17 0x080b7ab8 in schedule_async_request (child=0x834edd0) at nsswitch/winbindd_dual.c:481 #18 0x08095cae in init_child_connection (domain=0x834e8f8, continuation=0x80b92c0 domain_init_recv, private_data=0x8351b60) at nsswitch/winbindd_util.c:373 #19 0x080b94b6 in async_domain_request (mem_ctx=0x82c5328, domain=0x834e8f8, request=0x83505e0, response=0x8350e40, continuation=0x8096400 trustdom_recv, private_data_data=0x8351b20) at nsswitch/winbindd_dual.c:359 #20 0x080962f0 in rescan_trusted_domains () at nsswitch/winbindd_util.c:217 #21 0x0808c47d in main (argc=) at nsswitch/winbindd.c:772 The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
I've got a couple more stack dumps from today as well that look a little different. Is it worth sending them through as well? Once if very similar except for slight variations in a number of the hex values. But at step #18 a different path down the functions calls happens. So I'll paste that. Replace steps #18 to #20 from the previous dump with: #18 0x080b89ef in async_request_fail (state=0x8374cf0) at nsswitch/winbindd_dual.c:208 #19 0x0808bc7a in rw_callback (event=0x834f1e0, flags=1) at nsswitch/winbindd.c:389 #20 0x0808c6c9 in main (argc=) at nsswitch/winbindd.c:854 I've also got another one where at step #14 it's called query_user_list instead of just query_user. That walks a different list of functions, but still finally dies at nsswitch/winbindd.c:854 Let me know if I should send full stack dumps of both or not. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484462: nagios-snmp-plugins: Problem using Getopt::Long in perl 5.10 from nagios3
Package: nagios-snmp-plugins
Version: 1.1.1-3
Severity: normal
I am trying to use plugins from this package on a Nagios3 installation.
The example service definition in nagios is as follows:
define service{
host_namefileserver
service_description Samba Daemon
check_commandcheck_snmp_process_v2!smbd!0!0!!public
use generic-service
}
The error that shows up in the Nagios display is:
**ePN /usr/lib/nagios/plugins/check_snmp_process.pl:
Use of uninitialized value $opt in string eq at
/usr/share/perl/5.10/Getopt/Long.pm line 497,.
However, if I run the command manually as follows it works:
/usr/lib/nagios/plugins/check_snmp_process.pl \
-H 10.100.1.3 -C public -2 -n smbd -w 0 -c 0
The response that comes back from above is:
2 process matching smbd ( 0)
So the problem is something to do with the interaction with the embedded
perl within nagios 3.
I'm not sure if the bug is correctly filed against this package or if it
should be filed against nagios3.
I am using other plugins successfully however.
Also note that I have another host in a different subnet also using this
plugin with perl 5.10, but with nagios2 and that seems to be working
fine.
Regards,
--
Jim Barber
DDI Health
-- System Information:
Debian Release: lenny/sid
Architecture: i386 (i686)
Kernel: Linux 2.6.18.7-alcatraz (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages nagios-snmp-plugins depends on:
ii libnet-snmp-perl 5.2.0-1Script SNMP connections
ii perl 5.10.0-10 Larry Wall's Practical Extraction
ii perl-base 5.10.0-10 The Pathologically Eclectic Rubbis
ii ucf 3.006 Update Configuration File: preserv
nagios-snmp-plugins recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484235: [Pkg-samba-maint] Bug#484235: panic-action called for /usr/sbin/winbindd
Christian Perrier wrote: Severity: critical Justification: breaks unrelated software Sorry, that's overestimated. Okay sorry about the overstated severity. I was going to put it in as 'normal' but I followed the descriptions from reportbug which mislead me. When this breaks, packages like exim4, squid, and courier-imap break because the users can't authenticate. Please at least try upgrading to 3.0.30 as soon as it enters testing (as you seem to be using testing). I have no idea if that may fix the problem or not, though. Okay. I think the problem happened earlier, but it took me a while to report it. ie. It happened in 3.0.27 as well and maybe even .26? I couldn't tell you if it corresponds with an upgrade to Samba or LDAP. When .30 comes along I'll install the samba-dbg package so that I can get a better stack dump. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484462: [Pkg-nagios-devel] Bug#484462: nagios-snmp-plugins: Problem using Getopt::Long in perl 5.10 from nagios3
it is just enabled by default with nagios3. You can disable it with inserting # nagios: -epn in the first 10 lines of the plugin. This will be the case for the next nagios-snmp-plugins package. With kind regards, Jan. Thank you. I added the following to the top of the /usr/lib/nagios/plugins/check_snmp_process.pl script: # nagios: -epn This fixed the problem. Regards, -- Jim Barber DDI Health -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445334: snort-mysql: Details are too cursory
I also just encountered this problem.
I tried the above steps described by Javier and hit the following problems.
I tried to do these updates by logging into MySQL using the snort user.
It didn't have the privileges to run the SQL commands described.
So I looked at my /etc/mysql/debian.cnf file to get the password for the
debian-sys-maint MySQL user and connected like so:
mysql -u debian-sys-maint -h localhost -p snort
Then supplied the correct password when prompted.
The next problem I encountered is that the word 'schema' is a reserved word (at
least in MySQL 5.0.45 it is).
Therefore any operation I tried to perform on the schema table failed with an
error.
The solution is to wrap the table name in backticks.
Finally it wasn't clear to me from Javier's description that in the third step
you need to specify the old vseq number.
So the steps are:
1. ALTER TABLE signature ADD sig_gid INT UNSIGNED;
2. INSERT INTO `schema` (vseq, ctime) VALUES ('107', now());
3. DELETE from `schema` where vseq=106;
Is it possible to have the package check the vseq number in the schema table
and then automatically perform the upgrade?
Fixing this problem involved a lot of mucking around since the information
required was not in any of the README.Debian or NEW.Debian files (or any other
file that I could find).
Regards,
--
--
Jim Barber
DDI Health
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
