Re: [Bug 973663] Re: quota returns nothing for NFS on 12.04
Thank you! Ryan -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quota in Ubuntu. https://bugs.launchpad.net/bugs/973663 Title: quota returns nothing for NFS on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quota/+bug/973663/+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 573919] Re: autofs doesn't work with lucid
#15 worked for me as well. I also set NEED_STATD=yes in /etc/default /nfs-common. But autofs should only depend on statd if it is mounting NFS volumes. autofs can be used with other filesystems besides NFS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/573919 Title: autofs doesn't work with lucid -- 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 409958] Re: Sends false disk space alerts
According to the output above, both disk space and inode usage are being
checked. For example
/var 88850 MB (91% inode=99%)
But
# df -i /var
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sdb56483456 36212 64472441% /var
# df -h /var
FilesystemSize Used Avail Use% Mounted on
/dev/sdb5 100G 8.2G 87G 9% /var
The nagios output is displaying free space and free inodes but appears
to be sending out a warning thinking the percentages are utilized space
and utilized inodes. Given that 91% (disk free) and 99% (inode free) are
greater than 20%, a warning should not have been sent.
localhost_nagios2.cfg:
# Define a service to check the disk space of the root partition
# on the local machine. Warning if 20% free, critical if
# 10% free space on partition.
define service{
use generic-service ; Name of
service template to use
host_name localhost
service_description Disk Space
check_command check_all_disks!20%!10%
}
--
Sends false disk space alerts
https://bugs.launchpad.net/bugs/409958
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios2 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 409958] Re: Sends false disk space alerts
On Fri, Oct 16, 2009 at 02:32:56PM -, Chuck Short wrote: We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks! I'm using the default commands.cfg file; no alterations. (8.04) Ryan -- Sends false disk space alerts https://bugs.launchpad.net/bugs/409958 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios2 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 409958] [NEW] Sends false disk space alerts
Public bug reported: Binary package hint: nagios2 I received the following message from nagios2 on my server running hardy: === Notification Type: PROBLEM Service: Disk Space Host: localhost Address: 127.0.0.1 State: WARNING Date/Time: Thu Aug 6 04:03:40 PDT 2009 Additional Info: DISK WARNING - free space: / 3763 MB (83% inode=93%): /var/run 4001 MB (99% inode=99%): /var/lock 4001 MB (100% inode=99%): /dev 4001 MB (99% inode=99%): /dev/shm 4001 MB (100% inode=99%): /tmp 3512 MB (97% inode=99%): /usr 3107 MB (34% inode=53%): /var 88851 MB (91% inode=99%): /var/tmp 7545 MB (83% inode=96%): /mnt/backup 3765 === I'm using the default localhost_nagios2.cfg config file which check for 20% free (warning) and 10% free (critical), however none of my partitions exceeds 66%. I received another message later which has nearly identical values. Note that I did not truncate the text below, it actually does end with an open parenthesis: === Notification Type: RECOVERY Service: Disk Space Host: localhost Address: 127.0.0.1 State: OK Date/Time: Thu Aug 6 04:08:40 PDT 2009 Additional Info: DISK OK - free space: / 3763 MB (83% inode=93%): /var/run 4001 MB (99% inode=99%): /var/lock 4001 MB (100% inode=99%): /dev 4001 MB (99% inode=99%): /dev/shm 4001 MB (100% inode=99%): /tmp 3512 MB (97% inode=99%): /usr 3107 MB (34% inode=53%): /var 88850 MB (91% inode=99%): /var/tmp 7545 MB (83% inode=96%): /mnt/backup 3765 MB ( ** Affects: nagios2 (Ubuntu) Importance: Undecided Status: New -- Sends false disk space alerts https://bugs.launchpad.net/bugs/409958 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios2 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 315241] Re: Mangles MAC in ethers lookup
Thanks Robert. http://bugzilla.padl.com/show_bug.cgi?id=388 (launchpad wouldn't let me add this URL to the remote bug tracking list since PADL isn't listed among the distributions) -- Mangles MAC in ethers lookup https://bugs.launchpad.net/bugs/315241 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap 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 315241] [NEW] Mangles MAC in ethers lookup
Public bug reported: Binary package hint: libnss-ldap http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310563 This bug occurs on Hardy. 'getent ethers hostname' properly looks up a machine, but when the client issues 'getent ethers 00:00:00:00:00:00' the LDAP server reveals that the filter is ((objectClass=ieee802Device)(macAddress=0:0:0:0:40:54)). The bug occurs on both i386 and amd64. ** Affects: libnss-ldap (Ubuntu) Importance: Undecided Status: New ** Affects: libnss-ldap (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #310563 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310563 ** Also affects: libnss-ldap (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310563 Importance: Unknown Status: Unknown -- Mangles MAC in ethers lookup https://bugs.launchpad.net/bugs/315241 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap 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 315241] Re: Mangles MAC in ethers lookup
A manual search using ldapsearch yielded the correct results, e.g. ldapsearch ... -b cn=ethers,dc=foo (macAddress=11:22:33:44:55:66) returned the correct entry from the server. ** Description changed: Binary package hint: libnss-ldap http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310563 This bug occurs on Hardy. - 'getent ethers hostname' properly looks up a machine, but when the client issues 'getent ethers 00:00:00:00:00:00' - the LDAP server reveals that the filter is ((objectClass=ieee802Device)(macAddress=0:0:0:0:40:54)). The bug occurs on both i386 and amd64. + 'getent ethers hostname' properly looks up a machine, but when the + client issues 'getent ethers 00:00:00:00:00:00' the LDAP server reveals + that the filter is + ((objectClass=ieee802Device)(macAddress=0:0:0:0:40:54)). This occurs + for all MAC addresses so the server never matches on any getent key. The + bug occurs on both i386 and amd64. -- Mangles MAC in ethers lookup https://bugs.launchpad.net/bugs/315241 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap 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 309816] [NEW] Include logrotate configuration
Public bug reported:
The dovecot package does not include a logrotate configuration. If
dovecot is configured to log to file rather than syslog its log file
will become unmanageable. There is a recommended configuration here:
http://wiki.dovecot.org/Logging
# dovecot SIGUSR1: Re-opens the log files.
/var/log/dovecot*.log {
missingok
notifempty
delaycompress
sharedscripts
postrotate
/bin/kill -USR1 `cat /var/run/dovecot/master.pid 2/dev/null` 2 /dev/null
|| true
endscript
}
This configuration will not interfere if dovecot is configured to use
syslog.
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
--
Include logrotate configuration
https://bugs.launchpad.net/bugs/309816
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 186080] Re: misleading man page category phrase
Sorry about that. The above snippet was from the named.conf man page within the bind package rather than bind9 package. -- misleading man page category phrase https://bugs.launchpad.net/bugs/186080 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 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
