Log Viewer issue

Status
Not open for further replies.

Serge

New Member
Oct 13, 2017
25
1
3
33
Hey guys,
Happy New Year.
I have a problem with my FusionPBX. I can't see any logs through Log Viewer page. It's just empty, but the freeswitch.log file exists and system is writing to it.
Did anybody had this issue?
 

Attachments

  • Fusion_Log_Viewer.JPG
    Fusion_Log_Viewer.JPG
    59.8 KB · Views: 47

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,497
413
83
Has this just happened or is this a new install of Fusion? Also have you modified the theme? I ask because your screenshot colours and fonts look very "browser default".

OS and Fusion version numbers may also help us to help you.
 

Serge

New Member
Oct 13, 2017
25
1
3
33
Has this just happened or is this a new install of Fusion? Also have you modified the theme? I ask because your screenshot colours and fonts look very "browser default".

OS and Fusion version numbers may also help us to help you.
This was installed about two years ago and was working fine. I did change the colours right after installation, this didn't affect the log viewer. It just stopped showing the logs at some point far after the initial installation.
OS - Debian 8
Fusion version 4.2.5
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,497
413
83
Ok thankyou for the information.
Given that the log file exists in the correct location and is being written to, the most likely cause is the permissions on the log file. Normally it is read/write for www-data but this also depends on the user that Freeswitch is running under.
Code:
root@a2es-test1:/var/log/freeswitch# ls -l
total 15104
drwxr-x--- 2 www-data www-data     4096 Jul 22 15:27 conference_cdr
-rw-rw---- 1 www-data www-data 15146226 Jan  1 18:05 freeswitch.log
-rw-rw---- 1 www-data www-data   305449 Nov 12 17:15 freeswitch.xml.fsxml
drwxr-x--- 2 www-data www-data     4096 Sep 12  2017 xml_cdr

If the permissions are not what you expect them to be, check if you have any log rotate process that may be changing the permissions.
 
Last edited:

Serge

New Member
Oct 13, 2017
25
1
3
33
Ok thankyou for the information.
Given that the log file exists in the correct location and is being written to, the most likely cause is the permissions on the log file. Normally it is read/write for www-data but this also depends on the user that Freeswitch is running under.
Code:
root@a2es-test1:/var/log/freeswitch# ls -l
total 15104
drwxr-x--- 2 www-data www-data     4096 Jul 22 15:27 conference_cdr
-rw-rw---- 1 www-data www-data 15146226 Jan  1 18:05 freeswitch.log
-rw-rw---- 1 www-data www-data   305449 Nov 12 17:15 freeswitch.xml.fsxml
drwxr-x--- 2 www-data www-data     4096 Sep 12  2017 xml_cdr

If the permissions are not what you expect them to be, check if you have any log rotate process that may be changing the permissions.
That's what I have.
Sorry for bad quality
 

Attachments

  • Screenshot from 2020-01-03 12-59-34.png
    Screenshot from 2020-01-03 12-59-34.png
    8.9 KB · Views: 29

Serge

New Member
Oct 13, 2017
25
1
3
33
Solved... Partially.
Apparently I can access the logs with Google Chrome. Looks like there is an issue with Firefox...
 

Serge

New Member
Oct 13, 2017
25
1
3
33
Hmmm... Now I can access it with Firefox also...
All I did is cleared the nginx access log....
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,497
413
83
Interesting... Did clearing the nginx access log involve restarting nginx / php-fpm?

Trouble is, once a fault has gone away, it is always difficult to work out what the issue was. There could be lots of possible causes, maybe you had hit an open file descriptor limit in php-fpm, anything in the php-fpm logs?
 

Serge

New Member
Oct 13, 2017
25
1
3
33
Interesting... Did clearing the nginx access log involve restarting nginx / php-fpm?

Trouble is, once a fault has gone away, it is always difficult to work out what the issue was. There could be lots of possible causes, maybe you had hit an open file descriptor limit in php-fpm, anything in the php-fpm logs?
Nope. No services were restarted.
Will check php-fpm logs later.
 
Last edited:
Status
Not open for further replies.