Ubuntu Forums Code of Conduct. Forum Quick Links Unanswered Posts New Posts View Forum Leaders FAQ Contact an Admin Forum Community Forum Council FC Agenda Forum Governance Forum Staff Ubuntu Forums Code of Conduct Forum IRC Channel Ubuntu Community Ubuntu Get Ubuntu Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search.

Page 1 of 2 1 2 Last Jump to page: Results 1 to 10 of Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode. August 12th, 1. The shares work absoluetly fine, but I'm seeing some errors in my logs that I don't know how to get rid of.

Every time I boot up my machine, I see this error in my logs: August 16th, 2. It seems the error is related to the way smbd is called by upstart. Why is this happening? Anyone elese sees these messages in their logs? August 18th, 3. Originally Posted by silentcreek. Ok, I narrowed down the problem by checking the upstart configuration file for smbd.

August 20th, 4. Originally Posted by bab1. My assumption is this is a standalone server workgroup and somewhere you have misconfigured the smb.

Samba nmb (nmbd) will not start on boot - CentOS

I have my suspicions, but it is easier to just start over. With a default installation with no modifications at all, samba should work correctly. August 20th, 5.

I just set up Ubuntu Server So, this issue is not related to my smb. The messages about the printers disappear if you set your smb. But the issue "standard input is not a socket, assuming -D option" stays. August 21st, 6. Ok, this is definitely a Ubuntu issue. August 21st, 7.

All I can say is this is NOT the normal Samba reaction to a default install. I have to think you have changed or installed something to cause this problem. What is the specific environment? Have you made any networking files changes? By default Samba listens on all interfaces so this problem should not occur by default.

August 21st, 8. I've installed or helped others install Samba [ It always works fine.

[/09/19 , 0] smbd/server.c(main) smbd version started - etygivusyx.web.fc2.com

The package is stable for Ubuntu in that regard. August 21st, 9. Here's the description of what I did: I checked OpenSSH and Samba file server the same selection as on my production server. August 21st, I will try another clean installation and install samba manually afterwards to see if this solves it.

However, I have to postpone any further testing until next week as I'm traveling now.

Samba error : standard input is not a socket - Wyldeplayground dotnet

About the VM environment: No, my actual production server is not virtualized. The installation in a VM was for testing purposes only to see if a new installation behaves differently.

It was just easier to do this in a VM quickly without touching a psychical machine. If you're assumption about tasksel is right, though, it might be less ambiguous if this was indicated in future versions i. Especially since the default smb. I'll see next week. Tags for this Thread error messages , samba , server , trusty.

Bookmarks Bookmarks Digg del. The time now is User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4. For details and our forum data attribution, retention and privacy policy, see here.