Ad Widget

Collapse

zabbix database error connection refused when accessing login page

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #16
    That looks pretty good, but a way you can verify before rebooting is do this:

    Code:
    mount /var/lib/mysql
    df -h
    See what it says for size and available space now, after the xfs_growfs. It should show some free space now, rather than what it was showing earlier.

    Comment

    • pgp82
      Junior Member
      • Nov 2020
      • 23

      #17
      Originally posted by tim.mooney
      That looks pretty good, but a way you can verify before rebooting is do this:

      Code:
      mount /var/lib/mysql
      df -h
      See what it says for size and available space now, after the xfs_growfs. It should show some free space now, rather than what it was showing earlier.
      See below, still says 100%? I really don't get this

      [root@appliance ~]# df -h
      Filesystem Size Used Avail Use% Mounted on
      devtmpfs 3.9G 0 3.9G 0% /dev
      tmpfs 3.9G 0 3.9G 0% /dev/shm
      tmpfs 3.9G 8.5M 3.9G 1% /run
      tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
      /dev/sda2 4.0G 1002M 3.1G 25% /
      /dev/sda3 1014M 40M 975M 4% /tmp
      /dev/sda1 488M 80M 373M 18% /boot
      tmpfs 787M 0 787M 0% /run/user/0
      /dev/sda5 4.5G 4.5G 20K 100% /var/lib/mysql

      Comment

      • tim.mooney
        Senior Member
        • Dec 2012
        • 1427

        #18
        Yeah, something with the filesystem resize didn't work. So, you've successfully resized the partition (that part's done), now we just need to figure out what the problem is with resizing the filesystem.

        I'm going to do some reading with 'xfs_growfs' and see if I can spot what the issue might be.

        For now, you can reboot your VM appliance. We haven't fixed the problem yet (you're still out of space in the critical mysql partition), but you've made progress.

        Also, the most difficult/dangerous part is done. If you need to, you could remove the snapshot. It was mainly in case there was a problem with parted, and that part is done.

        Comment

        • pgp82
          Junior Member
          • Nov 2020
          • 23

          #19
          Originally posted by tim.mooney
          Yeah, something with the filesystem resize didn't work. So, you've successfully resized the partition (that part's done), now we just need to figure out what the problem is with resizing the filesystem.

          I'm going to do some reading with 'xfs_growfs' and see if I can spot what the issue might be.

          For now, you can reboot your VM appliance. We haven't fixed the problem yet (you're still out of space in the critical mysql partition), but you've made progress.

          Also, the most difficult/dangerous part is done. If you need to, you could remove the snapshot. It was mainly in case there was a problem with parted, and that part is done.
          ok thank you. I will reboot for now. Really appreciate your help so far. Hopefully can get it sorted.

          Comment

          • tim.mooney
            Senior Member
            • Dec 2012
            • 1427

            #20
            It might be that two of the online guides I looked at both had typos in them. Try this:

            Code:
            xfs_growfs -d /var/lib/mysql

            Comment

            • pgp82
              Junior Member
              • Nov 2020
              • 23

              #21
              Originally posted by tim.mooney
              It might be that two of the online guides I looked at both had typos in them. Try this:

              Code:
              xfs_growfs -d /var/lib/mysql
              Sorry tim.mooney I don't think that worked either. See the output below.

              Code:
              [root@appliance ~]# xfs_growfs -d /var/lib/mysql
              meta-data=/dev/sda5 isize=512 agcount=4, agsize=294784 blks
              = sectsz=512 attr=2, projid32bit=1
              = crc=1 finobt=1, sparse=1, rmapbt=0
              = reflink=1
              data = bsize=4096 blocks=1179136, imaxpct=25
              = sunit=0 swidth=0 blks
              naming =version 2 bsize=4096 ascii-ci=0, ftype=1
              log =internal log bsize=4096 blocks=2560, version=2
              = sectsz=512 sunit=0 blks, lazy-count=1
              realtime =none extsz=4096 blocks=0, rtextents=0
              data size unchanged, skipping
              Code:
              [root@appliance ~]# df -h
              Filesystem Size Used Avail Use% Mounted on
              devtmpfs 3.9G 0 3.9G 0% /dev
              tmpfs 3.9G 0 3.9G 0% /dev/shm
              tmpfs 3.9G 8.5M 3.9G 1% /run
              tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
              /dev/sda2 4.0G 1003M 3.1G 25% /
              /dev/sda3 1014M 40M 975M 4% /tmp
              /dev/sda1 488M 80M 373M 18% /boot
              /dev/sda5 4.5G 4.5G 20K 100% /var/lib/mysql
              tmpfs 787M 0 787M 0% /run/user/0
              [root@appliance ~]#

              Comment

              • tim.mooney
                Senior Member
                • Dec 2012
                • 1427

                #22
                Yeah, the "data size unchanged, skipping" is xfs_growfs saying it's not doing anything.

                So looking back through the thread, I'm now pretty suspicious that the 'parted' resize did not work, and that's why you're having the trouble with 'xfs_growfs'.

                The "Size" column for sda4 and sda5 both show them as still only about 4.5 GiB in size, which means that 'parted' hasn't done what's needed yet.

                Comment

                • pgp82
                  Junior Member
                  • Nov 2020
                  • 23

                  #23
                  Originally posted by tim.mooney
                  Yeah, the "data size unchanged, skipping" is xfs_growfs saying it's not doing anything.

                  So looking back through the thread, I'm now pretty suspicious that the 'parted' resize did not work, and that's why you're having the trouble with 'xfs_growfs'.

                  The "Size" column for sda4 and sda5 both show them as still only about 4.5 GiB in size, which means that 'parted' hasn't done what's needed yet.
                  Do you think if I re-run parted commands it will work? or there is no simple solution here?

                  Comment

                  • pgp82
                    Junior Member
                    • Nov 2020
                    • 23

                    #24
                    also looking at the structure, do you think I need to run parted in partition 4?

                    Code:
                    [root@appliance ~]# ldbsk
                    -bash: ldbsk: command not found
                    [root@appliance ~]# lsblk
                    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
                    sda 8:0 0 30G 0 disk
                    ├─sda1 8:1 0 512M 0 part /boot
                    ├─sda2 8:2 0 4G 0 part /
                    ├─sda3 8:3 0 1G 0 part /tmp
                    ├─sda4 8:4 0 1K 0 part
                    └─sda5 8:5 0 4.5G 0 part /var/lib/mysql
                    sr0 11:0 1 1024M 0 rom
                    Code:
                    [root@appliance ~]# df -l
                    Filesystem 1K-blocks Used Available Use% Mounted on
                    devtmpfs 3990932 0 3990932 0% /dev
                    tmpfs 4025304 0 4025304 0% /dev/shm
                    tmpfs 4025304 8620 4016684 1% /run
                    tmpfs 4025304 0 4025304 0% /sys/fs/cgroup
                    /dev/sda2 4184064 1026396 3157668 25% /
                    /dev/sda3 1038336 40424 997912 4% /tmp
                    /dev/sda1 499656 81168 381792 18% /boot
                    /dev/sda5 4706304 4706284 20 100% /var/lib/mysql
                    tmpfs 805060 0 805060 0% /run/user/0
                    Code:
                    [root@appliance ~]# parted -l /dev/sda
                    Model: Msft Virtual Disk (scsi)
                    Disk /dev/sda: 32.2GB
                    Sector size (logical/physical): 512B/512B
                    Partition Table: msdos
                    Disk Flags:
                    
                    Number Start End Size Type File system Flags
                    1 1049kB 538MB 537MB primary ext4 boot
                    2 538MB 4833MB 4295MB primary xfs
                    3 4833MB 5907MB 1074MB primary xfs
                    4 5907MB 10.7GB 4831MB extended
                    5 5908MB 10.7GB 4830MB logical xfs

                    Comment

                    • tim.mooney
                      Senior Member
                      • Dec 2012
                      • 1427

                      #25
                      Extending the appliance size was discussed in another recent thread that I was also part of, and the procedure worked there: https://www.zabbix.com/forum/zabbix-...e-hyper-v-2012

                      How much did you increase the virtual disk by in your hypervisor, and are you certain that procedure worked?

                      Comment

                      • pgp82
                        Junior Member
                        • Nov 2020
                        • 23

                        #26
                        Originally posted by tim.mooney
                        Extending the appliance size was discussed in another recent thread that I was also part of, and the procedure worked there: https://www.zabbix.com/forum/zabbix-...e-hyper-v-2012

                        How much did you increase the virtual disk by in your hypervisor, and are you certain that procedure worked?
                        I increased the virtual disk to be 30GB. Should I increase it more? also I wonder if the parted was run in partition 4 rather 5 which in my case ran against 5.
                        Last edited by pgp82; 02-12-2020, 23:26.

                        Comment

                        • pgp82
                          Junior Member
                          • Nov 2020
                          • 23

                          #27
                          Also when I run fdisk -l, size is still shown as 4.5GB. Should I be seeing the size I see when I run parted --> print command?

                          Code:
                          [root@appliance ~]# fdisk -l
                          Disk /dev/sda: 30 GiB, 32212254720 bytes, 62914560 sectors
                          Units: sectors of 1 * 512 = 512 bytes
                          Sector size (logical/physical): 512 bytes / 512 bytes
                          I/O size (minimum/optimal): 512 bytes / 512 bytes
                          Disklabel type: dos
                          Disk identifier: 0xf8386911
                          
                          Device Boot Start End Sectors Size Id Type
                          /dev/sda1 * 2048 1050623 1048576 512M 83 Linux
                          /dev/sda2 1050624 9439231 8388608 4G 83 Linux
                          /dev/sda3 9439232 11536383 2097152 1G 83 Linux
                          /dev/sda4 11536384 20971519 9435136 4.5G 5 Extended
                          /dev/sda5 11538432 20971519 9433088 4.5G 83 Linux
                          Code:
                          [root@appliance ~]# parted
                          GNU Parted 3.2
                          Using /dev/sda
                          Welcome to GNU Parted! Type 'help' to view a list of commands.
                          (parted) print
                          Model: Msft Virtual Disk (scsi)
                          Disk /dev/sda: 32.2GB
                          Sector size (logical/physical): 512B/512B
                          Partition Table: msdos
                          Disk Flags:
                          
                          Number Start End Size Type File system Flags
                          1 1049kB 538MB 537MB primary ext4 boot
                          2 538MB 4833MB 4295MB primary xfs
                          3 4833MB 5907MB 1074MB primary xfs
                          4 5907MB 10.7GB 4831MB extended
                          5 5908MB 10.7GB 4830MB logical xfs

                          Comment

                          • tim.mooney
                            Senior Member
                            • Dec 2012
                            • 1427

                            #28
                            fdisk and parted are likely saying the same thing, they're just using different units. Try using the "unit s" command with 'parted' to get it to display in units of sectors, so you can compare with the output from fdisk.

                            Comment

                            • pgp82
                              Junior Member
                              • Nov 2020
                              • 23

                              #29
                              Originally posted by tim.mooney
                              fdisk and parted are likely saying the same thing, they're just using different units. Try using the "unit s" command with 'parted' to get it to display in units of sectors, so you can compare with the output from fdisk.
                              Code:
                              (parted) unit s
                              (parted) print
                              Model: Msft Virtual Disk (scsi)
                              Disk /dev/sda: 62914560s
                              Sector size (logical/physical): 512B/512B
                              Partition Table: msdos
                              Disk Flags:
                              
                              Number Start End Size Type File system Flags
                              1 2048s 1050623s 1048576s primary ext4 boot
                              2 1050624s 9439231s 8388608s primary xfs
                              3 9439232s 11536383s 2097152s primary xfs
                              4 11536384s 20971519s 9435136s extended
                              5 11538432s 20971519s 9433088s logical xfs
                              looks ok? I don't really understand why my sda5 partition won't grow

                              Comment

                              • pgp82
                                Junior Member
                                • Nov 2020
                                • 23

                                #30
                                hi tim.mooney I have managed to fix my issue by using gparted iso. Had to to resize/move both sda4 and sda5 using that tool. After that it was all good. Now showing mysql using only 14% of the disk space.


                                Comment

                                Working...