Problems after upgrade 2.2.4 to 2.2.5

[uaxero]

sorry It meant that a check of pfsense server hosted on one esx vmware server has not shown errors

[Gertjan]

@borbelyb:

Bla bla bla . Error message: disk I/O error. rhon rhon rhon

If everybody starts posting about their hardware problems (or other, related issues like "disk full" (which will be communicated as a "disk I/O error")) pfsense should open a new forum …. I propose calling it "/etc/null"

edit : On the other hand: "Error message: database is locked." is less funny ....

[nongshin]

I also have the same problem after upgrading to 2.2.5 (From both upgrade and new installation).
And I don't think it is from I/O problem.


[borbelyb]

@Gertjan:

@borbelyb:

Bla bla bla . Error message: disk I/O error. rhon rhon rhon

If everybody starts posting about their hardware problems (or other, related issues like "disk full" (which will be communicated as a "disk I/O error")) pfsense should open a new forum …. I propose calling it "/etc/null"

edit : On the other hand: "Error message: database is locked." is less funny ....

Thank you for your "kind" reply. I've tested this on the server's CARP pair, and after a few hours I got the same error. On completely different hardware. This is clearly not a hardware issue.

[Gertjan]

It becomes clear (as far as I can count 4 users who post about these "Error message: disk I/O error. / Error message: database is locked") very recently.

You will find a thread were a test is going on : putting the database file on a RAM disk - not the drive.
https://forum.pfsense.org/index.php?topic=103732.0
https://forum.pfsense.org/index.php?topic=103707.0

Agreed, this might not be a hardware issue, but it's not a pure software (pfsense) issue neither. Otherwise, it would show up for every one (tens of thousands) who uses the Captive Portal.

[cmb]

Probably related to this.
https://redmine.pfsense.org/issues/5622

which we're looking into.

[mogaeng]

Dear all
I have the same problem after upgrade from 2.2.4 to 2.2.5 :-\

[Gertjan]

Look also here https://forum.pfsense.org/index.php?topic=103732.new;topicseen#new

[cmb]

Those who are seeing this issue, please try the newest available 2.2.6 snapshot and report back. It looks to be fixed, but I would like additional confirmation.
64 bit
https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_RELENG_2_2/updates/?C=M;O=D

32 bit
https://snapshots.pfsense.org/FreeBSD_releng/10.1/i386/pfSense_RELENG_2_2/updates/?C=M;O=D

[uaxero]

apparently now is working fine.

after of 14 days any restart of database.

thanks