AP9631J log files - is event.txt shown in the web UI?

Anonymous user · ‎2021-06-29

Other posts on this forums recommend logging into the UPS via FTP and copying down the event.txt file when there is a problem. My question is, is this file the same as what is shown in the web UI? Is there more specific information in event.txt or is is the same thing you can get via Logs > Event > Log in the UI?

We are using a AP9631J in a SmartUPS 3000, and encountered a sudden warmstart. All the other UPS on the same subnet didn't have a problem, so I dont think it was the 9.5 minute reset for not receiving broadcast data. The event log in the web UI didn't give any real indication of what caused the warmstart, so I was hoping the logs on the UPS might be a bit more detailed.

Thanks in advance for your help!

Message was edited by: Lambent

Message was edited by: Lambent

BillP · ‎2021-06-29

event.txt provides the same information for the most part (it adds the unique hex code for each event at the end of the line and shows the firmware version at the top) but we prefer it because it is text based and does not have HTML in it. it also provides the full log versus just a subset if you don't filter the web UI correctly. thus, tech support requests the full event.txt.

what firmware is on this card? if you have an unexplained warmstart, some log files are available to help explain this issue. these files i speak of (debug.txt/dump.txt) are ONLY available via FTP. debug.txt is available on AOS 5.1.1 and higher and dump.txt is available from AOS 5.1.6 and higher.

if you have these files, i can help you determine why the card warmstarted hopefully. i'll also need event.txt please 🙂

See Answer In Context

Anonymous user · ‎2021-06-29

Yes, the event.txt file is the same as the event log in the web UI of the network card. Generally its easier to pull the log as a txt file than it is to copy it over as a text document, since the formatting can get messed up when copied and make it difficult to read. The event.txt file also includes extra information, such as the model type of the UPS and the firmware revision on the card, both important pieces of information when troubleshooting a warmstart.

BillP · ‎2021-06-29

event.txt provides the same information for the most part (it adds the unique hex code for each event at the end of the line and shows the firmware version at the top) but we prefer it because it is text based and does not have HTML in it. it also provides the full log versus just a subset if you don't filter the web UI correctly. thus, tech support requests the full event.txt.

what firmware is on this card? if you have an unexplained warmstart, some log files are available to help explain this issue. these files i speak of (debug.txt/dump.txt) are ONLY available via FTP. debug.txt is available on AOS 5.1.1 and higher and dump.txt is available from AOS 5.1.6 and higher.

if you have these files, i can help you determine why the card warmstarted hopefully. i'll also need event.txt please 🙂

Anonymous user · ‎2021-06-29

Sorry for the late response. Thank you, the info about event.txt answered my question!

voidstar_apc · ‎2021-06-29

>
Generally its easier to pull the log as a txt file than it is to copy it over as a text document, since the formatting can get messed up when copied and make it difficult to read.
>

You may find it easier to read if you paste into a spreadsheet like excel.