Sail7 on Debian 9

[compsos]

Hi
Sail 7 installs on Stretch no problems, can import ver 5 data and apply srkV4reloader.sh. Navigation is good and data correct
Eventually found how to get into templates as the template menu item lists them, but no access.
From the home screen can enter 'yealink.common' and there is the file. But no way of saving the changes. No save or commit buttons etc.
Is it a module that did not install causing a lack of control?
The repo only lists sailhpe_6.0.0-2_amd64.deb but the install pulled HPE Release: 7.0.0-7.  Is that a problem? the apt was set to the 7.0 repo.

Code Select Expand

System
PBX release: 13.14.1
SAIL Release: 6.0.1-38+deb9u1
HPE Release: 7.0.0-7
Endpoints defined: 10
Serial Num: 376535
Network
MAC: 08:00:27:10:7D:F1
hostname: pbx2
Public IP: xxx.xxx.xxx.xxx
Local IP: 192.168.xxx.xxx
Resource
Disk Usage: 0%
RAM Size: 2052524
RAM Free: 1545032
PBX: RUNNING
Master Timer: AUTO
Timer State: CLOSED

[compsos]

Just tried 6 on Stretch and got the same outcome except I had a cancel button but no save.
The cancel button does work.

I do feel like I am missing something?

[sysadmin]

These are SAIL admin permissions issues you are hitting.  This can be caused by one of two things.   The first is the permissiond ownership of the sqlite db.   We often see users bringing and old version forward while logged in as root resulting in the db being owned by root.

the file /opt/sark/db/sark.db should look like this

Code Select Expand


ls -l /opt/sark/db/sark.db
-rw-rw-r-- 1 www-data www-data 540672 Mar 26 07:31 /opt/sark/db/sark.db


Another issue might be that the internal sqlite table UserPanel has the wrong permissions set.   It should look like this

Code Select Expand


sqlite3 /opt/sark/db/sark.db 'select * from userpanel'
admin|100|create
admin|110|create
admin|115|create
admin|120|create
admin|130|create
admin|134|create
admin|140|create
admin|150|create
admin|160|create
admin|170|create
admin|180|create
admin|190|create
admin|200|create
admin|210|create
admin|215|create
admin|220|create
admin|224|create
admin|230|create
admin|232|create
admin|235|create
admin|236|create
admin|240|create
admin|250|create
admin|252|create
admin|255|create
admin|260|create
admin|265|create
admin|270|create
admin|280|create
admin|290|create
admin|310|create
admin|320|create
admin|330|create
admin|331|create
admin|333|create
admin|335|create
admin|340|create
admin|350|create
admin|370|create
admin|390|create
admin|400|create



Usually one of these two. 

[compsos]

Thanks for the tips.
Ver 5 No problems
DB permissions OK but the userpanel table lacks the perms column entirely.
So a drop table and import one exported from the clean db solved that issue.

Code Select Expand

sqlite3 /opt/sark/db/sark.db
drop Table UserPanel;
.headers on
.mode csv UserPanel
.import userpanel.csv UserPanel
SELECT * FROM UserPanel;
.quit


On running the srkV4reloader.sh it complained of mbstring.so was not available.

Code Select Expand

apt-get install php7.0-mbstring
So it looks like the table schema was updated but old data is not adjusted for 3 columns. Unless there is another way to import the previous database.

Ver 6

Code Select Expand

System
PBX release: 13.14.1
SAIL Release: 6.0.1-52+deb9u1
HPE Release: 6.0.0-2
Endpoints defined: 10
Serial Num: 376535
Network
MAC: 08:00:27:10:7D:F1
hostname: pbx2
Public IP: xxx.xxx.xxx.xxx
Local IP: test PBX
Resource
Disk Usage: 6%
RAM Size: 2052524
RAM Free: 1249876
PBX: RUNNING
Master Timer: AUTO
Timer State: CLOSED
So we have the same issue that templates are overridden and then can not be edited. See the attached png file. The data has been modified but only a cancel button. Could there be other errors in the DB like the UserPanel table?

[sysadmin]

I can't take this further without looking at the system.  If it's urgent then call Paul at Brindley and we'll take a look.  As you can imagine we're pretty busy at the moment but we'll get to it as quickly as we can.



 

[compsos]

Thank you S
Yes understand. If like here everyone wants to "work from home" even if the infrastructure may not be big enough.
I will see if I can find any failed calls in the logs and also try a new VM.