nmbd core dumps
[2002/12/29 19:26:45, 0] lib/fault.c:fault_report(41) === [2002/12/29 19:26:45, 0] lib/util.c:smb_panic(1094) PANIC: internal error Here's the gdb trace: tethys# gdb /usr/local/sbin/nmbd nmbd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `nmbd'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/local/lib/libcups.so.2... (no debugging symbols found)...done. Reading symbols from /usr/lib/libssl.so.2...(no debugging symbols found)... done. Reading symbols from /usr/lib/libcrypto.so.2...(no debugging symbols found)... done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)... done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)... done. #0 0x28214b78 in kill () from /usr/lib/libc.so.4 (gdb) quit tethys# I recompiled libc.so.4 as a result of the above error and tried again. No change. However, since I'm installing samba from a package, it shouldn't matter. In addition, I have tried compiling from source different versions of samba and they all fail the same way. I haven't found this posted anywhere else so I'm completely stumped. Any ideas or help would be appreciated. Sincerely, Rusty Nejdl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: nmbd core dumps
I've tried the following versions of samba: samba-2.2.4_1.tgz samba-2.2.6.p2_1.tgz samba-2.2.7a.tar.gz samba-2.2.7a.tbz samba-3.0a19.tgz samba-3.0a20.tbz All produce the same results. I'm looking to see if there's just something I changed on the way to installing my box that would cause this. I'm not sure if this the key to it or not: [2002/12/29 19:30:01, 0] lib/util_sock.c:set_socket_options(165) Failed to set socket option SO_BROADCAST (Error Bad file descriptor) Ideas? Thanks! Rusty Nejdl Jack L. Stone(jackstone) wrote: > At 01:39 AM 12.30.2002 +, Stacey Roberts wrote: > >On Mon, 2002-12-30 at 01:32, Rusty Nejdl wrote: > >> Ok, I'm completely stuck with this one. I am trying to get Samba > >> running on my FreeBSD 4.7 - Release computer. Everytime I try to run > >> any version of nmbd, it core dumps. The config doesn't matter. Now, > >> of note is the fact that I did get Sambda running properly on this > >> computer when I first installed it, but in the process of building the > >> computer (installing more packages, configuring, and rebuilding a > >> kernel) samba broke. > >> > >> So, in knowing that, I used another computer to try to cause samba to > >> break in the same way and I can't do it. I installed all the same > >> ports and rebuilt the kernel and nmbd still ran. The only big > >> difference was that I didn't get all of the processes configured and > >> running. > >> > >> Here's /var/log/log.nmbd using a debug level of 3: > >> [2002/12/29 19:26:45, 0] nmbd/nmbd.c:main(794) > >> Netbios nameserver version 2.2.6pre2 started. > >> Copyright Andrew Tridgell and the Samba Team 1994-2002 > >> [2002/12/29 19:26:45, 3] param/loadparm.c:init_globals(1261) > >> Initialising global parameters > >> [2002/12/29 19:26:45, 3] param/params.c:pm_process(577) > >> params.c:pm_process() - Processing configuration file > >> "/usr/local/etc/smb.conf" > > > > > > > >> > >> I recompiled libc.so.4 as a result of the above error and tried again. > >> No change. However, since I'm installing samba from a package, it > >> shouldn't matter. In addition, I have tried compiling from source > >> different versions of samba and they all fail the same way. > >> > >> I haven't found this posted anywhere else so I'm completely stumped. > >> Any ideas or help would be appreciated. > >> > >> Sincerely, > >> Rusty Nejdl > > > >Hi, > > Out of curiosity, is there a reason why you're not running the latest > >version of samba? Or has 2.2.7_b already failed before this one? > > > >If the other box still has nmbd up and running fine, then I'd suggest > >you load more and more services (that are on the failing box) until nmbd > >cores. > > > >I'm no hacker, hence my avoidance of the core dump file :-) > > > >Regards, > > > >Stacey > >> > > Some months ago, I was having frequent core dumps for nmbd and an upgrade > of Samba cured it for me. Suggest the latest portupgrade > > Best regards, > Jack L. Stone, > Administrator > > SageOne Net > http://www.sage-one.net > [EMAIL PROTECTED] -- Any technical problem can be overcome given enough time and money. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: nmbd core dumps
Stacey, Okay, got it. Would you belive that portsentry caused nmbd to core dump when it runs? Rusty Stacey Roberts(stacey) wrote: > On Mon, 2002-12-30 at 02:14, Rusty Nejdl wrote: > > I've tried the following versions of samba: > > > > samba-2.2.4_1.tgz > > samba-2.2.6.p2_1.tgz > > samba-2.2.7a.tar.gz > > samba-2.2.7a.tbz > > samba-3.0a19.tgz > > samba-3.0a20.tbz > > > > All produce the same results. I'm looking to see if there's just something I > > changed on the way to installing my box that would cause this. I'm not sure if > > this the key to it or not: > > > > [2002/12/29 19:30:01, 0] lib/util_sock.c:set_socket_options(165) > > Failed to set socket option SO_BROADCAST (Error Bad file descriptor) > > > > Ideas? > > Silly suggestion. > > Is it possible for you to try: > # cd /usr/ports/net/samba; make install clean > > Unless you've got some other reason for not doing it like that, of > course. > > Regards, > > Stacey > > > > > Thanks! > > Rusty Nejdl > > > > Jack L. Stone(jackstone) wrote: > > > At 01:39 AM 12.30.2002 +, Stacey Roberts wrote: > > > >On Mon, 2002-12-30 at 01:32, Rusty Nejdl wrote: > > > >> Ok, I'm completely stuck with this one. I am trying to get Samba > > > >> running on my FreeBSD 4.7 - Release computer. Everytime I try to run > > > >> any version of nmbd, it core dumps. The config doesn't matter. Now, > > > >> of note is the fact that I did get Sambda running properly on this > > > >> computer when I first installed it, but in the process of building the > > > >> computer (installing more packages, configuring, and rebuilding a > > > >> kernel) samba broke. > > > >> > > > >> So, in knowing that, I used another computer to try to cause samba to > > > >> break in the same way and I can't do it. I installed all the same > > > >> ports and rebuilt the kernel and nmbd still ran. The only big > > > >> difference was that I didn't get all of the processes configured and > > > >> running. > > > >> > > > >> Here's /var/log/log.nmbd using a debug level of 3: > > > >> [2002/12/29 19:26:45, 0] nmbd/nmbd.c:main(794) > > > >> Netbios nameserver version 2.2.6pre2 started. > > > >> Copyright Andrew Tridgell and the Samba Team 1994-2002 > > > >> [2002/12/29 19:26:45, 3] param/loadparm.c:init_globals(1261) > > > >> Initialising global parameters > > > >> [2002/12/29 19:26:45, 3] param/params.c:pm_process(577) > > > >> params.c:pm_process() - Processing configuration file > > > >> "/usr/local/etc/smb.conf" > > > > > > > > > > > > > > > >> > > > >> I recompiled libc.so.4 as a result of the above error and tried again. > > > >> No change. However, since I'm installing samba from a package, it > > > >> shouldn't matter. In addition, I have tried compiling from source > > > >> different versions of samba and they all fail the same way. > > > >> > > > >> I haven't found this posted anywhere else so I'm completely stumped. > > > >> Any ideas or help would be appreciated. > > > >> > > > >> Sincerely, > > > >> Rusty Nejdl > > > > > > > >Hi, > > > > Out of curiosity, is there a reason why you're not running the latest > > > >version of samba? Or has 2.2.7_b already failed before this one? > > > > > > > >If the other box still has nmbd up and running fine, then I'd suggest > > > >you load more and more services (that are on the failing box) until nmbd > > > >cores. > > > > > > > >I'm no hacker, hence my avoidance of the core dump file :-) > > > > > > > >Regards, > > > > > > > >Stacey > > > >> > > > > > > Some months ago, I was having frequent core dumps for nmbd and an upgrade > > > of Samba cured it for me. Suggest the latest portupgrade > > > > > > Best regards, > > > Jack L. Stone, > > > Administrator > > > > > > SageOne Net > > > http://www.sage-one.net > > > [EMAIL PROTECTED] > -- > Stacey Roberts > B.Sc (HONS) Computer Science > > Web: www.vickiandstacey.com > > -- Any technical problem can be overcome given enough time and money. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: VirtualBox: out of swap space
On Mon, 9 Aug 2010 17:37:39 +0200, Samuel Martín Moro
wrote:
> Hi,
>
>
> I'm trying to have a few BSD VMs (4.7, 5.5, 6.2, 7.2, 8.1)
> running under VirtualBox-OSE / FreeBSD-8.1-RELEASE-amd64
>
>
> First problem:
> Sometimes, when I start a VM, all other running VM stop,
> their status switch to 'abort' (or whatever the
> traduction is, here it's "avorté").
> Reading my /var/log/messages, I see a few
> 'pid (VirtualBox), uid 0, was killed: out of swap space'
>
> I've got 8Gb of RAM, and so assumed I wouldn't need any swap.
> Was I wrong?
> Have I to reinstall my server to add some swap?
> (and if so, how much?!)
Samuel,
It is generally a bad idea not to have a swap partition. I have 12GB
of memory and I even hit swap, though very little.
[tethys]:/home/rnejdl> swapinfo -h
Device 1K-blocks UsedAvail Capacity
/dev/ada0s1b 4194304 4.5M 4.0G 0%
I have 4GB on mine and that is plenty.
I don't have answers for the below though.
Sincerely,
Rusty Nejdl
>
>
> btw, my PC (home) have the same HWare (core i7 930, 8Gb DDR3)
> I can run two 8.1-RELEASE (amd64 + i386), and two debian
> while host is running compiz and all that gay stuff...
> (ArchLinux x86_64)
>
> except VirtualBox, the server I'm having problems with, is
> hosting some nfs shares and running ion2 (since VBoxVNC
> segfaults... I need a WM). And that's it.
>
>
> Second problem:
> When I'm creating a disk (in VirtualBox), and while there's
> some scp or so running on other guests, these guests display
> some gvfs errors, about not finding ad0.
> Sometimes, they just halt, and wait I pressed a key to reboot.
>
>
> Third problem:
> I already posted that on emulation this morning:
> I can't boot FreeBSD-8.1-amd64. It's stuck in
> 'md0: preloaded image x bytes 0xsomewhere'
> nothing else happend...
>
>
> I could have finished already if I just had installed a Linux
> host in the first place...
> I read so much posts recently, from FreeBSD/VBox users, saying
> everything's working just fine.
> I assumed it would be OK.
> Obviously not...
>
> Is there some hope sticking with BSD?
> (if I can get rid of the swap and the 8.1 problems, it would
> be fine enough)
>
>
> I'm seriously thinking on dropping that BSD idea, and choosing
> some random linux to make it work... (and maybe, try xen...)
>
>
> What should I do?
>
> Thanks for any advices.
>
>
> Samuel Martín Moro
> {EPITECH.} tek4
> CamTrace S.A.S
> (+033) 1 41 38 37 60
> 1 Allée de la Venelle
> 92150 Suresnes
> FRANCE
>
> "Nobody wants to say how this works.
> Maybe nobody knows ..."
> Xorg.conf(5)
> ___
> freebsd-emulat...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [kde-freebsd] startkde: Could not start kdeinit4. Check your installation.
On Tue, 20 Jul 2010 18:51:50 +0200, claudiu vasadi wrote: hello fellas, can no one give me any ideas ? I reinstalled libthr.so.3 in the meantime but with no effect. I got it last night and simply recompiling kdelibs was sufficient: sudo portupgrade -f kdelibs Rusty Nejdl http://networking.ringofsaturn.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [kde-freebsd] FreeBSD-8.0-RC2 problems
On Mon, 9 Nov 2009 17:46:06 +, Masoom Shaikh wrote: On Fri, Nov 6, 2009 at 2:41 PM, Rusty Nejdl wrote: On Fri, 6 Nov 2009 17:33:00 +0530, Masoom Shaikh wrote: Hello, Last Saturday I installed 8.0-RC2 from source by compiling on 7.1 installation. building and installing was smooth as always has been. Then I pkg_add'ed xorg and KDE4, this was painless too. I am very disappointed with my experience problem # 1 The problem is KDE4 is not able to display anti aliased fonts. I have made the required changes to make it work, of course, in System Settings -> Appearance -> Fonts Hinting -> Full, and there is is one more option, the name i cannot recall ATM, I have set it to RGB. DPI to 96..this is has worked for all combination of installs I have used so far, viz KDE3 on FreeBSD-6.x to KDE4.1.x on FreeBSD-7.x and KDE4.2 on FreeBSD-8.0RC1 problem # 2 I observed that both FreeBSD8.0-RC1 and FreeBSD8.0-RC2, simply freeze due to no reason. The pain is I don't get a core dump. When it freezes the only option is to hard boot by reseting the power. This might need more information to guess the cause. I will give basic info. This is Dell Inspiron 1525 Laptop, with Intel Core2. My suspect mostly goes to wpi driver, no proof, just my gut feeling. problem # 3 starting with 8.0 wpi driver no longer is the interface, wlanX is to be created. this is not news, but every time I manually create the wlan0 interface and spawn wpa_supplicant. This shuould be automatic, as I have followed the guidelines of rc.conf(5). I can provide output of rc_debug="YES" if someone is willing. How can i install all files under /etc from the source ? Masoom Shaikh Regarding #2, I suggest disabling ACPI. I also had system freezes happen on my computer until I did this but this has always been an ongoing issue with my system and I lose nothing by turning it off. Sincerely, Rusty Nejdl http://networking.ringofsaturn.com [3] how do we disable acpi ? is it hw.acpi.disable_on_reboot ? if it is I guess I shud set it to 1 in loader.conf, it still remains 0 You can disable APIC support with hint.apic.0.disabled="1" in loader.conf. http://www.freebsd.org/doc/en/books/handbook/acpi-debug.html Sincerely, Rusty Nejdl http://networking.ringofsaturn.com Links: -- [1] mailto:rne...@ringofsaturn.com [2] mailto:masoom.sha...@gmail.com [3] http://networking.ringofsaturn.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
