;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION: google.com. 299 IN A 172.217.215.138 google.com. 299 IN A 172.217.215.100 google.com. 299 IN A 172.217.215.101 google.com. 299 IN A 172.217.215.139 google.com. 299 IN A 172.217.215.113 google.com. 299 IN A 172.217.215.102
If you select stable in the IPFire>Pakfire screen and Save, it should revert you back to 145.
(you may have to decrement the value in /opt/pakfire/db/core/mine to 145)
Hi Paul, Yes, I figured that out in previous bash screenshots I posted. Seems either a circular reference or a cname out there in dns somewhere. In either event, it was a 302 to a 404, but prob due to them not moving 146 to stable
Earlier today, I had to jumpstart this thing by switching DNS to TCP, then saving, then back to UDP and saving again. Then testing allowed rDNS to connect. Darn strange…
Now, trying to do the same thing you asked above, just now, I backed off the mine file to 145, saved it out, then went back to GUI and hit the save button on the stable option. This time it can’t reach pakfire.ipfire.org. Dang this crap is frustrating.
I tried again to kick it by switching to TCP and back to UDP, but no dice!
but maybe you might be about to key me in on this.
cat /var/log/messages | grep -i unbound:
Jun 20 12:55:02 ipfire unbound: [3282:0] error: SERVFAIL <ping.ipfire.org. A IN>: all the configured stub or forward servers failed, at zone .
Jun 20 12:55:09 ipfire unbound: [3282:0] error: SERVFAIL <img-resize-cdn-prod.samsungnyc.com. A IN>: all the configured stub or forward servers failed, at zone .
I do not have a manual forward zone, and when I tried to add one for . it said there was a duplicate. In any event, I seen a downright ton of the zone . failures.
I finally was able to coherse the pakfire GUI to resolve something, but something seems off now with the installation, before and after I rebooted. I can only guess I am at core update 145 now, but these 3 sections are not in agreement. They usually are.
I totally had to kick this thing to get it to work. That is tragic… The ping timeout is soo bad from my network across the internet that I literally had to start a ping and again to get it started to the downloads server then use another putty window to launch the backupiso script. Holy crap, who can fix that?
[root@ipfire bin]# ./backupiso testing
Fetching https://downloads.ipfire.org/releases/ipfire-2.x/2.25-core145/ipfire-2.25.x86_64-full-core145.iso.md5
Checking md5 of ipfire-2.25.x86_64-full-core145.iso
md5 mismatch
Fetching again https://downloads.ipfire.org/releases/ipfire-2.x/2.25-core145/ipfire-2.25.x86_64-full-core145.iso
Checking again md5 of ipfire-2.25.x86_64-full-core145.iso
md5 is OK
Remastering iso
mount: /dev/loop0 is write-protected, mounting read-only
cp: cannot stat ‘/var/ipfire/backup/testing.ipf’: No such file or directory
Running mkisofs
I: -input-charset not specified, using utf-8 (detected in locale settings)
Size of boot image is 4 sectors -> No emulation
Size of boot image is 2880 sectors -> No emulation
3.52% done, estimate finish Sat Jun 20 23:21:44 2020
7.02% done, estimate finish Sat Jun 20 23:21:44 2020
10.53% done, estimate finish Sat Jun 20 23:21:44 2020
14.03% done, estimate finish Sat Jun 20 23:21:44 2020
17.54% done, estimate finish Sat Jun 20 23:21:44 2020
21.04% done, estimate finish Sat Jun 20 23:21:44 2020
24.55% done, estimate finish Sat Jun 20 23:21:44 2020
28.05% done, estimate finish Sat Jun 20 23:21:44 2020
31.56% done, estimate finish Sat Jun 20 23:21:44 2020
35.06% done, estimate finish Sat Jun 20 23:21:44 2020
38.57% done, estimate finish Sat Jun 20 23:21:44 2020
42.07% done, estimate finish Sat Jun 20 23:21:44 2020
45.59% done, estimate finish Sat Jun 20 23:21:44 2020
49.09% done, estimate finish Sat Jun 20 23:21:44 2020
52.60% done, estimate finish Sat Jun 20 23:21:44 2020
56.10% done, estimate finish Sat Jun 20 23:21:44 2020
59.61% done, estimate finish Sat Jun 20 23:21:44 2020
63.11% done, estimate finish Sat Jun 20 23:21:45 2020
66.62% done, estimate finish Sat Jun 20 23:21:45 2020
70.12% done, estimate finish Sat Jun 20 23:21:45 2020
73.63% done, estimate finish Sat Jun 20 23:21:45 2020
77.13% done, estimate finish Sat Jun 20 23:21:45 2020
80.64% done, estimate finish Sat Jun 20 23:21:45 2020
84.14% done, estimate finish Sat Jun 20 23:21:45 2020
87.66% done, estimate finish Sat Jun 20 23:21:45 2020
91.16% done, estimate finish Sat Jun 20 23:21:45 2020
94.67% done, estimate finish Sat Jun 20 23:21:45 2020
98.17% done, estimate finish Sat Jun 20 23:21:45 2020
Total translation table size: 2048
Total rockridge attributes bytes: 7777
Total directory bytes: 18432
Path table size(bytes): 74
Max brk space used 25000
142617 extents written (278 MB)
Cleaning up
I think, your main problem is the DNS thing.
Without a functioning name resolution all the other tasks will have problems.
I agree, there could be more error output. But with a running DNS system, the IPFire sites are reachable 95% of the time. Thus an effort in more error logging for accesses to the code base isn’t worth. My opinion.
You are invited, to think about reporting the fail of the process more clear and how to implement.
Any user of IPFire is welcome as developper of even small enhancements.
Bernhard, are you talking about this site on community.ipfire.com or a different site? Can you throw the URL in here? Not sure where you are talking about specifically.
Creating the ISO includes the download of the standard .iso file from the IPFire site. Problems in reaching download.ipfire.org result in a .iso with size 0. Main reason for the fail is a broken DNS.
Yea, I kinda figured thst one out but I am glad you posted it so others can see. I realized that when I pulled the backups script snd threw it in notepad so I could study what it was doing. My biggie is that for some reason the ipfire domain is slow in responding to my network and has been timing out. Probably the #1 reason the darn thing kept failing and giving me 0 bytelength files.
I’ve seen other posts from people with the same issue. Beside a bad DNS setting, I’m not sure I’ve seen any other solution.
I looked through the thread above and I didn’t see (or I missed) the “slow in responding”. Is this referring to the backup being slow or zero? Or something else? If something else you may want to open new thread.
