Welcome to Pandora FMS Community!

Find answers, ask questions, and connect with our community around the world.

Welcome to Pandora FMS Community Forums Community support Problem with the 3.1 GUI on CentOS 5.3

  • Problem with the 3.1 GUI on CentOS 5.3

    Posted by CoolKoon on June 3, 2010 at 01:56

    Hi!

    I’m having a strange problem while trying to install the GUI. I’ve installed the server using the RPM correctly (after resolving all the dependencies). Then I wanted to proceed by installing the console package. Then did the problems begin. First I got this:

    [root@server60 ~]# rpm -ivh pandorafms_console-3.1rc1-1.1.noarch.rpm 
    warning: pandorafms_console-3.1rc1-1.1.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 155987ef
    error: Failed dependencies:
    	apache2 is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-gd is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-snmp is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-pear is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-json is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-gettext is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-mysql is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-ldap is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-mbstring is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5 is needed by pandorafms_console-3.1rc1-1.1.noarch
    	xorg-x11-fonts-core is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php5-pear-db is needed by pandorafms_console-3.1rc1-1.1.noarch
    	php-pear-xml_rpc is needed by pandorafms_console-3.1rc1-1.1.noarch
    [root@server60 ~]#
    

    The thing is, I DO have Apache2, but the package’s called “httpd” (version 2.2.3-22, to be precise). I also had most of the PHP modules the package’s been complaining about as well (including php5). The problem was also with their names (package “php” version 5.2.13-1 instead of package name “php5”, which applies to its modules as well).  After I’ve installed all dependencies but “xorg-x11-fonts-core” (which I’ve also downloaded and tried to install, but failed with some nasty error messages involving “rpmlib”), I’ve decided to proceed with the “–nodeps” option, which helped. The only warnings I got were a bunch (well, actually a LOT) of these:

    warning: group www does not exist - using root
    warning: user wwwrun does not exist - using root
    

    I presume this happened because the install script was expecting user “wwwrun” and group “www”, but I only got user/group “apache” instead. I also found out that the GUI has been installed into the /srv/www/htdocs/pandora_console folder (WTF?). That also stroke me as odd, since AFAIK /var/www/htdocs is the default Apache web folder as has been for years. Nevermind I thought, I’ve just made the appropriate changes in the Apache config (solved it wth an alias) and tried to install it. The problems have just escalated from here, as in the second step the script’s been complaining of missing “PEAR PHP Library”, “PEAR:DB PHP Library” and “PEAR::XML_RPC PHP Library”. So I’ve made sure that they’re installed, which they were. Yet the error persisted and the problem didn’t go away. Therefore I’ve forced my way through the rest of the setup. When finished however, I was greeted by the following message:

    PEAR::DB not found. Please install it with:
    
    pear install DB

    It’s needless to say that I ran the command numerous times before as well (when the errors in the setup wizard popped up) and afterwards as well. No luck. Then I stumbled upon a description of a similar error on this forum, but in the Spanish language part. It said something about trying to install the PEAR::DB using the “pear” command and/or via the package manager as well. I did that i.e. tried out all four combinations possible (uninstalling both, installing only via pear, then only via yum, then both), to no avail. Now unfortunately I wasn’t able to inquire about the problem in that topic, since I don’t speak Spanish (yet :P) and translated the whole thing using Google Translator (I wish the translations from my native language to English would be of the same quality as the ones from Spanish :S). Could you lend me a hand in this, please? It goes without saying that I wasn’t able to log in to the interface at all.

    rnovoa replied 14 years, 8 months ago 2 Members · 4 Replies
  • 4 Replies
  • rnovoa

    Member
    June 4, 2010 at 14:01
    0 Karma points
    Community rank: tentacle-noob-1 Tentacle noob
    Like it
    Up
    0
    Down
    Drop it
    ::

    Hi CoolKoon,

    Did you download the CentOS specific RPMs? The generic RPMs are just tested on openSUSE.

  • CoolKoon

    Member
    June 5, 2010 at 02:04
    0 Karma points
    Community rank: tentacle-noob-1 Tentacle noob
    Like it
    Up
    0
    Down
    Drop it
    ::

    Now that you’ve mentioned it, I’ve double-checked it and yes, I’ve downloaded the right package (meant for RedHat/CentOS and Fedora as well, I presume). This also gave me the idea  of trying the “generic” RPM as well. The results (read: dependency errors) were the same plus an rpmlib error: “rpmlib(PayloadIsLzma) <= 4.4.6-1 is needed by pandorafms_console-3.1rc1-1.noarch". So no luck with that either. Any other suggestions? Or additional info?

  • rnovoa

    Member
    June 8, 2010 at 15:15
    0 Karma points
    Community rank: tentacle-noob-1 Tentacle noob
    Like it
    Up
    0
    Down
    Drop it
    ::

    RedHat/CentOS RPMs were built using the SUSE build service, since only openSUSE RPMs are officially supported. That explains the different package names and paths, but I’m not sure about the pear errors. Do you have a DB.php after installing PEAR::DB?

  • CoolKoon

    Member
    June 8, 2010 at 17:58
    0 Karma points
    Community rank: tentacle-noob-1 Tentacle noob
    Like it
    Up
    0
    Down
    Drop it
    ::

    Yep. It’s in /usr/share/pear. Could this be a path issue or something?
    BTW I can’t say I care for the failed deps as long as the script works regardless (as it would, had it not been for this PEAR error).