Imperva Cyber Community

communities_1.jpg
 View Only

  • 1.  management-server not running

    Posted 06-09-2021 13:39
    Hello everyone,

    Hope you are doing well :)
    I was wondering if anyone has came across the following error on the Management Server:


    This is a MX as a lab setup, therefore I can't open a support ticket. The filesystem /dev/mapper/sysvg-root.vol was 100% used and I deleted some temp files to free the space.

    When I try to start the management-server service, it says there is already a process trying to start.

    I tried reboot-ing several times, however the service still does not start.

    Is there something else I can do?

    Any feedback is much appreciated,

    Best regards
    #On-PremisesWAF(formerlySecuresphere)

    ------------------------------
    Edvin Fiku
    System Engineer
    S&T Albania
    Tirane
    ------------------------------


  • 2.  RE: management-server not running

    Posted 06-10-2021 12:31
    do you have a previous backup? so you can delete and import the backup.

    ------------------------------
    Andres Moore
    Globant
    ------------------------------

    Original Message


  • 3.  RE: management-server not running

    Posted 06-16-2021 05:43
    In this state, you should still get full backup from MX to restore on newly deployed MX (with the same version of problematic one) if this is applicable solution.

    ------------------------------
    Cezmi Cal
    technical support engineer
    Barikat Cyber Security
    Ankara
    ------------------------------

    Original Message


  • 4.  RE: management-server not running

    Posted 06-23-2021 16:43
    Edited by Shantanu Chaurasia 06-23-2021 16:47
    You'll have to delete mutex first. Follow this article to free mutex. Then try starting after that.
    https://docs.imperva.com/howto/7dcd29be


  • 5.  RE: management-server not running

    Posted 12-20-2022 15:05
    Usually this problem happens when using nfs action set in mx. Because when there is problem with nfs connection; It keeps files on mx that it cannot send with nfs.
    As a result, if you follow the steps below, the problem will be solved.
    For example: mount directory path "/mnt/backup/"
    1. take a snapshot before operation.
    2. login with root user.
    3. "umount /mnt/backup/"
    4. create a directory under to "/var" 
    For example: the new directory path "/var/tmp/imperva/"
    5. "mkdir /var/tmpimperva"
    6. "chmod +x /var/tmpimperva"
    7. "chmod +x /mnt/backup/"
    8. "mv /mnt/backup/ /var/tmpimperva"
    9. "impctl restart"


    ------------------------------
    Ulku Erdem Kaya
    Senior Security Technologies Specialist
    Barikat Sistem Bilisim Teknolojileri Tic. A.S.
    Ankara
    ------------------------------

    Original Message