Debian Configuration :: Samba + Aufs Leads To Kernel Crash
Apr 20, 2010
I've got a server with bit of chaos on it. There is similar data on different partitions which I like to mount remotely with samba. So I setup aufs on the server and then share the merged aufs directory (as read only). All seemed fine, and I was able to mount it nicely. However, when I enter the directory in question does the kernel on the mounting puter start misbehaving.
First it freezes for about a minute. Then I get a bunch of oops-looking messages in dmesg and the system eventually locks up totally. This is what it looks like:
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
I run an old Toshiba Satellite M35x S114 Laptop with Debian Testing, it always runned smoothly - although it IS testing . Since the latest update to kernel 2.6.32 , the X server just freezes. The init goes all the way to gdm, and then a blank screen , no mouse pointer, no way to get out of this screen (not CTRL+ALT+BACSPACE not CTRL+ALT+F1 / F2 ... etc) just a hard reset.
I can boot to the older .30 kernel with absolutely no problem, gdm starts normally login successfull (as I am able to write this on the reffered machine and all).
Here comes the gory details:
>>> The graphic card: lspci | grep gra 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) >>> When it works with .30 kernel: cat /var/log/Xorg.0.log code....
Noting that there are no more Modlines in the new Xorg.0.log
Besides, X is disabling the mouse and keyboard in the configuration.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I got a notification that there was an upgrade available today in ubuntu 9.10 64, after the update i restarted my system and while booting i encountered this error message:
Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block (8,17)
does this have something to do with the OS looking at the wrong hd? theres no command prompt to actually do anything and i tried booting in safe mode and had the same problem. Let me know what i can do!
I'm using Squeeze and icedove and iceweasel and I've installed the package linux-image-2.6.36-2.dmz.2-liquorix-686. It works fine on my Dell 1521 Inspiron laptop with only one exception. If I'm surfing the web or checking my mail via a wired internet connection I'm fine... if I'm surfing the web or checking my mail via a wifi connection everything is fine... but if I happen to forget to connect to a wifi connection, and I'm in a situation where a wired connection is not available, I can start iceweasel (it doesn't do anything constructive), but checking my mail with icedove (simply starting the program) crashes my computer.
If I boot up with the 2.6.32-5 kernel, the one that's in the regular debian repository, I can not duplicate the crash. Somewhere I read that the liquorix kernels are optimized for a desktop computer. Is this my problem? Is it something else?
During the crash my screen goes to a text console and I see syslogd messages on the screen -- which I cannot reproduce here.
First of all, my computer is running Debian Jessie. uname -a gives me this output: Code: Select allLinux felix-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
So today I updated my system with aptitude update and aptitude upgrade, and there was few paquages that were updated. Among them was one "linux-image" or "linux-headers". I believe that it is linked to this security update: [URL].... .
During the time aptitude upgrade was running, I was simply surfing on Iceweasel. However, it seems that my system suddenly restarted, without asking me the permission or without notifying me. It really looked like I pressed the restart key, but I actually didn't. My computer battery was full charged and plugged in. So, I do believe that it is my system that rebooted himself after the aptitude upgrade was completed (or even during the upgrade, I don't know).
So my computer restarts, and brings me to GRUB menu: I boot Debian and then I get the usual [ OK ] ***** lines telling that the system boots normally. But this time, I get some errors:
Code: Select all[FAILED] Failed to set up automount Arbitrary Executable file format file system Automount point ... [FAILED] Failed to start load kernel module ... [FAILED] Failed to mount /boot/efi [DEPEND] Dependency failed for Local File Systems
I arrive then in Emergency mode with this message: Code: Select all Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
I tried systemctl default but it doesn't boot my system normally. I also tried Control-D but it just reprints the same message. And finally I typed journalctl -xb, which gives me a long log file (855 lines) that I do not understand.
I would give this log file, but it seems that my internet connexion is broken (because of the kernel, I mean), even with an Ethernet cable. So I can't connect with ssh to the computer I use at the moment, and I can't either send it to myself by mail. I tried to mount an usb key, but it seems that any key won't be mounted because of a kernel problem.
An obvious solution to my problem may be to come back to an older kernel version. However, only the lasted kernel version (x86_64 Linux 3.16.0-4-amd64) is installed. dpkg --list | grep linux-image gives me indeed:
Code: Select alliF linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 amd64 Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
I do not know how to come back to an older kernel, as far as I haven't any internet connection and as far as I seem to not be able to load an usb key.
I tried assuming that the touchpad was a synaptics device and configure it as such, but it wasn't and this caused X to crash. (I also tried piping the output to grep -i and search for some key terms).
I am on debian jessie. I ran "apt-get update && apt-get upgrade" and midway through the upgrade my computer suddenly rebooted.
I wasn't paying close attention to the upgrade process so I didnt see if there was any error messages right before the reboot. The laptop was plugged in, fully charged and I've never had issues with overheating.
When I boot now I get to a shell with a message that says:
Code: Select allWelcome to emergency mode. After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
If I try "systemctl default" there's a message that simply says "Hangup", nothing else happens.
Looking through "journalctl -xb" I see this:
Code: Select allFailed to insert module 'autofs4' Failed to open /dev/autofs: No such file or directory Failed to initialize automounter: No such file or directory Failed to set up automount Arbitrary Executable File Formats File System Automount Point. Failed to start Load Kernel Modules. If I retry "apt-get upgrade" it says: Code: Select alldpkg was interrupted, you must maually run dpkg --configure -a to correct the problem If I run "dpkg --configure -a" stops at the package cups-browsed with message saying "Hangup"
Output of a few commands I saw in another forum thread:
Is this fixable without jumping through too many hoops or should I just reinstall the system? I need the computer for work so Im not gonna spend days trying to fix it without reinstalling.
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
My computer has been installed a system of Windows XP,and I want to experience the outstanding of this Linux system.So I decide to install two system on my computer,but bad luck ,I've found that I can't find the netcard in the new installed system ,and it is the in the primary system.
I had set up as a NT4 style PDC. There is no longer any PDC/BDC dynamic with Samba4 and MS AD support.
I purged samba packages and winbind et al and provisioned the domain correctly, and everything works well now.
What follows is the original post.
========================================================================================== After much struggling with DNS settings, I finally got a basic samba AD controller up and running, and then that's about as far as I got.
As soon as I tried to use the RSAT I found that I could not connect RSAT to the AD server while logged in as root.
The error I get is:
Naming information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your system adminsiotrator to verify that your domain is properly configured and is currently online.
I'm running sid, reasonably updated. I decided to add a samba share. I installed samba (2:3.4.8~dfsg-2), samba-tools, smbclient, smbfs, & samba-client. I did a "/etc/init.d/samba start" and even rebooted. But when I try to add a samba password for my regular user I can't.
# smbpasswd -a praxis bash: smbpasswd: command not found I did a "locate smbpasswd" but I'm only seeing:
0 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.Need to get 49.2MB/55.5MB of archives. After unpacking 149MB will be used.Do you want to continue?
I'm using Xfce 4.8, which now provides built-in samba browing in thunar. This works like a charm. I can browse a samba share (external HD connecter to router via USB). Yet it appears to me now that the support is limited to thunar. I mean double clicking on a file allows me to open/edit that file if and only if the software itself has samba support. In practice, double-clicking on a movie opens it with vlc thanks to vlc's own smb support. Even then, I can't find a way to add the subtitle file. I reckon that to use the share transparently, I would need to mount it the "mount" way. Either on a mount point like /mnt/hard_drive or something like .gvfs/hard_drive.
Is my understanding correct ? Is that my only option? Considering the disk won't be switched on at startup, fstab is not the solution. Would gigolo be the right choice? I spent some time trying gigolo a few days ago, following an easy tuto found on the web and it didn't work as expected. If needed I could give it another try.
I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.
Output of "systemctl status samba.service":
Code: Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)
Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating. Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).
[Code] ....
Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.
I currently have a Samba share on a Debian 7 system. This share was only ever used by Windows systems on the network.
I just finished setting up a Debian 8 system with Xfce, and now I would like to connect to the share. I already installed gvfs-backends and gvfs-bin. When I go to Thunar file manager, and click browse network, I'm presented with a "Windows Network" shortcut. When clicked it says: Failed to open "Windows Network". Failed to retrieve share list from server: No such file or directory.
Following yesterday's and then today's upgrade of my Debian 8 32-bit system (among other things to samba 2:4.1.17+dfsg-2+deb8u2 (yesterday: ...deb8u1)) I cannot connect my Mint 17.3 laptop to the server anymore. Were there any changes to smb.conf regarding authentication or other aspects that might lead to this problem? I am enclosing part of my smb.conf. By the way - I also have trouble using ssh to connect to the Debian machine, such as the ssh-command taking "for ever" and then getting the message "Write failed: Broken pipe" when entering an ls-command on the command line.
H. Stoellinger smb.conf: [global] workgroup = RAINERMUSIK netbios name = hsdesk server string = Samba Server hsdesk
Let me introduce myself, my name is Carlos Alegría from Chile and I'm System administrator for a educational Institute. We use samba+ldap, for login accounts and file sharing but we not use samba with PDC.
Long time ago at the 2009 year, I was Installing the same system and this worked perfectly. But on our summer the hard disk of server has broken, so i was need installing all the system again. So the problem is with SAMBA, when i connect to the network resource, this is to slow, and when i try transfer files are slow.
My sistem is on Debian 8 Jessie and the Samba Version is 2:4.1.17+dfsg-2+deb
Code: Select all[global] workgroup = LABORATORIO netbios name = Shinigami server string = debian
Is it possible (on lenny, in case that matters) to backup some directories with rdiff-backup, with the target being a WinXP Pro Host, i.e. the target being a SMB share? My idea is to start the XP-Box over WOL, run rdiff-backup and then shut it down using "net rpc SHUTDOWN"...
Using Debian 5.0 Stable, with all current updates, if I type \192.168.0.249 I get samba access and can use all the shared files ok.if I go via the network the computer should be called \squ-eee-zeboxserver but instead comes up as \SQU-EEE-ZEBOXSERsqu-eee-zeboxserver which when clicked gives the attached error.
I'm trying to setup roaming profiles on our Samba PDC. I've been at it all day, running into a lot of issues with access denied, and going around changing permissions hoping to fix it
The problem seems to have evolved over the day, getting worse. Right now it's an error message on logging in: Windows cannot locate the server copy of your roaming profile.....
DETAIL- The network name cannot be found. In addition, the user does not have access to any shares by default.
The server can be accessed manually and the user can connect to shares. The server can be pinged by the client. The client's user profiles do not get stored or retrieved on logout/in
current smb.conf # Samba config file created using SWAT # from UNKNOWN () # Date: 2010/08/22 16:34:42 [global] workgroup = ROSHNI.LOCAL
I just noticed after installing a new server with samba that a portscan will show the samba used ports. This server has two interfaces, a world address eth0 and an intranet eth1. The samba ports show in scanning either interface, even after I changed samba to listen only to the intranet (192.168.x) address.
I am concerned especially about the 139 and 445 ports, which could attract a lot of garbage traffic.This is Debian 5.05 default samba installation.Otherwise similarly installed Ubuntu box with two interfaces does not show samba at all, even though smbd is running and working just fine.
I've been at this for hours now and am still not getting it to work. I recently installed Squeeze on my home server, overwriting a Lenny installation. I've been able to add my NT domain accounts back in and pdbedit shows the expeted values - e.g.:
root@whenim64:/home/samba/profiles# pdbedit -Lv garydale Unix username: garydale NT username: Account Flags: [U ] User SID: S-1-5-21-832165970-4128531365-4003982369-1002 Primary Group SID: S-1-5-21-832165970-4128531365-4003982369-513 Full Name: Gary Dale [Code].....
However, although I can log on, I can't get the roaming profiles working. I get the "windows cannot locate the server copy of your roaming profile" message. Since my Unix account names/numbers are the same and the profiles are in the previously working /home folder that didn't get touched, I can't see how it''s a permissions problem. Noneheless, I removed an old profile which should have let WIndows create a new one. It didn't. I still got the same error. I did have to reinstate the groupmaps (don't know why the samba install doesn't do this) but they seem OK.
I noticed that KDE does not have a way to browse for network printers like Gnome does. I installed system-config-printer to fix this(if there is a KDE route that would be nice as well). Anyway, I go to add a printer and select "Network Printer" and click "Windows Printer via SAMBA". This is where i would typically press "Browse..." but it is unclickable. This leads me to believe that I am missing a package. Essentially my question is: What are the necessary packages to access Windows printers via SAMBA with system-config-printer?
I installed the Gnome desktop CD1 AMD 64 version of Debian Squeeze. I installed samba and python-smbc. I am missing samba printers in my system-config-printer. Anyone know why? [url]
