Nothing I'm aware of 😃

host -va osticket.com
Trying "osticket.com"
Trying "osticket.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8835
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;osticket.com. IN ANY

;; ANSWER SECTION:
osticket.com. 3600 IN SPF "v=spf1 include:spf.osticket.co m include:spf.supportsystem.com include:spf.google.com include:amazonses.com - all"
osticket.com. 3600 IN TXT "v=spf1 include:spf.osticket.co m include:spf.supportsystem.com include:spf.google.com include:amazonses.com ~ all"
osticket.com. 43200 IN MX 40 aspmx2.googlemail.com.
osticket.com. 43200 IN MX 30 alt2.aspmx.l.google.com.
osticket.com. 43200 IN MX 20 alt1.aspmx.l.google.com.
osticket.com. 43200 IN MX 50 aspmx3.googlemail.com.
osticket.com. 43200 IN MX 10 aspmx.l.google.com.
osticket.com. 3600 IN SOA ns-1179.awsdns-19.org. awsdns-ho stmaster.amazon.com. 1 7200 900 1209600 86400
osticket.com. 3600 IN NS ns-970.awsdns-57.net.
osticket.com. 3600 IN NS ns-336.awsdns-42.com.
osticket.com. 3600 IN NS ns-1179.awsdns-19.org.
osticket.com. 3600 IN NS ns-1606.awsdns-08.co.uk.
osticket.com. 43200 IN A 96.126.117.188

Received 628 bytes from 127.0.0.53#53 in 7 ms

    deltabis_mk

    So I just downloaded the Polish language pack, installed it, set it as my Primary Language for the system, and cannot replicate this error. It seems you are having some sort of DNS issues.

    Cheers.

      deltabis_mk

      Sure, run this via command line:

      php -r '$phar = new Phar("/path/to/osticket/include/i18n/pl.phar"); var_dump($phar->getSignature());'

      That should output an array of hash (should be the SHA-1 hash) and hash_type (should be SHA-1).

      Cheers.

        So it appears I have a problem with generating signature 🙁 Any ideas?

        php -r '$phar = new Phar("/var/www/html/support/include/i18n/pl.phar"); var_dump($phar->getSignature());'
        PHP Fatal error: Uncaught UnexpectedValueException: phar "/var/www/html/support/include/i18n/pl.phar" SHA1 signature could not be verified: broken signature in Command line code:1
        Stack trace:
        #0 Command line code(1): Phar->__construct()
        #1 {main}
        thrown in Command line code on line 1

          deltabis_mk

          It seems your file got corrupted somehow. Download a fresh version of the language pack from the website, install that one, and retest.

          Cheers.

              Ok, I have a fresh version. Now I can check SHA-1 hash
              php -r '$phar = new Phar("/var/www/html/support/include/i18n/pl.phar"); var_dump($phar->getSignature());'
              array(2) {
              ["hash"]=>
              string(40) "28C63957F3FA0CA29271B45C60CBAAE646AA4369"
              ["hash_type"]=>
              string(5) "SHA-1"
              }
              But the problem is stil unresolved.
              After enabling display errors in bootstrap.php I have this:

              Fatal error: Uncaught ValueError: Path cannot be empty in /var/www/html/support/include/class.translation.php:568 Stack trace: #0 /var/www/html/support/include/class.translation.php(352): Translation->load_tables() #1 /var/www/html/support/include/class.translation.php(380): gettext_reader->get_plural_forms() #2 /var/www/html/support/include/class.translation.php(414): gettext_reader->select_string() #3 /var/www/html/support/include/class.i18n.php(576): gettext_reader->ngettext() #4 /var/www/html/support/include/staff/helptopics.inc.php(9): _N() #5 /var/www/html/support/scp/helptopics.php(246): require('...') #6 {main} thrown in /var/www/html/support/include/class.translation.php on line 568

                deltabis_mk

                The stream is empty so that most likely means permission/ownership issues or something of that nature. Basically it can’t read the contents of the PHAR file.

                Cheers.

                  7 days later

                  KevinTheJedi
                  after some research - it looks like SELinux is responsible for the problem. Any ideas how to stay with SELinux and language pack?

                      5 days later

                      So it looks like a SELinux bug in Fedora Core 36. After the last system update, this problem disappeared.
                      Thanks for your help.

                      Write a Reply...