Re: Failure on Qngateway Service
|
Nomis ? Put a # at the start of line 117, the qnvoice one, and see if it¡¯ll boot. If it will, I can help you prune your qn.cfg file down to what it only needs so its much easier to read. What Tom is saying is the #s are just to show you what you CAN do, only a few of them have to be uncommented.? The # at line 117 should make it work. Try it, and issue systemctl restart qngateway qnlink ; journalctl -u qngateway -f ? Show me what it says. ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Nomis Bayan Jr.
Sent: Sunday, September 9, 2018 12:17
To: [email protected]
Subject: Re: [QnetGateway] Failure on Qngateway Service? HI tom, Thank you for telling me. I was not aware that I can leave the #, comment on most of them. Just be to clear or as I understood what you provided. 1. Return the # as before. 2. Login enter Callsign, KM6VLB 3. Only module b ??????? b = {
??????????????? type = "icom"
??????????????? ip = "172.16.0.1" # all icom modules should have the same IP ad$
??????????????? port = 20319?????? # all icom modules should have the same UDP $
??????????????? frequency = 448.260
??????????????? offset = 5
??????????????? range = 15.0
??????????????? agl = 30.0
??????????????? latitude = 32.0
??????????????? longitude = 127.0
??????????????? desc1 = "La Mesa, CA"
#?????????????? desc2 = "" 4. ??????? admin = [ "N0MIS" ]????????? # only these users can execute scripts, bl$
#????????????????????????????????????????????????????? # you probabaly want you$
??????? link_unlink = [ "N0MIS" ]??? # if defined, only these users can link an$
What about the start to link? ? On 09/09/2018 08:59 AM, Tom Early wrote: Hi Nomis,
You're qn.cfg file is way too complicated, so it's hard to see what you've done. The example files I supplied, especially qn.everything.cfg and qn.icom.cfg define all of the config parameters you can change. The default values for those parameters are shown as comments (lines beginning with "#"). You don't need to uncomment those lines if the values of those config parameters are acceptable to you. In fact, for clarity, you can delete any lines that are just comments! For example your ircddb section just needs to be:
ircddb = {
???????? login = "KM6VLB"
}
It's also unnecessary to have an empty section. If you accept all the default values in a section (surrounded by parentheses), you can delete the section as well. For most configurations, this means that the qn.cfg file will usually be just a few lines.
In general the only thing you will need to define is your ircddb login, the module(s) (at a minimum you must define a type for each module) and usually a list of admins in the link section because these are the only callsigns that can execute the shutdown and reboot scripts.
?
|
