EQ Alert - Log Parser

[sharkukri]

I got it working, thanks! However one issue, after about ~5 minutes EQAlert stops parsing the logs and doesn't alert or do anything anymore. My logs are still being written to, so I'm not sure what the issue is.

[sharkukri]

I looked into it a bit more, it appears EQAlert stops reading the log when tailing .eqa/log/debug/matched-lines.txt

[sharkukri]

I tailed eqalert.log and killing a mob triggered the following

INFO:root:[2022-10-06_16:12:30]: action_q depth: 1
INFO:root:[2022-10-06_16:12:30]: action_q depth: 1
INFO:root:[2022-10-06_16:12:30]: process action: Error on line 184: 'unavailable'

Here is the debug from EQAlert

mob_slain_you                 │ You have slain a geonid!                                                                                                                      │
│  faction_line                  │ Your faction standing with GeonidCollective got worse.                                                                                        │
│  experience_solo               │ You gain experience!!

[sharkukri]

Okay I've isolated it to when killing a mob EQAlert breaks and stops tailing logs, so the previous message is the reason why it breaks

[sharkukri]

I managed to get EQAlert working finally. Installing python3.8 and changing the environment using venv and running eqalert through it works and no longer crashes when killing a mob. Maybe the readme should list compatible versions of python? It would be nice if 3.10 works as 3.11 is right around the corner.

Thanks!

[Indefinite]

Originally Posted by sharkukri [You must be logged in to view images. Log in or Register.]

I managed to get EQAlert working finally. Installing python3.8 and changing the environment using venv and running eqalert through it works and no longer crashes when killing a mob. Maybe the readme should list compatible versions of python? It would be nice if 3.10 works as 3.11 is right around the corner.

Thanks!

Tracking both of these issues under #175 and #176

[arksz]

Originally Posted by sharkukri [You must be logged in to view images. Log in or Register.]

Okay I've isolated it to when killing a mob EQAlert breaks and stops tailing logs, so the previous message is the reason why it breaks
Thanks!

I am also running into the same issue where it stops reading the logs after killing a mob. Any Ideas on how to fix?

[arksz]

tail -n 20 matched-lines.txt
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spell_fungal_regrowth_you_on : You are covered by a sticky substance.
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spell_fungal_regrowth_you_on : You are covered by a sticky substance.
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spell_fungal_regrowth_you_on : You are covered by a sticky substance.
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spell_fungal_regrowth_you_on : You are covered by a sticky substance.
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spell_fungal_regrowth_you_on : You are covered by a sticky substance.
spells_cast_you : You begin casting Cannibalize IV.
undetermined : Your body aches as your mind clears. You have taken 148 points of damage.
spells_worn_off : Your Envenomed Bolt spell has worn off.
mob_slain_you : You have slain a Ratfink!
experience_solo : You gain experience!!

INFO:root:[2022-11-08_14:25:43]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Paralyzing Earth.
INFO:root:[2022-11-08_14:25:45]: action_q depth: 3
INFO:root:[2022-11-08_14:25:45]: action_q depth: 2
INFO:root:[2022-11-08_14:25:45]: action_q depth: 1
INFO:root:[2022-11-08_14:25:47]: action_q depth: 1
INFO:root:[2022-11-08_14:25:47]: system_q depth: 1
INFO:root:[2022-11-08_14:25:49]: encounter spell [spells_fizzle_you] not added to encounter stack: Your spell fizzles!
INFO:root:[2022-11-08_14:25:51]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:25:52]: action_q depth: 3
INFO:root:[2022-11-08_14:25:52]: action_q depth: 2
INFO:root:[2022-11-08_14:25:52]: action_q depth: 1
INFO:root:[2022-11-08_14:25:55]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:00]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:03]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:07]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:11]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:14]: encounter spell [spells_cast_you] not added to encounter stack: You begin casting Cannibalize IV.
INFO:root:[2022-11-08_14:26:29]: encounter spell [spells_worn_off] not added to encounter stack: Your Envenomed Bolt spell has worn off.
INFO:root:[2022-11-08_14:26:41]: action_q depth: 1
INFO:root:[2022-11-08_14:26:41]: process action: Error on line 184: 'unavailable'

Here is a tail of my logs up to the kill when it stopped working

[Indefinite]

Originally Posted by arksz [You must be logged in to view images. Log in or Register.]

I am also running into the same issue where it stops reading the logs after killing a mob. Any Ideas on how to fix?

This may be caused by either a python version greater than 3.7.3 running EQ Alert or an issue with encounter parsing, which has a pretty messy implementation right now. Otherwise, disabling the encounter parse should resolve the issue.

This should hopefully be resolved in the next version by splitting up the analysis of the encounter stack and the reporting from it.

I've been developing on Debian stable so the python3 version I'm using is a bit older, planning to address that once encounter parsing is cleaned up.

[steve]

Is this abandoned? No updates on github recently.