[solved in 2.2.6] 2.2.5 problems with XMLRPC sync - the server 2 is not updated
-
Thank you, Renato!
I have tested the behaviour on pfSense 2.2.5 with lighttpd 1.4.38 from today's pfSense-LiveCD-2.3-ALPHA-i386-latest.iso.gz (09-Dec-2015 02:57). The problem does not reappear!
I could not find any snapshot for pfSense 2.2.6 :-\
Regards
yarick123Great! Thanks!
2.2.6 can be found at https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_RELENG_2_2/
-
BTW, @Renato: the i386 snapshot builder is stuck YET again.
-
BTW, @Renato: the i386 snapshot builder is stuck YET again.
Fixed, thanks!
Build script used on 2.3 doesn't have this kind of issue of getting stuck when one error happens, it tries again after some time.
-
Renato Botelho,
BTW, @Renato: the i386 snapshot builder is stuck YET again.
I have i386 platform and indeed there are no today's snapshots in https://snapshots.pfsense.org/FreeBSD_releng/10.1/i386/pfSense_RELENG_2_2/livecd_installer/ .
The latest i386 snapshot is dated 19-Nov-2015 18:49.
Regards
yarick123 -
Renato Botelho,
BTW, @Renato: the i386 snapshot builder is stuck YET again.
I have i386 platform and indeed there are no today's snapshots in https://snapshots.pfsense.org/FreeBSD_releng/10.1/i386/pfSense_RELENG_2_2/livecd_installer/ .
The latest i386 snapshot is dated 19-Nov-2015 18:49.
Regards
yarick123New snap will be available soon, logs can be followed at https://snapshots.pfsense.org/logs/pfSense_RELENG_2_2__FreeBSD_10/i386/build.log
-
I have tested the behaviour on pfSense 2.2.5 with lighttpd 1.4.38 from pfSense-LiveCD-2.2.6-DEVELOPMENT-i386-20151209-0736.iso.gz.
The problem does not reappear!
Regards
yarick123 -
Hi!
Any solution for this issue?
Thank you all!
-
Any solution for this issue?
May I suggest reading the thread before posting such questions?
-
And that's what I did :)
Since there is not a "Final" 2.2.6 I was asking if there was an official solution for the 2.2.5 ;)
-
The solution is to run 2.2.6 when 2.2.6 is released (or a snap if you can't wait)
I would not attempt to put pieces of 2.2.6 on 2.2.5 as was done previously in the thread.
-
After installing the version 2.2.6 the problem has gone!
Thank you for the great product!
Happy new year,
yarick123