Ad Widget

Collapse

Suse Packages

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • steveboyson
    Senior Member
    • Jul 2013
    • 582

    #1

    Suse Packages

    How comes that there is always an appliance available based on OpenSuse, but there are no SuSE RPM packages? Do you guys really want us to self-compile all the stuff?

    Please provide the RPMs you use to build/install the appliance! Thanks!
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    server:monitoring repository should provide rpms - please see https://build.opensuse.org/package/s...package=zabbix
    Zabbix 3.0 Network Monitoring book

    Comment

    • steveboyson
      Senior Member
      • Jul 2013
      • 582

      #3
      Thanks, richlv, I've found these already.

      Unfortunately they are 2.0.9 and not current (2.0.10 or 2.2.x). Is there any chance to get the "original" RPMs used for the appliance?

      Comment

      • richlv
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Oct 2005
        • 3112

        #4
        hmm... you can probably grab those from suse studio, but it might be somewhat complicated to migrate from those to more official ones later. you could ask user BManojlovic on irc about getting more up to date packages
        Zabbix 3.0 Network Monitoring book

        Comment

        • steveboyson
          Senior Member
          • Jul 2013
          • 582

          #5
          Thanks again, richlv!

          I was in the hope that these mentioned packages are "floating around" somewhere in the "Zabbix-Dev cloudspace" ;-)

          At least they need to come from $SOMEWHERE in order to be installed ...

          Comment

          • f.koch
            Member
            Zabbix Certified Specialist
            • Feb 2010
            • 85

            #6
            Hi,

            i have done a simple rebuild with 2.0.10
            http://download.opensuse.org/reposit...r:/monitoring/

            regards
            f.koch

            Comment

            • steveboyson
              Senior Member
              • Jul 2013
              • 582

              #7
              Hi f.koch,
              thank you very much, I will give them a try.
              May I ask about your build environment? I tried a test compile on a OpenSuse 12.3 VM and ran into errors while compiling zabbix_java.



              Code:
              opensuse:/usr/src/packages/BUILD/zabbix-2.0.10/src/zabbix_java # make
              /usr/bin/mkdir -p class/src
              /usr/bin/mkdir -p class/tests
              javac -d class/src -classpath lib/org-json-2010-12-28.jar:lib/logback-core-0.9.27.jar:lib/logback-classic-0.9.27.jar:lib/slf4j-api-1.6.1.jar src/com/zabbix/gateway/*.java
              src/com/zabbix/gateway/BinaryProtocolSpeaker.java:48: error: ZabbixException cannot be resolved to a type
                      public String getRequest() throws IOException, ZabbixException
                                                                     ^^^^^^^^^^^^^^^

              Comment

              • steveboyson
                Senior Member
                • Jul 2013
                • 582

                #8
                Yeah, my compile error is still there, also when using f.koch's src.rpm.

                Could it be that "javac" has to be the "original one" from Oracle and not gcc's javac?
                Anyone?

                Code:
                opensuse:/usr/src/packages/BUILD/zabbix-2.0.10/src/zabbix_java # javac -v
                Using built-in specs.
                Reading specs from /usr/lib64/gcc/x86_64-suse-linux/4.7/libgcj.spec
                rename spec startfile to startfileorig
                rename spec lib to liborig
                COLLECT_GCC=javac
                COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.7/lto-wrapper
                Target: x86_64-suse-linux
                Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,java --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7 --enable-ssp --disable-libssp --disable-libitm --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-java-home=/usr/lib64/jvm/java-1.5.0-gcj-4.7-1.5.0.0/jre --with-ecj-jar=/usr/lib64/gcc/x86_64-suse-linux/4.7/ecj.jar --disable-java-awt --disable-libjava-multilib --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --enable-linker-build-id --program-suffix=-4.7 --enable-linux-futex --without-system-libunwind --with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux
                Thread model: posix
                gcc version 4.7.2 20130108 [gcc-4_7-branch revision 195012] (SUSE Linux)

                Comment

                • f.koch
                  Member
                  Zabbix Certified Specialist
                  • Feb 2010
                  • 85

                  #9
                  Hi,

                  i used the obs (Opensuse Build Service), it do all the dirty building for you...., i only branched the "orginal" project, and bump the spec file to the new version.

                  regards f.koch

                  Comment

                  • steveboyson
                    Senior Member
                    • Jul 2013
                    • 582

                    #10
                    Ah, ok. Thank you nevertheless!

                    Comment

                    • steveboyson
                      Senior Member
                      • Jul 2013
                      • 582

                      #11
                      Originally posted by f.koch
                      Hi,

                      i used the obs (Opensuse Build Service), it do all the dirty building for you...., i only branched the "orginal" project, and bump the spec file to the new version.

                      regards f.koch
                      Interesting thing: in your packages, all files have "-" in the names while the original zabbix packages have "_" (underscore)

                      zabbix_agentd <=> zabbix-agentd
                      zabbix_server <=> zabbix-server
                      etc.

                      Seems to come from the SPEC file, there are a couple of 'sed' commands which rename files and patch configs ...

                      Comment

                      • richlv
                        Senior Member
                        Zabbix Certified Trainer
                        Zabbix Certified SpecialistZabbix Certified Professional
                        • Oct 2005
                        • 3112

                        #12
                        yep, suse guidelines talk about using a dash, so the packages try to adhere to those guidelines
                        Zabbix 3.0 Network Monitoring book

                        Comment

                        Working...