Tokens.txt not updating

Discussion topics related to mobile applications and ZoneMinder Event Server (including machine learning)
User avatar
asker
Posts: 1553
Joined: Sun Mar 01, 2015 12:12 pm

Re: Tokens.txt not updating

Post by asker »

Code: Select all

619] [Websockets: New Connection Handshake requested from ::ffff:162.208.37.32:58949 state=pending auth, id=1578795968.2891]
bad bcrypt settings at /usr/bin/zmeventnotification.pl line 942.
I think that is a big reason. Log into ZM web console with the same account you are using in zmNinja. Then run Es again.
I no longer work on zmNinja, zmeventnotification, pyzm or mlapi. I may respond on occasion based on my available time/interest.

Please read before posting:
How to set up logging properly
How to troubleshoot and report - ES
How to troubleshoot and report - zmNinja
ES docs
zmNinja docs
cafftab
Posts: 48
Joined: Mon May 06, 2019 6:03 pm

Re: Tokens.txt not updating

Post by cafftab »

While being logged in zm console as the same user as zmninja

https://gist.github.com/tombu2130/ad61c ... ed56d30a73

2020-01-11 20:27:11.052672 zmeventnotification[11127].INF [main:619] [using config file: /etc/zm/zmeventnotification.ini]
2020-01-11 20:27:11.089777 zmeventnotification[11127].INF [main:619] [using secrets file: /etc/zm/secrets.ini]
2020-01-11 20:27:11.125606 zmeventnotification[11127].INF [main:619] [ES will be restarted at 10800 seconds]
2020-01-11 20:27:11.303092 zmeventnotification[11127].INF [main:619] [Push enabled via FCM]
2020-01-11 20:27:11.334013 zmeventnotification[11127].INF [main:619] [MQTT Disabled]
2020-01-11 20:27:11.384002 zmeventnotification[11127].INF [main:619] [You are running version: 4.7]
Can't ignore signal CHLD, forcing to default.
2020-01-11 20:27:11.575384 zmeventnotification[11127].INF [main:619] [Event Notification daemon v 4.7 starting]
2020-01-11 20:27:11.603146 zmeventnotification[11127].INF [main:619] [Initializing FCM tokens...]
2020-01-11 20:27:11.636336 zmeventnotification[11127].INF [main:619] [Total event client connections: 3]
2020-01-11 20:27:11.693740 zmeventnotification[11127].INF [main:619] [Reloading Monitors...]
2020-01-11 20:27:11.726102 zmeventnotification[11127].INF [main:619] [Re-loading monitors, emptying needsReload() list]
2020-01-11 20:27:11.761545 zmeventnotification[11127].INF [main:619] [About to start listening to socket]
2020-01-11 20:27:11.796699 zmeventnotification[11127].INF [main:619] [Secure WS(WSS) is enabled...]
2020-01-11 20:27:11.834880 zmeventnotification[11127].INF [main:619] [Web Socket Event Server listening on port 9000]
2020-01-11 20:29:13.476396 zmeventnotification[11127].INF [main:619] [got a websocket connection from ::ffff:162.208.37.32 (3) active connections]
2020-01-11 20:29:13.514892 zmeventnotification[11127].INF [main:619] [Websockets: New Connection Handshake requested from ::ffff:162.208.37.32:59117 state=pending auth, id=1578799753.51463]
bad bcrypt settings at /usr/bin/zmeventnotification.pl line 942.
User avatar
asker
Posts: 1553
Joined: Sun Mar 01, 2015 12:12 pm

Re: Tokens.txt not updating

Post by asker »

The "bad bcrypt" message typically only comes when the password of that user has not been migrated to the new password scheme in ZM. When you log into ZM with that same user the password _should_ be migrated.

Try this:

1. Create a new user in ZM (as a test). Once created, switch the zmNinja user to the new user. See logs on the ES as zmNinja tries to "register" and see if you get the same error.

2. If 1 fails, upgrade ES (in general, you should upgrade - you are running an old version). When you upgrade ES please also upgrade hooks (refer to upgrade/install procedure in docs)
I no longer work on zmNinja, zmeventnotification, pyzm or mlapi. I may respond on occasion based on my available time/interest.

Please read before posting:
How to set up logging properly
How to troubleshoot and report - ES
How to troubleshoot and report - zmNinja
ES docs
zmNinja docs
cafftab
Posts: 48
Joined: Mon May 06, 2019 6:03 pm

Re: Tokens.txt not updating

Post by cafftab »

Thank you Thank you, it was the username issue. I removed the other users, revoking tokens for them didn't work. I don't think I have ever seen logs looking this way.

When I get a chance I will upgrade but I want to run it this way for a while
Post Reply