¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: QnetGateway dashboard issue


 

Good point Colby.. Have had that happen on other sites more times than I care to count.


"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 Thursday, May 28, 2020, 01:07:55 PM EDT, Colby Ross W1BSB <colbypr@...> wrote:


It could be his browser caching this information and not refreshing correctly.

Colby

?

?

From: [email protected] <[email protected]> On Behalf Of Tom Early
Sent: Thursday, May 28, 2020 1:04 PM
To: [email protected]
Subject: Re: [QnetGateway] QnetGateway dashboard issue

?

Sorry Elden, I can't reproduce what you are seeing. If I link to XRF757 A, it shows that on my dashboard. If I then reboot my ZUMspot and it comes back up, the dashboard shows I'm not linked.? One of the first things QnetLink does when it starts it to automatically clear all linking information from the Sqlite3 database, so I'm not sure how that bogus linking information is surviving a reboot. Please double check you configuration to make sure that your module is not programmed to automatically link to a reflector upon boot up. (It's called "Link at startup" and is the first menu item in the configured module submenu.)

Another possibility is that somehow the database can no longer be opened with write permission. To check that, open a new terminal window and do "sudo journalctl -u qnlink -f" and then link and reboot you system and watch for database writing error message. If these occur, uninstall your system from the ./qnadmin tool. The uninstall should remove the damaged database, but just to be sure, you can exit qnadmin and do "sudo rm /usr/local/etc/qn.db". Then you can use ./qnadmin to reinstall you system.

Also, just to let everyone know, it is a feature of QnetLink that you can only link a module if it is currently unlinked.

Join [email protected] to automatically receive all group messages.