I’m not sure how we transitioned from “Node Remote” to the “astdb.txt” file. But, for the latter, I will direct you to the following ASL3 Manual page :
This page will tell you how to enable/populate the “astdb.txt” file on an ASL3 system.
Because it’s an error inside of the Node Remote app.
But I’ll look at that other info…
Because it’s an error inside of the Node Remote app.
Since the Node Remote app is not running on your node then downloading the “astdb.txt” file to the node likely won’t help.
As it’s an iOS app, it doesn’t run on a node… It does however pull info from your node, after you configure the app. The error on the app is from, I believe, it not being able to see the astdb.txt file for some reason that I am not aware of… The info from the developer only mentions making some changes on the node for the app to function (see his site: Node Remote – M0DQW).
Further inquires will be sent to the developer via his site and the App Store…
Jeff K3JRZ
Fixing astdb.txt in Node Remote for ASL3, from the link above, with one minor change:
1. Enable astdb.txt service in ASL3 (using following commands)
systemctl enable asl3-update-astdb.service
systemctl enable asl3-update-astdb.timer
systemctl start asl3-update-astdb.timer
2. Reboot Node
3. sudo mkdir /var/www/html/allmon2
4. sudo ln -s /var/lib/asterisk/astdb.txt /var/www/html/allmon2/astdb.txt
5. Fully restart the "Node Remote" app. Force close and reopen.
Rather than copy the file and have to setup a job to do it, just create a symlink so that accessing astdb.txt from Node Remote will always pull the updated copy. No duplication of data and always up to date.
I am confused by your instructions to link the astdb.txt file with "allmon2". All Node Remote needs is access to AMI.
That’s just a copy/paste from the developers website, but what’s happening is essentially:
Enable service that creates the astdb file, then create a url path that Node Remote is looking for, in this case it’s (your_IP/allmon2/astdb.txt), followed by creating a symlink that references the actual file.
And all of those “reboot” instructions really aren’t necessary, maybe the one after enabling the service, but not the last one.
Allmon2 doesn’t exist in the ASL3 world, but that’s what Node Remote is looking for, so you’re creating a directory that doesn’t exist because you can’t change where Node Remote is looking.
Can you share a link to the document / documentation you've been looking at?
This would suggest that Node Remote is communicating with the node using AMI *and* is making an assumption that a web server is also running on the same IP with the astdb.txt file available via HTTP.
I remain confused.
K3JRZ’s post above has the link, from who I presume is the developer of Node Remote.
Not sure what AMI is, but the astdb.txt error didn’t resolve until I followed those steps from the link. My recommendation was simply to replace the ‘cp’ with a ‘ln -s’, or create a symlink to the originating file rather than copying it manually (and scheduling it, as the dev recommended).
Have you not gotten the astdb.txt error resolved yet?
@subtly_irritated I am *not* the developer of Node Remote. M0DQW is. If you scroll up in the thread, I was also asking for help with it.
Just a quick injection for you to check the ownership/permissions of the astdb file if it is in the place where the app is looking for it.
That worked for me. Thanks & 73!
My mistake on how I phrased that. I meant to say that your post had a link to the developers page that addresses the issue.
- I now see the
Unable to fetch astdb.txtmessage. I don't remember seeing this the last time I had used the app (many many months ago) but at the time I was more interested in seeing how/if the app worked. - Yes, in this case, using a symlink (
ln -s ...) would be preferred over the copy (cp ...) command. - I have reached out to the developer