[Bug 1053414] Re: smbd crashed when trying to connect from Ubuntu
Hi. Right now every time I try and connect to the server, smbd crashes after sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal libgl1-mesa-glx-lts-quantal xserver-xorg-lts-quantal libgl1-mesa-dri- lts-quantal:i386 libgl1-mesa-glx-lts-quantal:i386 works fine but samba crashed... Downgrading to kernel 3.2.0-38-generic helped. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f45b1fc643e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6 #0 0x7f45b1fc643e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f45b1f4c29e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f45b539ebec in smb_panic () #3 0x7f45b50e9be6 in ?? () #4 0x7f45b50e9f0f in set_sec_ctx () #5 0x7f45b50d8db5 in ?? () #6 0x7f45b5100e2b in ?? () #7 0x7f45b510176e in ?? () #8 0x7f45b5101aea in make_connection () #9 0x7f45b50b282c in reply_tcon_and_X () #10 0x7f45b50fcfa4 in ?? () #11 0x7f45b50fd3bb in ?? () #12 0x7f45b50fd7d3 in ?? () #13 0x7f45b53ae8ae in run_events_poll () #14 0x7f45b50fef42 in smbd_process () #15 0x7f45b560c66f in ?? () #16 0x7f45b53ae8ae in run_events_poll () #17 0x7f45b53aea4a in ?? () #18 0x7f45b53af5d0 in _tevent_loop_once () #19 0x7f45b507d030 in main () A debugging session is active. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1053414 Title: smbd crashed when trying to connect from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1053414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1053414] Re: smbd crashed when trying to connect from Ubuntu
sorry its : Description: Ubuntu 12.04.2 LTS Release: 12.04 Codename: precise 3.5.0-23-generic aptitude show samba Csomag: samba Állapot: telepítve Automatikusan telepített: nem Verzió: 2:3.6.3-2ubuntu2.3 Prioritás: opcionális Szakasz: net Karbantartó: Ubuntu Developers Architektúra: amd64 Tömörítetlen méret: 23,4 M Függőségek: samba-common (= 2:3.6.3-2ubuntu2.3), libwbclient0 (= 2:3.6.3-2ubuntu2.3), libacl1 (>= 2.2.51-5), libattr1 (>= 1:2.4.46-5), libc6 (>= 2.15), libcap2 (>= 2.10), libcomerr2 (>= 1.01), libcups2 (>= 1.4.0), libgssapi-krb5-2 (>= 1.10+dfsg~), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.10+dfsg~), libldap-2.4-2 (>= 2.4.7), libpam0g (>= 0.99.7.1), libpopt0 (>= 1.14), libtalloc2 (>= 2.0.4~git20101213), libtdb1 (>= 1.2.7+git20101214), zlib1g (>= 1:1.1.4), debconf (>= 0.5) | debconf-2.0, upstart-job, libpam-runtime (>= 1.0.1-11), libpam-modules, lsb-base (>= 3.2-13), procps, update-inetd, adduser, samba-common-bin Ajánlott csomagok: logrotate, tdb-tools Javasolt csomagok: openbsd-inetd | inet-superserver, smbldap-tools, ldb-tools, ctdb, ufw Ütközések: samba4 (< 4.0.0~alpha6-2), samba4 (< 4.0.0~alpha6-2), samba Helyettesíti: samba-common (<= 2.0.5a-2), samba-common (<= 2.0.5a-2) [2013/02/20 13:35:23.160931, 0] lib/util.c:1221(log_stack_trace) BACKTRACE: 21 stack frames: #0 smbd(log_stack_trace+0x1a) [0x7f7dabefdaea] #1 smbd(smb_panic+0x25) [0x7f7dabefdbc5] #2 smbd(+0x163be6) [0x7f7dabc48be6] #3 smbd(set_sec_ctx+0x8f) [0x7f7dabc48f0f] #4 smbd(+0x152db5) [0x7f7dabc37db5] #5 smbd(+0x17ae2b) [0x7f7dabc5fe2b] #6 smbd(+0x17b76e) [0x7f7dabc6076e] #7 smbd(make_connection+0x1ea) [0x7f7dabc60aea] #8 smbd(reply_tcon_and_X+0x1dc) [0x7f7dabc1182c] #9 smbd(+0x176fa4) [0x7f7dabc5bfa4] #10 smbd(+0x1773bb) [0x7f7dabc5c3bb] #11 smbd(+0x1777d3) [0x7f7dabc5c7d3] #12 smbd(run_events_poll+0x34e) [0x7f7dabf0d8ae] #13 smbd(smbd_process+0x812) [0x7f7dabc5df42] #14 smbd(+0x68666f) [0x7f7dac16b66f] #15 smbd(run_events_poll+0x34e) [0x7f7dabf0d8ae] #16 smbd(+0x428a4a) [0x7f7dabf0da4a] #17 smbd(_tevent_loop_once+0x90) [0x7f7dabf0e5d0] #18 smbd(main+0xed0) [0x7f7dabbdc030] #19 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f7da8a8776d] #20 smbd(+0xf7515) [0x7f7dabbdc515] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1053414 Title: smbd crashed when trying to connect from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1053414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 879710] Re: ubuntu-vm-builder crashes when trying to umount tmp directory.
Well, that workaround did not help me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/879710 Title: ubuntu-vm-builder crashes when trying to umount tmp directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/879710/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1008596] Re: vmbuilder policy-rc.d denied access
I am aware of workaround but it does not work for me. that problem still persist. ** Changed in: vm-builder (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1008596 Title: vmbuilder policy-rc.d denied access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1008596/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1132302] [NEW] drbd8-utils are not compatible with kernel 3.8
Public bug reported: Ubuntu Raring is going to ship with kernel 3.8, which contains DRBD v8.4.2 Unfortunately, the userland tools in drbd8-utils are still v8.3.13, which is 1 major version behind: they are not compatible with the kernel module. >From my testing (both in a vmware environment and a live-usb), loading the module and then using drbdadm to bring up a resource blocks for a long time and eventually leads to the message "No response from the DRBD driver! Is the module loaded?". Replacing the packaged tools with a locally compiled v8.4.2 totally fixes the problem. Lionel Sausin ** Affects: drbd8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1132302 Title: drbd8-utils are not compatible with kernel 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1132302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037571] Re: vmbuilder should use distro-info to determine available Ubuntu releases
I've just encountered this on 12.04 Precise, wanting to build raring VMs. I created the attached shell script that will add any new suites a.k.a. distro a.k.a releases (e.g. quantal, raring) to the installed list. Simply call the script once and it will add the required files. Needs calling each time a new suite a.k.a. release is available. Don't forget to give it execute permissions: sudo chmod a+x /usr/local/bin/vm-builder-add-suites ** Attachment added: "shell script to add all releases to vmbuilder" https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037571/+attachment/3544016/+files/vm-builder-add-suites -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1037571 Title: vmbuilder should use distro-info to determine available Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037571/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1132313] [NEW] lbvirt cannot start VM due to missing kvm-spice in /etc/vmbuilder/libvirt/libvirtxml.tmpl
Public bug reported: Using Ubuntu 12.04.2 Precise on amd64 with kvm_intel, libvirt and vmbuilder. Building VMs with vmbuilder using, e.g: $ sudo vmbuilder kvm ubuntu --suite precise --flavour virtual --arch i386 -o --libvirt qemu:///system --hostname vm-ubuntu-precise-playpen followed by: $ virsh -d 0 -c qemu:///system start vm-ubuntu-precise-playpen results in a failure: error: Failed to start domain vm-ubuntu-precise-playpen error: internal error Process exited while reading console log output: Supported machines are: pc Standard PC (alias of pc-1.0) pc-1.0 Standard PC (default) pc-0.14Standard PC pc-0.13Standard PC pc-0.12Standard PC pc-0.11Standard PC, qemu 0.11 pc-0.10Standard PC, qemu 0.10 isapc ISA-only PC I eventually tracked this down to the libvirt domain definition using /usr/bin/kvm instead of /usr/bin/kvm-spice editing that line using: $ virsh -d 0 -c qemu:///system edit vm-ubuntu-precise-playpen allows the VM to start correctly. The problem stems from the libvirt template installed by vmbuilder at "/etc/vmbuilder/libvirt/libvirtxml.tmpl" using the wrong emulator. It should be "/usr/bin/kvm-spice" not "/usr/bin/kvm". A simple fix is: $ sudo sed -i 's,\(/usr/bin/kvm\),\1-spice,' /etc/vmbuilder/libvirt/libvirtxml.tmpl ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1132313 Title: lbvirt cannot start VM due to missing kvm-spice in /etc/vmbuilder/libvirt/libvirtxml.tmpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1132313/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1090223] Re: The directory ubuntu-kvm disappeared after creating vms failed
** Changed in: vm-builder (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1090223 Title: The directory ubuntu-kvm disappeared after creating vms failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1090223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1132345] [NEW] grub 0.97 and 2.00 installed in VMs causes confusion
Public bug reported: Using Ubuntu 12.04.2 Precise on amd64 with kvm_intel, libvirt and vmbuilder. After building a VM for raring using: $ sudo vmbuilder kvm ubuntu --flavour virtual --suite raring --arch i386 --hostname vm-ubuntu-raring-playpen --proxy http://10.254.251.1:3142 --libvirt qemu:///system --addpkg linux-image-generic --addpkg acpid I was trying to force the console to be text-mode by removing "splash", adding "nomodeset" and "GRUB_TERMINAL=console" to "/etc/default/grub" and then doing 'update-grub'. The changed settings weren't having any effect. I found that "/boot/grub/grub.cfg" (from grub2) was missing. Further investigation showed "/boot/grub/menu.lst" (from grub 0.97) was present, but didn't reflect the changes I was making to "/etc/default/grub". Then I found: $ dpkg-query -l '*grub*' | grep -v ^un Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---=== ii grub 0.97-29ubuntu66 i386 GRand Unified Bootloader (Legacy version) ii grub-common 2.00-12ubuntu1 i386 GRand Unified Bootloader (common files) rc grub-pc 2.00-12ubuntu1 i386 GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.00-12ubuntu1 i386 GRand Unified Bootloader, version 2 (PC/BIOS binaries) $ lsb_release -a && uname -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Raring Ringtail (development branch) Release:13.04 Codename: raring Linux vm-ubuntu-raring-playpen 3.8.0-7-generic #15-Ubuntu SMP Thu Feb 21 20:44:11 UTC 2013 i686 i686 i686 GNU/Linux I had to purge "grub" then install "grub2" followed by running the grub to grub2 upgrade script: sudo apt-get --purge remove grub sudo apt-get install grub2 sudo /usr/sbin/upgrade-from-grub-legacy sudo rm -f /boot/grub/menu.lst* ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1132345 Title: grub 0.97 and 2.00 installed in VMs causes confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1132345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
