Bug#484503: re tightvncserver startup failure
Hello, It worked for me after installing the xfonts-base package. There should probably be a dependency? Erno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#461420: apache vs native.log permission problem
On Fri, Jan 18, 2008 at 09:44:30AM -0800, Russ Allbery wrote: Erno Kuusela [EMAIL PROTECTED] writes: There seems to be a permission problem in the default configuration: strace -f apache2 -X - ... 8986 open(/var/log/apache2/native.log, O_WRONLY|O_APPEND|O_CREAT, 0644) = -1 EACCES (Permission denied) ... Hm, it looks like we could change native.logger to log to syslog instead. Do you think that would be better? I'm betting the answer is going to be that log4cpp can't log to the Apache log and the Shibboleth folks are hell-bent on using log4cpp even though it doesn't make a lot of sense inside an Apache module Yes, syslog would be better. In fact... Would it be possible to make the other bits of shibboleth also log there? That way the events related to various moving parts would be easier to follow (shibd did this, then mod_shib did that, etc). Thank you for trying to sort this out, Erno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461420: apache vs native.log permission problem
Package: libapache2-mod-shib Version: 1.3f.dfsg1-2 Hello! There seems to be a permission problem in the default configuration: strace -f apache2 -X - ... 8986 open(/var/log/apache2/native.log, O_WRONLY|O_APPEND|O_CREAT, 0644) = -1 EACCES (Permission denied) ... I think it's with all the default permissions but can't be 100% certain. This was a bit annoying for me because it took me on a longish wild goose chase (eventually involving C++ and looking silly on shibboleth-users). A permission problem was silently preventing apache from reading some of the shibboleth config files, while shibd was reading them and happily logging its success in all the config files I could find... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448967: closed by Fabio Tranchitella [EMAIL PROTECTED] (Closing etch-only bug reports)
On Sun, Nov 25, 2007 at 08:26:54AM +0100, Fabio Tranchitella wrote: Hello, * 2007-11-24 18:06, erno wrote: I got around to trying the dovecot from backports (Version: 1:1.0.0-1~bpo.1), and same thing happened first time I connected. Second attempt worked correctly. Log: Does second attempt worked mean that now everything is working? Did the problem disappear or you are still experiencing it? Thanks for your follow-up. I started composing a reply saying it hasn't happened again, but stopped to try a few different IMAP operations with mutt to experiment, and managed to make it crash again when I hit 'R' to recall this message from the postponed folder! Retrying, as before, worked. I then tried postpone/recall a few times, and no more crashes... mysterious. It was intermittent with the etch version too, and fact seemed to stop happening altoghether perhaps due to usage patterns (which is why I only now got around to install the backports version). -- erno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448967: dovecot assertion failure
Package: dovecot-imapd
Version: 1.0.rc15-2etch1
I turned on indexes in my dovecot installation and now i sometimes
get hiccups wherein my imap connection dies, when opening a folder.
i'm running debian in a chroot under openwrt on mips (asus wl-500gp):
Linux haggis 2.4.30 #1 Sat Feb 3 13:16:08 CET 2007 mips GNU/Linux
here's a log:
haggis:/tmp# cat dovecot.log
dovecot: 2007-11-01 23:47:21 Info: Dovecot v1.0.rc15 starting up
dovecot: 2007-11-01 23:47:35 Info: imap-login: Login: user=erno,
method=PLAIN, rip=85.23.170.252, lip=80.75.107.196, TLS
dovecot: 2007-11-01 23:47:35 Info: IMAP(erno): Effective uid=1001, gid=1001
dovecot: 2007-11-01 23:47:35 Info: IMAP(erno): mbox:
data=/home/erno/Mail:INBOX=/var/mail/erno:INDEX=~
dovecot: 2007-11-01 23:47:35 Info: IMAP(erno): mbox: root=/home/erno/Mail,
index=~, inbox=/var/mail/erno
dovecot: 2007-11-01 23:50:58 Error: IMAP(erno): file mail-cache-transaction.c:
line 707 (mail_cache_add): assertion failed: (file_field != (uint32_t)-1)
dovecot: 2007-11-01 23:50:58 Error: child 16625 (imap) killed with signal 6
dovecot: 2007-11-02 00:01:03 Info: imap-login: Login: user=erno,
method=PLAIN, rip=85.23.170.252, lip=80.75.107.196, TLS
dovecot: 2007-11-02 00:01:03 Info: IMAP(erno): Effective uid=1001, gid=1001
dovecot: 2007-11-02 00:01:03 Info: IMAP(erno): mbox:
data=/home/erno/Mail:INBOX=/var/mail/erno:INDEX=~
dovecot: 2007-11-02 00:01:03 Info: IMAP(erno): mbox: root=/home/erno/Mail,
index=~, inbox=/var/mail/erno
here's the config with comments empty lines removed
protocols = imaps
disable_plaintext_auth = yes
shutdown_clients = yes
log_path = /tmp/dovecot.log
log_timestamp = %Y-%m-%d %H:%M:%S
login_process_size = 8
login_process_per_connection = yes
login_processes_count = 1
login_max_processes_count = 4
mail_location = mbox:~/Mail:INBOX=/var/mail/%u:INDEX=~
mail_extra_groups = mail
mail_debug = yes
mbox_min_index_size = 0
protocol imap {
login_executable = /usr/lib/dovecot/imap-login
mail_executable = /usr/lib/dovecot/imap
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
auth_debug = no
auth default {
mechanisms = plain
passdb pam {
}
userdb passwd {
}
user = root
}
dict {
}
plugin {
}
# end config
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242472: chroot for Debian package
hello, On Fri, 11 Feb 2005, Andreas Rottmann wrote: | | severity 242472 wishlist | retitle 242472 Please chroot radvd | tags 242472 + wontfix | thanks | | I just wanted to note that Debian packages do not set up chroots in | general, as also noted in the Securing Debian Manual[0]: | | , | | The daemons that you install with your Debian distribution will not | | come, however, chrooted [31] per default. | ` | | [0] http://www.debian.org/doc/manuals/securing-debian-howto/ch-sec-services.en.html#s-chroot | | There are tools in Debian however, that make it easier to set up | chroots, such as jailer or jailtool. you have to separate between packages setting up chroot environments for eg bind or apache, and on the other hand privsep-like things where daemons just chroot to empty or near-empty directory with no additional administrative hassle. the latter is infact done by eg postfix and sshd in debian... and radvd would, i think, be in the latter category as well. bear in mind that the howto referenced above is not any sort of normative policy spec :) -- erno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
