Service Notification
OnSite Help Center
ONSITE RETAIL (R-SERIES) RETAIL (X-SERIES) ECOM (C-SERIES) RESTAURANT (L-SERIES) RESTAURANT (K-SERIES)

    Known issues

    Below you'll find solutions to known issues you may have encountered.

    OnSite fails to launch after an OS upgrade

    Any update as of MacOS 10.15.X may have reduced the amount of shared memory OnSite has access to, resulting in the OnSite server failing to launch. To determine if this is the reason your OnSite server is failing to launch, you'll need to check your postgres.log file.

    1. Navigate to /Library/Application Support/LightSpeed Server/logs/postgres.log in Finder.
    2. Open postgres.log using any text viewer, such as TextEdit.
    3. Look for the following text:

    2019-10-30 22:47:20 CDT FATAL: could not create shared memory segment: Invalid argument

    2019-10-30 22:47:20 CDT DETAIL: Failed system call was shmget(key=5432001, size=37871616, 03600).

    2019-10-30 22:47:20 CDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37871616 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).

    If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.

    The PostgreSQL documentation contains more information about shared memory configuration.

    If you see the above text in the log, you are experiencing this known issue and you can resolve it by doing the following:

    1. Open System Preferences in MacOS.
    2. Click on Lightspeed Server.
    3. Click the lock icon in the lower left-hand corner of the panel to unlock it.
    4. Click Advanced.
    5. Click Reset Configuration.
    6. Click Done.
      Screen_Shot_2020-06-18_at_2.59.39_PM.png

    You will then need to reboot your computer to use the new configuation, after which you should no longer experience any trouble launching the OnSite server.

    If you did not see the above text in your postgres.log file or if your problem persists after performing the above steps, please contact Support.