Ad Widget

Collapse

3.2 serious problems from 2.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ebonweaver
    Member
    • Feb 2013
    • 71

    #1

    3.2 serious problems from 2.4

    We just upgraded from 2.4 to 3.2 and see a LOT of issues that I'm frankly completely baffled by.

    Editing of Maps and screens appeared to be gone, and then I found them under monitoring. WHAT? That's a massive issue in many ways, and it violates permissions structure.
    1. Most important, how do I stop people with view only access from making things?? They should NOT be able to make maps, screens, slideshows or anything else, they are to view only, not have any ability to create!
    2. I can no longer view and edit a map at the same time? Downgrade. Previously I could have two browser tabs open, one monitoring a map, the other configuring the map, and flip between for easy editing.
    3. Where is my easy clean drop down menu for viewing maps and screens? Now it's a big list with details that shouldn't be there because again it's a creation screen instead of a viewing screen.
    Given it seems that permissions STILL only exist at the host group level and not at any UI level, this is a serious problem and an extremely bad redesign...

    People with view access STILL can't see the Discovery tab. Unbelievable. This has been a useless feature since creation because non one but admins can see it. This combined with the previous issue is frankly maddening.

    The server itself seems to no longer monitor its own CPU, memory, and network use. The other graphs still work and report all the processes. How to restore monitoring the basic server stats?

    Looks like all the Actions inverted their status... enabled are disabled, disabled are enabled... annoying to say the least, but at least a clear fix...

    It appears maintenance windows wiped out entirely. Again, annoying, but seems straight forward enough to rebuild...
  • linzhiguo
    Junior Member
    • Mar 2017
    • 2

    #2
    Zabbix_proxy3.2 encountered a crash

    I don't know how to deal with this situation, I need help!
    Here is my error message


    2843:20170315:000438.109 3ed580a000-3ed5a09000 ---p 0000a000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2840:20170315:000438.110 3ed580a000-3ed5a09000 ---p 0000a000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2793:20170315:000438.110 3ed4fdf000-3ed4fe3000 rw-p 00000000 00:00 0
    2770:20170315:000438.110 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2774:20170315:000438.110 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2842:20170315:000438.110 3ed580a000-3ed5a09000 ---p 0000a000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2778:20170315:000438.110 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2803:20170315:000438.110 3ed5601000-3ed5602000 r--p 00001000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2838:20170315:000438.110 3ed580a000-3ed5a09000 ---p 0000a000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2753:20170315:000438.110 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2779:20170315:000438.110 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2849:20170315:000438.110 3ed580a000-3ed5a09000 ---p 0000a000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2762:20170315:000438.111 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2818:20170315:000438.111 3ed5601000-3ed5602000 r--p 00001000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2782:20170315:000438.111 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2765:20170315:000438.111 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2772:20170315:000438.114 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    2744:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2725:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2724:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2742:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2736:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2738:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2740:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2755:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2757:20170315:000438.115 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2731:20170315:000438.116 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2813:20170315:000438.116 3ed4fb8000-3ed4fd3000 r--p 001b8000 fd:01 42152 /usr/lib64/libcrypto.so.1.0.1e
    2730:20170315:000438.116 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2751:20170315:000438.116 3ed5800000-3ed580a000 r-xp 00000000 fd:01 42147 /lib64/libkrb5support.so.0.1
    2773:20170315:000438.116 3ed5602000-3ed5603000 rw-p 00002000 fd:01 14808 /lib64/libkeyutils.so.1.3
    "/var/log/zabbix/zabbix_proxy.log" 3251L, 376102C
    2769:20170315:000438.421 ================================
    2747:20170315:000438.422 Please consider attaching a disassembly listing to your bug report.
    2761:20170315:000438.423 ================================
    2764:20170315:000438.423 ================================
    2810:20170315:000438.424 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2781:20170315:000438.424 ================================
    2795:20170315:000438.426 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2800:20170315:000438.426 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2804:20170315:000438.427 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2776:20170315:000438.428 ================================
    2792:20170315:000438.428 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2790:20170315:000438.429 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2791:20170315:000438.431 ================================
    2763:20170315:000438.431 Please consider attaching a disassembly listing to your bug report.
    2794:20170315:000438.432 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
    2733:20170315:000438.433 This listing can be produced with, e.g., objdump -DSswx zabbix_proxy.
    2726:20170315:000438.433 This listing can be produced with, e.g., objdump -DSswx zabbix_proxy.
    2785:20170315:000438.434 Please consider attaching a disassembly listing to your bug report.
    2767:20170315:000438.435 Please consider attaching a disassembly listing to your bug report.
    2787:20170315:000438.436 Please consider attaching a disassembly listing to your bug report.
    2799:20170315:000438.437 ================================
    2801:20170315:000438.437 7fff4fbff000-7fff4fc00000 r-xp 00000000 00:00 0 [vdso]
    2771:20170315:000438.437 Please consider attaching a disassembly listing to your bug report.
    2777:20170315:000438.438 ================================
    2793:20170315:000438.439 7f4bcf109000-7f4bcf120000 rw-s 00000000 00:04 131076 /SYSV53010c1e (deleted)
    2770:20170315:000438.440 Please consider attaching a disassembly listing to your bug report.
    2774:20170315:000438.441 Please consider attaching a disassembly listing to your bug report.
    2778:20170315:000438.441 Please consider attaching a disassembly listing to your bug report.
    2224:20170315:000440.328 syncing history data...
    2224:20170315:000440.335 syncing history data done
    2224:20170315:000440.335 Zabbix Proxy stopped. Zabbix 3.2.1 (revision 62890).

    Comment

    • andresf
      Junior Member
      • Jan 2017
      • 16

      #3
      I've just starting to use it in version 3.2.4

      Originally posted by ebonweaver
      The server itself seems to no longer monitor its own CPU, memory, and network use. The other graphs still work and report all the processes. How to restore monitoring the basic server stats?
      You have to install the agent on the server to gather server metrics, it's not by default.

      Comment

      Working...