pagermon: node:internal/readline/emitKeypressEvents:71 error while monitoring a busy FLEX paging channel.
I’ve been running Pagermon for around 2 months now to monitor a Paging system my Company helps to support. It’s been a great tool to keep track of what is going out on the system and to look up CapCodes for customers that are missing pagers.
I just recently added a second channel to the system for a new customer of ours and noticed the original channel intermittently having this error.
Jan 05 11:38:37 Radio reader.sh[9830]: 2023-01-05 11:38:37: 000704866: THIS IS A TEST PERIODIC PAGE SEQUENTIAL NUMBER 2419 Jan 05 11:38:37 Radio reader.sh[9830]: 2023-01-05 11:38:37: 000602836: Q>]6M3a3f<amM1=mK<?GLAK?dl7OefS0]WDToOeFZ9
Jan 05 11:39:19 Radio reader.sh[9830]: 2023-01-05 11:39:19: 000603497: [9=7eT0EgQ=gE1m1F=lmWE0C\WaIU8Fg2kK@SfKL]oEdho8;gf;>l5HlLZC<fek3MUlZHDa?2Da@9P\Mc20_YM=lOKgCDQ?Cm0]Yl;b9=
Jan 05 11:39:19 Radio reader.sh[9830]: 2023-01-05 11:39:19: 000830538: THIS IS A TEST PERIODIC PAGE SEQUENTIAL NUMBER 2420
Jan 05 11:39:24 Radio reader.sh[9830]: 2023-01-05 11:39:24: 000603084: 777-7777
Jan 05 11:39:49 Radio reader.sh[9830]: 2023-01-05 11:39:49: 000603097: 777-7777
Jan 05 11:39:49 Radio reader.sh[9830]: 2023-01-05 11:39:49: 000603084: 777-7777
Jan 05 11:39:55 Radio reader.sh[9830]: node:internal/readline/emitKeypressEvents:71
Jan 05 11:39:55 Radio reader.sh[9830]: throw err;
Jan 05 11:39:55 Radio reader.sh[9830]: ^
Jan 05 11:39:55 Radio reader.sh[9830]: TypeError: Cannot read properties of null (reading ‘1’)
Jan 05 11:39:55 Radio reader.sh[9830]: at Interface.<anonymous> (/root/pagermon/client/reader.js:121:77)
Jan 05 11:39:55 Radio reader.sh[9830]: at Interface.emit (node:events:513:28)
Jan 05 11:39:55 Radio reader.sh[9830]: at Interface._onLine (node:readline:491:10)
Jan 05 11:39:55 Radio reader.sh[9830]: at Interface._line (node:readline:868:8)
Jan 05 11:39:55 Radio reader.sh[9830]: at Interface._ttyWrite (node:readline:1227:16)
Jan 05 11:39:55 Radio reader.sh[9830]: at Socket.onkeypress (node:readline:291:10)
Jan 05 11:39:55 Radio reader.sh[9830]: at Socket.emit (node:events:513:28)
Jan 05 11:39:55 Radio reader.sh[9830]: at emitKeys (node:internal/readline/utils:357:14)
Jan 05 11:39:55 Radio reader.sh[9830]: at emitKeys.next (<anonymous>)
Jan 05 11:39:55 Radio reader.sh[9830]: at Socket.onData (node:internal/readline/emitKeypressEvents:61:36)
`
But, it’s only having this error on the original system. The Original system is a mix of POCSAG 1200 and FLEX, but the new system is only POCSAG. So I’m thinking this may be an issue with FLEX decodes.
Another thing that might be causing this is the channel that is having the error carries encrypted FLEX traffic, So maybe it’s having an issue parsing that?
additional note Looking back in the logs it likes this has been happening for a while now, but I just didn’t notice it because I would restart the service it’s attached to every weekend when I did server backups. We haven’t had many issues with the system for the last month so I guess I didn’t notice the missing pages in the database. 😕
Any help on this would be appreciated. If this program works out in the long run I’m looking at deploying it on a raspberry Pi and using it as portable coverage monitor for customer reporting system issues in one area or who are on the edges of the system. Thanks for the great application and all the hard work on it!
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (1 by maintainers)
Interesting. There was a PR somewhere with a fix for zero length POCSAG pages. It was never included because there was other parts to it that remained unnecessary or unfinished. I cant recall. Let me see if i can find it and pull that part out and make it work for both FLEX and POCSAG