Please add Information about config.inc.php to REAMDE.md

[dl1nux]

Hi

when follwing the instructions, the dashboard doesn't show anything. I found out that the file include/config.inc.php has to me modified also.

define("HEADER_CAT","FM-Repeater"); define("HEADER_QTH",""); define("HEADER_QRG",""); define("HEADER_SYSOP",""); define("FMNETWORK_EXTRA",""); define("EL_NODE_NR",""); define("FULLACCESS_OUTSIDE", 0); define("ADD_BUTTONS", 1);

define("SVXCONFPATH", "/etc/svxlink/"); define("SVXCONFIG", "svxlink.conf"); define("SVXLOGPATH", "/var/log/"); define("SVXLOGPREFIX","svxlink.log"); define("CALLSIGN",""); define("LOGICS",""); define("REPORT_CTCSS",""); define("DTMF_CTRL_PTY",""); define("API",""); define("FMNET",""); define("TG_URI",""); define("NODE_INFO_FILE",""); define("RF_MODULE",""); define("PHP_AUTH_USER", "svxlink"); define("PHP_AUTH_PW", "password");

Some of these options are not self explaining. Please add information to your readme what to put there. API? FMNET? Format of LOGICS when using more? TG_URI? RF_MODULE? Just for example.

Thanks in advance

[f5vmr]

Some of these are for future expansion. The fact they are defined here has no impact on the visual aspect. You will see that the origin from Sp2ong, he has used these in his svxlink projects on the Polish network, but they have no relevance here in my project.

I am disappointed for you that it hasn't worked.

Chris

On Tue, 26 Mar 2024 at 22:34, Attila Kocis @.***> wrote:

Hi

when follwing the instructions, the dashboard doesn't show anything. I found out that the file include/config.inc.php has to me modified also.

define("SVXCONFPATH", "/etc/svxlink/"); define("SVXCONFIG", "svxlink.conf"); define("SVXLOGPATH", "/var/log/"); define("SVXLOGPREFIX","svxlink.log"); define("CALLSIGN",""); define("LOGICS",""); define("REPORT_CTCSS",""); define("DTMF_CTRL_PTY",""); define("API",""); define("FMNET",""); define("TG_URI",""); define("NODE_INFO_FILE",""); define("RF_MODULE",""); define("PHP_AUTH_USER", "svxlink"); define("PHP_AUTH_PW", "password");

Some of these options are not self explaining. Please add information to your readme what to put there. API? FMNET? Format of LOGICS when using more? TG_URI? RF_MODULE? Just for example.

Thanks in advance

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5AHM5EXUZE3LUGVBJ3Y2HSVLAVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDSNBWGE2TOMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[dl1nux]

Hi, thanks for the fast reply. I have added for example the correct path to the logfile, the callsign, the DTMF_CTRL_PTY Path to /tmp/..., and the filename to the node_info File. After that I could at least see the user history of the node and also a live status when somebody is talking. But the complete left area is still empty. So these information have really impact on the Dashboard. But actually no logics info, no module info and no TG info.

[dl1nux]

As addition, I have this "issue" on two seperate installations of svxlink. One at a repeater and one on my simplex node.

[f5vmr]

I cannot explain why your dashboard fails. I have always used user 'pi', and my scripts to build a node. There could be a clash between apache2 and nginx that vie for supremacy, if you have both installed. The code for the dashboard looks for the location of the svxlink.conf in /etc/svxlink. What is strange is that although the header and talkgroups are missing from the display, you are probably able to edit the configuration files if you apply the permissions.

The solution to the one time it happened to me, is to remove completely the html folder. Reinstall from the GitHub, to see if it resets. My dashboards continue to work, and the test one I built yesterday worked first time.

I can imagine your frustration...... I would be too. Chris

On Tue, 26 Mar 2024 at 23:01, Attila Kocis @.***> wrote:

As addition, I have this "issue" on twio seperate installations of svxlink. One at a repeater and one on my simplex node.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2021609023, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5C7ZXJR6R65LWIVIOLY2HVZ7AVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGYYDSMBSGM . You are receiving this because you commented.Message ID: @.***>

[f5vmr]

One query on your svxlink.... Did your install correctly modify the /etc/default/svxlink file, where the log location should now be svxlink.log and not just svxlink? This is also relevant for the dashboard.

On Tue, 26 Mar 2024 at 23:01, Attila Kocis @.***> wrote:

As addition, I have this "issue" on twio seperate installations of svxlink. One at a repeater and one on my simplex node.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2021609023, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5C7ZXJR6R65LWIVIOLY2HVZ7AVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGYYDSMBSGM . You are receiving this because you commented.Message ID: @.***>

[dl1nux]

Hi. I tried here again at my local installation. As soon as I provice the correct link to svxlink logfile, the Heard list appears. But all other display functions are not working. No Header, no svxlink info on the left. I also installed as user pi and where needed with sudo right. I only use apache2, no other webserver. I've installed the dashboard here several times from scratch, but it's always the same. My logfile is only called "svxlink", not "svxlink.log", because this is standard after svxlink installation. Correct name and path are given in svxlink.conf, /etc/default/svxlink and config.inc.php What file permissions and owner/group settings do you have for the dashboard files? Maybe it's a case of wrong file permissions.

[f5vmr]

This is fine.

1. I always change svxlink to svxlink.log
2. I have just looked at my /var/www/html folder and owner and permissions were set to to root:root. I changed them to www-data:www-data and it makes no difference. Everything still works. It should be www-data:www-data anyway. Permissions are set to 0644

I am at a loss to understand what occurs in your installation. Naturally the webpage seeks out the svxlink.conf to read the callsign and logics connected. It seems in your case this is not occurring.

I shall investigate further. I will advise you of anything I find. This will be difficult to replicate.

Chris

On 28 Mar 2024, at 08:47, Attila Kocis @.***> wrote:

Hi. I tried here again at my local installation. As soon as I provice the correct link to svxlink logfile, the Heard list appears. But all other display functions are not working. No Header, no svxlink info on the left. I also installed as user pi and where needed with sudo right. I only use apache2, no other webserver. I've installed the dashboard here several times from scratch, but it's always the same. My logfile is only called "svxlink", not "svxlink.log", because this is standard after svxlink installation. Correct name and path are given in svxlink.conf, /etc/default/svxlink and config.inc.php What file permissions and owner/group settings do you have for the dashboard files? Maybe it's a case of wrong file permissions.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2024687843, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5FBH6LGP5NF6XNX5GTY2PDKFAVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGY4DOOBUGM. You are receiving this because you commented.

[f5vmr]

I have made some changes to the code, relative to the session_start. I also found a malformed link to the parse_svxconf.php file. Please go to the html folder and sudo git pull. In relation to the svxlink.log I am surprised that sm0svx did not adhere to the principle that log file might have .log as a suffix. The svxlinkbuilder I have just completed, incorporates the change, and builds the dashboard as well. I hope to have a German Language version, but have only French Spanish, and English so far.

[dl1nux]

I have made some changes to the code, relative to the session_start. I also found a malformed link to the parse_svxconf.php file. Please go to the html folder and sudo git pull. In relation to the svxlink.log I am surprised that sm0svx did not adhere to the principle that log file might have .log as a suffix. The svxlinkbuilder I have just completed, incorporates the change, and builds the dashboard as well. I hope to have a German Language version, but have only French Spanish, and English so far.

Tahnks for Info. I tried it now on my RF Guru Hotspot. It seems to work there. But my changes made to the configuration files are not being saved. I will have to check if it is possibly a permission error. I will try it also on the other installations where I had problems and report again.

[f5vmr]

Yes it is. I have had to make significant changes to the sudoers additions. Some of the commands are in /bin and some of them are in /sbin, and I have shown these changes in the README.md

After which your changes will be applied.

Chris

On Sat, 27 Apr 2024 at 08:46, Attila Kocis @.***> wrote:

I have made some changes to the code, relative to the session_start. I also found a malformed link to the parse_svxconf.php file. Please go to the html folder and sudo git pull. In relation to the svxlink.log I am surprised that sm0svx did not adhere to the principle that log file might have .log as a suffix. The svxlinkbuilder I have just completed, incorporates the change, and builds the dashboard as well. I hope to have a German Language version, but have only French Spanish, and English so far.

Tahnks for Info. I tried it now on my RF Guru Hotspot. It seems to work there. But my changes made to the configuration files are not being saved. I will have to check if it is possibly a permission error. I will try it also on the other installations where I had problems and report again.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2080404107, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5AYS4KV75KYNDM4CTDY7NJVTAVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQYDIMJQG4 . You are receiving this because you commented.Message ID: @.***>

[f5vmr]

If you make a new file called /etc/sudoers.d/svxlink and place these lines in it, and save, there will be no further problem.

svxlink ALL=NOPASSWD: /sbin/service

svxlink ALL=NOPASSWD: /bin/cp

svxlink ALL=NOPASSWD: /bin/chown

svxlink ALL=NOPASSWD: /bin/chmod

svxlink ALL=NOPASSWD: /bin/systemctl

svxlink ALL=NOPASSWD: /sbin/reboot

svxlink ALL=NOPASSWD: /sbin/shutdown

On Sat, 27 Apr 2024 at 08:46, Attila Kocis @.***> wrote:

I have made some changes to the code, relative to the session_start. I also found a malformed link to the parse_svxconf.php file. Please go to the html folder and sudo git pull. In relation to the svxlink.log I am surprised that sm0svx did not adhere to the principle that log file might have .log as a suffix. The svxlinkbuilder I have just completed, incorporates the change, and builds the dashboard as well. I hope to have a German Language version, but have only French Spanish, and English so far.

Tahnks for Info. I tried it now on my RF Guru Hotspot. It seems to work there. But my changes made to the configuration files are not being saved. I will have to check if it is possibly a permission error. I will try it also on the other installations where I had problems and report again.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2080404107, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5AYS4KV75KYNDM4CTDY7NJVTAVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQYDIMJQG4 . You are receiving this because you commented.Message ID: @.***>

[dl1nux]

I made this file with it's content and rebootet the device. But it still won't work. The thing is, that the dashboard creates the backup files, but does not edit the original svxlink.conf

-rw-r--r-- 1 root root 6856 Apr 7 09:12 svxlink.conf -rw-r--r-- 1 root root 6723 Feb 2 19:47 svxlink.conf.02-02-2024_0747pm -rw-r--r-- 1 root root 6723 Feb 2 19:49 svxlink.conf.02-02-2024_0749pm -rw-r--r-- 1 root root 6723 Feb 2 20:40 svxlink.conf.02-02-2024_0840pm -rw-r--r-- 1 root root 6723 Feb 2 21:10 svxlink.conf.02-02-2024_0910pm -rw-r--r-- 1 root root 6818 Feb 2 22:37 svxlink.conf.02-02-2024_1037pm -rw-r--r-- 1 root root 6829 Mar 25 19:48 svxlink.conf.25-03-2024_0748pm -rw-r--r-- 1 root root 6829 Mar 26 18:55 svxlink.conf.26-03-2024_0655pm -rw-r--r-- 1 root root 6829 Mar 26 22:17 svxlink.conf.26-03-2024_1017pm -rw-r--r-- 1 root root 6857 Mar 26 22:30 svxlink.conf.26-03-2024_1030pm -rw-r--r-- 1 root root 6857 Mar 26 22:37 svxlink.conf.26-03-2024_1037pm -rw-r--r-- 1 root root 6857 Mar 26 22:50 svxlink.conf.26-03-2024_1050pm -rw-r--r-- 1 root root 6856 Apr 27 10:12 svxlink.conf.27-04-2024_1012am -rw-r--r-- 1 root root 6856 Apr 27 10:16 svxlink.conf.27-04-2024_1016am -rw-r--r-- 1 root root 6856 Apr 27 10:18 svxlink.conf.27-04-2024_1018am

And the tests on the other installations, where svxlink.conf could not be read and no information was shown on the left side of the dashboard, was also negative. There seem to be still permission issues. I have two of that installations, both were installed according to sm0svx installation instructions. I will have to investigate more this issue when I have more time.

[f5vmr]

This is very strange. Every build I have made since has worked every time since I made the repair.

Chris

On Sat, 27 Apr 2024, 09:27 Attila Kocis, @.***> wrote:

I made this file with it's content and rebootet the device. But it still won't work. The thing is, that the dashboard creates the backup files, but does not edit the original svxlink.conf

-rw-r--r-- 1 root root 6856 Apr 7 09:12 svxlink.conf -rw-r--r-- 1 root root 6723 Feb 2 19:47 svxlink.conf.02-02-2024_0747pm -rw-r--r-- 1 root root 6723 Feb 2 19:49 svxlink.conf.02-02-2024_0749pm -rw-r--r-- 1 root root 6723 Feb 2 20:40 svxlink.conf.02-02-2024_0840pm -rw-r--r-- 1 root root 6723 Feb 2 21:10 svxlink.conf.02-02-2024_0910pm -rw-r--r-- 1 root root 6818 Feb 2 22:37 svxlink.conf.02-02-2024_1037pm -rw-r--r-- 1 root root 6829 Mar 25 19:48 svxlink.conf.25-03-2024_0748pm -rw-r--r-- 1 root root 6829 Mar 26 18:55 svxlink.conf.26-03-2024_0655pm -rw-r--r-- 1 root root 6829 Mar 26 22:17 svxlink.conf.26-03-2024_1017pm -rw-r--r-- 1 root root 6857 Mar 26 22:30 svxlink.conf.26-03-2024_1030pm -rw-r--r-- 1 root root 6857 Mar 26 22:37 svxlink.conf.26-03-2024_1037pm -rw-r--r-- 1 root root 6857 Mar 26 22:50 svxlink.conf.26-03-2024_1050pm -rw-r--r-- 1 root root 6856 Apr 27 10:12 svxlink.conf.27-04-2024_1012am -rw-r--r-- 1 root root 6856 Apr 27 10:16 svxlink.conf.27-04-2024_1016am -rw-r--r-- 1 root root 6856 Apr 27 10:18 svxlink.conf.27-04-2024_1018am

And the tests on the other installations, where svxlink.conf could not be read and no information was shown on the left side of the dashboard, was also negative. There seem to be still permission issues. I have two of that installations, both were installed according to sm0svx installation instructions. I will have to investigate more this issue when I have more time.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2080415496, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5BTTNLDBJ3B2M223ALY7NOQ3AVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQYTKNBZGY . You are receiving this because you commented.Message ID: @.***>

[dl1nux]

OK, one mystery is solved. It's important go give the configuration files the correct permissions! The standard permissions of the files in /etc/svxlink/ are 644, and only the owner (normally root) can write to these files. Thats why the dashboard can not write the new configuration after change. You have to give all configuration files at least 666 permissions so that group an other can also write this file.

sudo chmod 666 /etc/svxlink/svxlink.conf sudo chmod 666 /etc/svxlink/gpio.conf sudo chmod 666 /etc/svxlink/svxlink.d/ModuleEchoLink.conf sudo chmod 666 /etc/svxlink/svxlink.d/ModuleMetarInfo.conf sudo chmod 666 /etc/svxlink/node_info.json

Or possibly you can chown the files to the other owner (svxlink?). But I did not try that. I think you should add this to your README so that everyone will prove the permissions to the files.

[f5vmr]

Normally no issue, but I'll check. I thought the .conf files get 777. 73 Chris

On Sat, 27 Apr 2024, 09:56 Attila Kocis, @.***> wrote:

OK, one mystery is solved. It's improtant go give the configuration files the correct permissions! The standard permissions of the files in /etc/svxlink/ are 644, and only the owner (normally root) can write to these files. Thats why the dashboard can not write the new configuration after change. You have to give all configuration files at least 666 permissions so that group an other can also write this file.

sudo chmod 666 /etc/svxlink/svxlink.conf sudo chmod 666 /etc/svxlink/gpio.conf sudo chmod 666 /etc/svxlink/svxlink.d/ModuleEchoLink.conf sudo chmod 666 /etc/svxlink/svxlink.d/ModuleMetarInfo.conf sudo chmod 666 /etc/svxlink/node_info.json

Or possibly you can chown the files to the other owner (svxlink?). But I did not try that. I think you should add this to your README so that everyone will prove the permissions to the files.

— Reply to this email directly, view it on GitHub https://github.com/f5vmr/SVXLink-Dash-V2/issues/3#issuecomment-2080421799, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5CIZS5BKVLAPHSQPBTY7NR5TAVCNFSM6AAAAABFJZRIRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQZDCNZZHE . You are receiving this because you commented.Message ID: @.***>

[dl1nux]

I think it's better to change the ownership of the file to avoid security issues. Instead of chmod the files a chown to the svxlink user should be done:

sudo chown svxlink:svxlink /etc/svxlink/svxlink.conf sudo chown svxlink:svxlink /etc/svxlink/gpio.conf sudo chown svxlink:svxlink /etc/svxlink/svxlink.d/ModuleEchoLink.conf sudo chown svxlink:svxlink /etc/svxlink/svxlink.d/ModuleMetarInfo.conf sudo chown svxlink:svxlink /etc/svxlink/node_info.json

Then the permissions with 644 will also work and are more secure. I've tested it now and it works. If the webserver runs under an other user (www-data for example), then the ownership should be changed to the other user.

[dl1nux]

And just as addition, every time the pages for editing the config files are visited, it makes automatically a backup of the file, if you change something or not. This "floods" the filesystem if you visit the sites often, maybe to only view the actual configuration. It would be better that the backup will only be made when the save button has been hit. Then there would not bee that many files allocated to the filesystem.