[Bug 584428] Re: For Lucid server with Samba, console login times out
I have finally physically got to where the machine is and rebooted it after making the changes to /etc/pam.d/common-auth. This has solved the issues I originally posted here. It has not solved the portmap issues I mentioned above which indeed seems to be a completely separate issue. Daniel thanks for the help. -- For Lucid server with Samba, console login times out https://bugs.launchpad.net/bugs/584428 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 573919] Re: autofs doesn't work with lucid
If you look in /etc/init/portmap.conf you will see that its prerequisite for starting is statd which is done in /etc/init/portmap.conf. However, there are numerous errors in my /var/log/boot.log file. I upgraded two machines and both have the same issue as mentioned above. A new install I did does not have this issue, so it obviously is some config issues that is going badly when upgrading. I was originally fixing this issue by stopping then starting portmap again. (A restart didn't work.) I have found this in my /var/log/boot.log file: init: statd main process (730) terminated with status 1 init: statd main process ended, respawning init: statd main process (736) terminated with status 1 init: statd main process ended, respawning init: statd main process (747) terminated with status 1 init: statd main process ended, respawning init: statd main process (754) terminated with status 1 init: statd main process ended, respawning init: rpc_pipefs pre-start process (703) terminated with status 32 init: statd main process (764) terminated with status 1 init: statd main process ended, respawning init: statd main process (770) terminated with status 1 init: statd main process ended, respawning init: statd main process (776) terminated with status 1 init: statd main process ended, respawning init: statd main process (782) terminated with status 1 init: statd main process ended, respawning init: statd main process (788) terminated with status 1 init: statd main process ended, respawning init: statd main process (794) terminated with status 1 init: statd main process ended, respawning init: statd main process (800) terminated with status 1 init: statd respawning too fast, stopped -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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 573919] Re: autofs doesn't work with lucid
This is the same bug as 590570, but this one has been around longer. I think the real issue underlying this bug is in bug 525154 which relates to a race condition while starting portmap which in turn starts statd. This only seems to be an issue if you have /var as a separate mount point where /var is not mounted when statd is started. Post 13 on bug 525154 seems to solve this issue, but it is only a workaround, it does not solve the race condition if my understanding is correct. -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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 573919] Re: autofs doesn't work with lucid
Post 13 in bug 525154 above has solved the issue with statd, but now autofs is failing to start. I tried to something similar with /etc/init/autofs.conf but to no avail. Still no joy here. k3nt-1 are you seeing the error messages in your /var/logs/boot.log file that I posted above? -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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 623520] [NEW] dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
Public bug reported: If dovecot -n is executed it will show the wrong settings. In other words it seems to be ignoring what is in the /etc/dovecot/dovecot.conf completely. For example I only have pop3s set in protocols but it is permitting everything. Also the wrong certs are being used not the ones in my config. This happens whether or not I start dovecot on the command line using my config file or with sudo service dovecot start. dovecot is also trying to write to my /root dir even though I have /etc/aliases pointing to my user account. ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: dovecot ssl -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
Yes the dovecot-postfix package is installed. I'm am using 10.04 Lucid. I updated the file in /etc/dovecot/conf.d to what I want, now dovecot -n gives me the right info, but I still get this: $ openssl s_client -connect localhost:995 connect: Connection refused connect:errno=111 This also happens on the domain name coming from the outside. -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
Yes port 110 only, but no matter what I do it will not listen to port 995. -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
Sorry for putting this directly into the post, but I was not on site when I ran the command and it was a lot easier to just grab the screen output an past it in. These are the certs and keys on my box. $ ll /etc/ssl/certs/ssl-mail.pem lrwxrwxrwx 1 root root 36 2010-07-28 22:19 /etc/ssl/certs/ssl-mail.pem -> /etc/ssl/certs/ssl-cert-snakeoil.pem $ sudo ls -l /etc/ssl/private/ssl-mail.key lrwxrwxrwx 1 root root 38 2010-07-28 22:19 /etc/ssl/private/ssl-mail.key -> /etc/ssl/private/ssl-cert-snakeoil.key I also cannot get dovecot to stop looking in the /root dir, so my log is full of error messages about permissions being denied. $ sudo dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-generic-pae i686 Ubuntu 10.04.1 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s ssl_listen: 995 ssl_cert_file: /etc/ssl/certs/ssl-mail.pem ssl_key_file: /etc/ssl/private/ssl-mail.key ssl_cipher_list: ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster mail_plugins: sieve quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
I know I'm not the only person getting this issue. It was said the issue is that the /etc/aliases file needs to point to a valid user on the system other that root. This I fix, but dovecot doesn't seem to listen to this even after bouncing both postfix and dovecot. The error below will show up in the log erratically over the day sometime 20 time in just a few minutes then not again for almost a day. I assume there is an algorithm that determines when to check. Aug 25 12:19:34 foundation dovecot: deliver(root): chdir(/root) failed: Permission denied Aug 25 12:19:34 foundation dovecot: deliver(root): sieve: stat(/root/.dovecot.sieve) failed: Permission denied (using global script path in stead) Aug 25 12:19:34 foundation dovecot: deliver(root): stat(/root/Maildir) failed: Permission denied Aug 25 12:19:34 foundation dovecot: deliver(root): stat(/root/Maildir/tmp) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root) -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
OK, I waited a day to see how the changes I made to the /etc/aliases file went and that seemed to solve the issue with dovecot trying to do things in the /root/ dir. There is still the issue where dovecot will NOT listen to port 995 either locally or externally. $ openssl s_client -connect localhost:995 connect: Connection refused connect:errno=111 The above is still an issue. -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
$ ls -dl /etc/ssl/certs/ssl-cert-snakeoil.pem -rw-r--r-- 1 root root 660 2010-01-27 22:39 /etc/ssl/certs/ssl-cert-snakeoil.pem $ sudo ls -dl /etc/ssl/private/ssl-cert-snakeoil.key -rw-r- 1 root ssl-cert 891 2010-01-27 22:39 /etc/ssl/private/ssl-cert-snakeoil.key OK, it seems removing both of the Lines you mentioned solved the problem, but all the docs I have read said to set ssl_listen: 995, verbose_ssl: yes I set on to try and debug the issue. So is this a bug in covecot or a bug in the tutorials I have been reading? -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
I suppose that ssl_listen = *:995 would have worked. So I have dovecot working now I cannot access postfix through smpts port 465. Almost the same problem I had with dovecot. -- dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases https://bugs.launchpad.net/bugs/623520 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
