database locking... still a problem
|
I haven¡¯t been using QnetGateway for quite awhile due to various things. I updated my two Pi¡¯s last night to give it another whirl. Looks like database locking is still a problem.
Here, I am connected to REF030C. When I connected, it told me so. And when I issue the ¡°i¡± command, it again tells me so. And I see activity on the dashboard. But the web dashboard continues to falsely report that I¡¯m not linked. |
|
I am not seeing that (Just checked says LINK REF030 C just like it should I still OCCASIONALLY have the "Not in list" issue when returning to a reflector however and "F" does not always fix it RX does. "Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis On Monday, August 17, 2020, 09:07:33 PM EDT, Elden W7LDN <w7ldn@...> wrote: [Edited Message Follows] I haven¡¯t been using QnetGateway for quite awhile due to various things. I updated my two Pi¡¯s last night to give it another whirl. Looks like database locking is still a problem.Here, I am connected to REF030C. When I connected, it told me so. And when I issue the ¡°i¡± command, it again tells me so. And I see activity on the dashboard. But the web dashboard continues to falsely report that I¡¯m not linked. |
|
Thank you Tom. I cannot say if there were extenuating circumstances. But the DB appeared to be locked immediately after a reboot. Actually, immediately after multiple reboots. I did look back at our previous thread on this. Last night I snagged the command strings that you provided in one of your last messages on this. I now have a command to grep the log for the word ¡°lock¡±... to tell me if I have the problem. Then one command to stop the gateway, link, and modem services. Another to nuke the DB. And another to start the services back up. You had provided me all this, so I figure this is a fine work around if I end up needing it.
toggle quoted message
Show quoted text
I¡¯ll paste them here just for kicks: alias chklock='sudo journalctl -u qnlink | grep -i lock'
alias stop='sudo systemctl stop qngateway && sudo systemctl stop qnlink && sudo systemctl stop qnmodem'
alias rmdb='sudo rm -f /usr/local/etc/qn.db && ls -l /usr/local/etc/qn.db'
alias start='sudo systemctl restart qngateway && sudo systemctl restart qnlink && sudo systemctl restart qnmodem'
I will go ahead and pull the new source tonight. Thanks again. On Tue, Aug 18, 2020 at 12:32 PM, Tom Early wrote: Forget the previous experiment. Reading the manual again and googling everybody's opinion, I'm using the correct options to open. |
Elden AI7HL
Tom Early