freebsd-update won't update 8.2-R-p9 to p10
I can't seem to get freebsd-update to do the jump from 9.2-RELEASE-p9 to p10. This is what I'm getting. sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree No updates needed to update system to 8.2-RELEASE-p10. WARNING: FreeBSD 8.2-RELEASE-p9 HAS PASSED ITS END-OF-LIFE DATE. Any security issues discovered after Wed Aug 1 00:00:00 UTC 2012 will not have been corrected. Note the complaint about mergemaster.mtree. I haven't modified that, so I'm not sure why it's complaining. It may be a red herring anyway though. However, since no changes have been downloaded, an install does nothing. sudo freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. However, after a reboot, I'm still running p9. uname -a FreeBSD obfuscated.com 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Mon Jun 11 23:00:11 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I'm running a generic kernel, which should be updated according to the freebsd-update docs. Any suggestions for how to get this to complete? ___ 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: Major version changes using portupgrade?
On 2011/12/04, at 02:29, Sergio Tam wrote: === postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They will not build together. Please remove them first with pkg_delete(1). pay attention here *** Error code 1 postgresql-client-8.4.8 make deinstall That's the ports makefiles talking, isn't it? In order to do that deinstall I need to also remove all of the things that depend on it... portupgrade is supposed to help me do the in-place upgrade without removing everything else first. Even if I forced the deinstall without letting the dependencies get in the way, wouldn't that break the dependency registration (+REQUIRED_BY) for all of those packages in the future? ___ 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: Major version changes using portupgrade?
On 2011/12/04, at 14:13, Matthew Seaman wrote: 4) Now for the updating bit. I'm going to use portmaster's '-o' functionality to swap out the postgresql versions. (portupgrade has very similar functionality if you prefer that.) postgresql is trickier than most, because there have to be both -server and -client ports to deal with. I also have postgresql-contrib-9.0.5 installed, which isn't critical but needs similar treatment. Everything depends on the -client port, so we start with that: # portmaster -o databases/postgresql91-client \ postgresql-client-9.0.5 # portmaster -o databases/postgresql91-server \ postgresql-server-9.0.5_1 # portmaster -o databases/postgresql91-contrib \ postgresql-contrib-9.0.5 This is the problem bit. The -o doesn't work with the ones I'm dealing with because of conflicts between 8.4 and 9.1. 9.1 *won't even build*. If you can find a way to get around that, then you can make life even easier for yourself by doing a recursive build of all of the things that depend on the client. It's getting around the conflict that I'm trying to figure out... the rest is handled. And by the way, if you're not already doing a recursive build then you can do the server upgrade more simply.. there are no dependencies attached to the server (normally) so you can just pkg_delete it and install 9.1. ___ 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: Major version changes using portupgrade?
On 2011/12/02, at 05:19, Matthew Pounsett wrote: I was expecting the following to work: sudo portupgrade -rf -o databases/postgresql91-client databases/postgresql84-client However, I'm running into a problem where the ports makefiles, and by extension portupgrade, are detecting that the two packages conflict, and so the 9.1 client won't even build[1]. Thanks to those who tried to help. After poking around in the Mk files A LOT, I eventually stumbled upon a solution. Not sure if this is right or not, but it worked: sudo portupgrade -M DISABLE_CONFLICTS=1 -rf -o databases/postgresql91-client databases/postgresql84-client Surprisingly, despite the -f, none of the dependencies were rebuilt.. I got warnings like this instead, for every dependency: --- Skipping 'databases/postgresql91-client' (apache-2.2.21) because it has already done However, the +REQUIRED_BY file was still rebuilt properly for the 9.1 client, so I can now easily go through and do dependency rebuilds as necessary. Cheers, Matt ___ 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
Major version changes using portupgrade?
I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've dumped the db and uninstalled the postgres-server port, and I'd like to use portupgrade to handle the client upgrade, since it has a number of dependencies that probably should be recompiled against the new client libs (and I'd like to keep the package's +REQUIRED_BY file properly updated anyway). I was expecting the following to work: sudo portupgrade -rf -o databases/postgresql91-client databases/postgresql84-client However, I'm running into a problem where the ports makefiles, and by extension portupgrade, are detecting that the two packages conflict, and so the 9.1 client won't even build[1]. This seems to be the sort of situation described by the -o example in the portupgrade man page, but I haven't been able to figure out how to make it work. Does anyone have any suggestions? Thanks! -- [1] [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 140 packages found (-1 +0) (...) done] --- Upgrading 'postgresql-client-8.4.8' to 'postgresql-client-9.1.1_1' (databases/postgresql91-client) --- Building '/usr/ports/databases/postgresql91-client' === Cleaning for postgresql-client-9.1.1_1 cd /usr/ports/databases/postgresql91-client make config; === postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They install files into the same place. You may want to stop build with Ctrl + C. === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for postgresql-client-9.1.1_1 = postgresql-9.1.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/postgresql. = Attempting to fetch ftp://ftp.se.postgresql.org/pub/databases/relational/postgresql/source/v9.1.1/postgresql-9.1.1.tar.bz2 postgresql-9.1.1.tar.bz2 100% of 14 MB 1349 kBps 00m00s === postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They will not build together. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20111202-57604-1bstor4-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=postgresql-client-8.4.8 UPGRADE_PORT_VER=8.4.8 make ** Fix the problem and try again. ___ 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
Starting tomcat7 port on 8.1-RELEASE-p1
I'm trying to get Tomcat 7 up and running for one of our developers, and seem
to have run into an odd roadblock.
I've installed everything using the ports, including the half-dozen distfiles
that need to be manually downloaded to satisfy dependencies. That went fine,
but tomcat won't start. I'm getting an empty file
localhost_access_log.2011-10-04.txt in /usr/local/apache-tomcat-7.0/logs/, as
well as the file 'catalina.out' which I'm pasting in at the bottom of this
email.
catalina.out seems to be suggesting that tomcat won't start because it can't
bind to localhost:8005, but I can't find a reason for this. I've done some
googling and seen some similar examples of this problem from earlier versions
of Tomcat, on earlier versions of FreeBSD, but nothing recent... the only fix
that has come up that looks like it could be relevant is forcing tomcat to use
IPv4 by adding this to rc.conf
tomcat55_java_opts=-Djava.net.preferIPv4Stack=true
I've tried this and it doesn't solve my problem.
The tomcat port doesn't seem to install any port-specific Getting Started docs
anywhere, and the Apache-Tomcat getting started documentation doesn't seem to
cover anything more than what the port install is supposed to take care of. Am
I just missing some setup instructions somewhere?
Any pointers appreciated.
--
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the java.library.path:
/usr/local/jdk1.6.0/jre/lib/amd64/server:/usr/local/jdk1.6.0/jre/lib/amd64:/usr/local/jdk1.6.0/jre/../lib/amd64:/usr/java/packages/lib/amd64:/lib:/usr/lib:/usr/local/lib
Oct 4, 2011 9:52:21 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
Oct 4, 2011 9:52:21 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 449 ms
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.21
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Oct 4, 2011 9:52:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener:
attributeAdded('org.apache.jasper.compiler.TldLocationsCache',
'org.apache.jasper.compiler.TldLocationsCache@6910b640')
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory host-manager
Oct 4, 2011 9:52:21 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory manager
Oct 4, 2011 9:52:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
Oct 4, 2011 9:52:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
Oct 4, 2011 9:52:22 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 468 ms
Oct 4, 2011 9:52:22 PM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[localhost:8005]:
java.net.BindException: Can't assign requested address
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.init(ServerSocket.java:185)
at
org.apache.catalina.core.StandardServer.await(StandardServer.java:422)
at org.apache.catalina.startup.Catalina.await(Catalina.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:654)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Oct 4, 2011 9:52:22 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-bio-8080]
Oct 4, 2011 9:52:23 PM
sed argument processing b0rked?
I'm running into a weird problem with sed. I believe what I'm trying to do should work fine, but seem to be stymied by weirdness in sed's argument processing. This is on 8.2-RELEASE-p2. which sed /usr/bin/sed According to years of experience and re-reading the man page five times today this should work, however sed is treating the second -e as a file name: sed -i'' -e 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ ? -e 's/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/'\ ? /tmp/pgdump sed: -e: No such file or directory If I drop the second -e it seems to work (the permission denied is expected): sed -i'' -e 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ ? /tmp/pgdump sed: /tmp/pgdump: Permission denied This is contrary to the sed man page: A single command may be specified as the first argument to sed. Multiple commands may be specified by using the -e or -f options. All commands are applied to the input in the order they are specified regardless of their origin. I thought maybe it was an argument order problem, since -i is listed after -e in the syntax synopsis (sometimes that matters) but that is actually even weirder: sed -e 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ -e 's/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/'\ -i'' /tmp/pgdump sed: -I or -i may not be used with stdin Fiddling around some more, I found that -e can't be supplied for the first command if there are multiple commands to be given.. but it does work if there's only one. That doesn't seem right. sed -i'' 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ -e 's/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/'\ /tmp/pgdump sed: /tmp/pgdump: Permission denied However, that breaks again if -i is moved: sed 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ -e 's/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/' \ -i'' /tmp/pgdump sed: -e: No such file or directory sed: s/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/: No such file or directory sed: -i: No such file or directory sed: /tmp/pgdump: Permission denied I'm fairly certain this has worked the way I'm expecting it to in the past. After all, I wrote it this way out of habit. Either way, it seems to me that argument processing in the current sed distributed with the OS is broken with respect to the way it's documented. Or am I missing something? ___ 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: sed argument processing b0rked?
On 2011/06/21, at 11:24, Lars Kellogg-Stedman wrote: sed -i'' -e 's/^\(REVOKE ALL ON SCHEMA public FROM \)postgres/\1pgsql/' \ ? -e 's/^\(GRANT ALL ON SCHEMA public TO \)postgres/\1pgsql/'\ ? /tmp/pgdump sed: -e: No such file or directory If you put a space after -i: sed -i '' ... Aha... I knew it had to be something. I couldn't quite wrap my head around the idea that sed is misbehaving.. it seems way too old and set in its ways for that. However, I did get the -i'' syntax from somewhere.. perhaps it's a GNUism and I just forgot where I picked it up. Thanks for the correction!___ 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: Portsnap Not Found Issues
On 05-Jan-2009, at 12:10 , Andreas Rudisch wrote: On Mon, 5 Jan 2009 12:02:40 -0500 APseudoUtopia apseudouto...@gmail.com wrote: Running FreeBSD 7.0-RELEASE-p5. [r...@host][/tmp] # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap2.FreeBSD.org... done. Re-run the command and with any luck it should switch to portsnap1.FreeBSD.org which will work correctly. Probably a minor problem with the portsnap2 server. I'm seeing a similar error on a different metadata file from portsnap1. portsnap3 seems to be working for me at the moment. PGP.sig Description: This is a digitally signed message part
lagg(4)/vlan(4) on-boot configuration problems
I'm trying to get a bonded vlan up using the new lagg driver on 6.3- RELEASE. I seem to be having problems with getting the network to configure at boot time, and I think I've found the reason. It would appear that order of operations is very important when configuring a lagg device. If I do this... # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport bce0 laggport bce1 # ifconfig lagg0.811 create # ifconfig lagg0.811 10.4.11.41/24 # ifconfig bce0 up # ifconfig bce1 up ... then everything works. If I do this... # ifconfig bce0 up # ifconfig bce1 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport bce0 laggport bce1 # ifconfig lagg0.811 create # ifconfig lagg0.811 10.4.11.41/24 ... then the lagg0.811 interface is useless, however no errors are emitted during configuration. It would appear that /etc/rc.d/netif is probably doing the latter, as when I try to configure the above interface using rc.conf nothing works. This is the relevant rc.conf block I'm using: cloned_interfaces=lagg0 lagg0.811 ifconfig_lagg0=up laggproto failover laggport bce0 laggport bce1 ifconfig_lagg0_811=10.4.11.41/24 ifconfig_bce0=up ifconfig_bce1=up Does anyone have suggestions for things I might be doing wrong here, before I file a bug? Thanks, Matt PGP.sig Description: This is a digitally signed message part
