I am trying out Allscan for the first time.
Initially I had a "file not found" when trying to execute the install/upgrade script.
This appeared to be because php was not installed on the system.
The script does not appear to check for pho or give you an option to install it.
I installed php and tried again.
Seemed to install fine with no errors.
In the web interface and setup the initial admin user. That worked fine.
I am now seeing this error:
Error parsing /etc/allmon3/allmon3.ini
No valid node/AMI definitions found. Run asl-menu to configure AMI credentials.
The file is certainly present and configured properly.
Is there an out of the box permissions issue?
I'm assuming it uses all of the allmon3 permissions.
Also allmon3 is working properly with AMI and that .ini file's settings.
Did I miss any instructions somewhere?
I'm browsing the site and do not seem be be finding generic setup instructions but I'm pretty sure they are there and I'm missing them.
Thanks!
-Steve
Reading the docs carefully.
php.ini is not in /etc/php
It's in /etc/php/8.2/cli
I added:
extension=pdo_sqlite
extension=sqlite3
sqlite3 is NOT installed on the system already.
I installed it.
Note: the Install script ran without errors (before) doing any of this extra stuff.
AND it created the /etc/allscan/allscan.db and allowed me to create an initial admin user that works.
Tried above and rebooted.
Still stuck on Problem:
Error parsing /etc/allmon3/allmon3.ini
No valid node/AMI definitions found. Run asl-menu to configure AMI credentials.
AMI is configured and works with allmon3.
Also tried re-installing allscan after above possible dependencies manually installed.
Still have same problem.
It's a file permissions issue:
allmon3.ini is only accessible by user:allmon3.
allscan is running as what looks like "www-data".
It did not install in such a way that it's running as allmon3.
Maybe my fault? not sure.
Anyhow giving www-data read access to the file fixed it at least for a test.
Glad you got it working. AllScan does do several checks during installation and when the app runs to find the AMI details from several possible sources.
Also note that on the github page the install instructions are currently listed as follows:
Log into your node by SSH and run the following commands:
Since you mentioned that php was not installed I am guessing that you did not run the first line in the above instructions, which installs php. And if that line was missed, possibly other commands were missed too; maybe you found some old install instructions somewhere else?
When the installer runs, and also when AllScan runs, they look for the AMI info in several places, and even if there is a permissions issue with one file it will move on the next, finally looking in /etc/asterisk/manager.conf. Thus I would have to suspect your node somehow had permissions set in a non-default way on all those files. The /etc/asterisk/ files will normally have 644 permissions. I tried some tests here where I chmod'd some various files to 600 and AllScan did then move to manager.conf and correctly read the AMI info there.
To say anything further I would need to see the log messages shown when you run the installer/updater, and also all messages shown in the log window in the main AllScan page under the Favorites table. Might also then be good if you could do a 'ls -la /etc/asterisk/' to confirm what permissions settings you have on that directory. If this doesn't all fit in a post here you can also email me at david at allscan.info. Thanks, David