Update hängt

Probleme bei der Installation?
pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Update hängt

Post by pixel » January 11th, 2018, 1:22 pm

Hallo zusammen,

ich versuche gerade ein IPFire auf den aktuellen Stand zu bringen. Nachdem das Update im WebUI ewig hing habe ich den Browser einfach zu gemacht. IPFire komplett neu gestartet und es dann auf der Konsole versucht. Aberauch hier hängt es schon seit 30 Minuten:

Code: Select all

[root@ipfire ~]# pakfire update
[root@ipfire ~]# pakfire upgrade
CORE UPGR: Upgrading from release 110 to 117
meta-core-upgrade... 100.00% |=============================>|   325.00 B
Auf der Platte ist genug Platz vorhanden. Wo kann ich ansetzen?

Viele Grüße
pixel

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

Re: Update hängt

Post by Arne.F » January 12th, 2018, 9:50 am

Seltsam. Der hängt so wies aussieht noch vor den eigentlichen Updates. Schau mal ins log (ALT+F12) oder 'tail -f /var/log/messages' ob der die Server erreichen kann.
Arne

Support the project on the IPFire whishlist!

Image

Image

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

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 12th, 2018, 10:41 am

Habe den Host nochmal komplett neu gestartet und:

Code: Select all

pakfire update
aufgerufen. Da bekomme ich auf der Konsole:

Code: Select all

[root@ipfire ~]# pakfire update
Giving up: There was no chance to get the file "counter.py?ver=2.19-x86_64&uuid=4729c71e-db1c-48cf-a670-f411b99bd00c" from any available server.
There was an error on the way. Please fix it.

Giving up: There was no chance to get the file "2.19-x86_64/lists/server-list.db" from any available server.
There was an error on the way. Please fix it.
und im Log:

Code: Select all

Jan 12 11:38:47 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.19-x86_64 started!                                                                                                           
Jan 12 11:38:47 ipfire pakfire: CRYPTO INFO: Checking GnuPG Database                                                                                                                        
Jan 12 11:38:47 ipfire pakfire: Sending my uuid: 4729c71e-db1c-48cf-a670-f411b99bd00c                                                                                                       
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD STARTED: counter.py?ver=2.19-x86_64&uuid=4729c71e-db1c-48cf-a670-f411b99bd00c                                                                      
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTP) - File: counter.py?ver=2.19-x86_64&uuid=4729c71e-db1c-48cf-a670-f411b99bd00c                                 
Jan 12 11:38:47 ipfire unbound: [1282:0] info: validation failure pakfire.ipfire.org. A IN                                                                                                  
Jan 12 11:38:47 ipfire unbound: [1282:0] info: validation failure pakfire.ipfire.org.stedry.local. A IN
Jan 12 11:38:47 ipfire unbound: [1282:0] info: validation failure win8.ipv6.microsoft.com. A IN
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to pakfire.ipfire.org:80 (Bad hostname 'pakfire.ipfire.org')
Jan 12 11:38:47 ipfire pakfire: Giving up: There was no chance to get the file counter.py?ver=2.19-x86_64
Jan 12 11:38:47 ipfire pakfire: MIRROR INFO: server-list.db is 80552 seconds old. - DEBUG: force
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD STARTED: 2.19-x86_64/lists/server-list.db
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTP) - File: 2.19-x86_64/lists/server-list.db
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD INFO: 2.19-x86_64/lists/server-list.db has size of  bytes
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to pakfire.ipfire.org:80 (Bad hostname 'pakfire.ipfire.org')
Jan 12 11:38:47 ipfire pakfire: Giving up: There was no chance to get the file 2.19-x86_64/lists/server-list.db from any available server. There was an error on the way. Please fix it.
Jan 12 11:38:47 ipfire pakfire: DB INFO: packages_list.db is 80550 seconds old. - DEBUG: force
Jan 12 11:38:47 ipfire pakfire: DOWNLOAD STARTED: lists/packages_list.db
Jan 12 11:38:47 ipfire pakfire: MIRROR INFO: 20 servers found in list
Jan 12 11:38:47 ipfire unbound: [1282:0] info: validation failure mirror.infotronik.hu. A IN
Jan 12 11:38:47 ipfire pakfire: PING INFO: mirror.infotronik.hu is unreachable
Jan 12 11:38:48 ipfire unbound: [1282:0] info: validation failure ipfiremirror.wildernesstech.com. A IN
Jan 12 11:38:48 ipfire pakfire: PING INFO: ipfiremirror.wildernesstech.com is unreachable
Jan 12 11:38:50 ipfire unbound: [1282:0] info: validation failure mirror.uta.edu.ec. A IN
Jan 12 11:38:50 ipfire pakfire: PING INFO: mirror.uta.edu.ec is unreachable
Jan 12 11:38:52 ipfire kernel: DROP_INPUT IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=74.207.241.132 DST=192.168.2.193 LEN=44 TOS=0x00 PREC=0x00 TTL=54 ID=16899 DF PROTO=UDP SPT=31431 DPT=43631 LEN=24 
Jan 12 11:38:52 ipfire kernel: DROP_INPUT IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=139.162.72.65 DST=192.168.2.193 LEN=44 TOS=0x00 PREC=0x00 TTL=46 ID=53890 DF PROTO=UDP SPT=45516 DPT=43631 LEN=24 
Jan 12 11:38:54 ipfire unbound: [1282:0] info: validation failure checkip.dyndns.com. A IN
Jan 12 11:38:54 ipfire unbound: [1282:0] info: validation failure mirror.switch.ch. A IN
Jan 12 11:38:54 ipfire pakfire: PING INFO: mirror.switch.ch is unreachable
Jan 12 11:38:58 ipfire kernel: DROP_NEWNOTSYN IN=green0 OUT=red0 MAC=52:54:00:be:0d:de:24:5e:be:1c:e7:46:08:00 SRC=192.168.1.60 DST=139.162.145.160 LEN=88 TOS=0x00 PREC=0x00 TTL=63 ID=62664 DF PROTO=TCP SPT=51312 DPT=443 WINDOW=381 RES=0x00 ACK URGP=0 
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-user.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-nice.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-system.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-idle.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-wait.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-interrupt.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-softirq.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/disk-vda/disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/disk-vda1/disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/disk-vda2/disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/disk-vda3/disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/disk-vda4/disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/interface/if_octets-green0.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/interface/if_octets-red0.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/ping/ping-gateway.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/ping/ping_stddev-gateway.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/ping/ping_droprate-gateway.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-sshd/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-sshd/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-sshd/ps_disk_octets.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-sshd/ps_disk_ops.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-smbd/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-smbd/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-smbd/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-nmbd/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-nmbd/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squid/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squid/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squid/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squid/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squidguard/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squidguard/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squidguard/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-squidguard/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-charon/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-charon/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-snort/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-snort/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-openvpn/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-openvpn/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-openvpn/ps_disk_ops.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-qemu/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-rtorrent/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-rtorrent/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-rtorrent/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mpd/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mpd/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mpd/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mpd/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-asterisk/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-asterisk/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-asterisk/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-asterisk/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-java/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mysqld/ps_data.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mysqld/ps_code.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-mysqld/ps_cputime.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes-spamd/ps_rss.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/processes/fork_rate.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-PSCAN/ipt_bytes-DROP_PScan.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-PSCAN/ipt_packets-DROP_PScan.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-NEWNOTSYN/ipt_bytes-DROP_NEWNOTSYN.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-NEWNOTSYN/ipt_packets-DROP_NEWNOTSYN.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-POLICYFWD/ipt_bytes-DROP_FORWARD.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-POLICYOUT/ipt_bytes-DROP_OUTPUT.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/iptables-filter-POLICYOUT/ipt_packets-DROP_OUTPUT.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/swap/swap-used.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/swap/swap-free.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/swap/swap-cached.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/swap/swap_io-in.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/swap/swap_io-out.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/entropy/entropy.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/load/load.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/memory/memory-used.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/memory/memory-buffered.rrd) failed: This RRD was created on another architecture
Jan 12 11:38:59 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/memory/memory-free.rrd) failed: This RRD was created on another architecture
Jan 12 11:39:02 ipfire unbound: [1282:0] info: validation failure mirror.infotronik.hu. A IN
Jan 12 11:39:02 ipfire pakfire: PING INFO: mirror.infotronik.hu is unreachable
Jan 12 11:39:04 ipfire unbound: [1282:0] info: validation failure array805-prod.do.dsp.mp.microsoft.com. A IN
Jan 12 11:39:07 ipfire kernel: DROP_NEWNOTSYN IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=139.162.145.160 DST=192.168.2.193 LEN=89 TOS=0x00 PREC=0x00 TTL=54 ID=9966 DF PROTO=TCP SPT=443 DPT=51312 WINDOW=241 RES=0x00 ACK PSH URGP=0 
Jan 12 11:39:07 ipfire unbound: [1282:0] info: validation failure elb-v2v-servin-spot-1601190957.us-east-1.elb.amazonaws.com. A IN
Jan 12 11:39:07 ipfire unbound: [1282:0] info: validation failure oem.twimg.com. A IN
Jan 12 11:39:11 ipfire kernel: DROP_NEWNOTSYN IN=green0 OUT=red0 MAC=52:54:00:be:0d:de:d8:c4:6a:4b:d4:bf:08:00 SRC=192.168.1.116 DST=172.217.18.14 LEN=83 TOS=0x00 PREC=0x00 TTL=63 ID=60250 DF PROTO=TCP SPT=37255 DPT=443 WINDOW=797 RES=0x00 ACK PSH URGP=0 
Jan 12 11:39:12 ipfire kernel: DROP_NEWNOTSYN IN=green0 OUT=red0 MAC=52:54:00:be:0d:de:d8:c4:6a:4b:d4:bf:08:00 SRC=192.168.1.116 DST=216.58.205.234 LEN=83 TOS=0x00 PREC=0x00 TTL=63 ID=18836 DF PROTO=TCP SPT=55663 DPT=443 WINDOW=819 RES=0x00 ACK PSH URGP=0 
Jan 12 11:39:12 ipfire kernel: DROP_NEWNOTSYN IN=green0 OUT=red0 MAC=52:54:00:be:0d:de:d8:c4:6a:4b:d4:bf:08:00 SRC=192.168.1.116 DST=216.58.205.234 LEN=83 TOS=0x00 PREC=0x00 TTL=63 ID=24614 DF PROTO=TCP SPT=55664 DPT=443 WINDOW=703 RES=0x00 ACK PSH URGP=0 
Jan 12 11:39:15 ipfire unbound: [1282:0] info: validation failure dualstack.qcloud-pr-ipv6api-1953151949.us-east-1.elb.amazonaws.com. A IN
Jan 12 11:39:17 ipfire kernel: DROP_INPUT IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=176.58.96.231 DST=192.168.2.193 LEN=44 TOS=0x00 PREC=0x00 TTL=54 ID=0 DF PROTO=UDP SPT=31431 DPT=43631 LEN=24 
Jan 12 11:39:17 ipfire kernel: DROP_INPUT IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=74.207.241.132 DST=192.168.2.193 LEN=44 TOS=0x00 PREC=0x00 TTL=54 ID=20444 DF PROTO=UDP SPT=31431 DPT=43631 LEN=24 
Jan 12 11:39:18 ipfire pakfire: PING INFO: mirror.uta.edu.ec is unreachable
Jan 12 11:39:19 ipfire kernel: DROP_INPUT IN=red0 OUT= MAC=52:54:00:de:4a:6d:4c:09:d4:80:cd:a6:08:00 SRC=192.168.2.1 DST=192.168.2.193 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=50504 DPT=137 LEN=58 
Jan 12 11:39:26 ipfire kernel: DROP_NEWNOTSYN IN=green0 OUT=red0 MAC=52:54:00:be:0d:de:00:15:5d:c7:db:01:08:00 SRC=192.168.1.21 DST=64.233.167.188 LEN=41 TOS=0x00 PREC=0x00 TTL=127 ID=20622 DF PROTO=TCP SPT=49310 DPT=5228 WINDOW=510 RES=0x00 ACK URGP=0 
Jan 12 11:39:29 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-user.rrd) failed: This RRD was created on another architecture
Jan 12 11:39:29 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-nice.rrd) failed: This RRD was created on another architecture
Jan 12 11:39:29 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-idle.rrd) failed: This RRD was created on another architecture
Jan 12 11:39:29 ipfire collectd[2216]: rrdtool plugin: rrd_update_r (/var/log/rrd/collectd/localhost/cpu-0/cpu-interrupt.rrd) failed: This RRD was created on another architecture

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 12th, 2018, 1:09 pm

kann dies damit zusammen hängen dass eine Sicherung von einem 32Bit - IPFire auf einer 64Bit-Version eingespielt wurde?

Da wir den Server neu eingerichtet haben haben wir die 64Bit Version installiert und vorher auf dem alten 32Bit System eine Sicherung über das WebUI gemacht.

DJ-Melo
Posts: 357
Joined: July 8th, 2014, 7:12 am

Re: Update hängt

Post by DJ-Melo » January 12th, 2018, 1:21 pm

denke eher an ein dns Problem welche DNS-Ser werden denn eingesetzt?

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 12th, 2018, 3:12 pm

Aus Sicht von IPFire keiner. Im LAN ist ein Bind im Einsatz. Auf der roten Schnitstelle von IPFire hängt die Vodaphone-Box (Router) die Als GW und DNS im setup von IPFire eingetragen ist.

DJ-Melo
Posts: 357
Joined: July 8th, 2014, 7:12 am

Re: Update hängt

Post by DJ-Melo » January 12th, 2018, 3:37 pm

geht den ein ping von pakfire.ipfire.org vom lan und der IPFIre selbst aus?

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 13th, 2018, 6:56 am

DJ-Melo wrote:
January 12th, 2018, 3:37 pm
geht den ein ping von pakfire.ipfire.org vom lan und der IPFIre selbst aus?
Da scheint das Problem zu liegen. Also der primäre DNS ist der Win2012-ADS. Sekunder der Bind. Auf einer Linux-Maschine im LAN:

Code: Select all

root@vmhost02:~# cat /etc/resolv.conf

domain  stedry.local
nameserver  192.168.[x].22
nameserver  192.168.[x].5
option timeout:2
22 = ADS
5 = Bind

Code: Select all

root@vmhost02:~# nslookup pakfire.ipfire.org
Server:         192.168.1.22
Address:        192.168.1.22#53

Non-authoritative answer:
pakfire.ipfire.org      canonical name = web01.ipfire.org.
Name:   web01.ipfire.org
Address: 81.3.27.41
Funktioniert.

Auf dem IPFire - unter setup auf der Konsole - habe ich bei DNS und Netzwerk das gleiche eingetragen. Was mich allerdings wunder dass dies nicht in die resolv.conf eingetragen wird. Dort steht 127.0.0.1 (also localhost) ... weiß nicht ob dass so richtig ist. Aber genau der wird bei der Auflösung befragt:

Code: Select all

[root@ipfire ~]# setup 
[root@ipfire ~]# nslookup pakfire.ipfire.org
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find pakfire.ipfire.org: SERVFAIL
Soll ich die resolv.conf einfach von Hand anpasen oder wird diese durch einen Automatismuss überschrieben?

Viele Grüße
pixel

Alorotom
Posts: 383
Joined: March 30th, 2015, 6:56 am

Re: Update hängt

Post by Alorotom » January 13th, 2018, 8:54 am

Hallo pixel,

ich geb hier mal einen Link zu einem Beitrag von Arne rein.
Genau das könnte bei Dir passieren. Wenn weder der W2K12 noch der bind DNSSEC-fähig sind, fällt IPFire auf local recursor zurück. Allerdings sollte trotzdem eine Namensauflösung von pakfire.ipfire.org erfolgen, wenn auch langsamer.

Die 127.0.0.1 scheint auf der Console von IPFire normal zu sein. Sprich, Du kontaktierst den lokalen unbound auf IPFire und er antwortet selber, ergo kommt die Antwort von 127.0.0.1

Gruß
Alorotom
Image
Image
Image

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 13th, 2018, 9:06 am

Code: Select all

[root@ipfire ~]# /etc/init.d/unbound test-name-server 192.168.1.22
192.168.1.22 is DNSSEC-aware
192.168.1.22 supports TCP fallback
EDNS buffer size for 192.168.[x].22: 4096
Wie erkenne ich damit ob er es kann?

Alorotom
Posts: 383
Joined: March 30th, 2015, 6:56 am

Re: Update hängt

Post by Alorotom » January 13th, 2018, 10:19 am

So sieht das hier auch aus.
Welchen DNS benutzt der W2K12 dann? Der Forwarded das ja auch für IPs, die nicht seine Domain betreffen. Und ist der dann auch DNSSEC-aware, wenn Du den mit test-name-server abprüfst?
Image
Image
Image

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 13th, 2018, 12:29 pm

Ich habe jetzte einfach mal zum testen im IPFire Setup den externen Vodafone-DNS angegeben und den Win-Server raus. Trotzdem:

Code: Select all

root@ipfire ~]# nslookup www.google.de
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find www.google.de: SERVFAIL
Das kann doch dann nicht mit dem lokalen DNS zusammenhängen oder liege ich da jetzt falsch?

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

Re: Update hängt

Post by Arne.F » January 13th, 2018, 3:01 pm

DNSSec Aware sollte gehen, aber aus irgend einem grund geht die Prüfung schief.

Geht die Systemuhr richtig?

Wenn ja versuch mal mit unbound-anchor den dns rootkey neu zu laden.
Arne

Support the project on the IPFire whishlist!

Image

Image

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

pixel
Posts: 92
Joined: September 30th, 2010, 6:49 am

Re: Update hängt

Post by pixel » January 15th, 2018, 8:10 am

Alorotom wrote:
January 13th, 2018, 10:19 am
So sieht das hier auch aus.
Welchen DNS benutzt der W2K12 dann? Der Forwarded das ja auch für IPs, die nicht seine Domain betreffen. Und ist der dann auch DNSSEC-aware, wenn Du den mit test-name-server abprüfst?
Das ist mir jetzt nicht ganz klar was Du meinst? Wie soll ich es prüfen?
Arne.F wrote:
January 13th, 2018, 3:01 pm
DNSSec Aware sollte gehen, aber aus irgend einem grund geht die Prüfung schief.
Geht die Systemuhr richtig?
Ja
Arne.F wrote:
January 13th, 2018, 3:01 pm
Wenn ja versuch mal mit unbound-anchor den dns rootkey neu zu laden.
Also einfach in der Konsole:

Code: Select all

unbound-anchor
ausführen? Habe ich gemacht aber trotzdem:

Code: Select all

[root@ipfire ~]# unbound-anchor
[root@ipfire ~]# ping www.t-online.de
ping: www.t-online.de: Temporary failure in name resolution

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

Re: Update hängt

Post by Arne.F » January 15th, 2018, 1:11 pm

Seltsam. Kann der den rootkey nicht runterladen oder nicht schreiben?

versuch nochmal mit "-v" und wann das dann auch nicht klappt mit "-f -v"
oder ist der dns traffic wirklich versaut?
Arne

Support the project on the IPFire whishlist!

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

Who is online

Users browsing this forum: No registered users and 2 guests