Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Reinstall server on ubuntu

Answered
Brian Faber

media server won't start and I see this in the logs

 

2020-12-03 16:18:37.314 9262 WARNING QnServerDb(0x7fb1a40a4dc0): Failed to vacuum mserver database

2020-12-03 16:18:37.314 9262 ERROR MediaServerProcess(0x55cc3818bc80): Stopping the Server because can't open the database

0

Comments

3 comments

Date Votes
  • Wendy Chuang
    • Network Optix team

    Hi Brian Faber,

    Based on the server log, it seems that the Nx service cannot read the server database for an unknown reason. Could you describe what did you do before the issue happening?

    At the moment, you could follow the steps below to recover the Nx service. But please notice that the bookmark. event logs and audit logs will be cleared.
    1. Stop the Nx mediaserver service.
    2. Backup the server database(mserver.sqlite) which is located in the corresponding path:

    • Windows
      C:\Windows\System32\config\systemprofile\AppData\Local\Network Optix\Network Optix Media Server\mserver.sqlite
    • Ubuntu
      /opt/networkoptix/mediaserver/var/mserver.sqlite

    3. Remove the mserver.sqlite after finished backup.
    4. Start the Nx mediaserver service again.

    Note: To stop and start the media server, please do it as follows:

    • Windows: Open the task manager, select tab ‘Services’ find the mediaserver application, right-click and select; Stop or Start
    • Linux: Open the terminal (Ctrl+Alt+T) and enter the following command; 
      sudo service networkoptix-mediaserver stop or sudo service networkoptix-mediaserver start.


    Thank you.

     

    0
  • Brian Faber

    The following steps were taken 

    service networkoptix-mediaserver stop copey

    /opt/networkoptix/mediaserver/var/mserver.sqlite to /archives/mserver.sqlite

    then removed /opt/networkoptix/mediaserver/var/mserver.sqlite

    service networkoptix-mediaserver start

    there is no change, also the error is the same in the log (with different time a stamp)

    what are the steps needed if the system gets reinstalled then all the data paths are reimported under the same path and network optix gets installed, what other steps we need to take to make it work with the existing data?

    Describing in detail what we did before the issue started happening:

    Couple of days ago a linux system update was attempted, while seemingly the update has run without any events, upon reboot there was a complete system lockup even before grub would load (no response from numlock or capslock keys)

    The server was booted with a linux live usb, and investigation begun, raid assembled, lvm imported, file system mounted, our initial assumption that /boot or the root file system would be full were not the case, in fact they were loking normal

    At this point while still running from the live boot, a chroot into the system was run to investigate for aborted dpkg or apt, the first error messages we got were about corrupted package cache files, this was remedied and we continued our investigation.

    Our second expectation was confirmed that there was a mishap with a grub upgrade (with the error "Package grub-pc is not configured yet."), at this point we attempted finishing the grub install inside the chroot, however it constantly barfed with errors and we discovered the grub install process itself would abrubtly get killed.

    Upon closer examination we noticed we would have this with other commands as well (there were no out of memory errors, file systems had ample free space, nothing out of the ordinary), but various comands in the chroot - always the same commands - while we were not seeing the same errors out of the chroot.

    Fschck shown zero errors on all file systems. The system is on an ssd raid that has write intent logs, the raid volumes are used in lvm then root, home, and so on are logical volumes and all use ext4 file system, with everything having ample of free space and no errors outside of the chroot we ruled out hardware problem and decided the system somehow got corrupted

    At this point we renamed the root logical volume, and while still running off the live linux, we have created a new root logical volume that we mounted and executed a bionic deboostrap into it, configured it for chroot, chrooted into it, finished network setup and ssh install, as well mdadm and lvm, installed the kernel package and grub all while in chroot. Everything went without errors, exited chroot, unmounted file systems, stopped lvm and then raid and rebooted.

    Then using ssh all the packages were intalled, all the local logical volumes and network storage all got mounted under the same diredtories, netowkoptix was installled, and we upon starting we always get the same error where the mediaserver attempts to start but then stops before giving a bunch of warnings as described at the top of this message

    0
  • Wendy Chuang
    • Network Optix team

    Hi Brian Faber,

    Thanks for all your information. Then it is likely that the system database was corrupted as well.
    Please follow the same procedure to backup/remove the system database(ecs.sqlite) and server database(mserver.sqlite). They are located on the same path.

    Moreover, you could refer to the article below for related topics:
    - Nx server data files: here
    - Preserve data from Nx product: here

    Let me know if it still cannot work with your Nx service.
    Thank you.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post