Event Logging after Upgrade - no 730 & Group Address

Discussion in 'C-Bus Toolkit and C-Gate Software' started by hugovg, Jun 22, 2009.

  1. hugovg

    hugovg

    Joined:
    Jun 22, 2009
    Messages:
    3
    Likes Received:
    0
    Location:
    NZ
    Sorry if this is a trivial question, but the logging of 730 events we used to use in the event.log for analysis purposes has stopped after an C-Gate/Toolkit upgrade.

    We have successfully used used:
    - Toolkit v1.5.3 (build 240)
    - C-Gate v2.5.23 (build 2123)
    - "global-event-level=7" in C-GateConfig.txt file
    and we get/extract events like this:
    20090621-210640 730 //site-name/254/56/17 64dbdf70-b8ff-102a-863f-9add5e703c4d new level=0 sourceunit=17 ramptime=0

    But after upgrading one site to Toolkit v1.10.0 (build 389) & C-Gate v2.7.0, we can't get this logging to work again, regardless of what event level we try:
    - the "730" staus events in event.log no longer show the group address, just the source unit
    - listenting to SCP (port 20025) gives us the group address but no time stamp

    eg. event.log line:
    20090611-002652 730 sys new level=0 sourceunit=21 ramptime=0

    Thanks for any help.
     
    hugovg, Jun 22, 2009
    #1
  2. hugovg

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    766
    Likes Received:
    20
    Location:
    Adelaide
    Hi hugovg,

    You may want to update to the latest version, Toolkit 1.10.4.

    This was a bug which was fixed in C-Gate 2.7.0 build 2267 (released with Toolkit 1.10.3).
     
    daniel, Jun 23, 2009
    #2
  3. hugovg

    hugovg

    Joined:
    Jun 22, 2009
    Messages:
    3
    Likes Received:
    0
    Location:
    NZ
    Thanks for the advice.

    You are right, 730 events are back, using "global-event-level=7", but so are a large number of 753 Net Sync events too! We filter them out, but C-Gate now generates a sequence of 4MB event log files (eg. "event.11.log"), sometimes only spanning a few days.

    I am sure the older version's log file: (a) did not have all the 753 events, and (b) appended to a single large file (no so good in the long run, but easier to handle).

    Do you know of any better way of logging group address status changes? Other than me writing code to listen on the SCP (20025) & timestamp each event entry and write to a log?

    Thanks again for your help.
     
    hugovg, Jun 23, 2009
    #3
  4. hugovg

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    766
    Likes Received:
    20
    Location:
    Adelaide
    Hi hugovg,

    The logging was changed to (a) provide more data, (b) split into files that could be easily opened in an editor or emailed, AND (c) enforce a max size so HDs didn't fill up. event.log is always the most recent.

    The behaviour is managed in \C-Gate2\config\C-GateConfig.txt:

    event-file.split=yes
    event-file.split-count=50
    event-file.split-size=5000000

    For example, to revert to the original single event.log file change the first option to <b>event-file.split=no</b> ... this will render the other two options ineffective and the log will grow indefinitely.
     
    daniel, Jun 24, 2009
    #4
  5. hugovg

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,392
    Likes Received:
    24
    Location:
    Adelaide, South Australia
    Which is a BAD idea!
     
    ashleigh, Jun 24, 2009
    #5
  6. hugovg

    hugovg

    Joined:
    Jun 22, 2009
    Messages:
    3
    Likes Received:
    0
    Location:
    NZ
    Thanks for the info, sorry for slow response!
     
    hugovg, Jun 30, 2009
    #6
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.