Log.dat won't load

Hi,

I cannot look at system logs through the WUI.

IPFire v156 on Pi3b+

It tries to go to https://192.168.2.1:444/cgi-bin/logs.cgi/log.dat

And just times out.

Rest of the WUI I appear to be able to access no worries.

I am not sure why it would do that but it is not happening on my just updated to Core 156 system.

I get the log.dat page and can select DHCP Server and get the log displayed.

Did you reboot after the update. It did not mention that you had to but I always do anyway, just to be safe and secure. So my test was done after a reboot.

1 Like

I’m on the testing version of v156 still, maybe i should switch to stable and try. I did restart for good measure however and same issue remains.

I’ll try see if I can update to stable from test build and let you know.

@bonnietwin it does not seem to offer me 156 stable as an update so I guess test and stable are now the same?

The version number is the same but whether everything is the same I am not sure.

In some other forum threads there was an entry about putting your IPFire back to an earlier version and then redoing the update. I will try and see if I can find it and link it to this thread.

2 Likes

Here at the end:

1 Like

https://community.ipfire.org/t/2-25-core-156-testing-feedback/5216/22

This link gives the command to use to set your system back to 155 and then redo the update.

1 Like

Got it thanks, I altered the value to 155 and am going to upgrade to 156 stable branch now

Unfortunately changing that value does trick ipfire to show me a newer version in pakfire, however it does not actually update, it looks like it is updating but it does not.

Hi @knightian

Your only option may then be to do a backup and download it out of IPFire and then do a fresh Core 156 install and then restore the backup.

I had to delete /var/log/messages and it fixed the timeout

It was very large and full of a lot of errors

1 Like

That’s great to hear you solved it and without needing to re-install.
:+1:

@bonnietwin Indeed, however I will need to inspect what is congesting my messages log so worryingly.

It is absolutely choking with errors, I think I will do the reinstall anyway:

Jan 1 10:47:10 NF-WKIT-01 kernel: Exception stack(0xecdd5fb0 to 0xecdd5ff8)
Jan 1 10:47:10 NF-WKIT-01 kernel: 5fa0: 2955cd77 e783a2ee eb71dd92 b6edb210
Jan 1 10:47:10 NF-WKIT-01 kernel: 5fc0: 33221111 21634221 ee2b5913 90ab3b90 21c78daa b6edb228 b6edb468 b6edb3fc
Jan 1 10:47:10 NF-WKIT-01 kernel: 5fe0: d570654b becb6358 00892590 b6dafb84 20000010 ffffffff
Jan 1 10:47:10 NF-WKIT-01 kernel: red0: hw csum failure
Jan 1 10:47:10 NF-WKIT-01 kernel: CPU: 0 PID: 4702 Comm: sshd Tainted: G O 4.14.212-ipfire-multi #1
Jan 1 10:47:10 NF-WKIT-01 kernel: Hardware name: Generic DT based system
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (show_stack) from [] (dump_stack+0xc4/0xe0)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (dump_stack) from [] (netdev_rx_csum_fault+0x3c/0x48)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (netdev_rx_csum_fault) from [] (__skb_checksum_complete+0xac/0xb4)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (__skb_checksum_complete) from [] (nf_ip_checksum+0x60/0x120)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (nf_ip_checksum) from [] (tcp_error+0x1c8/0x230)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (tcp_error) from [] (nf_conntrack_in+0xf8/0x6a0)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (nf_conntrack_in) from [] (ipv4_conntrack_in+0x2c/0x30)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (ipv4_conntrack_in) from [] (nf_hook_slow+0x4c/0xd4)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (nf_hook_slow) from [] (ip_rcv+0x4e4/0x654)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (ip_rcv) from [] (__netif_receive_skb_core+0x740/0xce4)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (__netif_receive_skb_core) from [] (__netif_receive_skb+0x20/0x70)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (__netif_receive_skb) from [] (netif_receive_skb_internal+0x4c/0x100)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (netif_receive_skb_internal) from [] (netif_receive_skb+0x24/0x98)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (netif_receive_skb) from [] (ifb_ri_tasklet+0x1a4/0x2c8 [ifb])
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (ifb_ri_tasklet [ifb]) from [] (tasklet_action+0xc4/0x204)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (tasklet_action) from [] (__do_softirq+0xec/0x390)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (__do_softirq) from [] (irq_exit+0xdc/0x188)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (irq_exit) from [] (__handle_domain_irq+0x8c/0xfc)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (__handle_domain_irq) from [] (bcm2836_arm_irqchip_handle_irq+0xb4/0xbc)
Jan 1 10:47:10 NF-WKIT-01 kernel: [] (bcm2836_arm_irqchip_handle_irq) from [] (__irq_usr+0x54/0x80)
Jan 1 10:47:10 NF-WKIT-01 kernel: Exception stack(0xecdd5fb0 to 0xecdd5ff8)

Oh wow.

And related to the kernel, at least in the section you showed. That is never good.

Sigh. Yes it looks like re-install time. Still good thing with IPFire is that an install is not a very long or complicated thing.

Good luck and let us know how things go :crossed_fingers:

I just downloaded the image again and when trying to clone it to the sd card it says “ipfire-2.25.2gb-ext4.armv5tel-full-core156.img.xz: Compressed data is corrupt

Perhaps this might be the problem? the arm image is maybe corrupted?

xzcat: /Users/lancealot/ipfire-2.25.2gb-ext4.armv5tel-full-core156.img.xz: Compressed data is corrupt

0+9770 records in

0+9770 records out

632673980 bytes transferred in 64.956844 secs (9739913 bytes/sec)

So I am guessing that I cannot even do a fresh install now?

I suspect that’s why my ipfire died when I tried to update it via pakfire as well. It totally destroyed it, unbound wouldn’t start, it stopped issuing dhcp leases, I couldn’t connect via ipsec. I think arm image is hosed.

Second download of torrent version gave a matching hash so something strange must have happened in the first download.

Hi @knightian

Glad to hear that a second download seems to have worked. I also just downloaded the torrent of the arm image and the sha256sum matched fine and the file could be accessed.

Hopefully the install will go easier for you.

Just as an in case reminder - make sure you have all the backups you need taken off IPFire before doing the install.

Thanks yea it started dying but I managed to get in via ssh and run the backup.pl perl script then I got the .ipf file off the sdcard before I reflashed. I’ve now got a clean state up and running and going to restore fron=m the backup now