Issue with apcupsd and gd.h missing?
When trying to do a portupgrade of apcupsd I received the following error: checking for gd2/gd.h... no configure: error: Found system GD library but no header file. Please find the file gd.h in your system include directories and report its location to apcupsd-users at lists.sourceforge.net The system is Freebsd 7.1. I checked and gd.h does exist so I'm a bit confused as to what is going on. The file is located in /usr/local/include, a path that it appears the port checks. Anyone else experiencing this? Any suggestions on how to fix it? gd is installed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Portupgrade not handling dependencies
I've been running Freebsd for several years on one of my primary public facing servers. Currently the server is running Freebsd 7.2. Up until about 2 weeks ago portupgrade always seemed to upgrade ports in the correct order so that any dependencies were built first, allowing all ports to be upgraded properly in one run. For the past 2 weeks though I have to run portupgrade 2-3 times every time I have more than one update because at least 1 port fails due to a dependency(which is seemingly upgraded after it tries to upgrade the other port). What the heck is going on and how do I fix it? Thanks, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade not handling dependencies
Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' As seen above, libtheora built and installed just fine, but ffmpeg was skipped for some reason. I ran portupgrade -a again and all worked fine. This ways also occuring when I ran portupgrade -arR. Ports tree is updated with cvsup each night. I don't believe I've overridden anything, most especially not in the past 2 weeks when this all started happening. The above is just one example of it happening. It happens almost everyday there is more than one port to upgrade(and different ports each time of course). Thanks again, Eric b. f. wrote: For the past 2 weeks though I have to run portupgrade 2-3 times every time I have more than one update because at least 1 port fails due to a dependency(which is seemingly upgraded after it tries to upgrade the other port). What the heck is going on and how do I fix it? We obviously can't help you without more information. What ports are failing? What are the dependencies that are out of sequence? What OPTIONS are you using with all of these? Have you overidden anything via pkgtools.conf? Is you ports tree up-to-date, and intact? b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade not handling dependencies
Actually, the bsdpan package is not the issue here. I was aware it wouldn't update that(no port for this perl module yet anyway). If you notice, it doesn't proceed to install ffmpeg, i force it to(highlighted by ): ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) ** %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) It should upgrade ffmpeg automatically, but doesn't and that is the issue. b. f. wrote: On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote: Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' I see. In the default /usr/local/etc/pkgtools.conf, there is a sample line (not commented out) that places any port that matches the glob bsdpan-* in HOLD_PKGS, meaning that portupgrade will refuse to handle it. Presumably this is so users can manage their own local tree of Perl ports that aren't in the regular ports tree. I don't do this, so I'm not familiar with how the two interact. But portupgrade seems to have done the right thing here: in the snippet you gave us, it ignored bsdpan-Acme-Damn and proceeded to begin building ffmpeg after updating libtheora -- the only problem seems to be that in the intermediate summary it lists ffmpeg, erroneously, as having been skipped -- but that seems to just be a cosmetic problem, because it then proceeds to start updating it. If later on it refuses to update it, then you've got a problem. In that case, you should try running pkgdb -L pkgdb -F to make sure that your pkgdb is in good shape, and then try your updates again. You might also try instead something like: portupgrade -ax bsdpan-* If that doesn't work, then you may either have to rip out your bsdpan-* ports, or just use a another tool for updating -- portmaster, for example. Or you can roll your own. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Portupgrade breaks Apache13-modssl
I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get apache started with no ssl but not with it. I have apache13-modssl installed. It wasn't modified during the upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? Thanks, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Portupgrade breaks Apache13-modssl
When I did the portupgrade I did 'portupgrade -arR'. Apache fails to start at boot. If I run it manually with 'httpd' it works fine but if I do 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl port with no luck. Not sure what other details I can give besides the messages log reports a core dump. -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Saturday, May 21, 2005 02:38 To: Eric Sheesley Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade breaks Apache13-modssl On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get apache started with no ssl but not with it. I have apache13-modssl installed. It wasn't modified during the upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. It is crashing, etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Portupgrade breaks Apache13-modssl
Here is the error from the log: May 21 10:49:30 rogue kernel: pid 69446 (httpd), uid 0: exited on signal 11 (core dumped) -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Saturday, May 21, 2005 02:38 To: Eric Sheesley Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade breaks Apache13-modssl On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get apache started with no ssl but not with it. I have apache13-modssl installed. It wasn't modified during the upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. It is crashing, etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Portupgrade breaks Apache13-modssl
That seemed to work. I removed the openssl extension from the php extensions.ini file and all seems to work fine now. Thanks, Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Kellers Sent: Saturday, May 21, 2005 11:01 To: postmaster Cc: 'Kris Kennaway'; Eric Sheesley Subject: Re: Portupgrade breaks Apache13-modssl On Saturday 21 May 2005 10:39 am, Eric Sheesley wrote: When I did the portupgrade I did 'portupgrade -arR'. Apache fails to start at boot. If I run it manually with 'httpd' it works fine but if I do 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl port with no luck. Not sure what other details I can give besides the messages log reports a core dump. -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Saturday, May 21, 2005 02:38 To: Eric Sheesley Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade breaks Apache13-modssl On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get apache started with no ssl but not with it. I have apache13-modssl installed. It wasn't modified during the upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. It is crashing, etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have had upgrades to php mysteriously (that is with no apparent logfile error) break apache. Try commenting out the following lines from your httpd.conf file: LoadModule php4_module AddModule mod_php4.c and restart apache. If that works, look in /usr/local/etc/php/extensions.ini and see if there are any obvious php conflicting modules and comment them out --extension=recode.so has sometimes gotten placed back in that file even though it's a known conflict after an upgrade. Then restart apache. If there is no obvious conflict like the recode conflict, you may have to begin commenting out the extensions in that file one by one, restarting apache until it starts again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Queue file write error and swap_pager issues
I have a Freebsd 6.2 server. For the past month or so I've been getting various messages from postfix saying Error: queue file write error and occasionally in the system logs I'll receive the following: +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 130435, size: 4096 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 130409, size: 4096 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 125548, size: 4096 I made some modifications to amavis-new to use the clamd virus scanning daemon instead of the command line version and most of the postfix errors went away but I still occasionally get one. I've used the system bios utilities to do a drive scan on both of the drives(raid 1) and they both were fine according to that. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
