[Bug 580700] [NEW] Package is actually called sasl2-bin
Public bug reported: Why is this package listed under cyrus-sasl2 on launchpad when the actual package name is sasl2-bin? This makes it hard to accurately report bugs. Please stick to the convention package_name = package_name_in_launchpad. Thanks. ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New -- Package is actually called sasl2-bin https://bugs.launchpad.net/bugs/580700 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 580700] Re: Package is actually called sasl2-bin
I should have also pointed out that using the URL http://bugs.launchpad.net/ubuntu/+source/sasl2-bin/+filebug?no-redirect produces a page not found sort of thing. -- Package is actually called sasl2-bin https://bugs.launchpad.net/bugs/580700 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 580708] [NEW] Can't run multiple saslauthd daemons as per the documentation
Public bug reported: I am trying to use postfix with cyrus. Since the debian postfix runs chrooted by default and since the version of cyrus shipping with Lucid has the location of the saslauthd socket hard-coded, it seems like the best idea is to run separate saslauthd daemons for these processes. (Making a symlink to the socket from the chroot jail to /var/run seems like a kludge to me, particularly since /var/run is cleared out on every reboot.) According to the document: /usr/share/doc/sasl2-bin/README.Debian.gz it should be possible to run multiple saslauthd daemons, but when I follow these instructions *precisely*, I get the error message: saslauthd[4747] :detach_tty : Cannot start saslauthd saslauthd[4747] :detach_tty : Another instance of saslauthd is currently running Let me preclude the question did I remember to set up a different socket for each instance of saslauthd(\w*) in /etc/default: yes, I did set up different sockets (/var/run/postfix/var/run/saslauthd and /var/run/saslauthd) and tried this several times. Is the included documentation incorrect or is this a bug in the currently shipping saslauthd? ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New -- Can't run multiple saslauthd daemons as per the documentation https://bugs.launchpad.net/bugs/580708 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 580708] Re: Can't run multiple saslauthd daemons as per the documentation
Please cancel this bug report -- I'm retarded. In the process of testing all this stuff I created a /var/run/saslauthd symlink which I had forgotten about. This is what was causing the second saslauthd instance to fail. ** Changed in: cyrus-sasl2 (Ubuntu) Status: New = Invalid -- Can't run multiple saslauthd daemons as per the documentation https://bugs.launchpad.net/bugs/580708 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 532286] Re: Samba: remote Win XP and Mac OS X machines can no longer mount shares
could you place a Linux system in that 192.168.1.0/24 network and reproduce the trace? Good call, Thierry! I was certain that the linux machine would be able to connect from 192.168.1.0/24, but was shocked to discover that it doesn't. A trace of the packets shows the same lack of response from the SMB server. This lead to a few more tests indicating that the problem must be that the ISP is blocking incoming port 445 traffic. Normally I would have suspected this, but in this case I have Windows XP users on another subnet for which this was working right up until the day of the system upgrade, and didn't work subsequently. Since (presumably) nothing changed on their end during this 3-day period; i.e. no new ISP, no new firewall, same Windows XP machines, I assumed the problem must be with the server. Since I've subsequently been able to mount shares from a Windows XP machine on a different subnet, this can't be the problem. I still don't have an explanation for why the TCP SMB connection was working for the actual Win XP users prior to the upgrade from Debian to Lucid, but not after. Please mark this bug as Invalid with my humble apologies!! I plan not to be fooled by this trick again. -- Samba: remote Win XP and Mac OS X machines can no longer mount shares https://bugs.launchpad.net/bugs/532286 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 532286] Re: Samba: remote Win XP and Mac OS X machines can no longer mount shares
Thierry, as usual, thanks for your rapid response/attention to these issues. Good suggestion; I will try using a linux machine to connect from 192.168.1.x, which is my home network. First, let me point out that Win XP and Mac OS X machines on various networks have been unable to connect to the Samba server -- I only tested linux from one location, but will try your suggestion this weekend. 128.83.133.100 is routable from 216.110.51.120, but 192.168.1.64 is not, as this is a private network using NAT. The external address for 192.168.1.64 is 99.91.6.24, and this is routable from 216.110.51.120. Using an ssh proxy on the firewall for the Samba server (i.e. using iptables to route port on the firewall to port 22 on the samba server), I can ssh from the Win XP machine directly to the Samba server, and using a windows SSH FS tool called ExpanDrive, can map and use drives over ssh; i.e. other TCP/IP protocols do work from the (firewalled) 192.168.1.64 Windows desktop to the (firewalled) Samba server. Re: server logs: The only thing in the server logs regarding 99.91.6.24 are the ssh connections: r...@data:/var/log# rgrep '99.91.6.24' * auth.log:Mar 3 21:07:10 data sshd[26848]: Accepted password for pgoetz from 99.91.6.24 port 1085 ssh2 auth.log:Mar 3 21:21:51 data sshd[26920]: Accepted password for pgoetz from 99.91.6.24 port 1118 ssh2 (etc. -- several ssh connections listed) Note that the new Samba server keeps track of all connection attempts (mostly unfriendly probes) and creates individual log files for them: log.___82.64.100.254(attempted hack) log.ea103 (legitimate internal desktop) log.lizard (linux desktop used for testing) (etc.) Log files exist even for failed connection attempts, but none exists for 99.91.6.24. -- Samba: remote Win XP and Mac OS X machines can no longer mount shares https://bugs.launchpad.net/bugs/532286 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 532286] [NEW] Samba: remote Win XP and Mac OS X machines can no longer mount shares
Public bug reported: Binary package hint: samba Distro: Ubuntu Lucid Alpha 3 Package: samba 2:3.4.5~dfsg-2ubuntu3 I've been holding off on reporting this as a bug for several days, but simply am not able to make any more progress. Previously we were running Samba 3.0.2 on a Debian machine behind a firewall which redirects Port 445 traffic to the samba (PDC) server. Authenticated Win XP, Mac OS X, and linux users outside the firewall were all able to mount CIFS shares from the samba server. Recently I upgraded to Lucid/Samba 3.4.5. Nothing else was changed, and the smb.conf is roughly the same as before. (Let me note that I went through the package maintainer's smb.conf file with a fine-toothed comb, read the smb.conf man page completely twice, and ran testparm to make sure everything in the smb.conf file was OK.) Everything inside the firewall works as before. From outside, Win XP and Mac OS X users are no longer able to mount shares; *however* linux hosts have no problems. Using Wireshark, I did a packet trace of an unsuccessful mount attempt from a Win XP machine outside the firewall to and from the Samba server and a successful mount on a linux machine outside the firewall. The .pcap files are attached. As far as I can tell, the Samba server is simply not responding to the Win XP TCP SYN request, but is responding to the linux machines TCP SYN request. The Wireshark packet summary differences are listed below. The server IP address is 216.110.51.120: From Windows XP: 192.168.1.64216.110.51.120 TCP 4617 microsoft-ds [SYN] Seq=0 Win=65535 Len=0 MSS=1360 (server never responds to this) From linux: 128.83.133.100 216.110.51.120 TCP 42098 microsoft-ds [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=347894238 TSER=0 WS=7 (server immediately responds to this) Let me note again that we never had any problems with Samba 3.0.2, same Win XP/Mac OS X clients. I'm not including the smb.conf file, because I assume this information is irrelevant: everything works on the local network and for linux hosts being redirected through the firewall. Unfortunately, all the actual users have Win XP and/or Mac OS X machines, hence: problem. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- Samba: remote Win XP and Mac OS X machines can no longer mount shares https://bugs.launchpad.net/bugs/532286 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 532286] Re: Samba: remote Win XP and Mac OS X machines can no longer mount shares
** Attachment added: windowsXP_connect_attempt.pcap http://launchpadlibrarian.net/40208367/windowsXP_connect_attempt.pcap -- Samba: remote Win XP and Mac OS X machines can no longer mount shares https://bugs.launchpad.net/bugs/532286 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 532286] Re: Samba: remote Win XP and Mac OS X machines can no longer mount shares
** Attachment added: linux_connect_negotiation.pcap http://launchpadlibrarian.net/40208374/linux_connect_negotiation.pcap -- Samba: remote Win XP and Mac OS X machines can no longer mount shares https://bugs.launchpad.net/bugs/532286 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
I don't know if it's worth backporting 3.4.5 to Karmic. In researching this problem and talking to a number of windows sys admins it seems that most samba server users have just given up on roaming profiles because they can't get them to work. It doesn't help that the XP Group Policy settings (managed using gpedit.msc) don't seem to work as advertised, at least not by my testing. Add to that the agony of ironing out a problem when local profile caching is turned on (i.e. the 3-reboot minimum). Unfortunately, in an office with XP clients where people move around there's not much alternative. Well, save for re-installing all the desktops with linux and running Windows apps using Virtualbox. :) -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
OK, Samba 3.4.5, as shipped with Lucid (2:3.4.5~dfsg-2ubuntu1) solves the roaming profile problem, more or less. Windows is very picky about the precise permissions of the profile folder. The permissions on the profile folders were drwx-wx---. This worked fine for fully patched Windows XP SP3 clients and Samba 3.0.2, but no longer works with Samba 3.4.x and the same clients, giving the windows can't load roaming profile error messages described previously. Changing the permissions on the profile folder to drwx-- solves the problem. Note that this is NOT the same problem encountered with Samba 3.4.0. For this version, the on shipping with Karmic AMD64 Server, one can create a new profile from scratch and it will give the window's can't load roaming profile error message the next time the user tries to log in. I've attached the latest smb.conf file, which is not much different from the original (also attached). -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
** Attachment added: smb.conf http://launchpadlibrarian.net/39499358/smb.conf -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
Were you able to confirm that 3.4.5 is working correctly ? Not yet; I will try and re-install with Lucid tomorrow and should have an answer by Monday. @Chuck: some indication of what additional information you want (smb.conf? log files? output from ubuntu-bug?) would be helpful. -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
I've attached the last iteration of my smb.conf file before I gave up and decided this must be a bug. ** Attachment added: smb.conf http://launchpadlibrarian.net/39275245/smb.conf -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
This is the similar current (original) smb.conf file which is still working with 3.0.2 The big difference as far as this issue is concerned is this change in the [profile] section: force create mode = 0777 force directory mode = 0777 --- create mode = 0600 directory mode = 0700 ** Attachment added: smb.conf.orig http://launchpadlibrarian.net/39275324/smb.conf.orig -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
Also attached output from ubuntu-bug. ** Attachment added: apport.samba.6Og_Ad.apport http://launchpadlibrarian.net/39275483/apport.samba.6Og_Ad.apport -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
Hmm, I see that you created and someone tested a modified 3.3.2 PPA version, followed by the comment Marking this fixed in development release (as 3.4.x contains the fix), and nominating for a Jaunty SRU. but didn't see any actual evidence that the patch made it into 3.4.x. My assumption was that it's fixed in 3.4.x where x = 1. In any case, I'm still having the problem, as described above, and couldn't find any mod to either the profile folders or smb.conf which worked. -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients
Let me know if I need to provide more information in order to confirm this bug. Since I'm trying to upgrade production servers and am already behind schedule, my plan was to go ahead and upgrade to Lucid (which has samba 3.4.5) in order to solve the problem. People stuck running Karmic who need roaming profiles for XP clients will be left sad little campers. -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 521085] [NEW] Samba 3.4.0 denies access to Roaming Profiles for XP Clients
Public bug reported: Binary package hint: samba Source Package: samba_2:3.4.0-3ubuntu5.4 Ubuntu Release: 9.10 (Karmic 64-bit AMD Server) This is basically the same problem as reported in Bug #397699; however the problem persists in Karmic (9.10) and has not been fixed, as far as I can tell. Using an smb.conf file which worked perfectly for (Debian) samba_3.0.2-2, one gets something similar to the following error message when trying to login using a roaming profile on a Windows XP machine: Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Windows did not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrator's group must be the owner of the folder. Contact your network administrator. Deleting the profile and starting with a clean slate allows the user to login and logout again, however the message above is repeated upon a subsequent attempt to login. I tried every suggestion I could find to fix this, including such ill- advised steps as chmod'ing the permissions on the profile to 1777. My original profile share configuration in smb.conf looked like this: [profile] create mode = 0600 directory mode = 0700 path = /home/%U/profile read only = no profile acls = yes browseable = yes One suggestion involved changing the create and directory mode masks as follows: [profile] force create mode = 0777 force directory mode = 0777 path = /home/%U/profile read only = no profile acls = yes browseable = yes This did not solve the problem. As far as I can tell, the bug reported for Jaunty samba 3.3.2 has not been fixed for Karmic samba 3.4.0. Given the importance of Samba in many linux server environments, the fact that this was not tested more thoroughly before Karmic was released is frankly shocking and disappointing. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- Samba 3.4.0 denies access to Roaming Profiles for XP Clients https://bugs.launchpad.net/bugs/521085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 434986] [NEW] postfix ignores the rsyslog configuration directives
Public bug reported:
Binary package hint: dovecot-postfix
I've been working with the dovecot-postfix package in karmic koala a5.
postfix seems not to be working properly with rsyslog; e.g. doesn't seem to be
aware of /etc/rsyslog.conf. All SMTP activity is logged to /var/log/syslog even
though the default /etc/rsyslog.d/50-default.conf is configured to send this
stuff to the usual /var/log/mail{.err, .warn,.log}. Furthermore, when I tried
to move IMAP logging to a separate log file by setting
log_path = /var/log/dovecot
in /etc/dovecot/dovecot-postfix, my system stopped accepting SMTP mail
deliveries with the following error message in /var/log/syslog:
Sep 15 06:22:20 ibis postfix/local[25505]: D554941122:
to=pgo...@internetbs.com, relay=local, delay=28665,
delays=28665/0.01/0/0.14, dsn=4.3.0, status=deferred (temporary failure.
Command output: Can't open log file /var/log/dovecot: Permission denied
)
I want to be able to keep IMAP stuff and SMTP stuff in separate log
files for easy analysis, and it seems pretty obvious that almost no one
would want SMTP traffic logged to /var/log/syslog.
Source package and release info:
r...@ibis:/etc/rsyslog.d# cd ..
r...@ibis:/etc# cat lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION=Ubuntu karmic (development branch)
r...@ibis:/etc# uname -a
Linux ibis 2.6.31-10-generic-pae #32-Ubuntu SMP Fri Sep 11 00:30:46 UTC 2009
i686 GNU/Linux
r...@ibis:/etc# dpkg -l | grep dovecot
ii dovecot-common1:1.1.11-0ubuntu8 secure
mail server that supports mbox and ma
ii dovecot-imapd 1:1.1.11-0ubuntu8 secure
IMAP server that supports mbox and ma
ii dovecot-pop3d 1:1.1.11-0ubuntu8 secure
POP3 server that supports mbox and ma
ii dovecot-postfix 1:1.1.11-0ubuntu8 full
mail server stack provided by Ubuntu se
r...@ibis:/etc# dpkg -l | grep postfix
ii dovecot-postfix 1:1.1.11-0ubuntu8 full
mail server stack provided by Ubuntu se
ii postfix 2.6.5-1ubuntu1
High-performance mail transport agent
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
--
postfix ignores the rsyslog configuration directives
https://bugs.launchpad.net/bugs/434986
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 398272] Re: New upstream version
Correction: dovecot 1.2.5 has just been released. This release includes some critical performance fixes for large installations. Surely it should be possible to upgrade this in Karmic before release? -- New upstream version https://bugs.launchpad.net/bugs/398272 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
