Re: [munin-users] Munin crashing : p5-Net-Server
On 2012-06-19T08:17:09+0100, Paul Macdonald p...@ifdnrg.com wrote: After a recent upgrade to p5-Net-Server-2.005 on various boxes, I'm finding that munin-node is going down regularly. (Multiple machines, looks to be affected on FreeBSD8.2 and FreeBSD8.3 REL, but not 9.0 machines) This is due to newsyslog sending a signal to munin-node (notice the first line of the log). As a workaround, if you comment the munin-node line in /etc/newsyslog.conf, munin-node will stay running, but you'll have to figure out another way to rotate the logs, if you care about rotating those logs. This is probably a bug somewhere. I haven't debugged further than this due to lack of time, but maybe this will help you determine the root cause, and a fix. It looks related to trying to start on an ipv6 interface ( which is not there) and i suspect this is a default from the perl Net-Server module rather than munin? Jun 19 00:00:01 ifdnrg20 newsyslog[24331]: logfile turned over Pid_file created by this same process. Doing nothing. 2012/06/19-00:00:02 Munin::Node::Server (type Net::Server::Fork) starting! pid(50897) sysctl: unknown oid 'net.ipv6.bindv6only' Resolved [*]:4949 to [::]:4949, IPv6 Resolved [*]:4949 to [0.0.0.0]:4949, IPv4 Binding open file descriptors 2012/06/19-00:00:02 Bad file descriptor at line 298 in file /usr/local/lib/perl5/site_perl/5.12.4/Net/Server.pm 2012/06/19-00:00:02 Server closing! shutdown() on unopened socket GEN0 at /usr/local/lib/perl5/5.12.4/mach/IO/Socket.pm line 295. shutdown() on unopened socket GEN1 at /usr/local/lib/perl5/5.12.4/mach/IO/Socket.pm line 295. Paul. -- Kenyon Ralph signature.asc Description: Digital signature
Re: Package building in clean/chroot environment
On 2010-03-13T10:42:40+, Brian Candler b.cand...@pobox.com wrote: Are there are any tools for building FreeBSD packages in a chroot cleanroom environment? This is so that I can be sure that all dependencies are properly declared, and so that I can be sure that the built binaries don't accidentally link to libraries which happen to be available on my build system but won't be available on the target system (oh, the joy of autoconf) Sounds like you want Tinderbox: http://www.freshports.org/search.php?query=tinderbox -- Kenyon Ralph signature.asc Description: Digital signature
Re: boost 1.41 and net-p2p/deluge
On 2009-12-30T09:46:55+0100, Pav Lucistnik p...@freebsd.org wrote: Michal Varga píše v st 30. 12. 2009 v 01:01 +0100: After the recent boost upgrade to 1.41, net-p2p/deluge needs to be recompiled to actually start, otherwise one just gets a nice crash/deadlock (I didn't investigate as I already remember the exactly same issue with previous boost upgrade, so went directly for recompilation). I have bumped deluge, thanks for the report. Same with graphics/gnash 0.8.6, it should be bumped. After the boost upgrade, gnash coredumped whenever I encountered a flash widget. Rebuilding gnash allows it to work again (or at least not coredump). Anyway, just an idea - shouldn't be those apps that depend on boost also bumped, to prevent issues like these? (again, might need some more investigation, this is just a quick notice) Bumping all ports en-masse sounds excessive to me. -- Pav Lucistnik p...@oook.cz p...@freebsd.org -- Kenyon Ralph signature.asc Description: Digital signature
Re: make config in editors/vim port
On 2009-11-08T13:34:43-0800, Naveen Nathan nav...@lastninja.net wrote: I've returned to using FreeBSD after a couple of years. I'm trying to compile vim without X11 and some other options that can be tweaked in the port. Everywhere I read suggests the user should supply -DWITHOUT_X11 when compiling Vim. However, I notice there is an options file which has a bunch of options other than just WITHOUT_X11 that I care about. When I try to do ``make config'' I get: [/usr/ports/editors/vim]# make config === No options to configure I do recall there being the ability to configure the port using dialog(1) awhile ago. Has this gone? Defining WITH_OPTIONS or WITH_VIM_OPTIONS in /etc/make.conf will enable the regular dialog configuration screen. -- Kenyon Ralph signature.asc Description: Digital signature
Re: portmaster: grep: Argument list too long
On 2009-10-18T23:04:41-0700, Doug Barton do...@freebsd.org wrote: Kenyon Ralph wrote: On 2009-10-18T21:43:24-0700, Doug Barton do...@freebsd.org wrote: I'm also concerned that there is something wrong with your /var/db/pkg directory, since grep can handle an argument list of many thousands of items without any problems. Can you do this and let me know what it says: ls -d /var/db/pkg/* | wc -l After doing portmaster --check-depends which did a few +REQUIRED_BY updates: % pkg_info | wc -l 845 % ls -d /var/db/pkg/* | wc -l 846 That is one more than portmaster -l: === 845 total installed ports Ok, can you please figure out what the extra entry is? The extra entry is just /var/db/pkg/pkgdb.db, so I presume that's not a problem. I also ran portmaster --check-port-dbdir, deleted the directories that did not seem to be installed, and noticed that x11/kde4 and kdeutils4 were not installed (even though the rest of kde4 seems to be installed). So I'm doing portmaster -v -t -D -R x11/kde4 right now, which is building several ports. I'll try resuming -r perl-threaded-5.10.1 after this. Ok, when you get back to the perl upgrade please apply the attached patch first. It is going to cause a lot of console output so you're probably better off starting script first to capture it. The patch had some problems with quoting and echoing from functions where there shouldn't have been any echoes, so the debug lines were being put into pkgdep entries and weird stuff like that. Anyway, without the debug patch, I tried the -r perl-threaded-5.10.1 again, and everything finished cleanly this time (I think this was at least the fifth time I started the process though). I guess it was running --check-depends that fixed it. Thanks, Kenyon Ralph signature.asc Description: Digital signature
portmaster: grep: Argument list too long
? Or am I doing something crazy and wrong here? Maybe it would just be better to delete all ports, and start from scratch with perl5.10 installed at the start? Also, this may be a separate issue, but looks like portmaster is going into a circle (this can also be seen in the snippets above): perl-threaded-5.10.1 kde4-4.3.1 kdeutils-4.3.1_1 security/gnupg ftp/curl dns/libidn lang/perl5.10 ... perl-threaded-5.10.1 kde4-4.3.1 kdeutils-4.3.1_1 security/gnupg ftp/curl dns/libidn lang/perl5.10 databases/gdbm devel/gmake devel/gettext converters/libiconv (Meanwhile, an important user of perl, vim, still hasn't been rebuilt.) Thanks, Kenyon Ralph signature.asc Description: Digital signature
Re: portmaster: grep: Argument list too long
On 2009-10-18T21:43:24-0700, Doug Barton do...@freebsd.org wrote: Kenyon Ralph wrote: I'm trying to replace perl 5.8 with perl 5.10, so I did this (as in the 20090328 /usr/ports/UPDATING entry): % sudo portmaster -v -t -D -o lang/perl5.10 lang/perl5.8 % sudo portmaster -v -D -R -m 'FORCE_PKG_REGISTER=yes' -r perl-threaded-5.10.1 (FORCE_PKG_REGISTER seems to be needed to keep libtool22 from erroring and stopping the portmaster run.) I'm looking into this in more detail, but first I wonder why libtool is being built at all. Did you follow the instructions in the 20090802 UPDATING entry to replace libtool15 with libtool22? You should not need to use FORCE_PKG_REGISTER in this situation, that's a sign that there is something wrong. I also suspect that it's masking a deeper problem and is the cause of having things installed more than once in the same portmaster run (which should never happen). This system was first created around 2009-08-14, so it always had libtool22. I'm also wondering if all your other ports are up to date (other than switching perl versions). At least on my system perl is not required by libtool so it doesn't make sense that it (or several of the other things in your log) are being built at all. Yes, before I started this perl upgrade, I had just csup'd /usr/ports and completed portmaster -a. I'm also concerned that there is something wrong with your /var/db/pkg directory, since grep can handle an argument list of many thousands of items without any problems. Can you do this and let me know what it says: ls -d /var/db/pkg/* | wc -l After doing portmaster --check-depends which did a few +REQUIRED_BY updates: % pkg_info | wc -l 845 % ls -d /var/db/pkg/* | wc -l 846 That is one more than portmaster -l: === 845 total installed ports That number should match the number of ports that 'portmaster -l' tells you that you have. Finally I would run 'portmaster --check-depends' just to see if there is anything else strange going on. You will probably get some errors about no installed version of perl5.8 which is normal. Ah, I do remember seeing some warnings flying by saying that I should try --check-depends. As I said above, I executed it. Didn't see any errors about perl5.8. I also ran portmaster --check-port-dbdir, deleted the directories that did not seem to be installed, and noticed that x11/kde4 and kdeutils4 were not installed (even though the rest of kde4 seems to be installed). So I'm doing portmaster -v -t -D -R x11/kde4 right now, which is building several ports. I'll try resuming -r perl-threaded-5.10.1 after this. Thanks, Kenyon Ralph signature.asc Description: Digital signature
Re: python26 (python26-2.6.2_3) build ERROR in FreeBSD ports tree
On 2009-09-15T10:08:52+0100, David Southwell da...@vizion2000.net wrote:
I want to understand why bug reports get closed prematurely and without any
discussion with the original person submitting the report.
...
Yrs frustrated
David Southwell
ps the PR link is:
http://www.freebsd.org/cgi/query-pr.cgi?pr=138835
(ports/138835: Python compile failure)
I am wondering the same thing. extra-patch-setup.py is wrong. miwi's
can't confirm post in ports/138835 doesn't even show the patch being
applied.
Here is the rejects file:
***
*** 1273,1279
)
libraries = []
- elif platform in ('freebsd4', 'freebsd5', 'freebsd6', 'freebsd7',
'freebsd8'):
# FreeBSD's P1003.1b semaphore support is very experimental
# and has many known problems. (as of June 2008)
macros = dict( # FreeBSD
--- 1277,1283
)
libraries = []
+ elif platform in ('freebsd4', 'freebsd5', 'freebsd6', 'freebsd7',
'freebsd8', 'freebsd9'):
# FreeBSD's P1003.1b semaphore support is very experimental
# and has many known problems. (as of June 2008)
macros = dict( # FreeBSD
Kenyon Ralph
signature.asc
Description: Digital signature
