Ad Widget

Collapse

Configuration file error on frontend after Ubuntu update from 14.04 to 16.04

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Valelinn
    Junior Member
    • Feb 2018
    • 8

    #1

    Configuration file error on frontend after Ubuntu update from 14.04 to 16.04

    Hello,

    I'm working in a DEV environment for the Zabbix server which is running on Ubuntu 14.04.5 LTS and Zabbix 3.0.14. The DEV server was working properly until I updated to Ubuntu 16.04.3 LTS. After the update, the frontend displays the following message:

    Configuration file error
    DB type "POSTGRESQL" is not supported by current setup.


    I've checked the zabbix.conf.php file, and is identical to the file running on the (functioning) production server. I've also changer the php version from 7.X to 5.6.33.

    I tried running the Zabbix update procedure as outlined in the documentation but that didn't solve the issue either.

    I'm hoping that someone would be able to provide a suggestion for hat the issue may be and how to resolve it.

    Thank you.
  • volter
    Member
    Zabbix Certified Specialist
    • Dec 2011
    • 85

    #2
    That sounds like you are missing the postgresql php module.

    Comment

    • MR_Andrew
      Junior Member
      • Dec 2015
      • 27

      #3
      Hello!
      Totally the same issue.

      Now running Zabbix 3.0.14 LTS (recently successfully updated from 2.2.11) on Ubuntu 14.04.5 LTS.

      I was made a clone of production server, all tests proceed on test server.

      Task - update Ubuntu 14 to 16.
      And the same problem with only 1 difference - I have MySQL.
      Downgraded PHP from 7 to 5.6 by this guide: How can I downgrade from PHP 7 to PHP 5.6 on Ubuntu 16.04? [duplicate] No results. But one more thing. When I downgrade PHP from 7 to 5.6 on Zabbix 3.0 running - frontend started to work, but dashboard had a lot or errors like "unsupported module". Only little part of interface was good, most part - errors. Updating Zabbix to 3.4 destroy all frontend in total.

      Found that Zabbix server do not starting automatically after reboot. Execute "update-rc.d zabbix-server enable" - looks like works.
      Also, had error described here: https://www.zabbix.com/forum/showthread.php?t=54581
      Looks like fixed. But main problem not solved - no frontend.
      Trying upgrade version of Zabbix from 3.0 to 3.4 with hope that this will overwrite configs and fix errors. Upgraded, now I have Zabbix 3.4.7 but no frontend the same.

      Trying to access - "HTTP 500 Internal Server Error"

      Also, trying to reinstall zabbix:
      Code:
       apt-get install --reinstall zabbix-server-mysql zabbix-frontend-php
      No result. No frontend.

      At this moment, after a big part of manipulations, Zabbix server log is good:

      Code:
       4688:20180304:223938.660 Starting Zabbix Server. Zabbix 3.4.7 (revision 77720).
        4688:20180304:223938.661 ****** Enabled features ******
        4688:20180304:223938.661 SNMP monitoring:           YES
        4688:20180304:223938.661 IPMI monitoring:           YES
        4688:20180304:223938.661 Web monitoring:            YES
        4688:20180304:223938.661 VMware monitoring:         YES
        4688:20180304:223938.661 SMTP authentication:       YES
        4688:20180304:223938.661 Jabber notifications:      YES
        4688:20180304:223938.661 Ez Texting notifications:  YES
        4688:20180304:223938.662 ODBC:                      YES
        4688:20180304:223938.662 SSH2 support:              YES
        4688:20180304:223938.662 IPv6 support:              YES
        4688:20180304:223938.662 TLS support:               YES
        4688:20180304:223938.662 ******************************
        4688:20180304:223938.662 using configuration file: /etc/zabbix/zabbix_server.conf
        4688:20180304:223938.679 current database version (mandatory/optional): 03040000/03040006
        4688:20180304:223938.679 required mandatory version: 03040000
        4688:20180304:223941.570 server #0 started [main process]
        4690:20180304:223941.574 server #1 started [configuration syncer #1]
        4691:20180304:223941.578 server #2 started [alerter #1]
        4692:20180304:223941.582 server #3 started [alerter #2]
        4693:20180304:223941.585 server #4 started [alerter #3]
        4694:20180304:223941.591 server #5 started [housekeeper #1]
        4695:20180304:223941.594 server #6 started [timer #1]
        4697:20180304:223941.599 server #8 started [discoverer #1]
        4696:20180304:223941.604 server #7 started [http poller #1]
        4698:20180304:223941.613 server #9 started [history syncer #1]
        4699:20180304:223941.618 server #10 started [history syncer #2]
        4706:20180304:223941.621 server #17 started [vmware collector #2]
        4707:20180304:223941.629 server #18 started [task manager #1]
        4700:20180304:223941.633 server #11 started [history syncer #3]
        4701:20180304:223941.636 server #12 started [history syncer #4]
        4702:20180304:223941.641 server #13 started [escalator #1]
        4703:20180304:223941.645 server #14 started [proxy poller #1]
        4704:20180304:223941.649 server #15 started [self-monitoring #1]
        4705:20180304:223941.651 server #16 started [vmware collector #1]
        4708:20180304:223941.654 server #19 started [poller #1]
        4709:20180304:223941.666 server #20 started [poller #2]
        4710:20180304:223941.669 server #21 started [poller #3]
        4711:20180304:223941.673 server #22 started [poller #4]
        4712:20180304:223941.685 server #23 started [poller #5]
        4713:20180304:223941.690 server #24 started [poller #6]
        4714:20180304:223941.693 server #25 started [poller #7]
        4715:20180304:223941.706 server #26 started [poller #8]
        4716:20180304:223941.714 server #27 started [poller #9]
        4718:20180304:223941.742 server #29 started [poller #11]
        4717:20180304:223941.761 server #28 started [poller #10]
        4719:20180304:223941.786 server #30 started [poller #12]
        4720:20180304:223941.814 server #31 started [poller #13]
        4721:20180304:223941.841 server #32 started [poller #14]
        4722:20180304:223941.850 server #33 started [poller #15]
        4723:20180304:223941.861 server #34 started [poller #16]
        4724:20180304:223941.898 server #35 started [poller #17]
        4726:20180304:223941.934 server #37 started [unreachable poller #1]
        4725:20180304:223941.938 server #36 started [poller #18]
        4728:20180304:223941.978 server #39 started [unreachable poller #3]
        4727:20180304:223942.017 server #38 started [unreachable poller #2]
        4729:20180304:223942.026 server #40 started [unreachable poller #4]
        4731:20180304:223942.074 server #42 started [trapper #1]
        4730:20180304:223942.090 server #41 started [unreachable poller #5]
        4732:20180304:223942.150 server #43 started [trapper #2]
        4734:20180304:223942.205 server #45 started [trapper #4]
        4733:20180304:223942.237 server #44 started [trapper #3]
        4736:20180304:223942.358 server #47 started [icmp pinger #1]
        4735:20180304:223942.360 server #46 started [trapper #5]
        4737:20180304:223942.365 server #48 started [icmp pinger #2]
        4738:20180304:223942.370 server #49 started [icmp pinger #3]
        4739:20180304:223942.406 server #50 started [icmp pinger #4]
        4740:20180304:223942.438 server #51 started [icmp pinger #5]
        4742:20180304:223942.498 server #52 started [icmp pinger #6]
        4743:20180304:223942.502 server #53 started [alert manager #1]
        4745:20180304:223942.586 server #54 started [preprocessing manager #1]
        4748:20180304:223943.095 server #57 started [preprocessing worker #3]
        4747:20180304:223943.119 server #56 started [preprocessing worker #2]
        4746:20180304:223943.131 server #55 started [preprocessing worker #1]
      Please, can anybody help me with frontend problem?
      Thanks!

      Comment

      • huangyingja
        Junior Member
        • Apr 2015
        • 27

        #4
        Trying to access - "HTTP 500 Internal Server Error"
        please check apache2 or nginx logs ,
        should be miss some php module

        Comment

        • MR_Andrew
          Junior Member
          • Dec 2015
          • 27

          #5
          Originally posted by huangyingja
          Trying to access - "HTTP 500 Internal Server Error"
          please check apache2 or nginx logs ,
          should be miss some php module
          Hello!
          Thanks for your reply!

          Maybe it's possible to "freeze" some modules updating for Ubuntu? Just update system only, without MySQL/php/apache/etc. Needed components Zabbix will update itself..
          Thanks!

          Comment

          • huangyingja
            Junior Member
            • Apr 2015
            • 27

            #6
            should be php had been upgrade to new version.

            Comment

            Working...