Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Saillogger Community

  1. Home
  2. General Discussion
  3. Cerbo GX memory full issue - and fix

Cerbo GX memory full issue - and fix

Scheduled Pinned Locked Moved General Discussion
2 Posts 2 Posters 133 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mlee390
    wrote on last edited by
    #1

    I ran into a problem when trying to update the Saillogger plug-in inside SignalK which caused several days of head scratching and frustration until I emailed Ilker and he provided the solution. Wondering if I should do a full write up and put it in the FAQ section in case someone else runs into this?

    The short story is that I have an older Cerbo GX I'm running SignalK and Saillogger on and it only has 1Gb data unlike the newer ones that have 4Gb. I wanted to update Saillogger to the latest 4.0.1 version but I could not due to the Cerbo memory being at 100% full (have to use SSH into the Cerbo to find this out). This was mostly my fault at leaving the SignalK server settings for "how many hourly log files to keep" at the default '24' instead of a much smaller # even though I had "keep only most recent data log files" set to 'on'.

    I ended up having to entirely delete ServerK off the Cerbo and re-install. After reconfiguring everything again, all was well except for MarineTraffic not receiving data (it was working fine before the re-install of signalK) and I really wanted to keep my AIS station live with them and keep receiving my free enterprise upgrade.

    Ilker messaged me back and told me to make sure and include in the AIS forwarder plug-in configuration 'nmea0183' along with the default 'nmea0183out' to the NMEA 0183 events box. As soon as I did this, I checked the logs on the AIS forwarder plug-in and it started transmitting AIS data again to MarineTraffic! My AIS station is finally back online. Thank you Ilker!

    Feel free to ask any in depth details.

    1 Reply Last reply
    2
  • I Offline
    I Offline
    ilker
    wrote on last edited by
    #2

    I'm very glad to hear that we could help and that your issue with MarineTraffic has been resolved! Re-installing SignalK on the Cerbo GX can indeed come in handy when the installation becomes unstable, and several other users have found this approach helpful.

    Your idea to create step-by-step instructions is excellent. Please post them here, and we can update our FAQ to include a reference. We're also considering developing a video tutorial for your Youtube Channel that walks through the re-installation process, along with some additional tips to enhance the user experience on the Cerbo GX.

    -Ilker

    1 Reply Last reply
    0

Powered by NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular