Can’t Update Action in Harmony Interface? 2009-12-01T02:41:13+00:00

HOME Forums Gateways EZSrve Can’t Update Action in Harmony Interface?

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • Anonymous
    Post count: 55
    #40231 |

    The functionality of the Harmony interface has improved to the point where I have started to try using it. Entering actions appears to be a lot easier than the HTML interface. Unfortunately, after modifying an action condition in the Harmony interface I get an error when I try to save it. The interface reports “File not saved! Failure: Invalid XML Line 182 Char 52”. I can’t directly evaluate the actions.xml file from the Harmony interface (I can’t find the “List Files” equivalent and the “Save” button in the EZSrve file management panel doesn’t seem to work). When I look at the actions.xml file from the HTML interface, I don’t see any obvious errors and there isn’t anything unusal at the list/char location.

    I tried to add a new action with similar results (the reported error was in a different location however).

    Any ideas? (Thanks in advance…)

    Anonymous
    Post count: 1001

    The “Invalid XML Line ….” has been reported to SHN. I have not heard of a resolution as yet. I could not see anything wrong with my Actions file either when it happened here. The error occurs when the Harmony client is trying to send the updated XML file back through the XML API. Could be a problem with the original XML file being corrupted before it is retrieved by the Harmony client. Could be corrupted after being retrieved before being sent back through the XMP API. Since I could not see anything wrong when I downloaded the Actions file through the HTML it could be either one. I eventually recreated my Actions file at 02.06.01 from scratch and have not seen the “Invalid XML Line …” error since. Don’t know if recreating the Actions file from scratch actually fixed the problem or I just have not encountered that error yet with the new file.

    There is no direct equivalent to asking for a LIST FILEs. From the EZsrve File Management pulldown you can select All Files or an individual file for a Save or Upload request. Save does not appear to be implemented as it is not working at 0.21.4 and nothing is traced by telnet to suggest any attempt was made to retrieve any of the files. Harmony is still in Beta status so some things may not be there yet even though the client is much further along than just a few months ago.

    Anonymous
    Post count: 55

    Thanks. Glad to know that the issue is known.

    You probably already did this, but from a debug trace it looks like the Harmony client reads the actions file and is trying to write something when the error occurs.

    12/01/2009 19.14.10: Read Operation: File FLASH0/data/Actions.xml Open Successful & NoofParams 1, CurrReq.NumberofAttr[1] 0
    12/01/2009 19.14.13: Read File Closed
    12/01/2009 19.14.13: Structure Memory Reset!
    12/01/2009 19.14.13: Handler.c – Returning message handler
    12/01/2009 19.15.38: ezbridge_socket.c – We got a message: No of bytes rcvd 28
    12/01/2009 19.15.38: Structure Memory Reset!
    12/01/2009 19.15.38: cmd name: GetClock
    12/01/2009 19.15.38: Structure Memory Reset!
    12/01/2009 19.15.38: Handler.c – Returning message handler
    12/01/2009 19.16.39: ezbridge_socket.c – We got a message: No of bytes rcvd 7300
    12/01/2009 19.16.39: Structure Memory Reset!
    12/01/2009 19.16.39: cmd name: Write
    12/01/2009 19.16.39: In Read/Write/ReadCluster/WriteCluster Handler
    12/01/2009 19.16.39: In fill attr: level2 noofAttr[2] 3
    12/01/2009 19.16.40: Handler.c – Fatal Error: 7, line 182, char 52
    12/01/2009 19.16.40: Structure Memory Reset!
    12/01/2009 19.16.40: ezbridge_socket.c – We got a message: No of bytes rcvd 8760
    12/01/2009 19.16.40: Structure Memory Reset!
    12/01/2009 19.16.40: Handler.c – Fatal Error: 16, line 1, char 1
    12/01/2009 19.16.40: Structure Memory Reset!
    12/01/2009 19.16.40: ezbridge_socket.c – We got a message: No of bytes rcvd 7249
    12/01/2009 19.16.40: Structure Memory Reset!
    12/01/2009 19.16.40: Handler.c – Fatal Error: 16, line 1, char 1
    12/01/2009 19.16.40: Structure Memory Reset!
    12/01/2009 19.17.40: ezbridge_socket.c – We got a message: No of bytes rcvd 28
    12/01/2009 19.17.40: Structure Memory Reset!
    12/01/2009 19.17.40: cmd name: GetClock
    12/01/2009 19.17.40: Structure Memory Reset!
    12/01/2009 19.17.40: Handler.c – Returning message handler
    12/01/2009 19.19.40: ezbridge_socket.c – We got a message: No of bytes rcvd 28
    12/01/2009 19.19.40: Structure Memory Reset!
    12/01/2009 19.19.40: cmd name: GetClock
    12/01/2009 19.19.40: Structure Memory Reset!
    12/01/2009 19.19.40: Handler.c – Returning message handler

    Anonymous
    Post count: 1001

    That is what I saw. The Actions file was read successfully with the error occurring during the subsequent write. I’m not altogether sure there is an actual failure now. There were some problems in earlier images that destroyed the integrity of things so the Actions file might have been damaged by a problem that no longer exists. Since I have not seen that error since I rebuilt my Actions file from scratch I’m left with the possibility that the error being detected by the XML API Write call is damage that was done on an earlier image and only now being detected when the Actions file is processed by the XML API Write call from the Harmony client. The HTML side of things does not use that XML API call so the validation there might not be as good. I know more validation has been added to the XML API calls to be sure past corruption did not continue to propagate. The Devices file will be reset to nothing but the EZServe device entry if that file is found to be corrupted. I know that is an ugly thought for those who have large Actions files.

    Anonymous
    Post count: 55

    Thanks… I assume that comparing your old actions.xml file to your rebuilt one didn’t reveal an obvious difference…

    @grif091 wrote:

    The Devices file will be reset to nothing but the EZServe device entry if that file is found to be corrupted. I know that is an ugly thought for those who have large Actions files.

    Been there, done that. I’ve gotten in the habit of using the “List Files” in the HTML interface to make a backup of my xml files before doing any tinkering. 8)

    Anonymous
    Post count: 1001

    I did not have the Actions in the same order in the new one so a file compare would not have been effective. There were no obvious problems with the file at the record number indicated in the message. Always thought it would have been nice to have the record in question displayed along with the error so there would be no doubt about which record was involved. Checked records on either side of the record number identified and found nothing wrong there either. It is a little frustrating as I don’t know for sure if rebuilding the file fixed a corrupted file or just changed the data enough so I don’t see a failure any more. One of those “time will tell” situations.

    Anonymous
    Post count: 55

    I looked at the line/char indicated in my actions file and didn’t see anything obvious either. I do think you are right about something in the file. I tried to upload my XML files through the Harmony interface. The areas file was uploaded successfully. My devices and actions files gave a “file not saved!” error. It looks like I’ll be doing some rebuilding too…

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.