Error 500 while updating

Getting Started with IPFire Updates Trouble
1

Hi,

I have just updated to 161.

Got an error 500 while updating:

[Fri Nov 26 18:25:35.509760 2021] [core:error] [pid 29327:tid 125760722282048] (70007)The timeout specified has expired: [client 192.168.0.74:50013] AH00574: ap_content_length_filter: apr_bucket_read() failed, referer: https://192.168.0.254:444/
[Fri Nov 26 18:46:05.750124 2021] [cgid:error] [pid 30714:tid 125760736056320] (13)Permission denied: AH01241: exec of ‘/srv/web/ipfire/cgi-bin/pakfire.cgi’ failed
[Fri Nov 26 18:46:05.750563 2021] [cgid:error] [pid 29327:tid 125760697103936] [client 192.168.0.74:52336] End of script output before headers: pakfire.cgi, referer: https://192.168.0.254:444/

After reloading the web-interface shows:

Ein Update erfordert einen Neustart! (needs a reboot)

What went wrong?

Thanks

1 Like
2

Usually there is nothing really wrong.

This error happen sometime if cgi’s are updated. The update has changed the webif files while the site was generated.

1 Like
3

OK, thanks. Happened quite many times before so I was wondering.

1 Like
4

BTW, this mirror caused confusion, too. The download almost stalled so I thought something was broken:

https://mirror.datacenter.by/pub/ipfire/pakfire2/2.27.2-x86_64/paks/core-upgrade-2.27-161.ipfire

It needed almost an hour to download.

5

Hi,

currently, IPFire randomly picks one of our mirror servers do download an upgrade or add-on. Not a very sophisticated approach, this might take pretty long if the server in question is located at the other end of the planet, or bad to reach in terms of routing.

Unfortunately, we currently lack time to make things more smart on this end. However, a faulty update will never be processed further, since its GPG signature does not verify.

Sorry to disappoint, and best regards,
Peter Müller

1 Like