[Bug 1503611] Re: systemd: spamassassin not starting after upgrading to 15.04
After 14.10 to 15.04 upgrade, with amavis so spamassassin is installed, but spamd shouldn't be running IIRC, root is receiving /etc/cron.daily output. /etc/cron.daily/spamassassin: Job for spamassassin.service invalid. invoke-rc.d: initscript spamassassin, action "reload" failed. Here, I've $ grep '^[^#]' /etc/default/spamassassin ENABLED=0 OPTIONS="--create-prefs --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 $ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774380 looks related. ** Changed in: spamassassin (Ubuntu) Status: New => Confirmed ** Bug watch added: Debian Bug tracker #774380 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774380 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1503611 Title: systemd: spamassassin not starting after upgrading to 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503611/+subscriptions -- 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 729288] Re: squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2
cache.log, attached, shows nothing odd AFAICS, normal shutdown. dist- upgrade failed, Preparing to replace squid 2.7.STABLE9-2ubuntu5.1 (using .../squid_2.7.STABLE9-2ubuntu5.2_amd64.deb) ... Unpacking replacement squid ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for ufw ... Processing triggers for man-db ... Setting up squid-common (2.7.STABLE9-2ubuntu5.2) ... Setting up squid (2.7.STABLE9-2ubuntu5.2) ... restart: Job failed to restart dpkg: error processing squid (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: squid E: Sub-process /usr/bin/dpkg returned an error code (1) $ After finding this bug report I tried $ sudo status squid squid stop/waiting $ sudo start squid squid start/running, process 11334 $ sudo status squid squid start/running, process 11334 which is 12:43:30 in the log file. It appears to be working fine now. ** Attachment added: "/var/log/squid/cache.log" https://bugs.launchpad.net/ubuntu/+source/squid/+bug/729288/+attachment/2582857/+files/cache.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/729288 Title: squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/729288/+subscriptions -- 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 416264] Re: ssh client pauses during GSS negotiation due to delay on reverse lookup in avahi
Just experienced this with a 8.04 ssh client talking to a CentOS ssh server. Turning off GSSAPIAuthentication avoids the delay. -- ssh client pauses during GSS negotiation due to delay on reverse lookup in avahi https://bugs.launchpad.net/bugs/416264 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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
Re: [Bug 24741] Re: Installing samba gives spurious "account_policy_get failed" messages
> > The fix is in the development release (Lucid), not backported to > > Karmic. > > Making it useless to the majority of Ubuntu users, who are not all on > Lucid and many of whom will not be upgrading to Lucid for some time... > (need to wait for bugfxes to be released, wontfixes to be worked > aroud, and spuriously removed hardware support to be added back > in...etc) You could apply your argument to the fix of every bug, not just this one. It's not practical in terms of manpower to fix a bug for all the versions. The tone of your comment suggests you know this. -- Installing samba gives spurious "account_policy_get failed" messages https://bugs.launchpad.net/bugs/24741 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 561779] Re: squid is not started on runlevel transition 1 -> 2
It isn't a matter of being able to work around the problem; an experienced user can do that, I agree. As I pointed out, it's that squid not running on moving to run level 2 isn't obvious to the admin that's just made the change. It has to affect users before the admin gets to know about the problem and investigate. A bug which affects the users of the system before the admin notices, and the admin will then have to spend time investigating *why* squid isn't running, doesn't seem low priority. Working around the bug is trivial, it's the upset and work it causes before the workaround stage is reached that's the problem. -- squid is not started on runlevel transition 1 -> 2 https://bugs.launchpad.net/bugs/561779 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid 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 561779] Re: squid is not started on runlevel transition 1 -> 2
Is it low importance? It's easily worked around if I know it occurs, but if I don't know this bug exists then I'm left with a server at runlevel 2 without squid, and it may cause users all kinds of problems before they get back to me and I work out what's wrong. -- squid is not started on runlevel transition 1 -> 2 https://bugs.launchpad.net/bugs/561779 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid 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 24741] Re: Installing samba gives spurious "account_policy_get failed" messages
** Summary changed: - Spurious "account_policy_get failed" messages on install + Installing samba gives spurious "account_policy_get failed" messages -- Installing samba gives spurious "account_policy_get failed" messages https://bugs.launchpad.net/bugs/24741 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 24741] Re: samba account_policy_get fails on install
Just an update; installing package samba on 8.04 still gives Setting up samba (3.0.28a-1ubuntu4.4) ... Generating /etc/default/samba... tdbsam_open: Converting version 0 database to version 3. account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0 Importing account for nobody...ok Importing account for peter...ok Importing account for ralph...ok Adding group `sambashare' (GID 126) ... Done. Adding user `peter' to group `sambashare' ... Adding user peter to group sambashare Done. Adding user `ralph' to group `sambashare' ... Adding user ralph to group sambashare Done. * Starting Samba daemons[ OK ] It would be nice to tidy this up a bit since anyone who sees the messages, harmless though they may be, has to then investigate (and hopefully end up here). -- samba account_policy_get fails on install https://bugs.launchpad.net/bugs/24741 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- 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 39249] Re: (Dapper) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied
Hi Martin, I saw this on a fresh 8.04 install and try to give some detail, see https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/39249/comments/24 above. -- (Dapper) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied https://bugs.launchpad.net/bugs/39249 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 242666] Re: gnome-keyring asks for passphrase for plain `ssh-add -l'
Given it's /usr/lib/gnome-keyring/gnome-keyring-ask displaying the dialogue box I'm guessing gnome-keyring is the right package. ** Changed in: gnome-keyring (Ubuntu) Sourcepackagename: openssh => gnome-keyring -- gnome-keyring asks for passphrase for plain `ssh-add -l' https://bugs.launchpad.net/bugs/242666 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 242666] Re: seahorse asks for passphrase for plain `ssh-add -l'
/usr/lib/gnome-keyring/gnome-keyring-ask is the program prompting with the dialogue box, from package gnome-keyring 2.22.2-0ubuntu1. ** Summary changed: - seahorse asks for passphrase for plain `ssh-add -l' + gnome-keyring asks for passphrase for plain `ssh-add -l' -- gnome-keyring asks for passphrase for plain `ssh-add -l' https://bugs.launchpad.net/bugs/242666 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 242666] Re: seahorse asks for passphrase for plain `ssh-add -l'
The above was originally https://answers.launchpad.net/ubuntu/+source/openssh/+question/36438 rather than a bug. However, on thinking about it, prompting for the passphrase for `ssh-add -l' seems broken compared to the old behaviour. -- seahorse asks for passphrase for plain `ssh-add -l' https://bugs.launchpad.net/bugs/242666 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 39249] Re: (Dapper) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied
Seeing this on a new 8.04 Server install. Given Martin said it needs info so long ago I'm changing it back to confirmed in the hope there's since been enough info. Here's mine; it's just got eth0 and lo interfaces. $ cd /var/lib/dhcp3 $ ls -la total 8 k drwxr-xr-x 2 root root 4096 2008-04-30 23:30 . drwxr-xr-x 24 root root 4096 2008-05-27 16:40 .. -rw-r--r-- 1 root root0 2008-04-30 23:30 dhclient.leases $ $ p=`pidof dhclient3` $ ps lww $p F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 1 101 4014 1 18 -2 2340 820 - S Confirmed -- (Dapper) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied https://bugs.launchpad.net/bugs/39249 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 239302] [NEW] Setting squid's udp_incoming_address address to 127.0.0.1 stop its DNS requests working
Public bug reported:
Binary package hint: squid
Ubuntu 8.04, squid 2.6.18-1ubuntu3.
By default, squid was listening for TCP connections and UDP packets on
all interfaces. This can be checked with
sudo netstat -tulep | grep -i squid
I wanted to make listen only on localhost for incoming HTTP connections
on port 3128, the default port, and also only send and receive on
localhost for inter-squid ICP packets since I've no other squids to talk
to.
Editing /etc/squid/squid.conf to set `http_port localhost:3128' worked
for the TCP port.
Setting `udp_incoming_address 127.0.0.1' did cause the UDP listening
socket(s) to be only on that interface, but also caused squid to stop
proxying. /var/log/squid/cache.log has pairs of lines, several for each
incoming request.
2008/06/11 21:45:00| comm_udp_sendto: FD 6, 212.159.6.10, port 53: (22)
Invalid argument
2008/06/11 21:45:00| idnsSendQuery: FD 6: sendto: (22) Invalid argument
strace(8) confirmed that squid was attempting DNS lookups on the
request's host but sendto(2) was returning EINVAL. lsof(8) can be used
to confirm that the DNS request is trying to be sent to my ISPs DNS
server through a UDP socket bound to the loopback interface. The socket
used by idnsSendQuery() for DNS requests is initialised in
src/dns_internal.c's idnsInit().
if (DnsSocket < 0) {
int port;
struct in_addr addr;
if (Config.Addrs.udp_outgoing.s_addr != no_addr.s_addr)
addr = Config.Addrs.udp_outgoing;
else
addr = Config.Addrs.udp_incoming;
DnsSocket = comm_open(SOCK_DGRAM,
IPPROTO_UDP,
addr,
0,
COMM_NONBLOCKING,
"DNS Socket");
By default, Config.Addrs.udp_outgoing is 255.255.255.255 (no_addr) and
Config.Addrs.udp_incoming is 0.0.0.0. This means the DNS socket is
opened on 0.0.0.0, all interfaces, so sendto() to the DNS server works
wherever it is. By setting `udp_incoming_address 127.0.0.1', I've made
squid send UDP DNS requests out of 127.0.0.1 destined for the Internet;
EINVAL.
It should be possible to specify a new `dns_outgoing_address' config
item separately and have that default to 0.0.0.0. At it stands, I have
to have squid sitting on the Internet, listening for UDP packets from
the Internet, when it doesn't need them.
Having found the problem, I find it was known about in 2003.
http://www.squid-cache.org/mail-archive/squid-users/200301/0676.html
I really think this needs addressing. It's more reassuring to have
servers listening on as few interfaces as necessary.
** Affects: squid (Ubuntu)
Importance: Undecided
Status: New
--
Setting squid's udp_incoming_address address to 127.0.0.1 stop its DNS requests
working
https://bugs.launchpad.net/bugs/239302
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid 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
