Topic: sail beta 3.2

[SARK devs]

I wanted to know what the perms and ownership were on /var/log/sark.   Should be www:www & 755.   

check them and then attempt to fetch up apache with

Code: [Select]

sv u httpd-srk
you can check with ps x or sv s httpd-srk

Kind Regards

S

[Jáder]

/var/log/sark already was ok:
[root@guepardo ~]# sv s httpd-srk
down: httpd-srk: 1s, want up
[root@guepardo ~]# ls -lad /var/log/sark
drwxr-xr-x 2 apache apache 4096 May  3 22:03 /var/log/sark

but it do not start

Code: [Select]

[root@guepardo ~]# chown -R www:www /var/log/sark
[root@guepardo ~]# ls -lad /var/log/sark
drwxr-xr-x 2 apache apache 4096 May  3 22:03 /var/log/sark
[root@guepardo ~]# sv u httpd-srk
[root@guepardo ~]# sv s httpd-srk
down: httpd-srk: 1s, want up
[root@guepardo ~]#

[root@guepardo ~]# chmod -R 755 /var/log/sark
[root@guepardo ~]# sv u httpd-srk
[root@guepardo ~]# sv s httpd-srk
down: httpd-srk: 0s, want up
[root@guepardo ~]#


[SARK devs]

[root@guepardo ~]# ls -lad /var/log/sark
drwxr-xr-x 2 apache apache 4096 May  3 22:03 /var/log/sark

Why does the sark log directory have ownership apache:apache?   

What do you see in the error-log? (/var/log/sark/error_log)

Kind Regards

S

[Jáder]

Why does the sark log directory have ownership apache:apache?   

Not sure... as you can see by above commands, I chmod www:www ... so I presume www is an alias to apache!

What do you see in the error-log? (/var/log/sark/error_log)

I have no files in /var/log/sark directory !

[SARK devs]

There is some permission issue here which I'm not seeing on my test rig.  I don't understand the apache:apache ownership of the directory.  Mine is www:www and that allows apache to create the two log files access_log and error_log (both should be www:www and 644).

I have just done a bare metal vanilla sme install followed by a sail install and it works as advertised so I'm confused as to why yours doesn't. 

I guess you can either start over or, if you have a spare machine or VM load the latest iso which also checks out OK on our test systems here.  You can find the iso at http://sailpbx.com/iso/SME8b7/3.2-beta/

Kind Regards

S

[Jáder]

Humm... indeed it's strange:

Code: [Select]

[root@guepardo ~]# grep www /etc/passwd
apache:x:102:102:Apache:/var/www:/sbin/nologin
www:x:102:102:e-smith web server:/home/e-smith:/bin/false
[root@guepardo ~]# 
I've create both log files using touch and verify the 644 permission.
So I restarted httpd-srk ..nothing changed!

[compsos]

Hi Jeff
I am getting the same results as Jader. No httpd-srk process.
Running
smesailenv-3.2.0-16
sail-3.2.0-11
Kernel 2.6.18-308.4.1.el5PAE
httpd-2.2.3-63.el5.centos.1
asterisk18-1.8.7.0-2_centos5

Now starting httpd-srk

/etc/init.d/httpd-srk start
Starting httpd-srk:                                        [  OK  ]

But no ps httpd-srk lists and no log entries. Where on the earlier version we had 1 ps .

Is there a special reason for not using the system's apache. At least we can get it to work?

[SARK devs]

Yes it's important to use the new apache instance because it achieves a clean separation from the sme mechanics and it uses mod-perl so it runs a lot faster. 

However, I am seeing different results to you.  Is it possible for you to give me a login to the system so I may look at it?  Email me at admin@aelintra.com and mark it for jeff

Cheers

S

[SARK devs]

OK, this seems to be fixed now.  I've also fixed a bug in the password change panel.

I've uploaded the latest releases to the server; they are

sail-3.2.0-14
smesailenv-3.2.0-17.

These will fix the issue of the sail http server not starting correctly.  If you already have installed an earlier version of 3.2 then run the following command before installing these two new rpms.

Code: [Select]

rm -rf /opt/sark/httpd/sslcerts

Kind Regards

S

[compsos]

Looks good Jeff.
We have not seen any more hiccups since 16 with the certs corrected. But these files went straight in and worked. I think you can take the beta tag off. Thank you.

[Jáder]

I got errors about /sail not available...so I went to logs ( /var/log/sark/ )
and found:

Code: [Select]

[root@guepardo www]# tail /var/log/sark/error_log
[Wed May 16 16:50:35 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/favicon.ico
[Wed May 16 16:50:39 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:50:40 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:50:40 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:50:41 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:50:41 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:51:26 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:51:27 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/favicon.ico
[Wed May 16 16:51:48 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/sail
[Wed May 16 16:51:49 2012] [error] [client 192.168.13.164] File does not exist: /opt/sark/www/favicon.ico

Great news... with nothing to loose I removed /sail from URL and voilá... got first SARK screen!
Not sure why... but I finally get a SARK screen... will try it in some minutes.

[SARK devs]

To access the sail 3.2 manager you don't specify /sail.  It is enough to do

Code: [Select]

https://your.site.com:8443
Kind Regards

S

[SARK devs]

@compsos

cheers Gordon. 

Best

Jeff