Bug#896090: AH02611: create: apr_shm_create failed (No space left on device)
Package: apache2
Version: 2.4.25-3+deb9u4
Severity: normal
Dear Maintainers,
We're running into a problem on a graceful restart in combination with a
front proxy and mod_balancer:
[Mon Apr 09 09:10:17.169139 2018] [slotmem_shm:error] [pid 9268:tid
140349331453824] (28)No space left on device: AH02611: create:
apr_shm_create(/var/run/apache2/slotmem-shm-pe0653d6a_apidocs_cluster.shm)
failed
I found the No Space error bizarre, so I have verified if there is room in the
limits:
> $ ipcs -lm
> -- Semaphore Limits
> max number of arrays = 32000
> max semaphores per array = 32000
> max semaphores system wide = 102400
> max ops per semop call = 500
> semaphore max value = 32767
The amount of semaphores in use while running is around 2118.
I can reliably reproduce it with:
- 45 vhosts that use mod_balancer, with in total 138 BalancerMembers.
- a long running connection (keep alive) over one of the configured
vhosts.
- both on jessie and stretch
I observed that:
- Disabling "a few" vhosts makes the problem go away
- Stopping the long lived connection makes the problem go away
While browsing the apache mailinglist for this error, I found a
similar bug report which was fixed in 2.4.30 [1].
[1]: https://bz.apache.org/bugzilla/show_bug.cgi?id=62044
Let me know if I provided enough details.
Kai
-- Package-specific info:
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apache2 depends on:
ii apache2-bin 2.4.25-3+deb9u4
ii apache2-data 2.4.25-3+deb9u4
ii apache2-utils2.4.25-3+deb9u4
ii dpkg 1.18.24
ii init-system-helpers 1.48
ii lsb-base 9.20161125
ii mime-support 3.60
ii perl 5.24.1-3+deb9u3
ii procps 2:3.3.12-3
Versions of packages apache2 recommends:
ii ssl-cert 1.0.39
Versions of packages apache2 suggests:
pn apache2-doc
pn apache2-suexec-pristine | apache2-suexec-custom
pn www-browser
Versions of packages apache2-bin depends on:
ii libapr1 1.5.2-5
ii libaprutil1 1.5.4-3
ii libaprutil1-dbd-sqlite3 1.5.4-3
ii libaprutil1-ldap 1.5.4-3
ii libc62.24-11+deb9u3
ii libldap-2.4-22.4.44+dfsg-5+deb9u1
ii liblua5.2-0 5.2.4-1.1+b2
ii libnghttp2-141.18.1-1
ii libpcre3 2:8.39-3
ii libssl1.0.2 1.0.2l-2+deb9u3
ii libxml2 2.9.4+dfsg1-2.2+deb9u2
ii perl 5.24.1-3+deb9u3
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages apache2-bin suggests:
pn apache2-doc
pn apache2-suexec-pristine | apache2-suexec-custom
pn www-browser
Versions of packages apache2 is related to:
ii apache2 2.4.25-3+deb9u4
ii apache2-bin 2.4.25-3+deb9u4
-- Configuration Files:
/etc/apache2/apache2.conf changed:
ServerTokens Prod
ServerSignature Off
TraceEnable On
ServerName "xswebfront7.xs4all.net"
ServerRoot "/etc/apache2"
PidFile ${APACHE_PID_FILE}
Timeout 120
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5
LimitRequestFieldSize 8190
User www-data
Group www-data
AccessFileName .htaccess
Require all denied
Options FollowSymLinks
AllowOverride None
HostnameLookups Off
ErrorLog "/var/log/apache2/error.log"
LogLevel warn
EnableSendfile On
Include "/etc/apache2/mods-enabled/*.load"
Include "/etc/apache2/mods-enabled/*.conf"
Include "/etc/apache2/ports.conf"
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %s %b \"%{Referer}i\"
\"%{User-agent}i\"" forwarded
IncludeOptional "/etc/apache2/conf.d/*.conf"
IncludeOptional "/etc/apache2/sites-enabled/*"
/etc/apache2/mods-available/access_compat.load changed:
LoadModule access_compat_module /usr/lib/apache2/modules/mod_access_compat.so
/etc/apache2/mods-available/alias.conf changed:
Alias /icons/ "/usr/share/apache2/icons/"
Options Indexes MultiViews
AllowOverride None
Require all granted
/etc/apache2/mods-available/authz_host.load changed:
LoadModule authz_host_module /usr/lib/apache2/modules/mod_authz_host.so
/etc/apache2/mods-available/deflate.conf changed:
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/x-javascript application/javascript
Bug#816780: roundup: CVE-2014-6276: information leak
On 22/03/16 21:20, Salvatore Bonaccorso wrote: > Hi Kai, > > On Sat, Mar 05, 2016 at 08:45:53AM +0100, Salvatore Bonaccorso wrote: > [...] >> >From Kai Storbeck it looks the way forward would be to have roundup >> removed for unstable and stretch. Kai can you confirm that this is >> still the plan vs. update to new upstream releases? >> >> If so can you fill afer discussion with the Python App team a removal >> request? > > Any news on this? > > Regards, > Salvatore > Hi Salvatore, I've cc'ed you in my discussion with the Python App team. Thanks for nudging me. Regards, Kai signature.asc Description: OpenPGP digital signature
Bug#753892: Regular expressions are indeed mandatory
Hello Michael, On 10/28/14, 12:00 PM, Michael Vogt wrote: On Wed, Oct 22, 2014 at 02:08:19PM +0200, Kai Storbeck wrote: Dear Maintainer, Hi Kai, thanks for your bugreport. Appreciated. Thanks for getting back to it! I tried adding this package to the package-blacklist: libstdc++6 This will fail, as it is an invalid regular expression: [..] File /usr/lib/python2.7/re.py, line 242, in _compile raise error, v # invalid expression sre_constants.error: multiple repeat (this is on wheezy) Is this intentional, or is this a bug? This is sort-of intentional but I think you raise a interessting usability issue here. The blacklist/whitelist consists of regular expressions but that is actually not super user friendly as its not obvious and they are also hard to use compared to something like glob/fnmatch style matching (or plain packagenames). I can't change this easily without breaking existing setups though. Well, it was a basic stringcompare in squeeze. We're using a mix of squeeze and wheezy, and the blacklist is maintained through a puppet recipe templating the blacklist value. So I think better documenting it is the first step. It could simply use it as a plain string if the regexp fails and display a warning. I think that would certainly benefit me. I'm working around the problem by writing ^libstdc.*. Perhaps aborting due to invalid input is the best solution, but I might suggest a more friendly warning without a traceback. Or I could add a new Unattended-Upgrade::Package-Blacklist-Plain list for non-regexp content (it really should be the other way around, Unattended-Upgrade::Package-Blacklist-Regex and Unattended-Upgrade::Package-Blacklist would be plain but that is tricky due to the compatibility concerns I outlined earlier. I doubt you need another setting. The current list is quite fine. If I would have been at the design board, I would suggest parsing strings starting and ending with slashes (e.g.: /foo/) to parse as a regexp, and strings without slashes as real strings. But I grew up in a perl world and find python's regexps a but boilerplatey having to compile them explicitly. Regards, Kai Storbeck -- Systeembeheer XS4ALL Internet bv Internet: www.xs4all.nl Contact: www.xs4all.nl/contact signature.asc Description: OpenPGP digital signature
Bug#753892: Regular expressions are indeed mandatory
Dear Maintainer, I tried adding this package to the package-blacklist: libstdc++6 This will fail, as it is an invalid regular expression: # unattended-upgrade --dry-run --debug Initial blacklisted packages: libaio1 libboost-thread1.49.0 libc6 libgcc1 libgoogle-perftools4 libleveldb1 libnspr4 libnspr4-0d libnss3 libnss3-1d libstdc++6 libuuid1 Starting unattended upgrades script Allowed origins are: ['o=Debian,a=stable', 'o=Debian,a=wheezy', 'o=Debian,a=wheezy-updates', 'o=Debian,a=wheezy-lts', 'o=Debian,a=wheezy-security'] Checking: acpi-support-base ([Origin component:'main' archive:'stable' origin:'Debian' label:'Debian' site:'ftp.debian.xs4all.net' isTrusted:True, Origin component:'main' archive:'stable' origin:'Debian' label:'Debian' site:'ftp.nl.debian.org' isTrusted:True, Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True]) Traceback (most recent call last): File /usr/bin/unattended-upgrade, line 1011, in module main(options) File /usr/bin/unattended-upgrade, line 813, in main not is_pkgname_in_blacklist(pkg.name, blacklisted_pkgs) and File /usr/bin/unattended-upgrade, line 370, in is_pkgname_in_blacklist if re.match(blacklist_regexp, pkgname): File /usr/lib/python2.7/re.py, line 137, in match return _compile(pattern, flags).match(string) File /usr/lib/python2.7/re.py, line 242, in _compile raise error, v # invalid expression sre_constants.error: multiple repeat (this is on wheezy) Is this intentional, or is this a bug? Kai Storbeck -- Systeembeheer XS4ALL Internet bv Internet: www.xs4all.nl Contact: www.xs4all.nl/contact signature.asc Description: OpenPGP digital signature
Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)
On 27/01/2014 04:25, Andrew Starr-Bochicchio wrote:
On Thu, Oct 17, 2013 at 5:20 PM, Kai Storbeck k...@xs4all.nl wrote:
I have updated roundup_1.5.0-1 per the 17th of October with a few
changes after getting feedback by Sebastian Ramacher.
Hi Kai,
I came across your package on mentors, and I am interested in
sponsoring it. Though, I ran into a few issues that need to be fixed
first.
Hello Andrew,
Thanks for your response. I've marked the package as no need for a
sponsor, but your feedback is very welcome.
Perhaps my discussions with Sebastian should've been Cc'ed to this bug.
1) You seem to maintain the packaging in a VCS:
* Move to git-dpm packaging
In that case, it is very useful to include Vcs-{Git, Svn, Bzr} and
Vcs-Browser fields in debian/control:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields
Perhaps you can help me with this.
Since I'm joining the python application packaging team, I'll be moving
to SVN. I'm probably going to import the last uploaded version (1.20-1
or 1.1?) to svn.debian.org with this command:
$ svn import -m New import roundup \
svn+ssh://svn.debian.org/svn/python-apps/packages/roundup/trunk
Would that do the right thing? I presume I now have access to
svn.debian.org, being in the team listing on Alioth? Would you know that?
If you don't know, I'll ask on the debian-python listing.
2) There are minified version of JQuery and Bootstrap located in:
share/roundup/templates/jinja2/static
Thanks. I'm aware of that; Sebastian pointed this out too. I've already
posted upstream to ask them to include a non-minified version.
For 1.5.0 I'm a bit in the dark on how to proceed. Can I remove those
files, and ship a symlink to jquery and bootstrap packages? Or should I
make a full-fledged _dfsg.tgz file, and build from that?
As you already remove other copies of JQuery in other templates, you
probably already know that you should use the system copies.
Additionally, minified JavaScript objects that are installed with the
binary package must be built from source. Same goes for the minified
Bootstrap css files in that directory.
Ah. css too. Sometimes I think its less work to let upstream build a
package, and let it drop from debian.
Also, as long as these files are shipped in the tarball, their license
information needs to be documented in debian/copyright.
Ouch. They are using bootstrap 2.2.2. That tarfile is not downloadable
from getbootstrap.com anymore, so I can only guess that this was
licenced under Apache 2.0. Would that be enough?
So, what should I do: remove the not working template from 1.5.0, or
ship with a broken template? We're talking 1.5.0, since 1.5.1 is not
released yet, and I haven't heard words about estimates.
3) You seemed to remove some necessary bits from your postrm to clean
up when purging the package. From piuparts:
3m20.5s ERROR: FAIL: Package purging left files on system:
/etc/roundup/ owned by: roundup
/etc/roundup/service/ not owned
/etc/roundup/service/log/ not owned
3m20.5s ERROR: FAIL: Installation, upgrade and purging tests.
I'm aware of that too. I hadn't started working on both issues, pending
my move to subversion.
There maybe further issues. This is just as far as I got. I'd be happy
to do a closer review and hopefully sponsor the package once these
problems are fixed.
Thanks for your work on Debian!
Cheers. I find it quite a lot of work for a niche leave-package, and its
not an easy package to start out with. Sadly.
Regards,
Kai
signature.asc
Description: OpenPGP digital signature
Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)
On 8/15/13 3:21 PM, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. I have updated roundup_1.5.0-1 per the 17th of October with a few changes after getting feedback by Sebastian Ramacher. - I removed runit support; - added a NEWS.Debian section about this - Added in a WSGI example application and libapache2-mod-wsgi examples (And Suggests) - Rewrote large parts of the README.Debian to be consistent with the above changes. This should close an extra bug: #604074 - Made a debhelper Build dependency on 8.2 instead of 8. - Changed the debian/compat from 7 to 8. - removed an old occurrence of dh_installoverrides (unused) - /etc/defaults/roundup contains a $RUN variable defaulting to 'no'. - Added more NEWS about this. - Rebuild the documentation using sphinx, fix an upstream sphinx layout issue. This removed some lintian4py warnings. - #DEBHELPER# tags are now present in all the *.(pre|post)(inst|rm) scripts where they are needed. Removed lintian overrides. Lots of work done I think. Regards, Kai signature.asc Description: OpenPGP digital signature
Bug#719801: RFS: roundup/1.5.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package roundup, the python bug tracking software. * Package name: roundup Version : 1.5.0-1 Upstream Author : Richard Jones * URL : roundup-tracker.org * License : MIT / ZPL Section : web It builds those binary packages: roundup- Simple issue-tracking system To access further information about this package, please visit the following URL: http://mentors.debian.net/package/roundup Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/r/roundup/roundup_1.5.0-1.dsc More information about hello can be obtained from http://www.example.com. Major changes since the wheezy (1.4.20-1.1) version: * New upstream version (which fix 2 bugs) * Fix a documentation bug * Move to git-dpm packaging Please see the changelog for the exact changes. Kind regards, Kai Storbeck -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718213: roundup: new upstream version (1.5) is available
tags 718213 confirmed Hi Sebastian, On 7/28/13 9:48 PM, Sebastian Ramacher wrote: Source: roundup Version: 1.4.20-1.1 Severity: wishlist Hi, According to https://pypi.python.org/pypi/roundup roundup 1.5 has been released. It would be great if you could package it! Thank you for reporting this bug. I'm working on creating a 1.5 version of the package. Are you a user of (the current version of) the package? Regards, Kai signature.asc Description: OpenPGP digital signature
Bug#691893: RFS: roundup/1.4.20-2 [RC]
Hi Mike, Thanks for your prompt review. It seems I wasn't fully aware of the Freeze Policy. I was under a wrong assumtion that I could make the package's state better during the freeze. I've spoken with Salvatore who proposed an NMU for only the RC bug. I hope he can find the time to upload his proposed patch before the deadline of the 7th. The other bugs can wait for Jessie. + * do not remove roundup user on purge, due to possible dataloss This sounds like a grave issue. If so, why is there no bug report about it? If you think this needs to be fixed for wheezy, please write a bug report with sufficient rc severity. I'm unsure if I agree. There is only slight consensus about the matter. The discussion about removal of users in purge hasn't made it into a policy document as far as I understand. The thread I'm referring to is documented in this policy bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833 (Long). In the mean time, this bug can be closed I think? Regards, Kai signature.asc Description: OpenPGP digital signature
Bug#691893: RFS: roundup/1.4.20-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package roundup. I have a dedicated uploader (Toni Mueller), but another eye on my changes needn't hurt. It fixes 3 outstanding bugs, one of which is an RC bug. * Package name: roundup Version : 1.4.20-2 Upstream Author : roundup-de...@sourceforge.net * URL : http://www.roundup-tracker.org/ * License : Zope Public License (ZPL) Version 2.0 Section : web It builds those binary packages: roundup- Issue-tracking system in python To access further information about this package, please visit the following URL: http://mentors.debian.net/package/roundup Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/r/roundup/roundup_1.4.20-2.dsc Regards, Kai Storbeck signature.asc Description: OpenPGP digital signature
Bug#689257: only remove the initscripts and symlinks on purge
Hi Salvatore, Thanks for your patch. Since I still have a few outstanding issues to solve, I'm delaying an upload. I'm even thinking of removing the removal of the user, and the rest seems to be there due to a bug thats probably fixed now. Regards, Kai Storbeck Salvatore Bonaccorso wrote: tags 689257 + patch thanks Hi Kai Note I have not taken any upload action, only attaching here a patch. The postrm removes the two initscripts, but these should only be removed on purge. If I'm correctly it should suffice here, moving all the action to only the purge call, and do nothing else on remove, abort-install and disappear. Note: I only had a really quick look and this should/can maybe further improved. Regards, Salvatore signature.asc Description: OpenPGP digital signature
Bug#534338: OpenSSL bindings for Perl -- licensing questions
Hi guys, Cheers for the elaborate thread that emerged from my graveyard bump. Daniel Kahn Gillmor wrote: It seems like the CPAN module authors are going to have to be involved (harrassed) somehow, unless openssl is considered sufficiently different from OpenSSL to invalidate stanza 5 of the OpenSSL license. --dkg I'm a bit perplexed that the module authors have anything to do with this as long as they are clearly stating their code is released under the artistic license. Should Debian concern itself (too much) with the authority of such a claim? Is it debians task to mediate between all open source forges around the world and their claims for licensing? Apologies if this is in the debian policy. Sincere Regards, Kai Storbeck signature.asc Description: OpenPGP digital signature
Bug#677976: roundup: no way to rebuild documentation from source
Hi Jakub, Thanks for taking the time to make a report. Jakub Wilk wrote: Source: roundup Version: 1.4.18-1.1 Severity: important The README says: The *.txt files in the doc directory are written in reStructedText. If you have rst2html installed (part of the docutils suite) you can convert these to HTML by running make html in the doc directory. It seems that the upstream maintainers have decided to strip the release tarball from the files you mentioned (and an extra file, doc/security.txt). Interesting. I have contacted the upstream developers why this is done. In the mean time, I can create a patch to add those 2 files, and make these 2 commands work again. The errors you mention persist though. I'll forward those upstream as well. But this doesn't work: $ cd doc $ make html make: *** No rule to make target `html'. Stop. Trying to convert index.txt manually leads to: $ rst2html doc/index.txt 21 /dev/null | head -n1 doc/index.txt:8: (ERROR/3) Unknown directive type toctree. (NB, index.html with this error is already included both in the source and the binary package...) setup.py appears to provide a build_doc command, but it doesn't work either: $ cd .. $ python setup.py --help-commands | grep build_doc build_docbuild documentation $ python setup.py build_doc running build_doc /usr/bin/sphinx-build -d build/temp.linux-i686-2.7/doc doc share/doc/roundup/html Error: Source directory doesn't contain conf.py file. error: command '/usr/bin/sphinx-build' failed with exit status 1 This command runs fine, though there are a few documents having no pointers to it. Kind regards, Kai signature.asc Description: OpenPGP digital signature
Bug#677965: roundup: SyntaxWarning: assertion is always true, perhaps remove parentheses?
tag pending thanks Hi Jakub, Thanks for your report. Jakub Wilk wrote: Package: roundup Version: 1.4.18-1.1 The following warnings are show when installing the package: /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:82: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (expression.startswith($) and expression.endswith($), /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:103: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (expression.startswith($) and expression.endswith($), /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:165: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (macroName.startswith($) and macroName.endswith($), I'm considering this bug fixed in the upcoming 1.4.20-1 release by stepping away from python-support. Kind regards, Kai Storbeck signature.asc Description: OpenPGP digital signature
Bug#677965: roundup: SyntaxWarning: assertion is always true, perhaps remove parentheses?
Hi Jakub, Jakub Wilk wrote: * Kai Storbeck k...@xs4all.nl, 2012-06-18, 15:19: /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:82: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (expression.startswith($) and expression.endswith($), /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:103: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (expression.startswith($) and expression.endswith($), /usr/lib/pymodules/python2.7/roundup/cgi/TAL/DummyEngine.py:165: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (macroName.startswith($) and macroName.endswith($), I'm considering this bug fixed in the upcoming 1.4.20-1 release by stepping away from python-support. I'm confused. This bug has nothing to do with python-support. It's a bug in roundup code. I was assuming something that I shouldn't have. You're completely right, it is a bug. It exists in 1.4.18-1.1, and it is an upstream bug. The bug was fixed upstream release 1.4.20. - issue2550728: remove buggy parentheses in TAL/DummyEngine.py. Reported and fixed by Ralf Hemmecke. (Bernhard) I'll have to dig a bit on how to update the bug information. Again, my sincere apologies for my wrong assumption and putting the blame somewhere where it shouldn't. Kind regards, Kai Storbeck signature.asc Description: OpenPGP digital signature
Bug#496041: fixed in 1.4.11 ?
Hi Steko, I'm taking a look at all the open bugs in roundup, and this bug is still open. I have tried to reproduce this bug in the 1.4.18-1.1, but your bug seems to have been fixed somewhere in between. Would you be so kind to acknowledge this, or help me reproduce the bug? I'm proposing to close the bug otherwise. Kind regards, Kai Storbeck signature.asc Description: OpenPGP digital signature
Bug#665203: snmpd: Upgrade from lenny to squeeze breaks postinstall when using NIS
Package: snmpd Version: 5.4.3~dfsg-2 Severity: serious Justification: Policy 6.2 Maintainer scripts idempotency Dear Reader, When configured with NIS, deluser doesn't work properly. This is a bug in itself, but I can't find the right place to file *that*. Since part of the upgrade process of *snmpd* uses deluser, it violates the maintainer scripts. The scripts HANG, whilst waiting for the nisserver to magically remove the user 'snmpd'. To reproduce, configure nis, and add a password entry in /etc/passwd: +:*:/sbin/nologin Then try upgrading snmpd (any version where the postinst script will invoke 'deluser snmpd' will probably do). If you think this bug is not in the right place, please reassign it to the package adduser. Kind regards, Kai -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27.43-xsserver (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snmpd depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii libsnmp15 5.4.3~dfsg-2 SNMP (Simple Network Management Pr ii libwrap07.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip snmpd recommends no packages. snmpd suggests no packages. -- Configuration Files: /etc/default/snmpd changed [not included] /etc/snmp/snmpd.conf changed [not included] -- debconf information: snmpd/upgradefrom521: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660132: I fixed this bug.
Hello David, Christian,
I've fixed this bug by changing liveHead in Format.pm to Q Q instead of Q.
I tried this after looking at the last patch upstream which more or less did
the same thing.
The actual patch:
--- cricket-1.0.5.orig/lib/RRD/Format.pm2012-02-16 11:17:18.344788018
+0100
+++ cricket-1.0.5/lib/RRD/Format.pm 2012-02-17 14:29:49.900788105 +0100
@@ -164,7 +164,7 @@
$self-{'statHead'} = a4 a5 x7 d Q Q Q x80;
$self-{'dsDef'} = a20 a20 Q d d x56;
$self-{'rraDef'} = a20 x4 Q Q d x72;
-$self-{'liveHead'} = Q;
+$self-{'liveHead'} = Q Q;
$self-{'liveHead3'} = Q Q;
$self-{'pdpDef'} = a30 x2 Q d x64;
$self-{'cdpDef'} = d Q x64;
Cheers,
Kai
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610306: wrong status when snmptrapd not configured to start
I agree with Rob. At least one should consider moving it to Patch Available. Kind regards, Kai -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
