Newbie Question - How can i get my samba running again
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
May I horn in here? I did as suggested with the result posted below. I have no idea what this means. I also have just downloaded Samba. You help appreciated.
Bob
bob@Bob:~$ ps aux |grep smb
bob 26217 0.0 0.1 3004 764 pts/0 R+ 08:04 0:00 grep smb
bob@Bob:~$
"ps -aux" lists all the currently running processes on the machine.
"|" pipes the output into a second command, allowing you to filter or otherwise process the output.
"grep" searches each line fed into it for text strings, in this case "smb" (samba).
The output is therefore every line from ps that has "smb" in it. Since you got a hit, that means that smb is currently running on your system (as process number 26217).
Last edited by David the H.; 06-20-2008 at 08:40 AM.
@David the H.: Except in this case, smb isn't running. The output only shows one match, which is the 'grep smb' process. So the daemon didn't start properly.
The first thing I'd check are the logs. Since you're using the service command, I assume you're using redhat or fedora. In that case, have a look at the files in the /var/log/ directory. Particularly, take a look at the 'messages' and 'samba/*.log'. Also, check if you can start the smb daemon manually, by '/usr/sbin/smbd -i'. Play around with the debuglevel options to see if you can locate the problem.
edit: From the latest output, it looks like you've got a filesystem problem. Have a lok what output 'dmesg' gives. Also, are the filesystems mounted properly? Check with the 'mount' command.
Last edited by beadyallen; 06-20-2008 at 08:56 AM.
My mistake. It looks like you're right. the hit is not the smb process, it's the grep program searching for smb. I didn't realize the process output would list the search argument as well. If you had a second line in the output, THAT would be the running process.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.