How to upgrade to Core Update 62?

General questions.
Post Reply
werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

How to upgrade to Core Update 62?

Post by werwolf » September 14th, 2012, 4:52 am

I have installed IPFIRE 2.11 (61), but the choice Pakfire update 62 does not appear. What to do?

fazar
Posts: 44
Joined: March 29th, 2012, 2:07 am
Contact:

Re: How to upgrade to Core Update 62?

Post by fazar » September 14th, 2012, 5:51 am

good day, mate!

normally, IPFire will shown a notification to do upgrade on web interface when new core update is available.

you can also do manual upgrade by typing

pakfire update --force
pakfire upgrade

on your console. good luck.

User avatar
eXciter
Global Moderator
Global Moderator
Posts: 901
Joined: August 10th, 2005, 2:29 pm
Location: Erfurt
Contact:

AW: How to upgrade to Core Update 62?

Post by eXciter » September 14th, 2012, 7:54 am

Agrees with the system time of your ipfire?
Manchen gab Gott die Kraft Dinge zu ändern.
Mir gab er die Kraft die Dinge zu ertragen die ich nicht ändern kann.


Image

CU Exciter

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » September 17th, 2012, 8:26 am

fazar wrote:good day, mate!

normally, IPFire will shown a notification to do upgrade on web interface when new core update is available.

you can also do manual upgrade by typing

pakfire update --force
pakfire upgrade

on your console. good luck.


Download error: the downloaded file (pakfile2/2.11/lists/core-list.db) wasn't verified by ipfire.org
sorry - exiting...

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » September 20th, 2012, 4:57 am

What to do? reinstall?

fazar
Posts: 44
Joined: March 29th, 2012, 2:07 am
Contact:

Re: How to upgrade to Core Update 62?

Post by fazar » September 21st, 2012, 6:20 am

did you already check system time and date?

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » September 21st, 2012, 7:58 am

fazar wrote:did you already check system time and date?


Yes. time is correct.

fazar
Posts: 44
Joined: March 29th, 2012, 2:07 am
Contact:

Re: How to upgrade to Core Update 62?

Post by fazar » September 22nd, 2012, 12:37 am

hmm.. seems ipfire unable to verify downloaded file. in many case, it caused by wrong system time and date or interrupted/unfinished download (downloaded file corrupted).

you can do a little test by download ipfire core update then verify it manually.

Code: Select all

wget http://ftp.byfly.by/pub/ipfire/pakfire2/2.11/paks/core-upgrade-2.11-62.ipfire
gpg --verify core-upgrade-2.11-62.ipfire


it should be no error during verification in order to install it to current ipfire system.

otherwise, you *always* can do re-install to the latest core update. installation and configuration take 15 minutes or less. :)
Last edited by fazar on September 22nd, 2012, 12:40 am, edited 1 time in total.

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » September 23rd, 2012, 4:43 am

fazar wrote:hmm.. seems ipfire unable to verify downloaded file. in many case, it caused by wrong system time and date or interrupted/unfinished download (downloaded file corrupted).

you can do a little test by download ipfire core update then verify it manually.

Code: Select all

wget http://ftp.byfly.by/pub/ipfire/pakfire2/2.11/paks/core-upgrade-2.11-62.ipfire
gpg --verify core-upgrade-2.11-62.ipfire


it should be no error during verification in order to install it to current ipfire system.

otherwise, you *always* can do re-install to the latest core update. installation and configuration take 15 minutes or less. :)

[root@ipfire ~]# wget http://ftp.byfly.by/pub/ipfire/pakfire2 ... -62.ipfire
--07:41:20--  http://ftp.byfly.by/pub/ipfire/pakfire2 ... -62.ipfire
          => `core-upgrade-2.11-62.ipfire'
Resolving ftp.byfly.by... 86.57.151.3
Connecting to ftp.byfly.by|86.57.151.3|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,994,933 (8.6M) [application/octet-stream]

100%[====================================>] 8,994,933      1.81M/s    ETA 00:00

07:41:25 (1.71 MB/s) - `core-upgrade-2.11-62.ipfire' saved [8994933/8994933]

[root@ipfire ~]# gpg --verify core-upgrade-2.11-62.ipfire
gpg: Signature made Thu Sep  6 18:08:48 2012 EEST using DSA key ID 64D96617
gpg: Can't check signature: public key not found
[root@ipfire ~]#

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » October 15th, 2012, 5:25 am

Today we have an inscription Notice: There is an core-update from 61 to 62 available.

but when trying to update


Oct 15 07:46:33 ipfire pakfire: DOWNLOAD ERROR: The downloaded file (pakfire2/2.11/lists/core-list.db) wasn't verified by IPFire.org. Sorry - Exiting...
Oct 15 07:46:34 ipfire pakfire: TIME INFO: Time Server 79.142.192.4 has -7.729748 sec offset to localtime.
Oct 15 07:46:54 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.11 started!
Oct 15 07:46:54 ipfire pakfire: CRYPTO INFO: Checking GnuPG Database
Oct 15 07:46:54 ipfire pakfire: CRYPTO WARN: The GnuPG isn't configured corectly. Trying now to fix this.
Oct 15 07:46:54 ipfire pakfire: CRYPTO WARN: It's normal to see this on first execution.
Oct 15 07:49:54 ipfire pakfire: CORE INFO: core-list.db is 165179 seconds old. - DEBUG: force
Oct 15 07:49:54 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Oct 15 07:49:55 ipfire pakfire: MIRROR INFO: 13 servers found in list
Oct 15 07:49:55 ipfire pakfire: PING INFO: mirror8.ipfire.org is alive
Oct 15 07:49:55 ipfire pakfire: DOWNLOAD INFO: Host: mirror8.ipfire.org (HTTP) - File: pakfire2/2.11/lists/core-list.db
Oct 15 07:49:55 ipfire pakfire: DOWNLOAD INFO: pakfire2/2.11/lists/core-list.db has size of 265 bytes
Oct 15 07:49:55 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Oct 15 07:49:55 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Oct 15 07:49:55 ipfire pakfire: DOWNLOAD ERROR: The downloaded file (pakfire2/2.11/lists/core-list.db) wasn't verified by IPFire.org. Sorry - Exiting...
Oct 15 07:49:56 ipfire pakfire: TIME INFO: Time Server 62.149.0.30 has -7.750800 sec offset to localtime.
Oct 15 08:24:11 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.11 started!
Oct 15 08:24:11 ipfire pakfire: CRYPTO INFO: Checking GnuPG Database
Oct 15 08:24:11 ipfire pakfire: CRYPTO WARN: The GnuPG isn't configured corectly. Trying now to fix this.
Oct 15 08:24:11 ipfire pakfire: CRYPTO WARN: It's normal to see this on first execution.

User avatar
tmkoeln
Posts: 732
Joined: February 26th, 2012, 11:34 am
Location: Köln/Cologne
Contact:

Re: How to upgrade to Core Update 62?

Post by tmkoeln » October 15th, 2012, 7:38 am

Try to ping google.com from console/ssh (if activated)...

tmkoeln
@Köln/Koln/Cologne (Productive System) @ netcologne 100 Mbit VDSL2
Image
@Wesseling (Productive System) @ netcologne 100 Mbit VDSL2
Image

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » October 15th, 2012, 10:05 am

[root@ipfire ~]# ping google.com
PING google.com (212.188.10.119): 56 data bytes
64 bytes from 212.188.10.119: icmp_seq=0 ttl=44 time=112.009 ms
64 bytes from 212.188.10.119: icmp_seq=1 ttl=44 time=112.039 ms
64 bytes from 212.188.10.119: icmp_seq=2 ttl=44 time=112.068 ms
64 bytes from 212.188.10.119: icmp_seq=3 ttl=44 time=111.953 ms
64 bytes from 212.188.10.119: icmp_seq=4 ttl=44 time=112.011 ms
64 bytes from 212.188.10.119: icmp_seq=5 ttl=44 time=112.011 ms
64 bytes from 212.188.10.119: icmp_seq=6 ttl=44 time=112.141 ms
64 bytes from 212.188.10.119: icmp_seq=7 ttl=44 time=112.054 ms
64 bytes from 212.188.10.119: icmp_seq=8 ttl=44 time=112.184 ms
64 bytes from 212.188.10.119: icmp_seq=9 ttl=44 time=112.063 ms
64 bytes from 212.188.10.119: icmp_seq=10 ttl=44 time=112.069 ms
64 bytes from 212.188.10.119: icmp_seq=11 ttl=44 time=111.988 ms
64 bytes from 212.188.10.119: icmp_seq=12 ttl=44 time=112.223 ms
64 bytes from 212.188.10.119: icmp_seq=13 ttl=44 time=112.114 ms
64 bytes from 212.188.10.119: icmp_seq=14 ttl=44 time=111.957 ms
64 bytes from 212.188.10.119: icmp_seq=15 ttl=44 time=112.134 ms
64 bytes from 212.188.10.119: icmp_seq=16 ttl=44 time=112.070 ms
64 bytes from 212.188.10.119: icmp_seq=17 ttl=44 time=112.080 ms
64 bytes from 212.188.10.119: icmp_seq=18 ttl=44 time=111.922 ms
64 bytes from 212.188.10.119: icmp_seq=19 ttl=44 time=112.314 ms
^C--- google.com ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max/stddev = 111.922/112.070/112.314/0.093 ms

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: How to upgrade to Core Update 62?

Post by Arne.F » October 16th, 2012, 11:46 am

IPFire needs to download the gpg-keys at first update.

Have you blocked the gpg keyserver port (11371) in the outgoing firewall?
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

werwolf
Posts: 32
Joined: June 23rd, 2010, 5:22 am

Re: How to upgrade to Core Update 62?

Post by werwolf » October 17th, 2012, 6:02 am

Arne.F wrote:IPFire needs to download the gpg-keys at first update.

Have you blocked the gpg keyserver port (11371) in the outgoing firewall?


Thank you. Add rules and the update was successful. But the fact is that before the system updates without this rule.

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: How to upgrade to Core Update 62?

Post by Arne.F » October 17th, 2012, 9:31 pm

The key download is needed two times. One if the webif initiate pakfire downloads as nobody and one if the root user use pakfire on the commandline.

After both keyrings contain the ipfire keys it was not needed anymore (except we update the keys)
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

Post Reply