Bug 540002
| Summary: | address already used | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sergei LITVINENKO <sergei.litvinenko> |
| Component: | samba | Assignee: | Simo Sorce <ssorce> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 12 | CC: | bob, gdeschner, madko, ssorce |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-08 14:30:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sergei LITVINENKO
2009-11-21 22:14:01 UTC
Seems something break the configuration, I try to change the passdb backend to smbpasswd (passdb backend = smbpasswd in /etc/samba/smb.conf), then service smbd restart, and recreate my users and now it seems to work. This still occurs on 3.4.7 [2010/05/26 20:11:06, 0] smbd/server.c:1065(main) smbd version 3.4.7-58.fc12 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2010/05/26 20:11:06, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2010/05/26 20:11:06, 0] printing/print_cups.c:103(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2010/05/26 20:11:06, 0] smbd/server.c:457(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Address already in use [2010/05/26 20:11:06, 0] smbd/server.c:457(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Address already in use I have tried with smbpasswd and tdbsam but no success. My problem is fixed it works fine with tdbsam. I just needed the appropriate entries in the firewall. My lack of attention to detail. However I find the log messages very misleading when starting the service. |