Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 516 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

8.102 Postgres bug?

stimmerman
Hi all,

Just upgraded a new 220 from 8.01 to 8.102 with automatic up2date. Device is up and running again, but this appears constantly in the system log: 

2011:02:14-20:00:29 firewall ulogd[4452]: pg1: connect: FATAL: database locale is incompatible with operating system

2011:02:14-20:00:29 firewall postgres[22819]: [2-1] FATAL: database locale is incompatible with operating system

2011:02:14-20:00:29 firewall postgres[22819]: [2-2] DETAIL: The database was initialized with LC_CTYPE "en_US.UTF-8", which is not recognized by setlocale().

2011:02:14-20:00:29 firewall postgres[22819]: [2-3] HINT: Recreate the database with another locale or install the missing locale. 


Since the device is not in production yet, I can't tell if something is broken. Looks a bit serious though.

Best regards,
Sander


This thread was automatically locked due to age.
Parents
  • 0
    Hmm.. that is interesting... I've updates several units (test bed units, etc.) with the 8.102 update and have not seen that error (I just checked)...

    Under Web Security, Advanced, in Webadmin on your ASG... what is the "Default charset" set to?  The ones I've looked at (that are working fine) are set to "iso-8859-1"  (BTW, might have nothing to do with it, but it's the only place I know of where a user can specify character sets / locales .. you might just have a corrupt DB).

    You may want to start a support ticket with Astaro if the problem persists.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • 0
    Hmm.. that is interesting... I've updates several units (test bed units, etc.) with the 8.102 update and have not seen that error (I just checked)...

    Under Web Security, Advanced, in Webadmin on your ASG... what is the "Default charset" set to?  The ones I've looked at (that are working fine) are set to "iso-8859-1"  (BTW, might have nothing to do with it, but it's the only place I know of where a user can specify character sets / locales .. you might just have a corrupt DB).

    You may want to start a support ticket with Astaro if the problem persists.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
No Data
Cookie Information Banner